HEZOOMS DisplayPort to DisplayPort HDMI-Compatible Splitter Adapter MST SST Mode 8K@30Hz 4K@120Hz 1 in 2 Out Directional DP1.4 Splitter Dual Monitor for DP and HD Multi Screen simultaneous displays

<b>【INTRODUCTION】</b>This super slim DP to DP+HDMI-Compatible splitter is compact and efficient.It allows you to assign a high-definition source to one monitor and one TV at the same time without any signal los. The system is compatible with DP 1 . 4 ,1 . 3 ,1 . 2 ,1 . 0 and HDMI-Compatible 2 . 1 ,2 . 0, 1 . 4 , 1 . 3. Support 3D and 4K , 8K ultra HD. Support SST and MST. This splitter is ideal for home, office, hotel and any other installation that requires 2 ultra-high source display devices. <b>【MST Mode】</b> 1. In MST extended mode, HDMI-compatible single port output can reach 8K@30Hz, 4K@120Hz. Displayport single port output can reach 8K@30Hz, 4K@144Hz. Displayport and HDMI-compatible 2 ports can only reach 4K@60hz when output at the same time. 2. When the signal source input adopts Thunderbolt 3 USB C interface, DP and HDMI-Compatible output can only reach 4K. 3. MST mode of Apple system can only extend one screen (limited by iOS System). <b>【FEATURES】</b> 1. Compatible with all DP inputs and HDMI-Compatible、DP outputs. 2. Comply with DisplayPort 1.4, 1.3, 1.2 and 1.0 specifications. 3. Support Compatible resolution: 8K@30Hz. 4K@144Hz、120Hz、60Hz .1440P@165Hz 、144Hz、120Hz、60Hz. 1080P@240Hz 、165Hz、144Hz、120Hz、60Hz. (HDMI does not support 165hz, 144hz output) 4. Support operating system: IOS system, windows system,Android system 5. Support HDR,Support SST (mirror) and MST (Extended) mode, Support 4:4:4, 4:2:2, 4:2:0.

ASIN

B09J56DSX4

Embedding

CLIP ViT-L/14 · 768d

Distance metric

cosine

Doc fetch

1ms·cache hitGET /v2/namespaces/amazon-products/documents/B09J56DSX4

Similar query

26msre-embed title → /query

Doc fetch goes through Layer's Aerospike pull-through cache; cache hit served the row without touching turbopuffer. The similar query re-embeds this product's title with CLIP-text and runs a vector query — queries don't go through the doc cache, so no cache header is set.