Speed up Adobe Media Encoder conversion time?

Hello I started a topic that is now answered about After Effect which can't convert h.264 (MP4) without using Adobe's media encoder. That's fine with me I just want to be able to convert the video's I use the software After Effect gives you. But I started this topic over here to ask if their is a way to speed up conversion time using the media encoder. Thanks and sorry if I don't answer all the time I only reply to answers that help not comments about the same topic .

I don't think you can create such a thing for the general populace. There are just too many variables.
You can take a 1 minute segment and export at various settings on your computer to get such a chart, but that will apply only to you with that material.

Similar Messages

  • Problem wit the speed of Adobe Media Encoder

    Dear Sirs, my computer has two Xeon e5-2687w each 8 core processors. Why is Adobe Media Encoder running to only 20% CPU?
    Thanks,
    Jiri Stepanek

    Dear Sirs, my computer has two Xeon e5-2687w each 8 core processors. Why is Adobe Media Encoder running to only 20% CPU?
    Thanks,
    Jiri Stepanek

  • Adobe Media Encoder CS4 Causing Jerky Playback with Speed Changes

    Here is an Matrox AVI that was captured in Adobe Premiere Pro CS4. Watching the edited clip with a speed change of 600% looked fine when played in Premiere Pro CS4.
    When I export the clip using Adobe Media Encoder CS4 as MPEG2 Blu-ray with a preset of 1440 x 1080i High Quality playback is very jerky. An export of the same clip with normal speed looks great??
    Any suggestions would be greatly appreciated
    Thanks
    Type: Matrox AVI
    File Size: 119.9 MB
    Image Size: 1440 x 1080
    Pixel Depth: 24
    Frame Rate: 29.97
    Source Audio Format: 48000 Hz - 16 bit - Stereo
    Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
    Total Duration: 00;00;36;27
    Average Data Rate: 3.2 MB / second
    Pixel Aspect Ratio: 1.3333
    Codec Type: MPEG-2 IBP
    Bit Depth: 8
    Scan Mode: Interlaced - Upper Field First
    Actual Image Size: 1440 x 1080
    Here are the specs on my workstation
    Case: Coolmaster-830
    Op System: Vista Ultima 64 Bit
    Edit Suite: Adobe Creative Suite 4 Production Premium Line Upgrade
    Adobe Premiere Pro CS 4.0.1 update before installing RT.X2 Card and 4.0 tools
    Performed updates on all Adobe Production Premium Products as of 03/09/2009
    Matrox RTX2 4.0 Tools
    Main Display: Dell 3007 30"
    DVI Monitor: Dell 2408WFP 24"
    MB: ASUS P5E3 Deluxe/WiFi-AP LGA 775 Intel X38
    Display Card: SAPPHIRE Radeon HD 4870 512MB GDDR5 Toxic ver.
    PS: Corsair|CMPSU-1000HX 1000W
    CPU: INTEL Quad Core Q9650 3G
    MEM: 2Gx4|Corsair TW3X4G1333C9DHXR DDR3 (8 Gigs Total)
    1 Sys Drive: Seagate Barracuda 7200.11 500GB 7200 RPM 32MB
    Cache SATA 3.0Gb/s
    2 Raid 0: Seagate Barracuda 7200.11 500GB 7200 RPM 32MB Cache SATA 3.0Gb/s Using Intel's integrared Raid Controller on MB

    Have you ever upgraded Adobe Premiere Pro in the middle of a project?
    By the way I captured the same clip in Adobe software only mode using HDV as a capture settings.  The editing mode is Adobe HDV 1080i, 29.97 frames. The results are also jerky. When I render the clip captured it is also very grainy??
    Type: MPEG Movie
    File Size: 196.4 MB
    Image Size: 1440 x 1080
    Pixel Depth: 32
    Frame Rate: 29.97
    Source Audio Format: 48000 Hz - compressed - Stereo
    Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
    Average Data Rate: 3.2 MB / second
    Pixel Aspect Ratio: 1.3333
    Thanks for responding so quickly!

  • Long time for Adobe Media Encoder to encode 3 minute video

    I created a Premiere Pro project with a dynamic link to Adobe After effects (both CS4 versions).
    Upon finishing this PremPro project which is a 3 minute song with 3d animation playing in the background, I chose Export Media.
    Since first try was taking a long time (15 minutes and little progress), I removed the 3 transitions I had in my Premiere Pro Project, reduced the audio from 128 to 64 bit, decreased the bit rate to its lowerst 56 kbps instead of the default which is something like 1000-2000 kbps I believe (Please let me know default value so I can reset it ) and reduced video size from 960 x 620 to 380 x 244.  I also shut all of my programs that could be chewing up significant memory.
    I'm just looking for a rough feel of how things will look so only wanted to start with a 'draft quality' render of my flv - but the Adobe Media Encoder is still saying it will take 1 and a half hours, and this is on a 64 bit, Win 7 system with lots of RAM (24GB) and plenty of hard drive space.
    The actual After Effects compositions are fairly complex, with numerous 3d animations superimposed on one another, but I wasn't sure if this sluggishness suggested something was wrong that I need to correct to get quicker performance, or if it's simply a reflection of a complicated scene, and that's how long things will take even at those very minimal settings.
    Thanks for any suggestions.

    Not sure what you mean about the process.  From Premiere CS5, I click on "export" which brings up a menu. I select "media" from the menu which brings up the Adobe Media Encoder.  I adjust my settings and click "export" from the bottom of the screen to immediately render the Premiere file.  Clicking "Queue" would put the program into the AME Queue.  Am I missing something?  On the slowness issue, looks like I need to reinstall AME. I've been reluctant to do that, partially because I'm using some Matrox hardware and I'll have to reinstall the Matrox softare to populate the matrox settings into the media encoder. Looks like it may be worth it.
    Thanks.

  • Export Quick Time using Adobe Media Encoder...

    I'm a Windows (vista) user and I rarely use the Quick Time options in the Adobe Media Encoder but nonetheless, I have in the past. I was called on today to export a Quick Time of a video for a Mac using client and every time I selected an Adobe preset under Quick Time, 'Custom' would appear where it should normally say something like 'Source to Download 256' or whatever. (Sorry I can't check now, I'm rendering a big project). So no matter what preset I picked, I'd get 'Custom' appearing as my choice. Is this normal or has something gone wrong in the innards!?
    Sorry, I have no other computer to check with Premiere Pro CS3 installed.
    Thanks

    Thanks for the input. So just to confirm, you're saying that if I choose one of the Adobe Presets under QuickTime, that that setting should STAY visible in the selection box. Yes? Just like the others. Windows Media, Adobe Flash, etc...
    Because mine immediately changes to CUSTOM after I make a QuickTime selection. Also, it DOES NOT give me a file size estimate like the others. Does this make sense?

  • Long load times normal for Adobe Media Encoder from Premiere CS5?

    When I export a sequence from Adobe Premiere CS5 using Adobe Media Encoder, the system freezes for several minutes before giving me the exporter screen.  Then, when I've loaded my settings and clicked "export," the system again freezes for several minutes before beginning to encode.    I'm using a system with an Intel I7 CPU 930 @ 2.80Ghz 2.80 Ghz., 24 GB of ram, Windows 7 Ultimate 64 bit operating system and an Nvidia quadro FX4800 graphics card..  Everything else is fast, but AME is slow.  Is this normal? Should I reinstall AME?

    Not sure what you mean about the process.  From Premiere CS5, I click on "export" which brings up a menu. I select "media" from the menu which brings up the Adobe Media Encoder.  I adjust my settings and click "export" from the bottom of the screen to immediately render the Premiere file.  Clicking "Queue" would put the program into the AME Queue.  Am I missing something?  On the slowness issue, looks like I need to reinstall AME. I've been reluctant to do that, partially because I'm using some Matrox hardware and I'll have to reinstall the Matrox softare to populate the matrox settings into the media encoder. Looks like it may be worth it.
    Thanks.

  • Adobe Media Encoder CS5 - Can we crop and resize at the same time?

    Flash 8's video encoder, use to let you crop (cut x amount of pixels out) and then resize  a video (and in that order it did it).
    CS5's Media Encoder is confusing, from what I can tell it cannot do both, you either can crop or resize but not both. ANd if you can do both, you definately cant crop before the resize. So which is it?
    Resizing made sense last, because you could put in new values for the resize nad figure out how much you need to crop out.
    Please help this is driving me insane.

    Everyone in my office has the same problem!
    We really need an alternative to AME both because of the crop/resize problem and many other seamingly random issues with preview and export.
    Adobe Media Encoder sucks...

  • Time-specific Image Overlay using Adobe Media Encoder

    Basically I just want to add a black screen at the end of my video. Is there a way to easily do this in Adobe Media Encoder without having to use other video production programs like After Effects or Premiere Pro?

    Thanks for the input. So just to confirm, you're saying that if I choose one of the Adobe Presets under QuickTime, that that setting should STAY visible in the selection box. Yes? Just like the others. Windows Media, Adobe Flash, etc...
    Because mine immediately changes to CUSTOM after I make a QuickTime selection. Also, it DOES NOT give me a file size estimate like the others. Does this make sense?

  • Adobe Media Encoder 4.2 update forces Frame Blend

    I didn't really want to repost, but I felt the title and info in my previous post were innacurate (http://forums.adobe.com/message/2576915#2576915)
    In my previous post, I thought Premiere was to blame, but after a few reinstallations, I've found that the update to AME 4.2 causes the problem.
    I've found that Adobe Media Encoder 4.2 forces Frame Blend, even if it has been disabled on each clip of the timeline, when the frame rate of your sequence settings differ from the frame rate of the target format.
    Example: Exporting from 24fps Desktop -> MPEG2-DVD (23.976fps)
    Adobe Media Encoder 4.1 does not have this behavior.  I've reverted to 4.1 for the time being.
    If anyone has a workaround for this, or any other info on this problem, please share.

    I am having a similar problem.  Is it just me or is it Adobe?  I have had so many problems with Adobe Premiere CS4.  It may have also been exacerbated by the fact the I updated to 4.2.1 (mostly in part to determine if another issue was resolved with this update).
    I have some editing background in the Windows Movie Maker and iMovie world, and was excited to use Adobe Premiere, but I have had nothing but problems.
    Everything that I am trying to do, looks really washed out, and renders the video useless.
    I am trying to do what you just described, with speeding up and slowing video to match the computer actions with the person's voice.  I am capturing video using CamStudio and Helix YV12 CODEC, and tried to use HuffyUV lossless compression: using DV-NTSC as the standard format.
    Then I go to compose my video, and output the video, but the video is crap.  It sounds like the Adobe Premiere and Media Encoder are having major problems.
    I tried rendering it to Uncompressed Microsoft AVI with UYVY @ 100% quality, and tried to compare it with Windows Media at the highest quality, and it is frustrating.  When I hear that Frame Blend is being applied, it seems to look worse.
    I am running:
    Intel Core 2 Quad CPU 2.33 GHz (which is kind of slow)
    8 GB RAM, 2 SATA 1 TB Drives WD Caviar Green (a little substandard)
    Windows XP 64-bit
    Let me know there is another process that I am missing.  I don't really want to give up on Adobe Premiere, but from a end-user standpoint, I will have to revert back to using WMM due to time constraints.  I want to take full advantage of all of the editing and effects capabilities of Premiere, but can't because I can't even produce a decent export to be used by any other program (and given that every conversion will in some way affect the quality of the output, I want to reduce any intermediate steps).
    Arrggh!!!

  • New PC, downloaded CC 2014. Flash not showing up as option to rip in Adobe Media Encoder or in After Effects. Help?

    Why is .flv not an option in Adobe Media Encoder or Adobe After Effects?
    Also, when Adobe Captivate converts the video it looses the Alpha channel.
    Help

    Thanks for taking the time to answer this question. Knowing this isn't possible at least narrows my options down. It would be helpful to provide some kind of list of what comp settings carry over into AME from After Effects. Is it essentially everything that is enabled in the Timeline? (I know that motion blur settings do.)
    I'll put this in a feature request, but yes, we need the other half of After Effects Render Queue in AME in order for AME to be a good replacement for rendering from AE. I'll give you my thoughts on why Render Settings are essential before you would actually want to render with AME instead of doing so because you have to (either because you want to render in the background, or need a codec that has been removed from AE.)
    1. Speed: Simply applying a Render Settings preset is much faster than manually setting motion blur, frame blending, work area, etc.
    2. Reliability: Not being able to apply a Render Settings preset at the time of render is a recipe for missing a crucial setting buried in a comp, then having to redo a render and wasting time.
    3. Features: As noted above, there is no way to approximate Render Queue's ability to change resolutions at render, which results in a lot of wasted time when that feature is needed.
    Render Settings I think are crucial to making AME rendering worthwhile for AE users:
    1. Rendering resolution
    2. Work Area/Entire Composition toggle
    3. Field Rendering (wait, does this mean AME can't currently render to fields?)
    4. And PRESET ability these settings, so I'm not doing them manually every time.
    I realize that your team clearly doesn't spend the same amount of time I do making low res H264 previews and sending final files out in H264 format, so you don't appreciate the impact of the changes you made. Moving to AME for that stuff is a real inconvenience, but implementing the settings above could help soften the blow.
    Thanks,
    Jerry

  • Adobe Media Encoder error when encoding: winfile.cpp-759

    Mods: Please move this to the appropriate thread wasn't sure to move it to Premiere or Flash
    I receive this error when trying to encode AVI to H.264 using Adobe Media Encoder CS5 (64bit):
    When searching through the forums, several suggestions for CS4 and current releases that I have tried are:
    clearing the media cache through AME, and the folder location in %APPDATA%\Adobe\Common\
    installing K-Lite Codec pack
    changing the media cache files folder to a separate disk entirely
    updating to the latest version (at the time of post ver 5.0.1.0)
    uninstalling and re-installing AME (as an error might have occurred during updates)
    verifying that the CPU has SSE support and is enabled
    I expanded my search to google which gave similar errors (winfile.cpp-754, winfile.cpp-758, etc.) and a few responses were uninstalling any Nero products (don't have any burning programs on this computer - unless you count Windows)
    The system that I have is:
    MS Windows 7 64-bit
    Intel Core 2 Quad Q6600 @ 2.40GHz
    2x 1.0GB Dual-Channel DDR2 @ 800MHz
    512MB GeForce 9600 GHz
    2x 250GB HDD Mirrored
    External USB 500GB HDD
    Any ideas as to what the cause of this is?
    LK.

    The information about installing codecs packs is true. It usually does more damage to your codecs already present with software already installed on your computer, and the registry settings even after removing it. That is why it is in good practice to do full image back ups monthy, saving the latest 3 for when I utilize last resort methods such as codec packs.
    Adobe CS5 software has been working fine on my computer ever since its installation July. I forgot to mention that I have successfully used Premiere Pro CS5 for editing a dozen files ranging from SD small res to HD 1080i. This also includes just using AME CS5 itself for transcoding files for supported playback on different devices. I notice a greater difference in speed when using a more up to date machine that uses a GTX 285 card for GPU playback - a lot faster and smoother.
    I have a 2nd, slightly older computer, that houses an extra drive I put in there to use as a scratch disk. I occasionally add that disk to the computer that has CS5 currently installed as a scratch disk for editing video. The external USB drive is used to store the final product and my backups.
    This error has only come up 1 time out of the 49 files I have encoded that usually run 10 minutes to 1.5 hours. I had 9 AVI files in the encoding queue and it always stopped at this 1 particular file. I skipped the file and encoded the rest successfully, but I want to know why it causes an error in AME because this has never happened before. I have even used it on a more up-to-date machine spec wise, thinking that there is a 1% possibility that it doesn't like my computer. The same error was produced. The 9 files that I did encode are roughly the same video and audio format - just this one is the error.
    I gave the file to my friend who was supposed to analyze before I got home - I usually assist them in PC problems and built his better-than-mine PC.
    Any other suggestions for this error and/or a solution?
    Lk

  • Adobe Media Encoder CS6 Random Crashing Mid-Render

    Hello -
    I've been dealing with this issue for enough months and across enough computers to finally seek out some advise here, hope it works out...
    Basically I've got a 2 hour long film that I've been trying to export using Adobe Media Encoder CS6. It's never made it all the way through. I can usually skim through the generated quicktime file up to the point where the crash occurred. I've tried using that as a reference to check out my sequence in Premiere but there is never anything suspicious going on there. Most frustratingly the crash occurs randomly. Sometimes it will go through 10 minutes of the film; sometimes an hour. Regardless I get a crash with a report that has no specific information.
    Footage:
    r3d - Various resolutions, all being cut in a 2048x1152 sequence.
    Quicktime mov - ProRes4444 for the most part.
    Machine(s):
    I had been attempting to render this for the past few months with a Macbook Pro running OSX 10.8.4 w/ 16GB RAM, 2.7 GHz Intel i7, NVIDIA GeForce GT 650M 1024MB - never made it through a render longer than 50 minutes of the 2 hours.
    We recently got one of the new 2013 Mac Pro systems running OSX 10.9 w/ 16GB RAM, 3.5 GHz 6-Core Intel Xeon E5, AMD FirePro D500 3072 MB
    The hope was that this new powerful machine would overcome the issues we were running into with these renders. Since I'm posting this now you can probably figure out that it didn't really work out that way...
    Software:
    AME- 6.0.2.81
    Premiere - 6.0
    I know there are updates to be used here, but whenever I update Premiere from just 6.0, the project itself becomes a buggy mess, crashing constantly. I also run Creative Cloud and have tried to just jump over to Premiere CC hoping all my problems would vanish, but instead, I again get a buggy project that constantly crashes. The only version of Premiere that seems to work with this project is 6.0, so general updates have not been useful (and instead damaging, I've wasted several days trying everything I possibly can to make the project work in the updates).
    Any help appreciated. Thanks.

    Thanks for the reply MMeguro.
    Last night I was able to get my first full render through by doing a combination of things (so I'm not sure what did the trick in the end).
    To answer some questions first, never attempted to do the FULL render directly out of Premiere, always switched over to AME for that, so that potentially could work too. Smaller renders have worked directly out of Premiere Pro, but they've also worked out of AME.
    The initial render attempts that had been failing for the last few months were on the MBP which did not support GPU accleration due to an incompatible graphics card. I assumed the issue must be tied to something else because of this and was using it on the renders with the new 2013 Mac Pro. Using the workflow of Pr6.0, AME 6.0 and GPU rendering turned ON, I was failing to render to both Quicktime h264 and ProRes 422.
    What worked for last night's render:
    1. Convert Pr6.0 project to PrCC project (when I've done actual editing in CC after converting this project it tends to crash, but I figured just generating the project itself without doing any editing in it might satisfy what I was attempting to do).
    2. Open AME CC and import PrCC Sequence. Used custom ProRes 422 setting.
    3. Turned OFF GPU acceleration.
    So as long as I the PrCC project I create stays stable long enough to save it (without crashing, which has been a problem with that Pr6.0 to PrCC conversion) then it seems like this will work. Kind of an annoying couple extra steps but I'm just out of my mind glad that I can actually render this thing finally. We're still in the rough stages so being able to turn around a review version within a day is very important.
    Wish I could do more tests to figure out exactly which combination actually made this work for the benefit of others, but can't afford to do multiple 10 hour+ renders with random crash times.
    Anyway, thanks again for the reply MMeguro much appreciated.

  • Adobe Media Encoder CC - You Need to Add Unsupported CUDA Cards to supported_cuda_cards.txt

    Hi Folks
    I'm running on a Mac Pro with an NVidia GTX 770 with 4GB. Premiere Pro CC utilizes the GPU for playback and export but will give you a warning when you first enable CUDA in Mercury Playback Engine. However...
    I was noticing that when I queued the export to Adobe Media Encoder CC, it was taking forever to encode simple queued sequences.
    After doing a bit of research on the internet and even in these forums I realized that while Premiere Pro was being ok with supporting a non-supported card, Media Encoder was not. I added the GTX 770 to the supported_cuda_cards.txt file locate here: /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/ (you will need to be slightly geeky to find and modify this file - more info than I care to provide in this post but you can look up how to locate files in Mac OS).
    Voila! AME now encodes super speedly, like 4 times as fast as before!!!
    Thought I'd just provide this little tip for people experiencing this problem.
    Adobe... can you do something about this? I know it's a corner case but really - maybe something in AME preferences or something... Like "Use CUDA capable card even if not on supported CUDA list" checkbox or something.
    Now I can get back to work.
    -Keith

    I just made this change in the AME ".txt" file for my GeForce GTX 670 (i7, WIn 7 Pro, 32 GB, and I know it's not "certified" for CUDA), and now have it in both the PPro and AME ".txt" files. While I'm waiting for AME to finish, this thread raises questions in my mind.
    It's been my understanding that AME was engineered to run in the background, allowing other work to be done in PPro without the 2 "getting in each other's way".
    I'm happy with the rendering speed in PPro, and I see that hardware rendering is working there.
    If AME now makes use of the GPU while I'm doing other work in PPro, (like maybe "rendering the selection", or an entire sequence in PPro), does that affect the performance of either the file that AME is currently processing, or does it affect what I can do/performance I'll get while concurrently working in PPro?
    Are CUDA/GPU resources  "shared" between PPro and AME? Or, are the apps likely to "trip over each other"?
    If AME does, in fact, make use of the GPU, is there something other than the ".txt file hack" that I must do to enable the renderer in AME to use MPE hardware? As I type this I have AME working on a PPro sequence but I see that the "Renderer" is showing "Mercury Playback Engine Software Only".
    I feel like I'm missing some important tidbir of information, but I don't know what that is.
    What am I missing?

  • Adobe Media Encoder CS5 hangs when adding files of varying HD resolutions.

    I've seen questions similar to this related to CS4 but never explained very well, and my CS4 for mac worked fine.  I am unsure if this is a new problem or a windows specific problem but here is the situation, if you need more information I will gladly provide it.
    For the past week or so I have been encoding 1920x1080i mov files (h.264/aac) to 1280x720p (vp6/mp3) flvs.  When I stick to that single HD format in the AMC processing que everything works great. However, when I add older HD content into the AMC que, content with non-standard presets, the program hangs.  I tried to import about 15 files last night and the program just sat there all night in a '...NOT RESPONDING' state.  The video's have different audio and video settings and it's little difficult to pinpoint exactly what they were.  Some are 1440x1080, some are 1280x900, some have PCM audio some of mp3. 
    Now I temporarily resolved this issue by simply using cs4 master on my mac pro which worked great.  However I have noticed a huge speed increase in CS5 64bit AMC.  It takes 2-3 hours to encode 1 flash video on my mac pro (dual quad core xeon 2.9Ghz/32GB ram) with CS4.  It takes ~20 minutes on my windows 7 station (single core 2 quad 3Ghz/8GB ram) with CS5.
    How to replicate:
    If I drop a single file into the AMC CS5 que, regardless of the resolution, frame rate, or sound codec; it will import.  If I then add another file with a different resolution AMC will hang and become non-responsive.  It never crashed but I can't wait 12+ hours to see if it accepted a job or not.  As I said before this problem was not observed on CS4 for mac - it worked flawlessly, albeit a little slow. 
    Software used:
    Adobe Media Encoder CS5 windows 64bit
    Adobe Media Encoder CS4 mac 32bit
    System specs:
    Windows 7 home:
    Core 2 quad 3Ghz
    8GB ram
    80GB SSD x25-m
    nVidia Quadro 580
    OSX 10.6.3:
    Dual Xeon 2.99Ghz
    32GB ram
    4 7200 disks in 4TB raid 0
    Radeon HD 2600
    Matrox MAX h.264 compressor card
    Any advice on this situation would be greatly appreciated.  Thank you for your time
    -Michael Emanuel

    Hi Michael,
    Sorry to hear you're having problems with Adobe Media Encoder.  I'd like to get some more information about the problem so I can better understand your workflow, and potentially try to recreate the problem.  For what it's worth, I often import files of different resolutions without any problem, so I want to find out what's different about how you're using AME.
    Apologies for the long list of questions; the small details can be important.
    -- After you import the first file, what else do you do in AME?  Change the preset?  Change the settings?  Change the output destination?
    -- What are the properties of the files that are causing the problem?  You said it happens on "non-standard" files, but can you describe the specifications for one or more files that cause the problem?  Please include file type, length, frame rate, frame dimensions, field order (if applicable), alpha mode (if applicable), and audio type and rate.  If you know more the bitrate, both video and audio, that would be nice, too.
    -- If any of the files are small enough, could you post a couple online that I could try on my machine?
    -- How were these files generated?  What application created them?
    -- Where are the files stored? A local drive, a network drive, a removeable drive (USB or Firewire), etc.?
    -- Which Adobe application or suite do you have installed?  AME a limited set of options if you're using Flash or Web Premium compared to Master Collection, Production Premium, Premiere Pro, or After Effects.
    -=TimK
    -=Adobe Media Encoder QE

  • Adobe Media Encoder CS5 MAC Freezes

    Hi there,
    We all know that exporting files from Premier Pro into flv files (and some others takes some time).  An excellent way to work around this is to build up a queue of items in the Adobe Media Encoder. Then, you can run the queue when you are going to leave the computer for any length of time, say, overnight.
    I have Premier Pro CS5 and Media Encoder CS5 on a Mac and have just done all the various updates. Unfortunately, this does not solve my problem - if I have about 4 items in the queue, it works fine.  However, if I have, say 8 items in the queue, AME will freeze whilst working on about the 4th item.  This happens reasonably consistently and is very annoying - any suggestions how I can sort out this problem would be greatly appreciated.
    I am using a Macbook Pro with the i7 processor and 4 Gbyte of RAM, 7200 disk speed.
    Thanks in advance.

    Thank you ExactImage, if that is your real name.... I was able to reset AME 5.5 by holding down the Ctrl+Shift+Alt keys whilst starting the program. Your help is appreciated.

Maybe you are looking for