Did you know that there has been a major overhaul to prores and where\how it's installed? I've had the same issue, but I ran the following test:
I've installed the compressor, I used the cs6 prores and... ...FAILURE. I was on CS6, and it didn't work... ...Why? Tell ya in a moment... Next step:
I undid the last action by dumping the prores presets. Then I installed the cs7\cc version. Bingo.
I went and researched the problem.
Apple now includes most of the prores specification in the quicktime bundle (except their new 444). It's all in the same bundle. I looked into some workarounds people have used to get it working without pro-apps... ...they all focus on using the older prores which is installed as separate packages... ...and separate bundles. What does this mean?
If you are above 10.7 for your mac os, and you have compressor (latest), you have the prores built into the quicktime bundle. If you are 10.7 or below, and you have the version of compressor for that period (same codec, different file arrangement), you have the prores codecs all in separate bundles. They are inactive but still included in the quicktime bundle for 10.8 and above, so you couldn't use them without the right presets, along with compressor which changes the files to an actual bundle instead of a simple file inside the quicktime packaging.
If you are on later mac os and you have CS5 or above, use the CC version of the presets. If you have the older prores or an older compressor and wish to try and hack it in, you can do it, and then use the CS6 version of the presets supplied by adobe. They point to different bundles in the system. I use both, on different machines. IF you have cs5, you may want to use the "hack" way, and install the prores from older compressor, even if you have the newer one... ...They work faster in cs5 if you use the CS6 presets. Why? I do not know for certain, but I believe it has to do with the 32bit crosstalk. Cs6 starts with 64 and has to "dumb down" to 32 for a connection to quicktime directly, and then, if it finds 64bit architecture, smart-ass up to 64 again. In Cs5 you're stuck in 32 most of the way on the back end. Only a guess.
And when importing into premiere... ...HMM... >>>I had the same problems you had... It wanted to only import audio. If you have the time... Try:
Copy the presets from adobe that are for AME into the proper sequence preset folder of your Premiere app (the previews folder). You should also try and find a way to set up your main sequence edit. Try to remember that an AE import must be:
Fully Rendered into a file, and not linked from AE but from the file itself OR
The composition must be set to the same uncompressed codec (which means you need the preset in the AE app folder as well, finding this will be difficult, best of luck).
Remember to match your preset to your codec. IF you have separate prores bundles, use cs6 versions of the preset, and if you have the latest bundle, use the cC\cs7\2014 versions. This will let AE provide an uncompressed composition, but very slow in previewing, and if you render out, remember to render to a whole file (you can try to render-farm, but you still have to re-render in AME or Compressor afterward, as farm will only render out the frames and an audio file, not the proper file wrapper, even if you specify that wrapper; You have to build the file wrapper from the images and audio after you've rendered any effects).
.
45
Replies
AdChoices