-
MOV’s created in After Effects CS5 cause some QT components to disappear?
So here’s a weird one.
We use the XviD compressor component with Quicktime Pro 7. Any MOV that comes out of Adobe CS3 (using Apple Animation codec) will open in Quicktime and when we Command-E to export, we can do “Movie to XviD AVI”, which is great, because it plays back on our engines and is of decent file size.
Anyway, we just got CS5 on one of our test machines, and we rendered out an MOV. Same format, same compressor, everything. It shows up in Quicktime 7 as an Mov with Animation compression (same as the CS3 files).
Yet, when we go to export the movie, the “Movie to XviD AVI” option is gone (along with a few others).
This also occurs if we try exporting that MOV on a machine without CS5 as well.
On the machine with CS5, if we open an MOV from CS3 in quicktime 7 pro, it shows the XVID codec export option.
I also tried H264 encoding (which has previously worked from CS3) and even that MOV makes the option disappear.
Has something changed with the way CS5 outputs MOV files? they still open in quicktime 7, I just can’t export to AVI.
Anyone have a fix?
-
13 Replies
-
Khaannn!
Hopefully that gets resolved soon; as it’s a huge workflow problem for us if we can’t do native XVID AVIs from the mac!
-
Neither solution (compressor or media encoder) supports AVI exporting on the mac side.
I don’t get why the outputted MOV would be causing this issue though, it’s not like I’m trying to export them directly from AE CS5… the compression seems identical (even reports back in QT as the same compressor).. and even if i try encoding that MOV on a computer without Snow Leopard or CS5, the codec still disappears.
-
Yes, I know this. QT X doesn’t support exporting to any legacy codecs, so we installed QT 7.x from the disc, updated, added our pro license, and like I said, ONLY with MOV’s created from CS5 does the codec/component disappear.
Any old MOVs in QT7 (on that same machine!) can be converted to XVID, it’s only the MOVs created with AE CS5 that the option disappears.
As I said before, this happens on OTHER machines as well (If we copy the MOV from CS5 to another machine that has say, only CS3 and Leopard on it, it still disappears).
It’s something in the way AE exports the MOV, there’s got to be some new information or something that gets appended to it.
-
Because AE doesn’t support exporting to AVIs on the mac side. If I could export directly to an XVID AVI I wouldn’t be having this problem.
Our media player only supports XVID AVIs for the content we’re creating (Well, that’s no true, we can do HD MPEG2 BLURAY, but AVI is legacy for us and it’d require a lot of testing to convert over to mpeg2 reliably).
Anyway, yes. it MUST be an AVI, and it MUST be XviD, and for some reason the codec stopped working when we threw MOVs from AE CS5 at it.
I’ve got a temporary workaround using MPEG streamclip (as it accepts the MOVs and allows for XviD exporting using the very same component from QT), but it’s more of a hassle from a training standpoint when everyone knows how to hit Command-E and save stuff in batches.
-
I think we’d likely go the MPEG HD route before requiring an added step in workflow 😀
It’s weird, It’s the actual MOV though, it’s totally independant from AE when we’re doing the conversion.. totally mind boggling. I might end up looking at two exact files (one from CS3 one from CS5) and see whats different in a HEX editor or something.
-
are you mov files non-square pixel?
that’s the only thing i can think of that would be different from cs3-cs5 in a rendered mov file. adobe changed (corrected) the pars for non-square formats in cs4, and it is possible that an older format may require the older par. (i remember avid’s codecs being that picky, if you comp wasn’t d1, no avid 1:1)
if that is the case, i’d have to play around with trying to create a custom par comp setting to get the legacy par back… of course someone may have already figured that one out, you might search the web….
as far as the streamclip workflow, streamclip will do a batch conversion, which actually may improve the qt pro workflow, but i know what you mean about re-training people…
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW -
i was looking at the xvid site, and i’m less confident that there is a par/frame dimension issue (i’d still look into any discrepancies, though), but i did notice that they released an update friday that addressed some mac issues.
https://www.xvid.org/Home-of-the-Xvid-Codec.1.0.html
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW -
There doesn’t seem to be a link to the OSX component version, anything on their site is still sitting at 1.0 from 2007.
-
upon closer inspection of the date on the 1.2.2 update, it was may 29, 2009 (not 2010) sorry about that.
what are your comp settings–frame size, frame rate, pixel aspect ratio? and are there any differences in those settings from the cs3 comps/renders that you can transcode…
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW -
Comp settings are identical (in some cases we’re even bringing in the comps from CS3 AE project files),
Anyway, comps are as follows:
1280×720, square pixels, 30fps.
Reply to this Discussion! Login or Sign Up