I've also playback issues with my Red Rocket Card.

Last Version no problem, now I cant even edit in 1/8 res. Maybe 4 FPS.

It's really frustrating especially since I've some projects for some mayor labels and I've already missed one deadline, cause of this sh*t.

I'll never ever update befor reading this forums.

I rather watch other people fail, than getting my *** kicked by my customers.

I am not happy to pay this month because I am not satisfied with the product....

Experiencing the same issues with the last update and already missed a deadline!

Please tell me how to revert my Premiere app and projects because I need to end this project Today.

Matteo Marzano

---

MacBook Pro, Early 2013

OS X 10.8.5

i7 2.7 GHz

16 GB RAM

NVIDIA GeForce GT 650M 1024 MB

Have to finish today too...but its never going to happen XD

Will my *** get kicked to the moon.

Thx Adobe for losing one customer.

I'm desperately trying to export the project in order to work with Premiere CS6…but without success!

I tried to follow this instructions: Can You Open/Use/Export/Save Adobe CC Files on CS6 – and Back? | ProDesignTools

This is what I get when I open a sequence from the a XML for Final Cut…crash:

And this crash happens when trying to export an AAF file from CC

It's really frustrating Adobe. Users pay for a professional tool that should be functional...But what I am reading here is that many got same bugs using the same software release on different machines and os, and that they are not properly supported. How could this be possible??

Please give us a quick solution to go on working

Justin-Time wrote:

 

Experiencing the same issues with the last update and already missed a deadline!

 

Please tell me how to revert my Premiere app and projects because I need to end this project today.

 

Hi Justin, this guide should help:

Creative Cloud Version Control: How to Roll Back or Update to Any Version of the Adobe CC Apps

Adobe, and now?

What should I do? (wait for an update on CC2014 that fixes this or go back to the old version of Premiere?)

2 days passed, no reaction from Adobe side. I feel like no-one is there...

GGo back to 8.0.1.  It's the only known solution for those of us for whom 8.1 blew.

thank you, RedDirt.

...yes...it appears you, and others, have found a genuine software problem that affects your particular machines. I did notice,however, that your hardware is a littlle THIN for the newer versions of PPro that are designed to take advantage of the newer systems that feature more memory,higher CPU clock speeds with more cores, faster drive systems, and more powerful CUDA cards. Your "symptoms" remind me of when I was trying to edit on an underpowered PC. I am not sure of what your drive configuration is,but, I do know 12 GB of system memory is LOW....even my newer Haswell laptop has 24....PPro has been improved to use more memory....ESPECIALLY in handling the Canon MOVs that used to CHOKE a PC because of the 32 bit nature of the Quirktime codec which had limited system memory use to 4 GB. NOW, PPro handles the Canon MOVs in a 64 bit environment with INCREASED MEMORY USAGE. Also, PPro does NOT support" crossfire",or,  " SLI".... it WILL use two separate CUDA cards, ( providing they are both using the SAME driver ), in certain operations ONLY.... like " DVD export".  So, in general, as newer versions of PPro appear, older, less powerful machines may begin to suffer...this is where Adobe should play a role in informing customers of this IN ADVANCE ! Their PUBLISHED " minimum specifications" were a JOKE in the past, and I was stung pretty good  when I was a noob. They should maintain a range of different rigs for actual testing, so they can WARN customers in advance concerning REAL minimum hardware requiements. Although all these frequent version updates must be making it hard for Bill Gehrke to keep up with...go to PPBM 7 dot com and TEST your current machine with his video benchmark program for PPro, to see how your machine performs compared to others. Although, rolling back is working for you now, you may need to upgrade your rig to a new one.....like I am doing... to be able to keep up with all the advancements in codecs and PPro. Your current OS only supports 16 GB system memory....you really need 32GB now, as a minimum. CPU really needs to be over 3 Ghz under load, all cores running...many overclock up to 4.5 Ghz. Either Samsung 850 Pro or Crucial M550 SSDs are the best right now for OS drive and a cache drive....actually, in a desktop, you could use the cheper M550s. One 256 GB for OS, programs and page file ONLY.....then, 2 M550s in a RAID 0 for media, projects and all else.... add conventional HDDs for backup and archive.

JFPhoton -- this issue is not at all about system configuration.  I am running PPro on a new Mac Pro with dual 6-cores, 32GB RAM, and dual AMD FirePro D700 GPUs, with a Thunderbolt2 RAID5 array for storage.  Some folks are having the same issue with PC's and completely different configurations.  It's a pretty widespread issue with few if any commonalities.  But my case itself eliminates the question of hardware specs being the culprit.

...I was responding specifically to " cadillacula". However, you must be aware that AMD graphics cards DO NOT HAVE CUDA and are WAY BEHIND in GPU acceleration, compared to Nvidia CUDA cards. Also, there HAVE BEEN many issues reported on this forum with incompatibility between the Apple OS  and PPro.

To see how your machine is actually performing with PPRO, GO to the PPBM7 website and TEST your machine ! It will give you info on your drive speed, gpu acceleration, ( if their IS any with the AMD GPU ), and other important info. As I found out MYSELF, the HARD WAY, sometimes inadequate hardware CAN be tha cause of signicant problems with PPro. This test will go a long way to identify any bottlenecks,or, other hardware issues. Plus, you can see how your machine compares in performance to many others of various configurations.

Iam NOT SAYING that you guys have not found a significant software problem......however, you must RULE OUT any potential hardware problem FIRST ! THEN,  focus on the software problem.

WHY are you YELLING

....I don't hear anything.....DO YOU !!! Are you using " text to speech"....with HEADPHONES !!!!!

.... if I were using Apple and AMD , I would be HYPERSENSITIVE, TOO !!!

So, I've had the same issue as some of you and I found the primary issue (for me at least). It was an oversight on my part. What kind of monitors are you guys editing on? I'm using a 4K Samsung. My desktop resolution was set to 4K. I'm only handling 1080 footage but the 4K desktop resolution was enough to bog it down. I have a rather powerful system and it never occurred to me that this would be an issue. I dropped my resolution down and voila, all is well.

Thanks, xzoto!  Hopefully this helps Kevin, Mark and Bruce to narrow down the underlying problem on the Premiere 8.1 side.  Shouldn't be any difference between 8.0.1 and 8.1 -- if anything, an updated software like 8.1 should be BETTER able to handle the latest hardware... not worse off.

I have an LG 34UM95 monitor, which I am LOVING.  Works fine in 8.0.1 (at least as far as the sluggish problem that arose in 8.1 is concerned).  It's 3440x1440.  Did not try down-rezzing.  But that's not a solution, it's a hinderance.  Particularly for those of us cutting 4k.  I was not using it with Mercury Transmit, rather as my primary UI monitor. 

Not ignoring you, Cadillac, but it's a lot of work to put that together.  I've been in touch with Adobe's team directly on this now.  If I hear of a viable solution, I'll post it to this thread, which you are on.

Hi RedDirt,

RedDirt wrote:

 

Shouldn't be any difference between 8.0.1 and 8.1 -- if anything, an updated software like 8.1 should be BETTER able to handle the latest hardware... not worse off.

8.1 is not a minor update, it is a major version with changes to the structure of the Premiere Pro project file. Unfortunately, incompatibilities begin to surface when new versions of software are released: GPU drivers, third party plug-ins, third party hardware, etc. In my opinion, some customers are not always as ready as they think they might be when updating an application, OS, or both.

RedDirt wrote:

 

I have an LG 34UM95 monitor, which I am LOVING.  Works fine in 8.0.1 (at least as far as the sluggish problem that arose in 8.1 is concerned).  It's 3440x1440.  Did not try down-rezzing.  But that's not a solution, it's a hinderance.  Particularly for those of us cutting 4k.  I was not using it with Mercury Transmit, rather as my primary UI monitor.

That monitor looks really cool. For a test, what happens if you connect your previous monitor to your system?

Thanks,

Kevin

Thanks, Kevin.  I can def see that 8.1 was a major update that changed project file -- explains why you can take same file back and forth 'tween versions.

I was previously using simply a single Apple 27" Thunderbolt display, which continues valiant service as my 2nd monitor, both connected via Thunderbolt.  (T2 in the case of the LG)

Thanks, luckily I could go on without rolling back....

...this is for everybody still having issues: check how many free space is on your disk, I think PPro use a bunch of it as cache, then try to restart your machine.

I had 30gb free: now its 90gb and I turn off my macbook when Im not using it, which is an habit I lost since I have turned to mac.

Except a crash -which happens when I plug an external sound card- I hadnt any of the previous issues!!!

Should 5TB free be enough?

That's a very interesting data point re: the UHD monitor, xzoto. RedDirt has already reported that he's also on a very hi res (but not quite UHD by CEA standards). We'd be interested in a show of hands from others having the specific problem where basic actions in the Timeline lead to the app becoming unresponsive for some period of time. Please report the resolution of your monitor(s).

Mark, as you know i may not be able to test that for a while since I'm mid feature film.

However, when I do, you guys surely won't throw your hands up and say, "Aha!  Premiere just isn't compatible with hi-res monitors."  No, of course your engineers will go in and find the bug and the solution.

HOpefully, therefore, you are already doing that and not just waiting on little Ol me.

At this point, I'm not asking for any of you to test anything. Just looking for a show of hands to see whether very hi-def monitors is a common thread with this issue.

I'm not actually assigned to investigate this issue. If I were, I'd have to hand it off to a colleague to pursue the UHD angle. (I work from home, and while I have a respectable lab of 4 test systems, a UHD monitor is not in my arsenal.) I don't happen to know if Wes, the QE who's investigating the bug and also works from home, happens to be equipped on that front.

Retina

15 inches (2880x1800)

Intel HD Graphics 4000 512 MB

***

Premiere. Still having crashes with external soundcard. When plugged, the very first minute audio and video speed up...then crash.

Dreamweaver. Today I wanted to try the new release: I could barely give a look to the new interface, just after syncing settings from the cloud...then crash.

I have stopped Upgrading...Hey Adobe!...I think that any trustworthy company would have paid me back for a WHOLE MONTH of LOST JOB.

staying on obsolete versions rather than figuring out the actual issue is a solution without a future.

8.0 and 8.01 are hardly obsolete.  And for many, including myself, staying back a few versions and watching while others experience Adobe's beta program is the ONLY solution with ANY future as an editor.  However, I agree, not figuring out the actual issues before releasing software may may be a solution without a future for Adobe.

Statements by Adobe staff like:

Yes, it is fixed in the next version. We couldn't fix it in time for Premiere Pro CC 2014 (8.1)

Seriously?!  I don't recall this being an issue in previous versions.  It's pitiful that we've all become accustom to "here today, gone tomorrow" features in Premiere Pro.  I understand that programming is difficult.  But you couldn't fix it in time?  If you don't have time to "fix" what wasn't broken before, JUST TO INTRODUCE A NEW FEATURE THAT DOES WORK, then DON'T release the software!!

Cadillacula, RedDirt and manfredhaider, I KNOW you're not the only ones who *would* be experiencing this issue.  It's just that many of us have already learned this hard lesson, and we simply don't participate in Adobe's uninformed-public beta program anymore.  Of course we still fund the program every month.  It would be interesting to see Adobe's collected statistics to know exactly how FEW have actually upgraded to PPr 8.1.  I doubt it's hundreds of thousands.  Maybe only hundreds.  To the three of you, and to the other few who are currently beta testing 8.1, you have my thanks!  My hat is off to you.  It's important research and someone's got to do it.

8.0 and 8.01 are hardly obsolete.

Though it doesn't mean those versions are unusable (steam-powered?) antiques, the fact that 8.0 and 8.0.1 have been superseded by a new version makes them the very definition of obsolete.

I don't recall it [which by context I take to mean "not being about to implement and test every possible feature" -bbb] being an issue in previous versions.

It is an issue with every release, of all software, ever.

There is always more that could be done. In the past, the next release was months or years away; with our new CC release cadence, the next update comes much more quickly.

Some software publishers take the approach of cramming every possible feature/fix into a given release. By contrast, the PPro team is quite stringent about not releasing new functionality (fixes or features) which hasn't been fully tested. Consequently, there are often fixes or features which, even in the 11th hour, are not included in a given release, and are delayed until the next one.

And, despite our best efforts, there will always be bugs.

Side note: Many thanks to RedDirt, who's provided actual projects which replicate the behavior on his system, and has been responsive to the team's barrage of questions.

+1 for 2014.1 being unusable. For my team it's with multicam view. Laggy, and freezes up anytime you do a cut. Is there a definitive answer on how to get back to 2014.0?

Yes, one straightforward way to roll back or forward to any CC version was posted earlier above.

I get the access denied that they talk about when trying the direct download, swear I'm logged in but I'll try on another computer following those instructions.

ahh yes was able to get that link to work on another computer. Thanks!

bbb_999,

The newest update completely killed Premiere's performance for me.  I'm mid-edit on a feature film and there is no chance that I can go back with the project.  You're offering help.  I need it desperately.  Premiere is a complete nightmare to use right now.  It crashes regularly and performs like I'm trying to edit on a Commodore 64.  I've logged bugs and given as much information as I have on these forums.  Kevin has been unable to help.  If you or anyone at Adobe can get Premiere working like it was in the previous version, it would be greatly appreciated.

Right now I'm looking at 3min project load times and UI framerates in the 0.25 to 1 frame per second speed while Premiere is doing some kind of intensive file transfer in the background.  It never remembers thumbnails for my media and is constantly regenerating them.  It just crashed twice rendering out a project that it then renders without error after restarting.  One of the crashes blue-screened my PC.  This is the worst editing experience I've had in years.

Michael

If you or anyone at Adobe can get Premiere working like it was in the previous version, it would be greatly appreciated.

The tough part for us hasn't been getting previous performance; its' been reproducing the reported terrible performance. Even with the projects provided, we're still unable to repro the behavior.

We're still actively looking into the problem; I'll post anything we find here.

Can you fly one of your engineers up to Vancouver, Canada with his debugging machine/software and test my project on my computer?  He/she can stay at my place while I'm down at the American Film Market until the 12th.  Surely it's worth a few thousand dollars for Adobe to fix this terrible problem with their software.  You're not going to recreate the problem unless you have my computer setup to test on... and it's not possible to send you the 8tb of media for the project.

I've just spent the last 2 hours trying to render 2 different versions of 2 teasers of our film.  Premiere and AME just crash randomly or make that goat bleeting sound.  I'm turning off my GPUs and hope that this will solve the problem.