AME Rendering Slow

I have some 3D titles that I created in AE CC and I need them encoded as H.264 mp4 at 720x1280, which is not possible in AE anymore. AE will only let me encode an mp4 at 480x720, no matter the setting. I could just send to AME, however, it takes AME over an hour to render what AE renders in virtually ten minutes. I have matched the output settings exactly. I also have a Quadro K5000 GPU to speed up rendering but to no avail, in AME that is. Why is AME render time exponential compared to AE?

The AME will not use the GPU's Ray-traced rendering. You have two options, render to a production format to create a DI (digital Intermediate, my preferred method) then compress for delivery using AME or open your AE preferences and choose "Show Deprecated Formats in Output Module Settings" from the Output section of preferences, then render and live with single pass compression. It's better than it used to be but AME will give you a superior product for delivery.

Similar Messages

Premiere Pro 2014.1 rendering slower?

Is anyone else finding rendering slower with 2014.1? My hardware configuration (PC) used to render my sequences in about real time but now they're taking about 2X real time. I've got the same NVIDIA GPU I had before, have updated the drivers and PP says it will use it but I see no activity on it now. It's hard to compare because I can't go back to 2014. I get the same time whether I queue the render to AME or do it totally within PP. I'm tempted to go back to CC (pre-2014) and make some comparisons but haven't done it yet.

I gather that by "render" you mean exporting to encode an output file, yes? With Premiere, we generally reserve the term "render" specifically in reference to rendering preview files for smoother playback within Premiere; for creating an output file, we use the terms export and encode. I'm not saying "render" is incorrect--I know that's the common parlance with other NLEs. Just calling it out to help avoid confusion hereabouts.
As to the actual issue:
what format & preset (or custom settings) are you using?
Are you sure that all the export settings are the same as before? Any chance that before you were encoding VFR, One Pass but now it's Two Pass, for instance?
When you say "PP says it will use [the GPU]," do you mean that in the Project Settings panel, Renderer is set to GPU?
Exactly what graphics card do you have, and what driver version?
Is this a project created in a prior version and converted to 8.1? If so, can you toss together a simple sequence in a fresh 8.1 project and see if encode times are longer than expected?
If it's a new 8.1 project, are all the particulars of the sequence roughly the same: resolution of the source; sequence settings, including the Preview File Format/Codec; effects in use, ...?
As to the fact that the GPU shows no activity, that may be expected. In case you're not aware, the GPU is not used for all encoding. See this thread for more info: Mercury, CUDA, and what it all means. Of course, if we're dealing with a pretty clean apples:apples comparison and you checked GPU usage while encoding in prior versions, then you know for sure whether 2014.1 brought a change.

PP & AME Renders AE Clips Incorrectly

Hello, I've run into a problem I can't seem to resolve and think it may be a bug with AME or with QuickTime. I have a series of animated titles rendered from AE at sequence resolution in the Animation codec. When I bring them into PP and add them to my sequence they all play correctly. However, when I render the sequence, one of the transitions turns blue. The rest render correctly.
This occurs when rendering the sequence in the .Mov container format with the Animation, Motion JPEG, or ProRes 422 codecs, but not when I create an MP4 file through AME or use Dynamic link to send the sequence to Encore.
I've included screen grabs from QuickTime showing the original (warm sepia) version and the AME rendered version (blue).
I've encountered this problem on both a MacBook Pro (2.33 GHz Intel Core 2 Duo) running 10.6.5 and PP CS 5.5 and a Mac Pro tower 2 x 3.2 GHz Quad-Core Intel Zenon running 10.6.5 and CS 5.5.
Any help you can provide would be greatly appreciated.
Thanks,
Jay

Dennis,
Thanks for your advice. I've deleted the cache files, rendered everything in the work area and exported a couple of versions. The problem isn't resolved, but at least we have some more information to troubleshoot.
The timeline is built at 1024x768 30fps (primary output is digital projector). If I export the clip at 1280x720 the blue doesn't crop up. When I export at native size 1024x768, or half resolution 512x384, the blue appears.
Opening it in QuickTime 7 doesn't help any. I can see the blue clip in QTX, QT7, AME's preview window and in a H.264 version exported from Sorenson Squeeze 6.5.
In PPCS4, I had a similar problem with certain clips if Maximum Render Quality was checked. It doesn't seem to have a bearing on this clip as I get the blue shift with and without Maximum Render Quality Checked.
What's really puzzling to me is that the four transition segments (three of which render correctly) are generated from the same AE comp. I simply turn on and off the necessary layers and render the segment I need. If it was a problem with the AE comp or project, I would think the problem would occur consistently between all four clips.
Lastly, the clip previews correctly in the PP timeline.
What do you suggest as a next step? In the meantime, I'm going to try and replace the affected clip with a direct link to the AE comp and see if that helps.
Best regards,
Jay

Premiere CS4 - Encoding with AME ridiculously slow

Hello there.
After having read many threads on various forums, I have not come to a single hint as to why AME is encoding any type of video materal extremely slow. I'm sorry if this question has been asked many times on this forum, but maybe someone has come up with a working solution?
My computer specifications are:
Windows Vista 32bit (yes I know, upgrade is needed)
Intel Quad Core Q9000 @ 2 GHz
4 GB RAM
Nvidia GeForce 9700M GT - 512mb
500GB sATA HDD @ 5400 rpm
This is a notebook. I use Premiere CS4 and AME4 with the most current updates (v4.1)
Here is what I usually do:
I export my project media from Premier to AME with the appropriate format and encoder settings, close Premiere and kill all background tasks. My RAM usage is now at around 1.4 GB (out of 3 GB!).
In this case, I'd use the built-in MPEG2 codec with PAL settings (720x576 - 25i - 8Mbit/sec), the source file is in MPEG4 @ 20Mbit and 10 minutes long. I started the encoding process and it was slowing down from 10 minutes initially to a frustrating render time of 60 minutes. Why?
I have used VirtualDub and TMPGEnc, both achieved, compared to AME, incredibly low render times, a bit higher than double realtime. When I use AME the same way, as encoder for an avi file only and not a Premiere project, it is losing by 6-7 times of the other programs render time.
Second scenario:
I have 20 seconds uncompressed avi material (600Mbit/sec) and like to convert it to MPEG4 with AME. MPEG4 settings are at 50Mbit, I-frames only, 50fps and progressive. I started the encoding again and at first, AME was rushing through 1/4th of the progress bar in 5 seconds, and then slowing down to an overall encoding time of 50 (!) minutes and it ended about 52 minutes later.
During this rendering I had the windows resourcemonitor (of the taskmanager) open and checked the access rate to my hard disk. For the entire duration of 50 minutes, AME read between 50 megabyte and 125 megabyte per second on the hard disk. The file itself was less than 2 GB large - what on earth could it read? Also, my RAM usage came close to 2,8 GB but never reached 3 GB or higher.
Does anyone have an idea or is it just that freeware programs are superior to a costly AME?

I have already run that test about 4 hours prior to writing this thread. Now I'm not at this computer, but from top of my head the results were:
Total 180 (about)
Export Avi 38 (not entirely certain, could be up to 10 higher)
Encode MPEG 90 (not entirely certain, could be 20 lower or higher)
Render Time 7 (the only number I recall correctly)
I'm well aware my hard disk isn't fast - but why should VirtualDub be able to encode a 2gb uncompressed avi clip with a duration of 20 seconds to DivX in about a 1/3rd real time/8fps (using 50mbit, i-frames and 50fps and amazing quality) while AME takes 50 minutes (1/200th realtime) for the same file with the integrated MPEG4 encoder?
Now, I know that those are different codecs, yet their data reduction works on a similar base. From my point of view, there's not much that could explain such a high discrepancy of performance on the hardware side, other than AME just does not like my computer configuration. I know my computer is very capable to perform way better than that, just with about any other program but AME, and that is a royal pain.
Unfortunately, I am unable to install a second HDD in this notebook, because it is full. I do know it could perform better using a secondary HDD, but I have also encoded files with Adobe Premiere CS3, and that performed way better than CS4 on the same computer.

AME rendered files are bigger than in Premiere CS6

Hi!
I have a big project - 6 hours prepared for rendering in 4 sequences (each sequence is about 1h 30 minutes - 1h 45 minutes) I try to export them with H.264 - Blu ray default settings. Estimated file size for each sequence is about 17 - 20 GB, but when I export them into AME I got files 52 - 55 GB ! When I export same sequences one by one directly from Premiere CS6 I got 17 - 20 GB files. What's wrong with AME? Same input, same settings but files are more than duble sized?!
Thx!

Here are the screenshots of all export settings related to one of these projects. As you can see estimated file size is 16321 MB and when I click on "export", rendering is about 15% faster and file is about 17 GB. But when I click on "queue" rendering is slower and files are about 52 GB

ImageIO image renders slow in scroll pane

Hello all, I need some help understanding the behavior of BufferedImage(s)
retrieved from ImageIO.read(). The problem I am having is weird .. I load
a PNG image via ImageIO.read(), I use it to construct an ImageIcon which
is later used in a JLabel/JScrollPane for rendering. When I attempt
to scroll the image in the scroll pane, it is very chunky and slow.
If I load the same image with ImageIcon(byte[]), there is no problem. The
image on disk is 186k, when loaded from ImageIcon(), it consumes about
10M, when loaded with ImageIO about 5M is consumed ... when I scroll,
the memory usage increase about 9 MB, which can be collected immediatly
to return to 5M.
Is ImageIO doing some fancy optimization to preserve memory, if so ... how
can I alter the settings or turn it off completly. I tried setting
ImageIO.setUseCache(false); that did nothing as far as I can tell.
The code to load the image is as follows, I am just using the default right now.
      // perform base64 decoding from buffer
      ByteArrayInputStream bos = new ByteArrayInputStream(decoded);
      try
         image = ImageIO.read(bos);
      catch (IOException ioe)
      }Any help would be greatly appreciated!!!
Cheers,
Jody

I'm not sure if this is exactly what you are looking for but, here's code that works well for me:
private class MyJLabel extends JLabel {
    public void paintComponent(Graphics g) {
      super.paintComponent(g);
      Graphics2D g2d = (Graphics2D)g;
      URL imageLocation = MyJPanel.class.getResource("myImage.jpg");
      Image myImage = Toolkit.getDefaultToolkit().getImage (imageLocation);
      MediaTracker tracker = new MediaTracker (this);
      tracker.addImage(myImage, 0);
      try { tracker.waitForID(0); } catch (InterruptedException exception) { System.out.println("Image myImage.jpg wasn't loaded!"); }
      g2d.drawImage(myImage, 0, 0, getWidth(), getHeight, this);
}Once I reload images using the above method, image repainting is very quick. Extend the JLabel (MyJLabel) to overwrite the paint method as above. Should work fast when you do so. You can move the image retrieving code out of the paint method and into the 'MyJLabel' constructor.
How are you painting the icon and where are you retrieving the image? Can you post more code?
Regards,
Devyn

Swing app in JDK6 continues to rendering slow in Windows Terminal Server

Hi,
Because Swing apps create interfaces internally and not using default OS APIs,
when running into a Windows Terminal Server client, there is no way to optimize
rendering. Windows Terminal Server and Linux FreeNX use a mechanism to send
to client only commands to render the windows. But, because the way Swing works,
not totally integrated to OS APIs, it's not possible for terminal servers to do this,
and these servers render Swing like images, something like VNC do, very slower than.
I have tested native apps and AWT apps, and the difference is very significant,
something like 50-70% faster.
Is there some project in Swing APIs or java.net open-sources to better this?

We are also seeing this issue with a Compiere implementation. With 10 distributed sites across the US, our client wanted to use Windows Terminal Services to simplify the client desktop management of the Swing application.
But performance is terrible...and screen painting issues a real problem. We are also on JDK5 still, so I'm discouraged to see that JDK6 doesn't appear to offer much improvement?
Is there any project afoot to address this issue for installations using terminal services?
Thanks,
Peter

Rendering slowed to a grinding halt CS6 on brand new mac pro...

Unbelievably and excruciatingly painful slow rendering in AE CS6 on a brand new Mac Pro.
My Pro:
3.5 Ghz 6-core Intel Xeon E5
32 GB 1867 MHz DDR3 ECC
AMD FirePro D700 6144MB
OSX 10.9.2
1) Internal 500GB SSD - (using 90gb for AE media cache)
External Thunderbolt drives:
2) 2 TB WD Black Caviar - (hosting all project assets)
3) 2 TB WD Black Caviar - (rendering destination)
Running After Effects CS6
The footage in my comp is just a bunch of illustrator files, and shape layers. There are 2 videos, but removing them does not improve the rendering. All the illustrator files are RGB. I am using effects on layers, but nothing out of the ordinary, a few displacement maps, some grain (non animated), some distort mesh (pre-rendering the distort mesh helped a little, but pretty sure there is something REALLY wrong here)
When its rendering, and I look at Activity Monitor, 85% of the CPU is still idle! I'm using Rendering Multiple Frames... 6 Cores for AE - 4 for others. 3GB for AE.
Of the 32gb RAM saving 4 for others applications.
For 25 seconds of footage, the task bar says something like 6 hours to render... and then it doesn't even finish. Even pre-rendering the distort mesh in a 4 layer pre-comp, for 25 seconds, took 25 minutes.
Someone please help, I'm not sure whats going on, but something is horribly wrong.

Not new to AE. Was rendering with animation codec, and have also tried using pro res 4444 to see if it will help.
comp size 1920 x 1080 @ 60fps
Turned off RMFS - and while this helps with the RAM preview (also setting the RAM preview to skip 1)
I was able to render using pro res 4444 @ 50% resolution @ 50% frame rate @ draft quality in 11 min (25 seconds) after pre-rendering 2 pre-comps.
Which is much better, but really don't understand why it could be taking so long.
I want to be able to RAM preview @ 60 fps - but every time RMFS is turned on it throws errors like "AE needs 2 or more playback frames" and I've also seen the error about it skipping frames and to allocate more memory to background processes. But no other programs running...
And I made a mistake: 12 cores, 8 for AE and 4 for other apps is what I had RMFS set to.

Library Preview Rendering Slow

I'm sure I'm missing something here and am hoping someone can point me in the right direction. I just purchased lightroom 2.3 primarily as a workflow tool for the RAW photos I take at sports events. The first step in my process is to review all the photos and remove the ones with poor composition and ones that are out of focus so that I don't spend time cleaning them up before I do any cropping.
My problem is that the rendering of the preview thumbnails seems to take an inordinate amount of time before I can see the thumbnail in enough quality to make a decision on the focus quality. I opted to invest the time up front and generate 1:1 previews during the import process. I've got the thumbnails sized to display two thumbnails with the sidepanels hidden to use as much realestate as possible. However, when I move from thumbnail row to thumbnail row, at least one of the thumbnails is initially displayed in a blurry format and takes approximately 2 - 4 seconds to display in it's final state.
Considering I have 353 photos to review, I'm looking at sitting 17 minutes total just waiting on the final rendering of thumbnails to decide on whether they're in focus or not. This just doesn't seem right if I selected to pre-generate 1:1 previews. So I've got to have something set wrong somewhere. Any ideas or direction would be greatly appreciated!
Dale

Thanks all for your thoughts and ideas. It looks like I'll just have to live with the multiple pass slow rendering in Lightroom if I want to continue to use it. I ran a test with the same batch of photos in Capture One LE, the product I intended to replace with Lightroom. Once the folder and photos were imported into Capture One and thumbs rendered for the first time, moving from one large size representation of a photo to the next (there's no "library" module, it looks more like the LR Develop module and all work is done from there) took significantly less time than in Lightroom (less than 1 second).
Some other notes from the comments above:
- yes, I was using very large thumbnails to scan through the 300+ photos and filter out the bad ones and yes it requires me to do a lot more scrolling. Annoying, but necessary for me. One of the more difficult things for me to do is determine if a shot was in focus or not. This decision requires a large thumbnail for my old eyes ;-)
- I have 100Gb free on my catalog drive and 200Gb free on my data drive. I can't imagine Lightroom would require any more to render thumbnails and display photos in the develop module more quickly.
Thanks again everyone!

Exporting to mpeg WITHOUT rendering Slow MOtion Effects -Any loophole ???

I have made 2 clips in my timeline slow motion - 20%. In preview
mode when I play back in my timeline the effect looks slow and image
looks great. As soon as I render it - the images become in and out of focus
and looks crummy.
Is there any way for me to export and keep this portion in preview mode
(so it does not render) ? It just looks much better when its not fully rendered...
any loophole to this?

Maybe.
Probably the reason you're getting the effect you're seeing in preview is that Motion is dropping frames to do RT. If you ctrl-click on your sequence and select "Settings...", go to the Render Control tab, and set Frame Rate: to say 50% of Sequence Editing Timebase, that might help you...
Patrick

Source and Program preview look good, AME renders linked aftereffects very poor

I have searched high and low but cant figure this out:
I have CS4 Master Suite installed on HPZ600 workstation Windows 7 Enterprise 64bit
Intel(R) Xeon(R) CPU X5550 @ 2.67GHz, 2661 Mhz, 4 Core(s), 4 Logical 6GB ram.
I created a 720p PremierPro (PP) sequence. I added a “Black Video” then rightClick- replaced it with an aftereffects (AE) comp. I added several screen captures to the AE file and animated a few graphics over the images. When I jump back into PP the source preview (linked Comp) looks great, the Program preview looks good and when I Export media the 1st preview (still in PP) looks good. Once it opens in Adobe Media Encoder the quality (mostly text on white background) looks terrible.
I have tried endless combinations of settings and options with no luck. I render out the AE file and it looks great. Import it into PP, looks great. Send it to AME, looks like poop. If I take the images (used in AE) and import them directly into PP I get a good export in AME but I need them in AF to animate.
If anyone has any info that might help I would be greatly appreciative.
Thanks

No, but that does seem to be a good indicator. When the preview (AME) is bad, the rendered video comes out bad. When it is good, the video comes out good. I just rendered this. The preview showed about 1 second of good quality and then the busted look (with linked AE only, video was good). This is a 1280 x 720 png in AE with no animation or effects.
The linked AE is video2 in PP on top of 720p video in video1. If I create a new sequence and place (copy/paste from the old one) the linked AE alone it previews and renders great. Once I add the video (AE fades in over the video) and have 2 720p elements, the AE will randomly look bad.
Do you think it could be a RAM issue?
Here is an example: This is a rendered WMV about 20 seconds in.
Here is the same WMV 21 seconds in. It is the same image in AE. This quality shift was also identical in the AME window.
thank you for your time and info, I appreciate it.

AME rendering outdated AE content

It appears that AME CC (7.1.0.174) will render dynamic-link content in whatever state it was in when it was opened. Example:
I have a Premiere project that has a text card that is dynamically linked from AE. If I open AME, then hide the text in the AE project and save it and render out the sequence from Premiere the text will render (even though its now hidden). So even though the text is hidden in AE and in the Premiere project, it will still appear in the final render when exported from Premiere to AME.
So the only current work around I've found is that if you make a change in an dynamic linked project, you always have to restart AME to have the changes take effect in the final output.
Is there a solution where AME isn't 'caching' this content?

The AME will not use the GPU's Ray-traced rendering. You have two options, render to a production format to create a DI (digital Intermediate, my preferred method) then compress for delivery using AME or open your AE preferences and choose "Show Deprecated Formats in Output Module Settings" from the Output section of preferences, then render and live with single pass compression. It's better than it used to be but AME will give you a superior product for delivery.

Premiere CS5 AME Export slower than direct export?

Hello everyone,
I am testing premiere cs5 premium, and having some issues with AME export render times.
When I export media to AME it shows about 6hours to render a sequence which is 15min long.
Export settings :
H.264 1280x720 25fps
VBR, 2-Pass, Progressive
Target 8Mbps
Max 10Mbps
Input Squence is directly from AVCHD handycam with native settings no resizing but some simple color correction
However when I do the same export directly from Premiere Pro the render time drops to 38mins (which is btw also not so optimal)
My Hardware Specs:
Intel Core2Quad @ 2,40Ghz
Ram : 8GB (premiere uses 6GB)
Scratchdisk: non raid 1TB with 130Mbps average read/write
(Raw Files on Scratchdisk)
I used to export similar sequences alot faster with cs4 on the same machine..
What could cause this problem?
Thank you in advance for your answers

Thank you for your quick reply, but It couldnt solve the issue..
Harm Millaard wrote:
First of all, the remaining time indication in AME is not very accurate.
well thats also my experience, but after waiting over an hour, it was still below 25% on the scale.. so I paused and switched to direct export
Harm Millaard wrote:
Most of the time and especially with H.264 exports, there is no significant difference between direct export and AME.
Obviously in this case "most of the time" wont apply.. because I did export it directly from within Premiere 6 times faster..
There must be a problem somewhere between AME and PremierePro during reading the squence and rendering it.
Hardware Accelaration is turned on, and I have a supported Cuda Card

Text rendering slow

Using FCP X I am manually adding open subtitles, my sequences are short, but typing the text is taking ages to render and the typing speed is less than a character per second! I am using a 2x 2.66 6 core Mac Pro with 20GB RAM.

I have not had that particular problem, but certainly rendering of titles is slow. For instance, add a comma to a 45 second rolling credit and it takes 45 seconds to re-render (and you can't work while it is doing it, allegedly in 'background').
There are other problems with text and titles, all of which seem very flaky. One real problem is that when I come back to a re-edit a project that has already been successfully exported (sorry 'shared') I find that several of the titles have disappeared and been replaced by the place-holder 'Title'. It then seems difficult to put the original text back.
Titling effects also suffer from difficulty. Sometimes the build-in, build-out options for a fading title simply refuse to appear in the Inspector.
If you have two overlapping titles in two timelines, soloing one does not remove or obscure the other, so it can be difficult to see which title you are working on.
If you follow a letter-by-letter build-out with a cross dissolve, the last two letters can, randomly, 'jam' on and not fade.
Has anyone else experienced any of this?
MacPro 2.93GHz 12 Core, 6GB RAM ATI Radeon 5770, Snow Leopard 10.6.8.

AME hangs, slow - watch folders on NAS

Hi forum,
I love my AME CS6, when it works, but I've had anguish with some (possibly) related problems:
1) verry sllow output of .mov file (NTSC SD, h264)
2) constant hangs resulting from any interaction with the application (spending a lot of time looking at "Adobe Media Encoder (not responding)" at the top of the application window. These hangs usually don't cause a crash, but the waiting (usually 5-25 seconds) is agony, especially when a large batch of work is in queue. (The only time AME ever hangs on startup for me is when the mac is actually exporting into the watch folder, in which case the startup splash text says it is trying to load the file [which is at that moment incomplete] and so it sits there and hangs - this is probably not related to my core problem.)
Some details about my system:
1) AME (CS6) is hosted on a Win7 system on a Dell with Xeon quad 3.07Ghz, and Nvidia quadro 2000 grafx card, and 6Gb of RAM.
2) I am using watch folders that reside on a NAS connected by a gigabit switch
3) some files being contributed to the watch folders are coming from a Mac (usually 1080p prores 422) but most are coming from the local windows machine (some SD NTSC .AVI, some MPEG all-I - I generally queue finished shows to AME using the "same settings as sequence" checkbox from PrPro the file->export->media dialog
So my questions, based on my guesses as to what is going on:
1) Is the Adobe Quicktime plugin/manager to blame? How can I know, and what could I do to troubleshoot?
(observation: watch folder A includes 2 h264 outputs - one is .mov and the other is .mp4. When processing a master file from premiere, the .mp4 rips fast and the .mov chuggs [ratio of export time : run time is ~0.3:1 for the .mp4 and ~4:1 for the .mov - a huuuuge difference]. HOWEVER, when the file in process is a prores from the Mac [presumably need ing quicktime for all operations] BOTH the .mp4 and the .mov are pathologically slow to encode)
2) Is it possible that I need to modify some network setting/configuration? I am totally a noob at this skillset, and I work for a City Government where the IT guys dont really know how to give me what I need for the work I do - so can anyone suggest key words and concerns I can be asking about/checking on with regard to how I connect to my NAS and how their network policies might be affecting my traffic to those watch folders?
3) Is it possible that there is some registry conflict on my Win7 system? I did briefly load a demo of AVID media composer, and someone told me that this can create problems due to registry entries associated with both applications - would I need to completely reimage/rebuild my dell or is there some way to reset these associations? Is there some way to trouble-shoot/eliminate this as a potential cause to my problem?
Thanks in advance!
Eric D
production coordinator - CoralVision

Well guys, I checked up on the hyperthreading on this system - it was already disabled. Following the instructions on the page Todd links to above I found that the highest number of processors available on that "limit to" list is 4 - far below the 21 it says is the threshhold for trouble with QT server. For today I have enabled hyperthreading and enable the limit of processors to 4. and I will see how she performs.
Another Adobe staff (Tariq from chat support) member has suggested that the problem may originate in the way my user profile is configured, and suggested I try running AME as ADMIN from my current profile. When I did, AME could not find/connect to the NAS volumes where my watch folders live, and I ran out of time to test this option using manually loaded (non-watch folder) .mov encodes.
Also, another observation: at one moment (before changing anything) I opened AME and opened one of my .mov presets to change a setting (to disable the scripted FTP, which is also malfunctioning) and on OK-ing out of that dialog, AME froze and did not recover. I forced a quit, then reopened AME, and I discovered that just accessing that preset causes a permanent freeze every time - I don't have to change any settings in order to reproduce the fail (NOTE: despite the immediate fail, AME remembered the setting change). This speaks to Mitch's last statement above ("If the hanging is happening when exporting as H.264 compressed .MOV files...") - well, yes and no: The hang/freeze usually happens anytime I am manipulating the queue (adding/removing/reordering) or changing presets, whether I am encoding or not, and seems worse when there are .mov settings involved. My intuition is telling me that something is not working right in the way that AME interacts with those .xmp files it uses in the watch folders to track files in process.
At any rate, I appreciate your time and consideration of my problem. I will be grinding along with the current issues unresolved, as I have deadlines looming, and I will update this thread as new information emerges. Let me just say, however, that despite these issues, CS6 still seems to be best in class and best value for me and my operation.

AME Rendering Slow

Similar Messages

Maybe you are looking for