Isadora 2.0 Video Capture - Expertise and Opinions Needed

@keftaparty,
I did try the Usb3 Intensity Shuttle; I was really hoping it would work, but it didn't. To be fair, this was about a year ago and I've no idea if the situation has changed.

The MXO2 Mini basically worked out of the box, although I had to spend some time on the phone with Matrox support (they're excellent!) to get full HD working properly - I had downloaded the version of the drivers that appeared to be the right ones, but were not.

I used a BM usb3 Intensity Shuttle in a show with Isadora back in March.
Setup was tricky because the Shuttle is very specific about settings, and at first it was unclear the 'real' format I was receiving to the Shuttle (60i vs 30p)
In the end it worked great, and I was able to change capture resolution very last minute to gain a little system performance.

I don't know what the API offers, but what I found was that the BlackMagic software didn't give any information about incoming signals unless the settings were exact.
If the hardware is aware of an input (not sure it is unless settings match), it would be great if it would tell us something about it so that we might be able to check the settings.

Across the whole line of blackmagic capture boxes they do not auto select resolutions. For any advanced user (or at least one that knows what they want to capture) this is no problem, if you know what you are plugging into it then set the input to match. I dont understand why people find this difficult or a fault, @Dusx when you say "Setup was tricky because the Shuttle is very specific about settings" - meaning you have to tell it what you are capturing- I am not sure what you mean? Shouldn't you know what signals you have?

The using the API gives a performance boost- for me less than 1/4 of the cpu use capturing the same format from qtkit vs the API. It also gives the settings that qtkit took away, although @Mark this has to be programmed, but would suit an actor in its structure.

@[CitizenJoe](http://troikatronix.com/troikatronixforum/profile/105/CitizenJoe)mac or PC? the USB3 devices from BM require a full bandwidth USB3 bus, many manufacturers cut corners here and their chipsets dont stand up, less of a problem now that the integrated USB3 chipsets are better- OSX drivers for USB were and are in Beta, but now the beta is a very useable version.

Anyway as the price is so low, they are everywhere, it is worth supporting the API directly as there is such an improvement increase.

In my case I was interfacing a Motion capture software from another machine, that I had never worked with before. The motion capture technician had difficulty telling me what format I should expect, so I spent some additional time on her machine and my own figuring out how to get a supported feed from that system. In this case it was a software issue, mostly since it was unclear what the motion capture software was rendering out to, but an autoscan feature that could have told us where we were with things would have been nice.
Not necessary, but nice.

hi all i'm working with blacksyphon and BM thunderbold shuttle and it´s pretty cool... but every solution which would decrease latency will be perfect for me... I'm not enough aware of api's and Qt versus AVF stuff, but for a user which plays with live cams ( 16 for me) a lower latency still the best solution...

Hi, for me capture is all about minimum latency. I have both the Thunderbolt Ultrastudio Pro and Mini Recorder and tested on 2013 MacPro (8 core / D700). Using Millumin, which utilises the BM API, I get 3 frame delay with the Ultrastudio Pro at 1080 / 60p = 50ms. Mini Recorder has 4 frame delay, but at maximum of 30p only = 133ms. I tested the Ultrastudio Pro with Izzy 2.0 and got 4 - 4.5 frame delay. I hope to test the Ultrastudio Pro with a genlocked source when I can get my hands on a 1080 / 60p sync generator.

I too use the BM ultra studio-TB, but have a 2012 MBPro with only one TB port. So if I want to use the Matrox 3Head2go I'll need to also get a USB3 Intensity Shuttle. Aaargh. But it sounds do-able for corporate shows, which I do a lot of. 133ms is not a small delay but is definitely liveable. re; the OP, BM support would be a good thing, I'm seeing there gear more and more with AV/Rental house company gear.

I am just wanted to report that, after two weeks of non-stop work, I have integrated support for direct capture from Blackmagic hardware into the Live Capture Settings window. I am seeding this build to some of the top users who I know make use of Blackmagic devices.

But, If you are are _actively_ using Blackmagic hardware and are willing to give this build a go, I am willing to let you try it. Not everyone on the team has Blackmagic hardware, and so we do need some extra help ensuring this version works well for everyone.

Please only write me if you are willing to work with something that is potentially _very_ buggy!!!! It is very lightly tested, and I cannot make any guarantees at this point. You must indicate in your mail that you fully understand that this is in alpha test at this point, OK?

Great, thanks Mark. Coming late to this party but very excited about BM integration... will request a test version, and will have an exorcist on standby in case the new code has unwanted metaphysical consequences.