Alex Maranda
Forum Replies Created
-
I suppose. It does make the in/out audio path useful only in conjunction with the video – by design.
I hooked up an USB keyboard once and couldn’t use it over Blackmagic Audio because of the lag. Also audio capture (also delayed) is active only if there is video coming in.
-
Same behavior here. Someone from BM should state whether this is inherent with the hardware or it’s an issue with their (ASIO!) driver, which – in good style – they will never fix.
-
5.5 doesn’t support third party I/O at all, so the Decklink would not work there anyway. If all you want is playback (without external monitoring) simply remove the Decklink card from the system and AVID will behave.
There is absolutely no point in reinstalling Windows. Reinstalling AVID *may* help.
Check that you have the following versions:
Quicktime 7.7.1 (latest)
Desktop Video 9.0 (Decklink drivers – only 9.0 works, and NOT 9.1)
MC/Symphony 6.0.1Sounds like you spoke with a level 1 support guy. XDCAM argument is bogus, at least for playback.
-
man I keep telling you it’s not BM it’s AVID (or at least BOTH), and it affects the entire range of Intensity/Decklink products.
-
You need to get to the point where you record FROM the Decklink (Blackmagic) interface, even if you don’t have any video source connected. Do that for 1-2 sec (flashing red button) and then you’re all good. Keep the Capture Tool handy. In 6.0.0 I would keep it minimized and go through the workaround everytime when switching to/from Source/Record — Color Correction.
6.0.1 is…improved (but you need to use 9.0 drivers!), I would generally only do this once. Either Symphony or MC – makes no difference – it’s the same codebase on third party I/O.
BTW it’s not only the top-end card (Extreme 3D+), I also have the Intensity/Intensity Pro and it’s the same story. I expect the entire Blackmagic range to have this issue, which is in fact AVID’s (new code for 3rd party I/O rushed through QA).
-
I don’t think a replacement will make a difference but do let us know. My Decklink works fine in Premiere and FCP, it’s only in AVID that I need to “initialize” it. It’s most likely a combination of AVID issues and BM driver issues. We’ll see if 9.2 drivers fix any of this.
-
Do the Capture Tool workaround as I described it and it will work. It is hard to say which one of AVID or BM is at fault – maybe both. I lean on AVID. In Symphony 6.0.0 I had to reinitialize the board with the Capture Tool everytime after switching back and forth from Source/Record to Color Correction. In 6.0.1 one initialization (before the first timeline playback) is enough, so it is a modest improvement.
-
@Yair: I’ve been having the same issue and traced it to faulty Decklink (Desktop Video) version 9.1 drivers. Installing older 9.0 fixed it. Also, you need to “initialize” the Decklink card using the Capture Tool (select Blackmagic for Source, select V, deselect TC, set a name for the Tape Name, and briefly press Capture (flashing red)).
Doing this works around whatever the issue is. Hopefully they will fix this in 9.2
-
That’s not a gamma shift issue, which by definition affects midtones.
The Luma graph from the AVCHD recording shows full range data (full swing), with values from 0-255, which is good for dynamic range but is illegal video (for broadcast purposes). It has both superblacks and superwhites, which is good for CC.
The DNxHD recorded by the Shuttle shows legal video ranges (studio swing 15-235). Looking at the luma density around the black point it appears the full range signal outputted by FS100 has been COMPRESSED to studio range and not clipped. It is arguably correct behavior, if one was to broadcast the recording directly.
The dynamic range can be stretched back in color correction as the information is not totally lost (it’s a less than ideal situation though as the compression/stretching will induce artifacts).
I think there should be an option on how the data is to be recorded: full swing vs studio swing (Rec709).
Personally I would choose to record full swing (illegal video) at all times and color correct to legal range for broadcast delivery, as it keeps all options open (web, cinema).The trick in AVID is to import full swing data as Rec709, which leaves it as is. If you specify RGB it will compress/rescale it upon import to Rec709 (studio range).
-
Yes you install Desktop Video. There should be 32bit XP drivers in there as well, at least there used to be prior to version 8. If not you could try a driver from the archive (7.9.5 is known to be stable).
You will have audio sync issues when streaming from AME (or other streaming software like Wirecast). There is about 1/2sec delay between picture and sound. There is no delay when capturing (no streaming functionality though) with Blackmagic Media Express.
I haven’t re-tested this in the last 6 months, but I don’t expect they fixed it in newer drivers. I (and others) think their own app works properly because it hooks into a lower lever driver interface.