Native Editing of Canon Footage in CS5

Does CS5 recognize the proper white and black levels of 5D and 7D footage or is that something you would still benefit from using cineform to convert your footage first?

If I edit in the native MOV format will I be limited to the 4:2:0 color space or can I edit in the MOV format and apply my color correction and then export in an 4:2:2 or 4:4:4 format so that my colors don't break up as much?

This is the most important question !!!!
 
Thanks for sharing.

Are you mac or pc user?

Both, helps in Beta testing. The difference between the two platforms are marginal with CS5, in Prem, main difference is on the Mac you cant export to a WMV file or an MPEG 1 file out of the box (some weird licensing thing) Other than that they are functionally identical and you can even swap projects between the two systems with no probs.
 
Does CS5 recognize the proper white and black levels of 5D and 7D footage or is that something you would still benefit from using cineform to convert your footage first?

If I edit in the native MOV format will I be limited to the 4:2:0 color space or can I edit in the MOV format and apply my color correction and then export in an 4:2:2 or 4:4:4 format so that my colors don't break up as much?

OK, so I asked the exact same question to the Adobe techs a while back and they sent me this great response which I have promptly lost. But basically the gist of it was that the Canon files re in a non standard colour space, hence the messed up black levels when usually converting. That said Premiere only understands normal colour space like REC601, REC 709. Now, when you apply any kind of effects or transition that changes the image, the render is not done back to the H.264 CODEC, and if you set Maximum Bit Depth in the rendering options it will render it up to 48 bit (depending on the output CODEC). After Effects at the moment is the only package that can understand the non standard colour space and deal with it. So you can dynamic link the finished cut to AFX and do your grade their for the best results (although to be honest you should be doing this anyway, as Colour Finnesse is an awesome tool)

UPDATE: Just got a response from the propeller heads and it goes as follows

'The Canon color shift issues should be fixed with recent builds. Effects are always rendered in 444 regardless of source. Rendering is done at 32-bit only when you select maximum bit depth or always when you use a CUDA card. '
 
Last edited:
Does CS5 retain the clips timecode like Edius? I know before CS5 Edius was the only app to do this and Adobe said they couldn't retain timecode for AVCHD/h.264 clips. Vegas doesn't do it either.
 
I have a question about CS5 and video cards. I heard the new mercury engine will work with the Nvidia GTX285?

I have 2x GTX275 in SLI will that be able to run the new software or am I out of luck?
 
'The Canon color shift issues should be fixed with recent builds. Effects are always rendered in 444 regardless of source. Rendering is done at 32-bit only when you select maximum bit depth or always when you use a CUDA card. '

I've been trying to say this for ages on this forum but a lot of people don't believe it.

However, there is an issue with FCP which I would consider bad implementation where the project and source files must share the same color depth.
 
I have a question about CS5 and video cards. I heard the new mercury engine will work with the Nvidia GTX285?

I have 2x GTX275 in SLI will that be able to run the new software or am I out of luck?
Unfortunately no you will not get full Mercury Playback support via CUDA

Supported NVIDIA graphics cards for GPU acceleration
Quadro CX (Windows)
Quadro FX 3800 (Windows)
Quadro FX 4800 (Windows and Mac OS)
Quadro FX 5800 (Windows)
GeForce GTX 285 (Windows and Mac OS)
 
As far as I am aware DSLRs dont actually write timecode in clips, so there is no timecode to support.


I know... But I use both DSLR and HMC150 and HMC40.. How about timecode for those AVCHD files?

Plus the new AF100 will probably support timecode in AVCHD files.... What's the story morning glory?
 
As far as I am aware DSLRs dont actually write timecode in clips, so there is no timecode to support.

Actually they do. The new FCP plugin from Canon writes every prores file with TOD timecode. So, there IS something in those files.
 
No Timecode from DSLR's

No Timecode from DSLR's

Actually they do. The new FCP plugin from Canon writes every prores file with TOD timecode. So, there IS something in those files.

Technically there is no timecode in the Canon DSLR files for anyone to use. The Canon FCP plug-in takes the time of day stamp on the file and creates its own timecode during import. The end result is that you have timecode, but there isn't actually anything in the file for anyone else to use to generate timecode.
 
Hey Evan, thanks for all the posts, I've been really considering starting to use PP for certain work instead of FCP, with the round tripping, BOTH NLE's will probably benefit me in the work I do. Having more tools is always great.

Just a few questions if you have the answers. Is the media management pretty much the same as it was in CS4? If anything that's still something they need to get right... (FCP too, I came from Avid so media management was the first thing i noticed switching...)


In your opinion how much of a performance hit would I see if i got a gtx 285 over a quadro 4800? I don't plan to be doing many streams of 4k anytime soon, but the 285 is a pretty powerful card, and those are the only nvidia options for mac essentially that offer the juice you'd want. It's a huge price difference and I'm really debating which I should go for. What would be your advice on which card to go for?

do u know if it's gonna be blackmagic and or aja compliant?

is the media encoder software pretty much the same as cs4? or did they make any interface/option tweaks on it? it should be 64 bit too correct? so rendering out files should be much faster no?
 
Hey Evan, thanks for all the posts, I've been really considering starting to use PP for certain work instead of FCP, with the round tripping, BOTH NLE's will probably benefit me in the work I do. Having more tools is always great.

Just a few questions if you have the answers. Is the media management pretty much the same as it was in CS4? If anything that's still something they need to get right... (FCP too, I came from Avid so media management was the first thing i noticed switching...)


In your opinion how much of a performance hit would I see if i got a gtx 285 over a quadro 4800? I don't plan to be doing many streams of 4k anytime soon, but the 285 is a pretty powerful card, and those are the only nvidia options for mac essentially that offer the juice you'd want. It's a huge price difference and I'm really debating which I should go for. What would be your advice on which card to go for?

do u know if it's gonna be blackmagic and or aja compliant?

is the media encoder software pretty much the same as cs4? or did they make any interface/option tweaks on it? it should be 64 bit too correct? so rendering out files should be much faster no?

Wow, thats a few questions, OK, deep breath in and.......

-Media Management: Its better than FCP (ie it actually works some time) howevr for native files it wont trim them down, it just collects the files) but the good news is it is super stable and allows you to select individual timelines to manage)

-Mercury: I dont have a 4800, I went the 285. I think for most people the performance boost of the 285 is enough that they will think its awesome. Being able to drop a colour corrector on a 720/50p H.264 on a Core 2 Duo and have it play straight away is still something that shocks me. I think that as the software s release and eventually they add extra cards to the supported list, it is probably wise to just go a 285. Unless you are cutting RED footage day in and day out and doing heavy duty work on each and every shot, it is hard to justify the 4800

-Drivers: Still waiting on the final Decklink drivers (I have a MultiBridge Pro) so cant talk deffinitively about them till I get them, dont have AJA gear so cant comment

-AME: Is MUCH!!!!! Better than with CS4, it is super stable I have yet to have it fail on me even in BETA compared to CS4 that was not to put to fine a point on it a 'POS' I wouldnt say it is that much faster per se, but it is stable, has a lot more features (setting interpretation, fields etc. It has the prevew back which I always missed, it reads the 5D and 7D colour space correctly and did I mention it is super stable (I am actually running it right now converting 4 days worth of 7D footage to ProRes for our FCP editors) and as an added bonus they brought back direct export, so you can use AME and the que or you can just send it direct, but if you do send it to the que it has an autostart after a user configurable delay, so you dont have to send it to AME then click over and click start on AME, it will just do that in the background.
 
Adobe will send you CS5 Update for FREE

Adobe will send you CS5 Update for FREE

ugh... i bought CS4 a week before CS5 was announced.


I had bought CS4 Premiere like you recently, and then Adobe made their launch of CS5. However, I called Adobe sales and told them about my purchase. They said "No Problem", just gives us your Premiere or Production Premium serial number, and Adobe will send you your Free CS5 upgrade to you in the mail, starting April 30th. Just call Adobe Sales at 800-585-0774

No worries you will get the upgrade for free.
 
Wow, thats a few questions, OK, deep breath in and.......

-Media Management: Its better than FCP (ie it actually works some time) howevr for native files it wont trim them down, it just collects the files) but the good news is it is super stable and allows you to select individual timelines to manage)

-Mercury: I dont have a 4800, I went the 285. I think for most people the performance boost of the 285 is enough that they will think its awesome. Being able to drop a colour corrector on a 720/50p H.264 on a Core 2 Duo and have it play straight away is still something that shocks me. I think that as the software s release and eventually they add extra cards to the supported list, it is probably wise to just go a 285. Unless you are cutting RED footage day in and day out and doing heavy duty work on each and every shot, it is hard to justify the 4800

-Drivers: Still waiting on the final Decklink drivers (I have a MultiBridge Pro) so cant talk deffinitively about them till I get them, dont have AJA gear so cant comment

-AME: Is MUCH!!!!! Better than with CS4, it is super stable I have yet to have it fail on me even in BETA compared to CS4 that was not to put to fine a point on it a 'POS' I wouldnt say it is that much faster per se, but it is stable, has a lot more features (setting interpretation, fields etc. It has the prevew back which I always missed, it reads the 5D and 7D colour space correctly and did I mention it is super stable (I am actually running it right now converting 4 days worth of 7D footage to ProRes for our FCP editors) and as an added bonus they brought back direct export, so you can use AME and the que or you can just send it direct, but if you do send it to the que it has an autostart after a user configurable delay, so you dont have to send it to AME then click over and click start on AME, it will just do that in the background.



amazing! great to hear, it will probably be some time before i make the leap to cs5, I'll want 100% assurance it will work on my set up, and I'm kind of holding out till resolve comes out too, as I will be castrating my apple pro apps acceleration if i dump my ATI card for NVIDIA now. But it's good to hear that it's rock solid, and now round tripping anywhere and everywhere is easy :)
 
The day that I read that the GTX 285 is the only non-Quadro card supported by Mercury, I bought one through craigslist for only $250.
 
Back
Top