Alius Sato
Forum Replies Created
-
i guess i’ll try .png then.
but none of the source footage was GOP-compressed. in the instances where i’ve seen this, it’s been avid meridien 1:1 or jfif (, which i assume is motion jpeg) – going towards dnxHD.
-
kinda quiet on this thread for a while. what do we know, does sebsky tools work?
i need to port an fcp 7 project to avid mc5, and the producers don’t want to drop the $ for automatic duck…
how about some tutorial on sebsky workflow?
-
picking up an old thread, but:
avid can export either RGB or 601/709 dnxHD files, there’s a choice for that in the export settings dialogue.however, both types of files get flagged as YUV (601/709) inside the .mov container.
which means that:
– the export is faulty in the case that you’ve exported RGB, but it’s been flagged as YUV.
– how you import to FCP will have to depend on whether you did an RGB or YUV export. -
Alius Sato
February 15, 2011 at 8:58 pm in reply to: bizarre qt / avid mc5 (win7) problem – graphics are over-sizedok – have now bit the bullet & de/re-installed mc5, qt 7.6.6, digidesign audio drivers. am back in business.
what exactly was at the heart of it we’ll perhaps never know. thanks for pointing me to the right direction, job.
-
Alius Sato
February 12, 2011 at 3:21 am in reply to: bizarre qt / avid mc5 (win7) problem – graphics are over-sizeddear job – thanks for pointing me to the right version.
(though until i’ve tried i’m not sure that’s the glitch – it was working on winXP /w the old qt 7.3.1.70)
anyway – will report back.
-
Alius Sato
February 7, 2011 at 7:30 pm in reply to: bizarre qt / avid mc5 (win7) problem – graphics are over-sizedwin7 – 64 ultimate build 7600
qt – 7.3.1.70
mc5 – 5.0.3 -
if you need to share with two boxes maybe it’s doable with the iSCSI / nas -type hookups – i’m not enough of an IP storage guy to know.
i’m using the 4-bay areca box that’s much like this, save for the iSCSI. mainly happy with it. on the 8 bay one – i’ve read a german review complaining about disappointing throughput speeds. but then if you’re planning to use firewire and/or iSCSI, the hookup is going to be the link on the chain throttling your speed anyway.
likely the best raid boxes now are the caldigit ones, but to get the full benefit you need a miniSAS hookup.
-
having just spent several hours struggling with this problem, i think i have the answer. hoping to save an hour or two for someone else.
FCP appears only to be able to (“desktop preview” =) play back full screen sequences that are using standard codecs, frame sizes & aspects. while you can create whatever kind of a sequence and cut it, the preview function(s) only work when you conform with standards.
thus – it’s a good practice to load the closest standard sequence preset after you’ve allowed FCP to match the sequence to your imported clip.
-
Alius Sato
March 8, 2009 at 4:24 pm in reply to: avid mc, boris red 3 – an external photoshop file – interlace jitterhey peter – following your suggestion from earlier, i’ve now downloaded the latest trial. it fixes the problem.
many thanks for the pointers – let’s consider this thread closed with a successful conclusion.
-
Alius Sato
March 8, 2009 at 3:24 am in reply to: avid mc, boris red 3 – an external photoshop file – interlace jitterexcellent point, peter.
the media rendered straight out of red is pristine. (using qt-animation, highest quality settings, 1-2-1 deflicker tick-box.) so something is amiss in how red talks to the avid.
also it seems that avid’s 60i rendering doesn’t have the same problem, like PAL didn’t. but unfortunately i don’t know of a way to create a 60i SD project.