replaced the 2x1gb with 2x2gb.

Thanks so much, this is HUGE help. I hate being a dummy.

My video project involves five separate outputted MPG files - it's going to be show as five sync-ed videos. All five are very similar - one main track, with several additional tracks for the extra screens.

After editing, I've been trying to line up all five versions on AME. I'll just do one at a time.

The times with my renders the only still layers I had was PSD layers the size of the screen (1920x1080), and it would hang in AME in the middle of encoding sequences, not at the end.

Mark, this is EXACTLY what's going on in my case!

In my case I was queing up duplicates of the exact same sequence (titles, with the same background images but different PNG text tracks) and AME would run two sequences just fine and choke on the third sequence every single time. I had 16 different variations and no matter which I started with it would lock up at the start of the third sequence of the queue.

These sequences are 14 seconds long, 1920x1080p, but I was using a moving background track that was a 2324x1307 JPG file.

Turning off MPE and they queued up just fine (but oh so slow!).

Replacing the 2324x1307 JPG background image with the same (still moving) image at 1920x1080 and the queue worked just fine!

(of course there is a slight quality difference because I had a slight scale/zoom-in on the background image, but changing that image to a 1920x1080 image and no issues at all!).

If you need my system specs, please let me know. I've had this problem ongoing for six months but never tracked it down because it didn't always happen. I just got in the habit of only queing two sequences at a time.

In my case it is definitely the use of a scaling JPG that was larger than 1920x1080 that is causing the freeze.

Hi,

I just want to report that I am also experiencing random, intermittent freezing issues when exporting a sequence to queue up in AME CS5.5. I initially had CUDA GPU acceleration turned on.  I've been trying to encode for the last three days. More than half of my files have successfully encoded. However, lately, I've noticed that the freezing has become more frequent, to the point that I'm tired of restarting the queue and getting fed up. I will now try encoding the remainder of my sequences with GPU acceleration turned off. I hope that works.

FYI, here's my info when I was trying to encode with GPU acceleration on:

Video recording device: Canon HV20

Video recording mode: HDV 1080/60i (1920x1080)

Audio recoding mode: 2 channel, 384kbps, 48 kHz

Video capture software: HDVSplit 0.77 beta

Video clip captured files: AVCHD Video, m2t files

Sequence info: 29.97 fps, 1920x1080, 48khz stero,

Sequence lengths: between 14 and 37 mins

Sequence video layers: only one (imported video clips)

Sequence effects: Cross fade only between clips, no other effects or filters

Export settings:

   Multiplexer: MP4, iPod compatibilty

   NTSC: 1280x720, 29.97 fps, de-interlaced

   AAC: 64 kbps, 48Hz, Stero

   VBR: 2Pass, Target 5.00, Max 7.00 Mbps

   Use maximum render quality checked, Use Frame Blending checked

   Filters: none

CPU temperature: about 50.0 degs C

GPU temperature: about 51.0 - 53.0 degs C

Software: Adobe Premiere Pro Version 5.5.2

Software: Adobe Media Encoder Version 5.5.1.12 (64-bit)

System OS: Windows 7 Ultimate SP1, 64-bit

System Processor: : Intel Core i7-3930K CPU @ 3.2Ghz

Installed RAM: 16.0 GB (Corsair CMT16GX3M4X2133C9 DDR3 PC3-17066 2133MHz)

Graphics Card: EVGA GeForce GTX 580 3072 MB GDDR5

Graphics Driver: Version 296.10, (Graphics clock 772 MHz, Processor clock 1544 Mhz)

Graphics BIOS version: 70.10.48.00.82

Motherboard: Asus P9X79 Deluxe

I hope you guys are able to find the problem. The whole reason why I bought the GTX 580 was for the CUDA acceleration, and now its worthless.

--Peter

Hi, Paul.

Thanks for the tips. I did as you suggested and just ran the render manually for each sequence out of Premiere, rather than queuing up in AME. I did this for five sequences without any problems, with GPU acceleration turned on.

I then turned GPU acceleration off and ran the remaining four sequences by queuing up in AME. I let the queue render overnight. They all rendered without problems.

The GPU acceleration made rendering dramatically faster. A clip which would take about 2 hours 20 mins to render with GPU acceleration off took about 12 mins to render with GPU acceleration on.

I did not backdate the graphics card driver.

Hi,

This had been plaguing me for months. Down-sampling super HD stills in my project has resolved this issue for me.

I had several images (over 4k across) that I was using as slide overlays and AME would hang on exporting just one of these (not even multiple copies) using CUDA acceleration on my Dell Precision laptop with an Nvidia Quadro FX 3800M graphics card. I would also get Nvidia messages that my hardware wasn't good enough (Premiere Pro 5.5 would then crash) while I was editing these stills in the timeline - e.g. putting fade transitions onto them.

Changing the stills to be 1920 x 1080 last night has fixed both the export problem and the editing crashes and AME got to the end of the export no problem.

Hope that helps.

Kaleel

Have you tried exporting straight from PP?  I gave up on AME a long time ago.  All my exports from PP work just fine.

I've solved this problem for my system and it was easy.

I'm embarrassed to admit that I was cheating the system using a non-approved EVGA GTX550Ti and editing the approved list from a posting I had found on the internet.  Most of the time, everything worked well and the Mercury Render Engine raced through stuff.  On the more complex projects or with big stills, Premiere might occasionally crash and then on a couple projects, Media Encoder would just stop at random and couldn't get through the project.

This past week i had an issue on a fairly complex project and decided that the issue was costing me money, so i went out and bought a new EVGA GTX580 with 3 GB video ram.  The same project breezed through with no issues and as hard as we have tried, we can't even make problems any more.

I've learned that the Adobe and Nvidia experts may still be the real experts out there and I should just listen to them.  I paid a lot more in lost time and problems than I would have if I'd have just bought the right card in the first place.  I hope this same solution works for everyone.

Oversize stills have bothered Premiere Pro for me for years, way before Mercury.  Sorry to hear you have problem with approved card.

I can say my Asus notebook i finally had to give up on.  Its Nvidia graphics card always overheated and reset, and Agearnotebooks said there was nothing wrong with it.  Now i use a Macbook Pro 17 with Windows 7.  I'm not impressed with MacOSx - it's like working with handcuffs for an old-fashioned Unix/Pc guy.  My next notebook will be a real PC again with Nvidia and i hope it works right.

I do have quite a few stills but it doesn't freeze on a section with stills. Trying an export directly from PP now. I want to hand this baby over to someone else. Frustrated, tired.

@nreedus: When it's stills that cause my issues it doesn't freeze in the section with the stills, it just locks up at some point, usually not related to where the stills are in the sequence. Resizing the stills down to 1080 (or close) always fixes the issue for me. (I have 16GB of RAM and an approved nVidia card and still have issues if my stills are too big.)

Any beta testers of CS6 know if the new AME fixes the large stills issues?

That may reproduce the bug many of the reported cases, but in my case I had no stills whatsoever in any of my sequences. (See my post March 26, 2012).

I think you should be ok if you turn mercury render engine off.  It will be a lot slower, but should get through it I think.

I have a Nidia GTX 280 which is not supported.
I dont even get the choice to  enable GPU support.
It must be turned off by default..

Richard Fendelman:
I am not sure what you mean.

If you import stills via the menu and import, you can click on the first still in a folder and click on "continous file number" or so,

then all the still are being imported as one element, each still being 1 frame.
I contacted you via private message to not spam this topic here.

Message was edited by: staheph1

I am working off a SSD Drive, project data and everything is on there.

The slower cpu and no gpu support MUST NOT make the program

stop rendering, maybe go slower but not "freeze" like that.
I have a 7.3 Windowsrating (that doesn't say much I know), but at

least it should make PP run stable.

Hi Mark. I've just finished reading a lot of the posts on this forum and have been having similar problems with my system. Could you please let me know if there is a fix for this problem?

Thank you.

hi Kent. Thanks for getting back to me. I will definitel go through and test that which you've suggested. What if I don't have CS6 yet? I won't be getting CS6 for another 3 months. Is there another way around that?

Also, here are some screen shots of my hardware...

Hi Kent. Sorry. Premiere CS5.5

Hi Kent. I did some tests with exporting directly from Premiere(without opening AME) and it worked. I've just finished building my raid 5 and copying some files accross. I will try encoding with AME with Premiere still open in the background. I hope it works. :-)