Why is there no Batch Export of multiple clips from Premiere CS6?

[henryfilms]

This is a no brainer.  Every other NLE has had this for at least a decade, yet PP CS6 makes you INDIVIDUALY export clips rather than sending them as one batch. What a time waste for someone looking to move to CS6 from FCP and finding it's slower.  

[jbircher]

Absolutely option B.

[SebastianGrob]

The source range control is not working for me on cc11.1.1 when I export from de project window. I have two machines running Premiere, one in cc10.4.0 and the other cc11.1.1, the one in 10.4.0 can do this. Is there anyway you can help me?

[HarleyTDavis]

Unfortunately, working across versions can have a bug or two.  The source range modifier (I'm assuming in export dialogue as that is where Source Range is defined) is connected to your cached previews and work area in some way, I don't recall exactly how.  If you move from one version up to another, you'll have to:

1. resave the file as the new format file

2. Relink the datafiles so that the new version can grab them properly

3. save the project in the new version at least once and make sure the work areas are set

If you're talking about subcliping in the source window, you are doing a source selection range, and this is accomplished with the "i" key for in and "O" key for out points.  You should try using those first.  You can clear them also, check the menus for CLIP etc.  It will show you the keypress for clearing the selections.

[Elliott B.]

I'm using Premiere 7.1, and I want to make a digital intermediate like the other users, but I don't see how this is possible.  If I highlight all my clips in a sequence, and choose export media, it's going to export the entire sequence as a whole.  But I need to export each clip individually, so the timeline can be conformed in another software, such as Resolve.

Your post specifically mentions selecting items in the project panel.  But isn't the point of this feature to export after picture locking the edit?  If I shoot on a camera that's supported in Premiere, but not supported in Resolve (such as Sony FS700), I want to transcode only the necessary clips to ProRes 444 after locking the picture edit, I don't want to transcode all the hundreds of source files.

[jbircher]

Hey Elliott - I wrote a script that does this automically.  It will export each clip in a picture locked sequence by nesting each clip.  Feel free to email me at --- jeremy at storyandheart dot com  ---- and I can send it your way.

After you've run the script, you select all the nested sequences and export and voila!

[excited_Genie16B8]

You can easily sort the bins by usage, and then choose only those clips that are used for batch export.

Or, you can use the new Direct Link to SpeedGrade feature and skip this step entirely.

[Elliott B.]

Hi Jim,

I have a few dozen sequences, so sorting by usage sounds impractical.  But your comment got me thinking, I could import the timeline to a new empty PP project, then go from there.

[shooternz]

Consider that many Resolve Suites have Clip Wrap as a solution.

Consider using Speed Grade (Direct Link)

Avoid using DIs or transcodes for grading unless unavoidable.  Original Source is always best.

[Elliott B.]

Yes, I have been thinking about ClipWrap.  Haven't tried it yet, and I wonder how taxing it would be on the CPU to grade AVCHD.

Speed Grade's integration is indeed nice, but to say "original source is always best" is a gross exaggeration.  "Best" could refer to minimal generation loss, or software performance, or user experience.  Generation loss could be completely eliminated with an uncompressed DI.  In this case, ProRes 444 is close enough to lossless that I will happily accept it in order to use a more powerful grading tool that I am familiar with.

[shooternz]

In this case, ProRes 444 is close enough to lossless that I will happily accept it in order to use a more powerful grading tool that I am familiar with.

Is the transcode to PR444 writing time code correctly?

Yes, I have been thinking about ClipWrap.  Haven't tried it yet, and I wonder how taxing it would be on the CPU to grade AVCHD.

Clip wrap has worked very well for me in Resolve Suites.  Its uses source material with a header re right. ie...No transcode and the timecode works for the EDLs.

[Elliott B.]

Exporting multiple clips at a time would produce files with zeroed timecode.  But as of today, with Premiere 7.2, that's fixed!  Unfortunately the export still strips all tape names, and it names the files using clip names instead of original file names.  Slow progress...

[DLpres2]

+1

I also submitted a feature request. Note that this hasn't changed in CC.

To make it as simple as possible: it's possible to drag sequences over from PPro to AME, it's impossible to drag over clips.

Currently I have to project manage everything (which may require copying over to a new project), waste the drive space (thankfully I'm working on short projects, otherwise it'd be insane), and then drag the files over to AME. Doesn't make much sense.

I know that the development team is well aware of needed improvements to project consolidation and transcoding, so let's hope we see something in 7.1.

[mike_buckhout]

There is another way that I learned recently to get batches of sequences into AME, the trick is you have to start from AME, go to the File menu, and select "Add Premiere Pro Sequence...", then navigate to your project file, open it, then select the sequences you want to import.  In CS6 at least the browser window is strange and doesn't seem to sort folders in any regular way so if you have a ton of folders it might take a minute to find your stuff but it does work. 

Saved a bunch of time since I started doing it this way, although I would still like to see a push from PP to AME implemented in the future, since opening the project from AME seems really slow, I suppose it is loading the entire project into the Dynamic Link Manager, but if I already have it open in PP I don't understand why it would take so long.

[HarleyTDavis]

With PP open you are using memory for the program to run.  With PP closed, you have the extra memory, and AME still accesses the files by reading the project file (an xml readout of where everything is, how it is arranged, etc.).  If AME needs an actual file, it searches based on the project file, then links and renders.

[adjohnson62]

The only (ridiculous) workaround I can find to achieve something as rudimentary as getting a Premiere Pro CC sequence of clips into Resolve once the picture edit is locked is to make a new bin to hold a series of sequentially numbered sequences: create enough sequences to get to an integer with a number '1' in it eg. 'Sequence 21': discard all the unneeded sequences up to number 21 and then start smashing Ctrl + N, Return for the number of clips in the locked cut: then drag each clip in the locked cut down in order into Sequence 21, Sequence 22, Sequence 23: then drag that sequential series of sequences into Encoder with a 10bit YUV preset and a new assigned folder somewhere on my Write drive, run the encoder queue and then line the new exported clips up sequentially as a new Resolve timeline and grade from there. Utter madness, and no dissolves, obviously.

[HarleyTDavis]

I've noted something similar.  If you want to export many clips, they have to either be natively clipped (imported from their own file), or placed into their own sequence and rendered to a preview file.  From what I've seen and tested, the preview file is only used for frame alignment of the export in AME.  The clip markers are used as a reference, aligned frame by frame to the preview and then rendered into export file.  This appears to have something to do with the time code adjustment, and it's logical enough.  If you create sequences, their time codes start at zero unless you specify otherwise, and this zero time code allows the video to be processed as a separate entity.  when nesting sequences, add zero to the frame time code of the next frame after the previous clip's end, and the math works easy in your mind.  If you'd like to set the start to where it will go before nesting, you can, but you may have to change it later anyway.  Once you render a preview of a clip or sequence made of them,  the time code and framing are built into the preview.  sending to AME after that can work, but it's better to close premiere and import the batch to AME, then select the sequences, and choose the settings by batch selection, or individual clip-sequence.  Now AME has everything it needs to process all the framing and timing into useable files that you can import back to premiere, deleting the other sequences, and enabling you to work with your exported/imported clips, even batch exporting them without a new sequence as individual clips, or inside sequences as part of one compilation to export as one movie file.

when you wake up in the morning, render...

Before you do lunch, render...

when you need a mid-day nap, render...

bfore dinner, render...

see where I'm going?

before shower, render...

before relieving yourself... ...eh, save, go, then render when you get back...

[RuesterProd]

Is there a plugin for CS6 to do this?

[HarleyTDavis]

Somebody online named a different video software that has a plugin for this, but I can't remember where or what the name was for plugin.  So... ...Your best option is to nest clips into sequences of the length you need (IE if you have a sequence ready, mark in out, nest it in a new sequence), save project, quit, open AME, import from Premiere, select the sequences you want to have rendered as export and begin.  If you have a lot of clips from same single file:

dupe original sequence once for each sub clip, mark each sequence for in out, nest, and follow the above.  Or... ...use razor to cut up your clips and paste them into their own sequences, then save proj, quit, open ame and import as above.  If you have trouble with audio, you may want to render it out before save\quit.

On mac, you may be able to script, but on PC, you'd need an autohotkey-like app.  A plugin?  If you know what you're doing with adobe-scripting in java or javax, you might be able to script your own plug to export each clip to the AME queue, but I've had problems when they aren't in sequences, so if you could script THAT part, you'd be circumventing a possible issue.

[HarleyTDavis]

Okay... ...new answer...

If you want to export multiple sub clips, they need to be in their own sequence.  A sub clip is only a markup file that points to another file.  You can't export it because it has no metadata tags tying any of the data together, except of course, for the file it points to, which may even be a section from another sequence containing multiple camera angles and multiple files....

You need to make your sub clips, then nest them in a new sequence, then export the sequences to AME.

[Lennard.H]

For a new better method check out this extension!
www.ezclip.store