Dustin Foster
Forum Replies Created
-
As far as BM not being able to consistently recreate the problem. I would be more than happy to take a road trip with my setup in tow, or invite them to my suite for a nice cup of “watch this.” I am headed to NAB, but highly doubt anyone on the floor will have FCP 7 up with a BM Decklink card.
ProRes vs. 10 bit is an interesting thought. ProRes 422 is a go to for us. Is it just the sequence settings you are changing it to 10-bit, or are you bringing in actual uncompressed media?
-
I apologize for wearing my pessimist pants this morning. Sadly, I just don’t see them putting much effort into this fix. I spoke with BM on the phone and they thought it was being addressed in the latest patch; well that was November. I absolutely agree with you Jesse that we have to keep reporting it. I just find it hard to believe that BM is stumped by this, It makes me think that they are writing FCP 7 off. The only thing I have done is turn off the WARN WITH DROPPED FRAMES, I still hear the “crackling” but I am at least able to get through an edit, client reviews have become exporting REFERENCES and playing back. <—–worst workflow ever.
-
Sarah,
Are there any updates regarding this issue? I have downloaded and installed the newest DeckLink driver posted (Dec 14th, 2012). But the problem with constant dropped frames still exist.
-
Brandon,
Have you been able to resolve the issue. We just put in a new system with the BM Decklink Hd 3D+ etc. and are experience dropped frames with the 9.6.8 drivers (posted by BM support on Nov 8, 2012)
I haven’t gotten a response from Blackmagic, but I did get a nice reply telling me what dropped frames are.
Scratching my head.2x 3.06 6 Core Intel Xeon
24 GB 1333 MHz DDR3
240 SSD (with trim enabled) -
No – everything is set to zero.
Should I be in a 23.97 project – or a 24p project? Everything was shot at 23.97 – so to avoid the .01% pulldown in audio we stayed at 23.976. -
Im sure you have tried – but we had a similar program with a long format show as well. Once we conformed / onlined our 15:1 to 220DnxHD (Symphony) the timeline would no longer play – I could scroll and it would be there, I could load individual clips and they would play fine – but not in master timeline.
This worked for us, but again -it could be another Symphony bug and I understand you are on an Xpress system. Create a new sequence within the same project – add an in at the very first frame of your start – no bars tone / nothing and do the same with the end point – no extra black or anything. Copy it to the clipboard – and paste into a new sequence without changing timecode structure or anything. Then render entire sequence.
Once again – it has worked twice for us now on the symphony nitris – hopefully it works for you. I will try to uprez some footage on our Xpress to see what it does..
Good luck –
-
We have tried TIFF’s / PCTS / JPGS – you name it. I have found a work around but it can be very slow.
After selecting the image using the Avid Pan & Zoom effect – I then create my move – immediately render – save – and then clear the memory from the project window / bin window. Reopen a sequence and play back the effect making sure the picture is there. I then can add another effect on top – acting as a clip effect – and render – save repeat. Its just that with a 1 hour doc – I feel other post houses / users have to be using and doing the same process or something like it…..
until then……water – soap – rinse – repeat.
-
So far – it happens on all images. However – I just got off the phone with Avid Ds support and after changing some actual code in the bio’s – things are running smoother.
I sent my pics to Avid and they recreated my sequence or at least a few clips and tried the same moves, color corrections and are getting the errors. The image turns to Green when High quality is selected and then a fatal runtime error occurs.
So by fixing one memory error – right clicking on my computer – general and :edit: replacing userva2400 with userva2500 we have re-allocated the proper memory. Only bad thing is we seemed to have introduced a new error.
I am sure this post is as confusing as my phone convesation.
Until then….back to internet browsing, i mean rendering.
-
Thanks for the help! I put both sequences in the same bin and decomposed. It worked like a charm. Also for a test – I separated the bins and decomposed one sequence and relinked the other using “highest quality” and source tape and timecode!
Now know for the future this wont be a problem at all.