Brandon Kraemer
Forum Replies Created
-
I have been through 3 driver versions now and 2 OS versions (10.8.1,2) and this problem has been 100% consistant ever since I switched from AJA to BMD hardware. Very frustrating.
BMD basically said there will be no fix for this and blamed Apple for changing something in the OS.
I have been doing this for a really long time and I can’t remember a situation where such a significant hardware feature wasn’t repaired by the next driver revision.
It’s very disappointing.
-
Blase,
That is a good guess because I did that initially (rendered the entire sequence as interlaced) and thought it was the culprit so I re-rendered the 23.98 out progressive… didn’t change the end result. I did confirm the renders were over-written and that FCP saw them as progressive.
Thanks,
Brandon
-
Matt,
Thanks for your reply. Splitting out the frame rates did prove a work around however Resolve isn’t supposed to render anything with frame rate conversion and it’s sending clips back to FCP as both 29.97 and 23.98 as it should but the 23.98 clips look jacked up. In other words I am relying on Resolve NOT to do the cadence math which is the point of the support mixed frame rates option. This way I can have the entire edit on one timeline in A mode order so we can see everything in context.
Great feature… if it works in the end. So unless I am missing something I’d say this feature is buggy.
Anyone else ran into this and found a real solution?
Thanks,
Brandon
-
Blase,
FCP was not adding any filters like you suggested.
I can confim that seperating the 23.98 footage onto it’s own 23.98 FCP timeline and round tripping that through Resolve, then conforming those Resolve renders onto the 29.97 timeline is a workaround and now things play as they did in the offline.
Resolve is doing something to the clips when rendering and this doesn’t seem like it should be happening.
Appreciate any help in figuring this out, the work around adds a lot of time to the session.
bk
-
Adam,
After re-installing did you find you had to reinstall or reactivate any licenses on that machine? Did network settings for instance have to be manually setup? I have a number of node locked licenses that use OS generated system keys (Foundry, metaSAN) I am concerned about screwing up in this process.
Also after re-installing. are you sending audio out over the Decklink card with picture (audio follows video) and not getting dropped frames? How about with Pro-Res footage and timelines? I had found that Uncompressed 10-bit didn’t drop frames so much but ProRes did like crazy.
Thanks,
bk
-
please post back on how a non-mountain lion OS reacts. I am unfortunately hamstrung if I want my CUDA cores working but it would be nice to know all the same.
bk
-
I certainly don’t want to speak for BMD support, but I did hear back from them recently regarding my support ticket on this topic and they do not have a solution citing inconsistant results while testing. They said that with our without BMD hardware some Mountain Lion machines are working just fine with FCP 7 and others have issues. They said it was still open on their end but based on results so far it might not be something they can fix.
-
I got a response from what seemed like “level 2” support… but no resolution yet. I heard from someone with more direct links into BMD tech support that they are working on it.
-
Update… Disabling audio out on the Blackmagic card seems to stop the drop frames issue in FCP 7, but creates another one: out of sync audio!
See this thread, others are having this issue: https://forums.creativecow.net/thread/8/1164660#1166253
-
It’s definitely DeckLink. I isolated everything NVidia out of my system and the problem persisted.