[Eric Sanders]

Not exactly, no. Premiere Pro’s AVI importer is running in a 64 bit context, VLC and Movie Maker are both 32 bit apps, as is Windows Media Player in the contexts I’ve seen. What this means it they are only able to use and load codecs (or DirectShow components in this case, if VLC Player is using DShow) that are registered, and matching the application depth. It basically boils down to components must match for the depth of the app requesting them (32 – 32, 64 – 64).

Now, there are vendors who provide Direct Show components in both 32 and 64 bit depths, MainConcept comes to mind, I’m sure there are others.

https://www.mainconcept.com/products/plug-ins/decoding/decoder-packs.html

It might be worth trying their demo to see if it suits your needs. You are specifically looking for 64 bit Direct Show components. Do be careful installing any old codec though, as I’m sure you know.

Good luck!
-EricS

[Eric Sanders]

So what’s likely happening is this is a directshow codec, and sadly there aren’t as many 64 bit DirectShow codecs as there are 32 bit. If you find a 64 bit ac3 directshow codec this should do what you like.

Of course you can also rip the audio stream out in whatever app you like, and put them together in the premiere sequence.

Good luck,
-EricS

[Eric Sanders]

Hi Mike,

I have it on good authority that this was an issue fixed in the AME 6.0.1 update. Can you confirm?

-EricS

[Eric Sanders]

Which preset (or settings) are you using? I haven’t heard of this actually, can you tell us more about the sequence audio rate, video rate?

Thanks,
-EricS

[Eric Sanders]

Fair enough – I have observed cases on MacOS 10.6/.7 of RED playback (really, any thing on the disk, but RED is big data enough for it to me more directly observable) being affected by the FW800 controller bridge on some external drive housings, whereas the same file played back on a non-external disk were dandy – hopefully with that in mind a path to joy can be found.

Cheers,
-EricS

[Eric Sanders]

So the short answer – when AME is rendering either a Premiere Pro sequence or an AE composition, it is sending frame requests across a process boundary, getting that frame copied into its process space after being rendered in a ‘headless’ version of Premiere Pro (PProHeadless), or a similar ‘healdess’ version of AE for its composition. By its very nature this is going to be slower (not by much, but non-zero) than rendering directly in the process that is doing the rendering. When a frame request fails, as you’ve seen, AME closes the file from the export as best it can (why you have usable renders of quicktime movies when a failure happens), and that’s that.

When you render your Premiere Pro sequence ‘inline’ you get both the full access to whatever GPU rendering you have as well as Rocket support, you also are not crossing the process boundary (unless you have AE comps embedded, in which case the same out of process rendering happens for PPro as it does for AME).

The project sounds quite interesting!

-EricS

[Eric Sanders]

I would suggest you consider MXF OP1a with XDCAMHD 4:2:2 50 as one option as well (or lower bitrate depending on your needs), if your client can read these files – H.264 is certainly more available as a codec, though. That’s a decent choice for further editing as well, depending on how the audio tracks need to be setup.

Good luck,
-EricS

[Eric Sanders]

I have found that FW800 drives can have the issue of the controller resetting a bunch – as a test, if you work with say one of your clips on an internal drive rather than your FW800, does it change the behavior?

-EricS

[Eric Sanders]

Hi Dave,

Could you post a screenshot of the AME encoder dialog and the sequence settings values you are using? That might help us see what’s going wrong.

Thanks,
-EricS

[Eric Sanders]

Hi there,

This is what I use:
https://www.nvidia.com/object/product_quadro_fx_4800_for_mac_us.html

Very nice board, works on mac and win, so you can bootcamp into windows 7 x64 on the same rig. Read the limitations though, I seem to recall you have to be on Rev 3 or 4 or higher of the Pro Tower hardware.

Hope this helps!
-EricS