1 Correct answer
I don't know an easy or automated way..
<waving hand> Ooh, ooh! I do!
Of course, this assumes you have something that you didn't mention, but I'll operate on the assumption that you do: After Effects. Note that I can't fully test this on CS5.5, as I don't have the suite, but it *mostly* works in CS5. From what I know of CS5.5, though, this should work even better in several regards. Ready? Here goes...
- Assuming you have all of your clips in Premiere, and that you've already interpreted them to the
32
Replies
I don't know an easy or automated way..
<waving hand> Ooh, ooh! I do!
Of course, this assumes you have something that you didn't mention, but I'll operate on the assumption that you do: After Effects. Note that I can't fully test this on CS5.5, as I don't have the suite, but it *mostly* works in CS5. From what I know of CS5.5, though, this should work even better in several regards. Ready? Here goes...
- Assuming you have all of your clips in Premiere, and that you've already interpreted them to the frame rate you want (I'm guessing that's how you changed their speed en masse), select all the clips in the bin and copy them.
- Launch After Effects, create a new project, and paste all of the clips into AE; all the clips will be added to the project using the interpretation set in Premiere. Technically, you could start at this point by importing all of your footage into AE and doing the interpretation here; options, options.
- With all the clips selected in AE, drag them to the New Comp button at the bottom of the Project panel; this will open a dialog asking if you want to create a single comp with all clips, or multiple compositions. Pick the Multiple Compositions option, and hit OK. Wait...
You'll now have a bunch of comps, each containing one clip, with the proper intepretation and speed change... and they'll also have the name of your source clip. - Launch AME. Go to Edit > Preferences > General, and tick the "Specify output file destination:" checkbox. Pick the location where you want all of your encodes to land; the reason you need to do this is that AME lets you change the format and preset for multiple queued items, but stupidly, you can't change the location for more than one item. This step will save you a lot of headache x1400
- Go back to AE--and this is one cool new feature--select all your comps and drag-and-drop them into the AME queue. You can now change the format and preset for all of your queued items at once, and you'll see that they're all going to land in the location you chose in the Preferences. One final bit that changed in CS5.5 is that multiple queued PPro sequence or AE comps use that sequence or comp title--NOT the project title--when you add multiple items to the queue. This was an extremely annoying oversight in CS5 (and frankly, would have made your process pretty much a nightmare), that thankfully has been rectified in CS5.5.
Now, of course, the moment I typed all that up (which I'll leave so you can see how ridiculously easy the next process is), I figured out a better solution.
- Drag all your clips in AME.
- Select all your clips in AME.
- Right click a clip in the queue or go to File > Intepret Footage. Set the frame rate you want. Hit OK.
- Set your format, preset, and click the start button. You'll still want to have set the location preference as above in #4.
I'll let you decide which is easier 
Shoulda said:
Nice solution... if I had CS5.5.
Or, use the AME feature that imports Pr sequences. In the AME import window you maneuver to the Pr projects file and then select the sequences you want to encode.
The only problem with adding 1400 sequences to AME using this method
is that the output file names will all be identical (the name of the project that
the sequences were imported from).
You will need to specify different output file names one at a time.... 1400 times.
Or, check "Increment output file name..." in the Preferences menu.
That should work if generically named and numbered files are ok.
Is that really correct? I thought the files encoded from the sequences have the same names as the sequences, not the project from which they came. I'll have to try that as soon as I get a chance.
Actually, that used to be the case. Fortunately, CS5.5 saved us Premiere Pro sequences and After Effects comps added to the AME queue will now retain their names, instead of using the project name with a serial number. One of those tiny things that makes a huuuuge difference...
I'm away from my editing rig right now so can't double check, but In Premiere Pro CS5.5 try this -- with Pr open, open AME, then select all the sequences at once in Pr and drag to AME. Or, use the AME feature that imports Pr sequences. In the AME import window you maneuver to the Pr projects file and then select the sequences you want to encode.
Jerry,
What you're suggesting works, but the problem is that there is no way to quickly create 1400 single-clip sequences in Premiere Pro, and you can't send multiple clips sans sequences from Premiere Pro to AME. Fortunately, there are workarounds (see above.)
Colin,
Right. I was going by the post title, but OP does say clips at the end.
There is, perhaps, another solution without going to After Effects, and that is to use the Watch folder. This might be much quicker for large numbers of clips, depending on the work flow.
Colin Brougham wrote:
Jerry,What you're suggesting works, but the problem is that there is no way to quickly create 1400 single-clip sequences in Premiere Pro, and you can't send multiple clips sans sequences from Premiere Pro to AME. Fortunately, there are workarounds
There is, perhaps, another solution without going to After Effects, and that is to use the Watch folder. This might be much quicker for large numbers of clips, depending on the work flow.
It would, if you didn't need to manipulate the clips before encoding. In this case, the OP wants to slow the clips down, e.g. reinterpret their frame rate. With a Watch Folder, it's FIFO; adding them to the queue at least lets you do a modicum of clip manipulation (via Interpret Footage) before encoding. That's what my second solution entailed
okay, it works, just not as fast.
importing all the videos was no problem at all, but when it comes to changing the frame rate, it gets a bit more complicated. It can only process about 80-100 videos at a time (via "file --> interpret footage"), otherwise it crashes. but 14 clicks are better than 1400... 
its exporting the videos at the moment, seems to be working so far. takes about 15 seconds for each video.
Thanks a lot again for the help, you saved my day! 😃
importing all the videos was no problem at all, but when it comes to changing the frame rate, it gets a bit more complicated. It can only process about 80-100 videos at a time (via "file --> interpret footage"), otherwise it crashes. but 14 clicks are better than 1400...
Thanks for reporting. I wonder if the crash is a memory issue; it might be a situation where AME is not managing memory properly, and it just keeps trying to load clips into memory to change their interpretation, but isn't letting them go afterward. If you have a way of watching the RAM uitlization, you might be able to confirm this. If it is, it might be worthy of a bug report: Adobe Feature Request/Bug Report Form
In any event, glad you're able to make progress!
AdChoices