View Full Version : Canopus HQ and Adobe MC Cs5

05-16-2010, 10:59 PM
Been reading a lot about incompatibility with premiere pro cs5 and the canopus HQ codec. I am considering upgrading to CS5 as I do a lot of flash encoding with adobe. My current workflow is usually edit the project in Edius 5.5 then export clips or the entire project to a MS avi then use Adobe media encoder to export to flash, though sometimes I will use PPRO or AE for slicker titles before the export to flash. My question is will I now have to capture my edius project to another codec like lossless or an mpeg codec in order to keep my workflow or will I be Ok as long as I continue to export as a MS directshow avi?

Alter Ego
05-16-2010, 11:35 PM
If CS5 doesn't support HQ codec. I would think that as long as you don't export the project using Canopus HQ codec, all should be well. I usually export to After Effects using Canopus Lossless or Uncompressed RGB. This way in theory at least, if not visual, I keep the cleanest video I can going back and forth between applications and generations. I am also thinking about upgrading to CS5 just for the AE rotoscoping brush and the improved PhotoShop capabilities. That rotoscoping brush conjures up some cool possibilities. The HQ codec won't be an issue or show stopper for me...

David Clarke
05-17-2010, 10:04 AM
The problem is that 64 bit CS5 does not understand 32 bit codecs - and the Canopus codecs are not 64 bit. I just exported a couple of files from EDIUS 5.5 and loaded them into After Effects.
Canopus HQ does not work
Canopus Lossless does not work
Uncompressed RGB does work
Uncompressed YUV does work

All standard formats - MPEG, DV, HDV, AVCHD, DVCPRO XDCAM will work as will Quicktime Files since Adobe wrote their own importers for these.

A format that will not import generally only imports the sound not the picture.

05-17-2010, 03:23 PM
Adobe is trying to be an island all to itself !!! There is NO reason why a 64 bit program cannot call a 32 bits program. Just some nasty marketing stuff at Adobe at play.

David Clarke
05-18-2010, 11:11 AM
I do not think this is an Adobe problem but a GV one. Sony Vegas 64bit will not load Canopus HQ clips either. I would think that GV would be aware of the problem and would be deciding whether to produce a 64 bit versions of their codec, which I hope they will.

In the meantime you will either need to stick to CS4 or to export in a standard format like MPEG, AVCHD, DV or uncompressed.

05-18-2010, 12:47 PM
After Effects CS5, I have felt more... and not only 32-bit codecs are no longer with CS5, but all others plug-ins that work in 32 bits... the thing has changed for everyone, and of course the solution is urgent for us to have and to "Canopus HQ" as a 64-bit codec... with all this we see that EDIUS 6 has come out in 64 bit native yes or yes.

05-18-2010, 01:04 PM
Adobe Lightroom 64 has been out for a while and it has no problems with the raw codecs for stills that worked when it was 32bit. My guess is the problem is split between Adobe for lack of accomodation and others like GV for not taking the next step.

05-18-2010, 01:14 PM
Adobe is trying to be an island all to itself !!! There is NO reason why a 64 bit program cannot call a 32 bits program. Just some nasty marketing stuff at Adobe at play.

I agree! I don't see the big deal. I have CS3 and CS4. They both still work.
Just because the new version has been released doesn't mean that the older version shuts down.
Is it smart to go to 64bit, yes. Should it accept 32bit codecs, yes! It defintitely should be backward compatible.
They can market the fact that CS5 is 64bit. All of the programs are not 64bit but work under a 64bit OS. Encore is still 32bit. So why not accept all of the previous 32bit codecs?
Because they want you to use all ADOBE and know one else.
Is this GV's problem. NO! You can still export from Edius in other formats that will import into CS5. Would it be helpful, yes. Is it a deal breaker, no!
Many feel that GV needs to produce a codec just for Adobe import. Come on, get real. On one hand you are purchasing a proprietary product and complaining about another companies proprietary product not being able to be imported in the first proprietary product.

It was Adobe's decision to set it up that way. So, if you are planning on buying CS5, you know the limitation with HQ. Either use a different export codec, or stay with a previous version. I can understand the complaints from the early adopters. I would be ticked off as well. But now that it is well known, purchasing CS5 and using HQ will not work, you will have no reason to complain except that you could not wait.

05-18-2010, 02:01 PM
Thanks for all responses, I can work around the lack of a 64-bit HQ codec and that's what's important for my workflow. I am also interested in the rotoscope feature in AE but more interested in the hardware acceleration in CS5 and using more memory to do encodes.

David Clarke
05-19-2010, 10:37 AM
I spoke with an Adobe engineer about this and they say they cannot write support for someone else's codec without access to the code (which people don't tend to give out).
I don't think anyone has been under-hand or bad, its just something you need to be aware of when using CS5.

Worse for me is that fact that AE does not take AAF anymore. This is the way I would get timelines from EDIUS to AE as a collection of separate clips. The only way to get AAF to AE CS5 is to import the AAF to Premiere, then send that to AE.

And the Rotobrush is great!

05-19-2010, 02:50 PM
Oh? May we know the open source solution in that case? Thank you.

05-19-2010, 07:17 PM
I spoke with an Adobe engineer about this and they say they cannot write support for someone else's codec without access to the code (which people don't tend to give out).
I'm puzzled by this... the VfW/DirectShow interfaces are there to provide a standardized access.

If they couldn't use a codec without seeing the code, you wouldn't be able to say, install Xvid, Indeo, or VP3 codecs and be able to use them right away.

With ProCoder, VirtualDub, etc, as long as the codec is installed and it's the supported type (VfW/DirectShow) and architecture (x86/x64), then once it's installed it's accessible.

Maybe they meant they can't optimize for someone else's codec? That makes some sense, as many codecs have advanced options that require being documentation and sometimes even more.

05-19-2010, 08:28 PM
This is Adobe's fault.

Under OS X, AECS5 can access 32bit QuickTime codecs. It runs a separate process called "Adobe QT32 Server."

Plugins required to be 64bit is understandable. But not having access to 32bit codecs is not.