Participating Frequently

Question

Media Encoder Stops Encoding with the New CS5.5

Forum|Forum|14 years ago
May 24, 2011
31 replies
89363 views

I just upgraded to CS5.5 a yesterday and having some issues encoding an 1 1/2 program for a DVD. The program doesn't seem to crash per se, just stops encoding. The task manager says it's running. I tried to encode the same sequence, but shorter and have the in and out points go through the part where it always stops and it worked fine. It's just when I try the entire sequence it stops. Anyone have any experience like this with CS5.5 just coming out?

Thank you,

Doug

This topic has been closed for replies.

Show previous replies

N

nreedus

Participating Frequently

We're all in the same boat. Export freezes. Closed out PP5.5. Trying AME. We'll see. Leaving Wed. to present film at conference on Thursday. Do or die.

L

Louis_fre

Participating Frequently

I wish you well!

Started using a trial version of Vegas out of frustration, it now uses the GPU as well, seems easy and stable. we'll see

Z

zikade

Participant

Any news about it, epecially from those who joined the pre-release team?

Just yesterday I had to encode my current project, took 7 hours. But then, 7 hours is definately a night render job, so at least I am in no hurry...

____________

OK, just tried something else - I removed my Blackmagic HD card since I had a gut feeling that it hangs somewhere there. Upon the first try with 6 Videos it worked well. Becoming euphoric, I tried it a second time and it failed at a somewhat significant position: right where the clip ends and the closing animation starts. Most of the footage for the video came from a P2-Card (DVCPROHD), while the closing animation is either a Quicktime using the Animation Codec or an uncompressed AVI. For a change, I even got an error Message:

Message was edited by: zikade

_______________________

3rd try:

I have arrived at a complete new level of puzzlement. A sequence which AME did render well on Windows get some interesting effects on my Mac like this:

This part should look a bit different, trust me on that. The source is an ProRes422 movie, for some reason it's 960x720 with aspect ration of 1,333. So I created a new sequence having just this part in it, chose ProRes 422, 1280x720 square, replaced it in the sequence and it rendered just fine. Which is kind of odd, since the sequence has the settings 960x720 aspect ratio 1,333. Whats even funnier, on Windows I do not have that problem. There it gets interpreted correctly. All of that, and Playback in PPro is just fine, regardless of the OS or the spatial resolution of just that clip. Somebody can enlighten me why that is happening? I do guess that AME does have some problems with different Codecs and/or resolutions in a sequence - even more if both is different - which it shouldn't..

Message was edited by: zikade

W

water bowl

Participating Frequently

I am considering upgrading from CS5 Web to CS5.5 Web since there is a 30% discount until the end of the month. Would this problem many of you are having be a reason to avoid this upgrade, in your opinion? Or is this just a small bump in the whole package? I don't own Premiere Pro so I can't use the work around some of you are using.

Thanks

D

DirtyLowPull

Participating Frequently

it won't affect you if you don't use AME in your workflow.

R

RobertJB3

Participant

This is a seriously annoying problem...it's now effecting my shorter sequences. What could possibly cause AME to just stop encoding? with no errors or anything? The problem seems to go away after a restart but it shortly returns...

P

Pedaling Duo Productions

Participating Frequently

I am going to try wiping the OS tonight and starting from square 1. Again I am using CS4 with the latest updates and I am having this issue. I considered upgrading to CS5.5 to solve this but now I am glad that I did not spend the money.

L

Louis_fre

Participating Frequently

Good luck!

Sent from DisKreet Digital iPhone

R

RobertJB3

Participant

I had this same problem it was very infuriating to buy such expensive software only to have it not work randomly. I seemed to have fixed it somehow though, I turned off all of my firewalls and now I have no problems what so ever with encoding.

P

Pedaling Duo Productions

Participating Frequently

I ended up having to encode my sequences with After Effects. That seemed to work. I am going to wipe everything and do a new install of the operating system and the programs. I do not know what precipitated this problem. I did not have this trouble in the past.

M

miketrobo

Participant

Hi I have had the same problem I found I got rid of it by changing the graphics card and loading the latest drivers. I think its a grahics memory issue. My propblems started when I did a load of updates and even after rolling everything back it still did not go away. I know some find not queueuing the render gets them through with out it stopping.

J

Jason_Urbanski

Participant

Hey guys, any update on this subject? would be nice to shed some light on this issue.

Cheers Jason.

N

Neverends ProductionsAuthor

Participating Frequently

Here is the latest from Adobe and my response:

Hi Doug,

I'm writing to let you know that we're closing Case 182349424. The specific behavior that you've reported has been logged as a bug. There is a workaround, which is to disable GPU hardware acceleration in Premiere before rendering. We are investigating the root cause of this issue, but we do not provide specific notification when/if updates may become available to address the issue.

The members of the engineering team responsible for investigating this issue have been in contact via the forum (http://forums.adobe.com/thread/856263?tstart=0) and are providing additional information when available. There is nothing further that we can do from the tech support side, so as a matter of procedure we're closing the case. If I receive any new specific information on this issue, I'll send along an update.

Best regards,

Chad Baker

Tier 3 Technical Support, Adobe Pro Video

############################################################################################################################

Chad,

Your solution is not a very good one. It is like being a runner on a track team and you have a broken leg. Rendering the amount of projects I render with the MPE disabled is too time consuming and as a business owner, cuts into all the other tasks I have to manage. If you look at the forum, I’m the one who started it back on May 24^th, 2011 and I am not the only one having these issues. How long is this going to take? I will give you every file I have to help resolve this issue.

My confidence is very low with Adobe. Maybe I should switch to Final Cut Pro.

Very frustrated customer,

Doug Ferguson

Neverends Productions

Chad Baker

Adobe Employee

How long is this going to take?

I don't have any information on when this issue might be resolved, nor could I comment publicly about future releases if I did have that information. The best information that I have is included in Nariman's post above (http://forums.adobe.com/message/3991802#3991802).

I will give you every file I have to help resolve this issue.

Please see Nariman's response above if you would be interested in helping us investigate a fix.

I understand your objection to the workaround provided, and would gladly provide a better solution if one were available, but that's the extent of what we can do on the Support side at present.

F

FSMedia

Participating Frequently

Just a reminder of the important central fact to help prevent endless speculation and wild goose chases: My original problem with AME, and that of many others as well, started solely and immediately with the upgrade from CS Production Premium 5.0 to version 5.5. A single variable change. No concomitant change in hardware or drivers or configurations or any other variable. 5.0 worked, 5.5 didn't. This occurred immediately after the upgrade. Updating NVIDIA card drivers or any of the other list of routine things Adobe customer support sent did not solve the problem or improve the situation. Again, it was clearly something that changed in the code from 5.0 to 5.5. I would switch back to 5.0 except that projects once opened and edited in 5.5 are not backward compatible. So either I lose months of work, or I have to contend with AME 5.5's problems. The only workaround I've found is to switch from hardware to software GPU in PPro. That usually, but doesn't always work, and doubles or triples the render time. That's better than losing months of work, so I will have to contend with it.

Again, from the very start I read up on Adobe's hardware recommendations very carefully for what works best with the Adobe Production suite and built my system specifically for that purpose and nothing else: i7-980X chip, Quadro FX4800 card, 24 GB RAM, high speed HDs including SSD for the system. Nothing else installed but Adobe software and Microsoft Win7 64-bit OS. System works like a dream for everything else, can even render RED footage real time on the fly. Definitely NOT a hardware deficiency and NOT a driver deficiency, and NOT overheating or dust or loose connections, etc, etc. etc. AME 5.0 worked fine, after upgrade AME 5.5 hangs at random points when trying to export clips, but does not return an error or "crash" in the usual sense.

The last I've seen from Adobe on this is that they cannot replicate the problem on their test system. I don't know what else to suggest to anyone.

Z

ZackScott

Participant

Is it possible to keep using Premiere 5.5, but downgrade AME to 5.0?

A

AdferoVideo

Participant

Hi,

Has this problem been resolved yet?

I upgraded to cs5.5 yesterday and now AME is useless! It's much slower than it was on cs5, and like the other people in the forum, it freezes without giving any error. I have been rendering by turning off gpu acceleration and just exporting from premiere instead of sending it to media encoder. I don't think RAM is a problem, I've got 24gb, you'd hope that would be enough. It was super slow even with gpu accelleration turned on, so something is going really wrong.

I'm exporting an on2 flv file from a fairly basic timeline. I'm using a 3rd party plugin by Red Giant called Quick Looks. The piece I'm trying to encode is only 2.5 minutes long. I'm testing now to see if it renders using AME with the gpu acceleration turned off, it's very slow, but seems to be going through. This is quite distressing, as I missed a deadline yesterday because of the encoding speed. I really expected that after installing this expensive upgrade it would take the same time to render as it usually does, or speed it up a bit even. I'm really glad we held off on upgrading our other video workstations now, at least my workmates are able to get some work done.

R

RFendelman

Known Participant

I have Looks the full version and I'm always wondering if that is messing me up sometimes. I solved my AME problem by closing PPro before starting the encode and it worked for me and I only have 4GB ram on an iMac. Although, I only encode one project at a time. I've never tried a group of projects. Are you on a Mac or PC? Do you watch the Activity Monitor to see what is going on? Wish I could help more.

Z

ZackScott

Participant

I just want to add that I'm experiencing the same issues that others here are having. I'll queue up 4 or 5 videos to render overnight, and when I return in the morning, it will have stopped during one of them. There is never an error, and I have to force stop it in Task Manager. When I restart AME, my queue history is often gone, or it just has one or two videos that I had previously queued and already encoded (but AME has them marked as not yet encoded).

I can't recreate this process whenever I want. It just sometimes happens sporadically for no apparent reason. Also, I am using the Mercury GPU acceleration, and I have not tried this without it.

Here are my answers to Mark's original questions:

1. It is from a Premiere Sequence

2. As far as I can tell, it does not hang at the same point, but I'll keep a closer eye on this situation.

3. These are all video clips, AVI format, 1080p resolution, recorded with FRAPS. I am rendering to mp4 at 720p.

4. No effects are applied except Scale to Frame Size.

5. Memory usuage seems high and tied up. I'll have to pay closer attention to the CPU, but it seems to be low or none.

P

Paul_Duffey

Participating Frequently

Zack, you gotta make sure you have the most current updates for your video card, and the most current updates for your adobe software. I thought I had them already when I was having the trouble cause I loaded the drivers for my new card from the disk, and I purchased and downloaded the software from adobe, but no, I actually didn't have the "most current" drivers and updates for both. Once I did that the troubles were gone. Also the videos staying in the queue is actually a setting somewhere under AME.

For me I noticed the longer the video was the more likely it locked up without the updates. With 3 or 4 videos that were short it might not lock up, but if one of the videos were 10 mins or so, it would lock up, or if the 4th video of 4 wound up making the cumulative total be more than 10-15 mins of all clips, then it would probably lock up.

But anyway, make sure you video card is on the certified list, and make sure you're looking at the most updated list. I've googled and seen older lists that didnt include the gtx570, which is what I'm using,..but the most current one has them all.

Z

ZackScott

Participant

Thanks Paul, I am trying this out. I assumed I was mostly up-to-date, but there were new video card drivers for my GTX580 as of two days ago. Also, I'm updating to Premiere 5.5.1. I'll report back if I still have issues after the updates.

R

RFendelman

Known Participant

I'm still having lock-up issues.

A litle advice....

Currently, I'm Encoding straight from PPro an MPEG2-DVD. I changed a few things on the pre-set: Quality 5.0, CBR, selected Use Previews and Use Maximum Render Quality.

It's been sitting at 60% for about a half hour.

Is it stopped or still working?

Activity Monitor shows Adobe Premiere Pro CS5.5 with around 188% fluctuating and does NOT show Not-Responding.

My software is up to date per a check just now.

I know from previous experiece that if I select Cancel, it won't close and the Activity Monitor will eventually read that the program is Not Responding.

BTW, I'm on an iMac, 4gb ram, 10.6.8 Snow Leopard

P

Paul_Duffey

Participating Frequently

I'm on PC, so I'm not sure what the equivilent is, but I use the Performance Monitor in Task manager to view if it's really locked up or not. While rendering I see all my logical cores running 50-90% while it's rendering, when it stops or locks up that usually goes to around 3% on my i7. When it does that for more than a minute I'll force close it knowing it's locked up.

If you have a certified vga I'd say make sure you have the latest driver for that. I know with mac there's less cards that are "certified", and I think the certified part has more to do with the driver than the chipset of the card. Other than that, I wouldn't really know where to check.

R

RFendelman

Known Participant

Thanks, Paul.

I see that the CPU is around 190%, 48 threads, Real Mem 1.59 GB, Virtual Mem 1.96 GB.

I wonder if one clue is that the Disk Activity readout shows 0 bytes/sec read and only 68 KB/sec written.

I think that's a sign nothings happening.

I guess I'm going to re-boot the system and try again.

I just wonder if I'm better off Encoding directly with Export or choose Queue.

I don't have a lot of faith in the Media Encoder anymore.

My client is waiting for this DVD.

P

Paul_Duffey

Participating Frequently

I decided to do a post on here. I own sudosonic.com which is a tutorial company. One of my recent projects is 44 clips totaling over 4 hours on blu-ray. I was running into the same problem, rendering 22 of the seqs in a nested master seq, and even trying to render all those seq individually. I'd watch the performance on my windows task manager and the CPU USage would take a dive from 80% to 2%(idle). No warnings or errors in AME. I started queing one of the small seqs at a time and it would render it out, 2 or 3 in the queue even. Sometimes 3 or 4 would make it stop. ..why I dont know. I'm running a i7 980, 24gigs ram, gtx 580, all current updates.

By the way this error I'm assuming is what makes it look like encore is messing up too when you do a dynamic link. So thats why even I started rendering these out individually. You gotta drop in your seq to a master where they'll be nested and then tweak your render presets. I wound up doing H.264 bluray with really low CBR, like 1 or 5mb. Then the output showed at 14G. Then I saved that as a preset and used that same preset to render the clips individually, import them individually into Encore, it rendered an ISO in like 30 mins.

I know everybody doesn't have 4-10 min clips like I do, but then again they probably don't have picture in picture full hd or titles all the way through. I'm guessing it's the software that can't handle the memory management.

Hope this helps.

-Paul

N

Neverends ProductionsAuthor

Participating Frequently

I don't understand the time it is taking to trouble shoot this problem. With Adobe technicians logged into my system they see it happening, so why do you need to create the problem in-house. I will give you my raw materials if that helps.

P

Paul_Duffey

Participating Frequently

Yeah I agree. Really as much as Premiere/Encore/AME costs, it should run smoothly with HD in any situation. I've done a little programming and lots of video editing in the last 10 years, and I think it has to do with the memory management architecture. Clearly when larger files and composites have to render there's some sort of issues going on with AME not being able to handle it.

I myself am a little upset that AME can't take more than 3 or 4 of my seqs in the queue at a time. That's the whole point of having AME in the first place is so you can load it up and render over night.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded