Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Avid DNxHD QT codec now posted!

Thanks guys, I asked because I get nothing but noise.
 
I did tried the latest today but I will give a try again. Thanks.
 
It worked beautifully, I guess I was downloading the codec set for Composer. I'll help a post house to adopt this for the feature film offline editing we are working on.
 
Unfortunately these did not ship with Media Composer 3.0.5 but are compatible and supported with Media Composer 3.0.5 and later.

Michael
 
Make sure you have the latest R3D QuickTime Component from RED.

Michael
 
Oh...is there an R3D QT Component for PC? I thought it was just Mac. I'll hunt again.

EDIT: Yes, that component is Mac only. I'm Avid PC. Always PC. ;-)

The new Avid QT codec did solve the RedCine noise issue on export. But seems to have re-introduced the exact same issue in AE CS3. Like juggling flaming torches, right?
 
A question: Isn't there an unnecessary step to transcode an already DNxHD file?
Why can't you just do an output of let's say 720p from RedCine, put all files in a folder and then after doing some metacheating, relink to that folder without ever importing? That way you save discspace and erease a timeconsuming step (even if the import is fast).

Also, how the hell do I get sound through RedCine??? How can I edit something without sound?
 
The files, regardless of codec still need to be imported in order to rewrap as MXF instead of QT. The codec itself is a copy - whether that be DVCPRO HD or DNxHD, etc.

Audio is a whole other issue - the latest REDCINE does do audio, but seems to be early beta with some issues still. The lack of REDline and the R3D component on PC reduces the number of workflows we currently see on Mac.

PC users - hang in there. "A change is gonna come..." ;)

Michael
 
While the dedicated media structure on Avid has its advantages, it also has its flaws.
Michael - any chance there might be a softlink to external media in the future ? Think autodesk... hinthint..

Glazarus said:
Why can't you just do an output of let's say 720p from RedCine, put all files in a folder and then after doing some metacheating, relink to that folder without ever importing? That way you save discspace and erease a timeconsuming step (even if the import is fast). ...
Click to expand...
 
MichaelP said:
The files, regardless of codec still need to be imported in order to rewrap as MXF instead of QT. The codec itself is a copy - whether that be DVCPRO HD or DNxHD, etc.
Click to expand...
So who should I suck up to, to get MXF wrapped DNxHD files out of redline:-)
 
That would be RED... they are fully aware of this need... :)


Michael
 
This is probably obscure, but it has popped up again as a bug.

I'm using After Effects CS3 on the same computer as the Avid Media Composer and Redcine (but note these are the only programs we have on this workstation). I downloaded the new Avid codecs which give me correct DNxHD output from Redcine. Without these new codecs, you just get a colored miasma when you output from Redcine.

But here's the bug--when I use Cineform HD codec files (QuickTimes created with NeoHDV) within After Effects CS3, I now get the colored miasma in 16 bit and 32 bit projects. It's fine in 8 bit--the image looks normal. But in 16-bit/32-bit, I get the exact same colored miasma that Redcine used to give me with DNxHD files using the old Avid codecs.

So I uninstall the new Avid codecs, and re-install the old ones (Avid CodecsLE). And now my After Effects CS3 works perfectly again--the Cineform files appear normal in 8-bit/16-bit/32-bit projects.

Hm... Looks like I'll have to switch back and forth between Avid codec packages for now, using the new ones for Redcine and the old ones for Cineform + After Effects CS3.
 
I wasn't trying to get Cineform to decode DNxHD.

I was actually using Cineform NeoHDV. Nothing like the Cineform 4K products at all. In fact,they recently discontinued NeoHDV and rolled it into another lower-end product.

But I thought it was worth pointing out the bug, because lots of folks use NeoHDV. And it might have some relevance for other Cineform products, I don't know.

In the end, it seems to be something funky in the new Avid codecs, which were redesigned to include R3D compatibility...but the result is this funny bug with NeoHDV and After Effects.

I might be the only one in the world who cares about it. Just thought I'd let others know, in case someone does a search (like I tried) to get to the root of this esoteric problem.
 
Hi,
I've been trying to import DNxHD files created in RedCine (latest version, latest Avid codecs) on a PC, into Avid MC 3.5 (also latest version). These are PAL 25p files for offline editing.
It works fine, except I can't get it to make a "fast import", it always says "creating video", which is ok but takes longer. I've been trying to change all the import parameters, but it stays the same...

Any idea what I'm doing wrong ?
 
Look at the properties in MoviePlayer and make sure it is 1920 x 1080. Also look to see that your color settings in import is set to 601/709.

Michael
 
step by step needed

step by step needed

well, someone who definitely KNOWS how to FAST IMPORT may kindly explain that in STEP BY STEP manner.

it looks to me that in pal countries, despite is it 1920x 1080 or not and 601 or not - that fast import is not at all that fast.
but, maybe i am wrong... maybe i am making some small mistake somewhere... or at least cannot say what is FAST or how fast is fast import. who knows. (in my situation best results with using "fast import" is 3x the original time)

so, please be so kind and share some knowledge here...

btw. for that very reason - which is - very slow "fast import" we are building our own application (which we are testing right now), and results are very promising. the process is separated in two parts. one of them is not realtime, but really, really close and the other one is realtime... he, he... more info soon.

but anyhow - any additional info about "fast import" is welcomed. i.e. with importing times, software and hardware versions etc.

thank you,

filip
 
You must log in or register to reply here.
Back
Top