I needed the DataPath because I was trying to use two TripleHead2Go's and they simply wouldn't work together. My final configuration for 8 displays with my MacBook Pro M1 Max was:
DataPath FX4 -> Four Displays
TripleHead2Go -> Three Displays
HDMI Output on Compute -> One Display
I didn't get the DataPath to solve the long cable issue, because in fact, it too does not work with the Blackmagic converters! Next time, I'll go with CAT5 or optical or something else. (The Blackmagic converters were provided by the rental company; they weren't my choice.)
Best Wishes,
Mark
ah @woland, thanks for your reply, my mistake... i didn't realise Rosetta is only required for the install. Have enabled Rosetta 2, installed Isadora 3.2.6 and yes indeed it's showing as "universal".
Will report back performance findings shortly.
Rgds, Mr J
Glad to see it working, but I don't know how much you paid for the Datapath rental.... Ibirdie 100ft cables cost on Amazon is just 78 euros each. And 200 ft cable costs 128 euros.... Anyways. if it works with Datapath. You're got to go.
Glad to see the smile on your face after all that stress of kit not working!
It took renting a DataPath FX4 to get things where they should be, but here are some photos of something actually working. ;-)


Although, if all you're trying to do is play a movie more slowly or more quickly, you can adjust the speed input of the Movie Player actor.
@jfg said:
I think a possible workaround is to put the OSC actors in a User actor with the User Actor on/off.
Totally possible. I thought of doing it this way or with a background Scene but ended up going with the background Scene method because it lets me globally control the on/off state of OSC input and output while still letting me put the OSC Listener and OSC Transmit actors wherever they would normally go within the patch.
I've already got an extensive set of feature requests logged on this topic but I'll add your text to those entries.
Generally, it is best practice to prepare all your media to have the same framerate ahead of time, or to have framerates that can be divided by each other (e.g. pairing 15fps, 30fps, and 60fps content and pairing 25fps and 50fps content works fine with the highest framerate set as the target framerate, but you'd have issues with trying to pair 15fps content and 25fps content or 50fps and 60fps because one is not divisible by the other evenly).
Whatever display you are outputting to has a fixed refresh rate that cannot be changed on the fly without going into the system preferences of your computer, and the same concept applies there: If your display has a refresh rate of 60hz you'll do fine with 15, 30, and 60fps content and if your display has a refresh rate of 50hz you'll do fine with 25fps and 50fps content. So since you want your content's fps to all match or be divisible by each other, and you want those framerates to play nicely with your display's refresh rate, I don't think it would be best practice to change the target FPS on the fly even if you could.
