Dom Silverio
Forum Replies Created
-
Awesome. The command seems to fix the discrepancy between the edited media on the timeline and the actual media file. For example, the timeline will reference x amount of audio samples or frames, when in fact it needs to reference y.
Great to hear it works.
-
Open the bin but not the sequence. In the Console, type “reparisequences”. It will attempt to fix media-related issues.
You can also try uninstalling third party AVX plugins and see if the sequence will open without it. If it does, reinstall each plugin one a time. -
Right-click the sequence in the bin and Refresh all.
-
Off the top of my head
1st gen Nitris DX
2nd gen – same as 1st w/ undocumented internal change AFAIR.
3rd gen – possible to have AVC-I Intra codec board native (only helps if you capture AVC-I SDI baseband. Does not affect file ingest).In general, get the higher model # as it would be newer (7020-30008). Though that cannot vouch of actual usage hours.
-
Nice!
-
[Robin S. Kurz] “Because they’re trying to open up an important option for everyone (which doesn’t even include THEMSELVES) and therefore are challenging an absolutely ludicrous patent? Fascinating logic.”
I’m not sure if the intent is “open up…. for everyone” but more of ProRes RAW options for Apple.
The patent is no more ludicrous than a rounded corner icon. -
Unfortunately, this is a design flaw on that Mac. During heavy CPU and GPU usage, the computer is unable to dissipate heat fast enough thus can cause random corruption. I highly recommend keeping renders in short bursts to prevent heat build-up.
-
What kind of Mac and GPU are you using?
-
MPE still assists during playback. The extent depends on the codec. Just tested with XDCAM and XAVC-S, GPU load was significantly higher under OpenCL vs software only.
-
[Tod Hopkins] ” Apple has simply decided they don’t want to do this work anymore, but they are not stopping others from doing it.”
AFAIK, a lot of the codecs they are “retiring” were never written by Apple, thus that work was never on Apple. What they are actually doing is not allowing THIRD party codecs to be installed via AVFramework without their approval (no approval has been given to anyone AFAIK). Writing the code for your codec only satisfies specific applications you have control over. The previous QT platform allowed you to write a codec for the QT engine itself allowing any software to access the same codec.