[Richard Angle]

Thank you, Tim, for your response and explanation. However, if this is the issue, shouldn’t dedicating more memory to the Adobe global application make a significant difference? I don’t necessarily mind slowing down the background rendering in most cases. Could you suggest any work-around? I have a multi-purpose machine. Last I checked. computers are pretty darned good at multitasking these days. I’m telling you, It’s either Adobe on or Adobe off in this situation.

Thanks, man.

[Richard Angle]

But I truly don’t get the connection between the two. To me, it seems that internet connection speed should remain constant even if I am taxing my CPU at the same time. Think of it this way. A fast internet connection is available regardless of the computer’s CPU computing potential. If I were to have a much older model computer on a 56k modem, I’d suspect this performance. But put the same old box on a modern broadband connection and it should fly as far as general web surfing. No? I’m not talking about using graphics heavy programs. And even if I was, what does graphics processing have to do with internet connection speeds? Simply “surfing” the web slows to unimaginable speeds while encoding in both Premiere and Media Encoder and it’s like night and day and every single time. What does CPU potential have to do with the potential of the internet connection speed? Seems to me that they should not affect each other. They never interfere with each other while using other applications. They certainly never did in my old FCP days. Any help in understanding this on a truly technical level is very much appreciated.

[Richard Angle]

As you have witnessed, when the keyframe is slid to the end of a zoomed out timeline quickly, it “snaps” into place before the actual last frame. Drag the keyframe VERY SLOWLY AND CAREFULLY past the boundary and into the vertical scroll bar area and the keyframe will continue to the last frame and hide itself behind the vertical scroll bar area. All that will be visible is a single pixel on the corner of the keyframe. A bug or an easter egg? I have no idea, just another bizarre CS6 behavior to add to the list. Premiere is a mysterious beast.

Richard Angle

[Richard Angle]

Many claim that it not a bug at all. Rather a normal way in which GPU Acceleration deals with the dissolve. What? This is normal? Might be normal to some, but certainly unacceptable to me. I’m trying to do professional work here and Adobe simply doesn’t allow it to be done with the use of a CUDA card. So I turn off GPU and render in software mode for all final renders as well as approval files. Turns a ten minute render into an hour long render.

And to Will…. You hope CC handles it better? I am of the opinion that every single Adobe Premiere cs6 customer gets a free upgrade to CC. Adobe will get NO MORE of my money. This I assure you.

Also, on a side note, someone mentioned seeing the issue in software mode. In my experience, this happened when checking “Render at Maximun Quality” Who in their right mind wouldn’t be rendering at the highest quality for final master!

This whole thing just sickens me and Adobe should be stepping up to the plate!

Richard Angle

[Richard Angle]

I am absolutely livid on the issue and am baffled as to why more editors are not up in arms over this nonsense! I want my money back from Adobe and I want them to reimburse me for my CUDA card that I just bought to beter handle the .mts AVCHD files that Adobe said Premiere would handle. Utter trash and I am very disappointed with Adobe. This software simply should not be on the shelves at its current price. Buggier than a big box of ants in my opinion.

I just spent hours exporting three music videos that should have taken me fifteen minutes. I bought a Cuda card partially to speed up exports. Unfortunately, the trade off for fast renders is lousy dissolves and font fades! Hmmm… Export for 20 minutes and be done with the project? No! Can’t do that! Your dissolves and text fades will look like Micky Rourke’s face. So I choose to do the right thing and disable hardware acceleration. Utterly ridiculous and I want my money back!

And forget about getting in touch with anyone who cares at Adobe!

Richard Angle – The grumpy editor

I just want things to work like they used to back in the good old FCP days.

[Richard Angle]

I have to say I agree with Paul on this 100%. I am so frustrated with Adobe Premiere now, I just want to puke. This is program is far too buggy to be released at the price it is at. It has potential, and it is the smartest software choice available, but it is just not ready for prime time.

Must disengage Cuda card before renders and exports to get acceptable fades and dissolves? My renders go from 5 minutes to 35 minutes!

.MTS audio randomly disappears from files. Delete the XMP’s?

Severe lag when navigating H.264 .mts. Shall I transcode?

Relinking of moved large .mts based project? AVCHDs fault for the naming scheme. However, even when manually renaming every single clip and relinking, the audio disappears and the timeline has grey diagonal lines on the clips. I had to start all over on a two day rough cut due to this one.

So Paul. GO AHEAD AND SHOUT IT FROM THE MOUNTAIN TOP!!! Some of us hear you, man. People need to be more helpful and less critical here.

Richard Angle

[Richard Angle]

Bumping this thread. It is Summer of 2013 and cs6 and I am pulling my hair out with this exact issue.

I had a sequence that was fine a week ago for the export of the approval file. The exact same project/timeline now has somehow screwed up the nice linear transitions of last weeks project. Here’s the kicker… Grap a problematic clip and slide it out to the right into virgin timeline space. Voila. Fixed. Slide it back to it original position, back to square one. Unfortunately, I think the answer involves disabling my CUDA card for final renders. Which is a big reason I got the card in the first place! Faster renders.

Any advice any of you can offer?

[Richard Angle]

Can anybody offer any suggestions to this issue? Every time I turn around, something else is bugging out with this program. Please someone help me determine what is going on here.

I’ve experienced fades and dissolves not working linearly.
I’ve experienced .mts files not playing back audio.
I’ve had to can two days of rough cutting simply because it was impossible to relink my files. (grey diagonal lines though conformed footage.

I’m serious in saying that every single project presents itself with an astounding bug that costs me days of work!

Somebody, please. Can you reread this posting and help me get to the bottom of this. I literally cant finish a multi thousand dollar project because I can’t get my fonts to fade up evenly. The exact same project was flawless when outputting the approval file a week ago. Now I can’t output the final.

Please?
Richard Angle

[Richard Angle]

Oh. I think I understand you. I could set a series of the following keystrokes?

“Shift+4” to highlight the program monitor
“CNTR+L” to toggle the loop
“Shift+3” to go back to the timeline
“spacebar” to execute the play

Something like this?
“Shift+4” (+) “CNTR+L” (+) “Shift+3” (+) “Spacebar” And all of these commands coul be assigned to a single keystroke combo through this program?

Thanks Alonzo.

[Richard Angle]

Thanks for the response but I’m not sure I follow you, Alonzo. It’s simply not possible to assign a keystroke to toggle the loop function when working in the timeline. Ironically, when working in the timeline, its really the only time that I’d like to be using the toggling loop in the first place! If I am working in the timeline, why can’t I just hit Cntrl+L to toggle looping on or off? It makes no sense to me why the looping toggle can’t simply be a global program setting.

And what about when I am working in the fullscreen “`” timeline window? How on earth does one toggle loop on and off from that mode?