I made a simple testing system with Ableton and Isadora. Ableton outputs MTC (via the LiveMTC add-on) directly to Isadora, which is running a simple set with MTC Movie Locker, Movie Player and a Projector. I've also tested a second version with Ableton outputting LTC, which is then converted to MTC with Lockstep (I'm on a Mac) before Isadora receives it. Ableton also has the same video on a track, so I can compare them both and see how locked they are.

The thing is: I've noticed that there's always some delay between the moment I press play in Ableton and the moment Isadora starts following the timecode. And the worst part: this delay is always a bit different. Sometimes up to three whole frames, sometimes less than one. So there's no way for me to just add an offset. I've checked the FPS and everything matches. What could be causing this? Is that something I have to deal with or are there ways to troubleshoot/fix this? Thanks in advance.

@milt0n i ran it via proton on steamdeck. Wouldn’t have considered it stable or that usable but it worked. Tried launching it since and it doesn’t seem to work now. I wanted to see how capable steamdeck was for projects out of curiosity

@woland YUM! thanks for sharing the future!

@dusx Thanks, that really helped. It was in fact the opposite effect (to create a kind of negative fisheye process), but I tweaked the code you sent to do this.

@tlaloc

Performing some thread necromancy because I'm so excited that the next public release will (finally) include a way to do this (among many other things) 

@ray

Dual graphics cards is unsupported (meaning we are unable to provide tech support) since we have no way to create the same/similar setup.

With that said you can use more than one card. 
What is important is that you don't share/mix video from one output path to another.

So if you:

1.  add a movie player, and connect its output to stage 1 (using gpu1)
2. add a movie player, and connect its output to stage 2 (using gpu2)

Don't try to mix the two videos together in any way.. keep them separate. Mixing will require moving the texture from one gpu to the other, and will be a spped/bottleneck.

No Isadora allows you to move video in anyway you like, so its very flexible. If you can keep the video flow simple, and maintain individual paths, you can make it work very well.

TEST, TEST, TEST!

Start simple, and build up.. test constantly

@opmeyer1

I am recording this as an issue we need to investigate. Thank-you for the report.

Thanks for all of your suggestions. The datapath looks great but is beyond my budget. Please excuse my lack of knowledge but what type of output ports does the Blackmagic Decklink have and can I use an adapter to change them to HDMI? As far as multiple graphic cards on windows goes, I just slapped them in and they  worked. Dumb luck?

@opmeyer1

Hi! 

Thanks for making such a detailed bug report. Tagging our team here to log the bug report / get that into our system.

@woland @dusx

Hi Isadora team — short bug report and recommended fix for matching input signal pixel formats to capture setting pixel formats UltraStudio 4K Mini HDMI RGB/YUV feeds.

Problem (symptoms): When Isadora opens the Blackmagic driver the device is forced into YUV 4:2:2 input mode, producing a black preview even though the incoming HDMI signal is present at 1080p60 RGB 10‑bit. Launching Blackmagic Media Express immediately reconfigures the device to RGB10 and the image returns.

Possible root cause: Isadora is calling the Desktop Video API without negotiating or selecting the correct pixel format/display mode (or is explicitly requesting a YUV pixel format). The Blackmagic driver will accept an explicit RGB10 request or perform auto‑negotiation if asked; currently Isadora’s call path forces YUV.

Recommended fix 

1. Negotiate display mode + pixel format on open — call the Desktop Video API to enumerate supported display modes (GetDisplayModeIterator / display mode list) and choose the exact 1080p60 mode reported by the device.
2. Request RGB10 explicitly when available — call EnableVideoInput (or equivalent) with the matching display mode and bmdFormat10BitRGB (or the SDK constant for 10‑bit RGB).
3. Expose a UI override — add a simple capture setting: Pixel Format: Auto / Force RGB10/ Force RGB8/ Force YUV422 for troubleshooting and edge cases.