Title pretty much sums up my first question.
Trying to set up a 2x1 (or is it 1x2) square mosaic with a resolution of 3840x3840 of of a single A5000. Each display is set to a custom resolution of 3840x1920 @ 30Hz. Since it’s a custom resolution and refresh rate, do I absolutely need a Sync II card to achieve framelock? I heard somewhere that you absolutely need to for a setup with custom resolutions, but I can’t find the documentation on that.
Hi, did you solve the issue? I have the same question. Thank you.
Hi Luca,
I spoke with an engineer on this board who said that you don’t need the Sync II card to get framelock with a custom resolution if you’re only using one GPU. Some others I spoke with through other means said that I did need the card.
For my setup, I ended up needing it, but also because there was hardware down the chain that needed the Sync II card for us to be absolutely sure of framelock.
The easiest answer for you is to try it first without the Sync II card, since it’s gonna be over $1000 for that card. My other suggestion is to keep the resolution on all outputs on that card the same with the same FPS. I had one port on the GPU on a different resolution and that definitely caused an issue with my mosaic.
Mosaic (as well as sync) needs exactly the same screens/refreshrate/resolution to be stable! Mosaic on a single GPU does NOT need a sync card, only from 5 outputs up, so more than a single GPU, Mosaic with sync needs the sync card. If you doing like digital signage with slow moving content and like bezels, then you can live with Mosaic without sync as well, so wouldn’t need a sync card, but still be able to set up a mosaic with more than 4 screens, across more than one GPU …
Custom resolution is tricky, and needs to make sure, the sink device/screen/projector is actually able to properly display the timing that is OFF from what it advertises as being capable of (through its EDID), but custom resolution has nothing to do with the (need for) a sync card!
Beyond the sync of scanning out the pixels, there is a 2nd, a SW layer of syncing the frames, the content on multiple screens. (with Mosaic this ‘does not apply’ because you basically run a single window/thread across a single (Mosaic)desktop and display, but) when syncing multiple rendering threads (on multiple individual desktops on the same machine, or even on multiple machines across a cluster), you will need an app that uses our swapAPI, to get HW support for the faster=less busy thread to wait for the slowest=busiest one, so you also get to sync all outputs on the same frame=content, not just the same scanout of pixels… This prevents from any member of the syncgroup to display content this is a frame off from the content on any of the other threads…
I hope this clarifies any mixed messages?
thanks
-Frank