-
1. Re: Multiple Output formats from Single Source File? (Like Squeeze)
Supefan Apr 22, 2011 1:01 PM (in response to Tim@Monkeyraft)Here is an answer for you
I can't wait for this feature either.
-
2. Re: Multiple Output formats from Single Source File? (Like Squeeze)
harrijs1 Aug 9, 2011 4:33 PM (in response to Supefan)Any update on this ability? We create many in house videos that need to be encoded to 14 different
bitrates for use with Flash Media Server as dynamic http streams.
Currently when I am ready to export a finished sequence, I will pick my first preset and queue it in AME. Then I duplicate that thirteen times, setting each of the new thirteen queued items to their appropriate bitrates. Then I have to change each of the output names to be "filename_bitrate.flv".
This process is much slower when queued in AME than if I exported each individually from PP. I just don't have the time to manually export each version.
I have also started noticing that some of the last few projects won't render beyond the quality of the first queued item. Do I need to render the largest bitrate file first?
Any indication from Adobe on the correct workflow to create multiple bitrate files to be consumed by FMS as dynamic http streams would be appreciated.
The link above is dead. Does anyone have an updated link to the document above?
-
3. Re: Multiple Output formats from Single Source File? (Like Squeeze)
Mark Mapes Aug 9, 2011 6:03 PM (in response to harrijs1)There are at least two distinct feature requests wrapped up together here:
1) a convenient way to set up batch encodes. [separate feature: Bonus points for such a batch encode to be conducted in a more efficient (i.e., quicker) manner]
2) enhancements to filenaming options whereby certain information (such as bitrate) is automatically concatenated to a base name.
All three of these requests are in our official backlog. Company policy prevents me from commenting on if or when any feature will be implemented, but I can at least assure you that we're aware of the desirability of these features.
As for how to achieve the desired results within the shipping version of AME, I suggest you use watch folders. The general workflow is as follows:
- Create a folder to be used as a watch folder. Let's call it Folder X.
- set up one watch folder entry for each preset to which you want to encode. All of them can be set to watch Folder X (alternatively, you could set them up in series, where WF#1 writes to Folder Y, and WF#2 watches Folder Y and writes to Folder X, etc.)
- export your PPro sequence with the export path set to Folder X. For this encoding job, pick a high quality format/preset, with the same resolution as your sequence. If you have the storage space to spare, consider going out to a lossless format like Uncompressed AVI. That will yield the highest quality for the outputs through the watch folders.
When the encode from Step 3 is complete, each of the watch folders that you have set to monitor Folder X will automatically create a job to the specifications you set for that particular watch folder. In CS5.5, if you have the Auto-Encode Watch Folders option enabled in the Queue panel, then AME will automatically start processing those jobs; in earlier versions, there's a timer that triggers encoding to begin.
In case it isn't immediately obviouse, the advantage of using watch folders for cases where you're routinely encoding to the same set of presets is that you have to configure those presets only once. No more manual dupe-and-configure routine...
-
4. Re: Multiple Output formats from Single Source File? (Like Squeeze)
Colin Brougham Aug 9, 2011 6:09 PM (in response to Mark Mapes)Hi Mark,
Big ups for batch encoding presets; watch folders are fine, but are really not that efficient when exporting from a Premiere Pro sequence. Creating intermediates should not be a required step, because of... well, there are lots of reasons.
One clarification or correction to your proposed workflow, specifically, on this point:
(alternatively, you could set them up in series, where WF#1 writes to Folder Y, and WF#2 watches Folder Y and writes to Folder X, etc.)
Sounds good, but practically speaking, you'd never really want to do this. Unless I'm missing something, you're suggesting using compressed output as the source for another compressed output--obviously, that's not ideal. The workflow you suggested--exporting a high-resolution intermediate to a single watch folder--is fine, but the above will not provide the best results.
My $0.02...
-
5. Re: Multiple Output formats from Single Source File? (Like Squeeze)
Mark Mapes Aug 9, 2011 6:27 PM (in response to Colin Brougham)Agreed on both points. I should have either called out the significant downside of setting up a series of watch folders or simply left that option out altogether. Thanks for raising the point.
You're also right on the mark as far as watch folders being less than ideal for this purpose. Rest assured that the various features involved with batch jobs are relatively high on our priority list--we're not discounting their desirability one bit on grounds that watch folders are an acceptable alternative.
-
6. Re: Multiple Output formats from Single Source File? (Like Squeeze)
Colin Brougham Aug 9, 2011 6:32 PM (in response to Mark Mapes)Rest assured that the various features involved with batch jobs are relatively high on our priority list--we're not discounting their desirability one bit on grounds that watch folders are an acceptable alternative.
Can't wait! Generating four different outputs from projects with 8-12 sequences is a horror unmatched even by root canals without pain killers
-
7. Re: Multiple Output formats from Single Source File? (Like Squeeze)
Tim@Monkeyraft Mar 12, 2013 3:13 PM (in response to Tim@Monkeyraft)Just wanted to follow up and congratulate Media Encoder team for adding this feature with the CS6 update!
Thanks!
-
8. Re: Multiple Output formats from Single Source File? (Like Squeeze)
Todd_Kopriva Mar 12, 2013 3:44 PM (in response to Tim@Monkeyraft)Thanks, Tim.




