JesseSchluntz wrote:

 

... Why is there no simple web page with download options for each previous version? Please set me straight if this exists.

 

Hey Jesse, Adobe does have that for some tools but not all tools and not all releases...  However, we do have all download links collected here for all CC apps, and for each and every successive version:

All Adobe CC 2014 Updates: Direct Download Links for Windows

All Adobe CC 2014 Updates: Direct Download Links for Mac

Hi Sakari,

What happens if you choose Project Settings > General > Renderer > Mercury Playback Engine Software Only?

If exporting, can you also see if you have problems after setting to Software Only?

Thanks,

Kevin

Hi,

I have links from your site for the Premiere Pro CC 2014.01 (8.0.1) update in my blog post about how to revert to earlier versions here: http://blogs.adobe.com/kevinmonahan/2014/01/29/revert-to-a-previous-version-of-premiere-pr o-cc-or-any-creative-cloud-application/

Thanks,

Kevin

Hi Jesse,

Sorry for all the issues you're having.

JesseSchluntz wrote:

 

The new issues discussed in this forum are occurring on my laptop too. Sluggish performance when I apply simple filters at 1/4 resolution, and now a total loss of program monitor signal constantly. Plus it locks up crashes over and over again like most other versions of premiere I've had over the past few years (why is this so *******' hard to fix)?

Since you are a Mac OS X 10.9.x user, have you tried the following?

• Sign out from Creative Cloud, restart Premiere Pro, then sign in
• Update any GPU drivers
• Trash preferences
• Ensure Adobe preference files are set to read/write
• Delete media cache
• Remove plug-ins
• If you have AMD GPUs, make sure CUDA is not installed
• Repair permissions
• In Sequence Settings > Video Previews, change the codec to one that matches your footage
• Disconnect any third party hardware
• Disable App Nap
• Reboot

JesseSchluntz wrote:

 

The suggestion ProDesignTools helped me roll back to version 8.0, but I was shocked to discover I can't open my project created in 8.1 (the problem project). I also tried importing individual sequences and the progress bar just hangs with no results. Shouldn't I be able to trade projects between anything that's version 8? Does anyone have a fix for this!???

 

Also, a question for Adobe: please correct me if I'm wrong on this - but why do you make it so hard to roll back to previous base versions when you've given us buggy software? Why is there no simple web page with download options for each previous version? Please set me straight if this exists.

I agree that it should be easier. I'm doing my best in providing feedback up the chain about this. In the mean time, please see my blog post here: http://blogs.adobe.com/kevinmonahan/2014/01/29/revert-to-a-previous-version-of-premiere-pr o-cc-or-any-creative-cloud-application/

Thanks,

Kevin

Hi Michael,

Thanks for your post and sorry you are having such issues. The tone of your post is very accusatory but I will try and answer any questions if I can.

vanlazarus2013 wrote:

 

Dear Adobe,

 

A few questions:

1) Do you have a QA (Quality Assurance) department?

2) Does that QA department have more than 3 people in it?  20?  100?

3) Is each build tested thoroughly for at least a month before it's made public?  2 months?

4) Does your QA department have at least 20 different test computer configurations for both PC and MAC from budget to high end professional?

5) Does your QA department have at least 50 test projects that are loaded, manipulated for an hour, and rendered without error for each new build before it's posted?

6) Do you ship builds with known severe bugs?

7) Does your marketing department determine release schedules?

I'm not sure how relevant these questions are, but let me try:

• Like all software teams, of course we have a QA dept.
• Head count is confidential, of course.
• The latest build has been tested for months by engineering and our prerelease users (editors like you).
• We have a hardware lab with plenty of variation in components, including Mac and PC, and external I/O devices. We also have prerelease testers that have a variety of hardware that we get feedback from. Personally, I have not counted the many computers in our test lab as I never thought it was important. Let's just say, there are a lot.
• I don't know the magnitude of testing individual projects, but we do test a ton with various formats, complexity, duration, etc., all of it. We also have automation testing, as most software companies do.
• No, we don't ship with severe (show stopper) bugs.
• I'm not sure how to answer that question other than to say that the June release and last December's release did not coincide with any marketing events while this release it did. Take what you want from that info.

vanlazarus2013 wrote:

 

If your QA department doesn't have test projects, or if none of them include Red camera media.... please add a feature film Red camera media project to that collection.  Currently, I see NO indication that your software is being tested with long form projects with large volumes of media.

Is David Fincher's "Gone Girl" not good enough evidence? It was shot on RED Dragon and edited in Premiere Pro CC 2014.1 (8.1).

vanlazarus2013 wrote:

 

Prelude is broken for me and Premiere 2014.1 is getting there.

Have you filed a bug or created a post in the Prelude forum yet?

vanlazarus2013 wrote:

 

I don't know what your revenue stream is from the Creative Cloud, but I assume that it's reasonably extensive.  A good chunk of that monthly income needs to be spent on a robust and properly manned QA team that has the authority to delay an update if they deem it not ready.  Premiere and the Adobe Creative Cloud suite is an insanely complex piece of software and to pretend that you can keep adding features every quarter without an extensive QA team testing it thoroughly is naive, amateur, and will snowball your suite into oblivion.

We have an awesome QA team. It's certainly as large as other teams I've worked on at "other companies." Could we use more staff? Sure! You can never have enough engineers, QEs, support staff, etc., no matter which company or product you take into consideration.

I do understand your frustration, however. Bugs should not happen (but they do). Things should get fixed faster (but often it takes time). Etc.

vanlazarus2013 wrote:

 

Perhaps the next update for Premiere needs to be a 'bug fix only' update.... and done as quickly yet thoroughly as possible.

Tell this to the team in a bug report: http://adobe.ly/ReportBug

In the mean time, here's a list of what was fixed for 8.1: Bugs fixed in Premiere Pro 2014.1 Release | Premiere Pro work area

Let's get this back on topic now, shall we?

Thanks,
Kevin

I've been cautiously dipping my toes into the 8.1 release.  I have some very complicated projects that have been ongoing for months, and for that, I'm sticking to 8.0 (I have both installed, and they seem to be co-existing just fine.).  But, I've now started and finished two projects in 8.1, and have found it to be stable.  The only quirk I've seen is that some stills come in rotated at 90 degrees.

I have experienced what I've come to the forum here and described as "show stopping" or "job-killing bugs" only to find out that there was something corrupted in my OS or drivers.  One issue was so bad that only an OS re-install cured it.  So, I can attest to the notion that if you haven't tried EVERY SINGLE suggestion in Kevin's list above (including re-installing your OS), you haven't tried everything.

Even if you have the most updated drivers, they can get corrupted.  I've had several issues that reinstalling the same version of driver (including CUDA) has fixed.

And I can affirm that corrupt media can wreak havoc with any NLE, and Pr is no exception.  Sometimes, the seek and destroy method of taking media clips or files off-line in groups can help find bad media.

Fingers crossed that this post doesn't jinx me.  

How did you install 8.1 and keep 8.0.1

Like most experienced computer users, I clone my drive before upgrading anything.   After cloning, I updated Pr, renamed it to Adobe Premiere Pro CC 810, then I dragged the 8.0 application from my clone disk into my Pr application folder, and renamed it Adobe Premiere Pro CC 800.

Caveat here is that this practice is likely unsupported by Adobe, and that if you expect the CC app to work with Pr afterwards, you should revert the name of the current version to  Adobe Premiere Pro CC 2014, or it won't be recognized by the installer.

How does that work with 'Direct Link' to and from AFX?

Hi Kevin,

Thanks for your response and detail in answering my questions.  Yes, my tone was accusatory because within 20 minutes of using the new version I encountered the problems described by the poster of this thread.... and work was lost, and time wasted looking for solutions.

Your comments beg more questions.   They will be my last regarding QA in this thread.

I don't understand how a build can be tested for months with the release schedule of the last 2 builds.  A build (8.0.1) was released in late July, then the latest (8.1) in early October.  That's 2.5 months between releases. 

1) Was all the coding on the latest build done in 2 weeks, and then tested for 2 months?  I highly doubt this.

2) If new feature coding is happening concurrently with testing, how can quality be assured?  All tests need to be done AFTER all new features are added.  Coding during testing should only be done to fix problems found... and if significant code needs to be changed to fix a bug, the test schedule needs to be reset to the beginning.

3) How could Gone Girl have been edited on Premiere 8.1?  The movie was released on October 3rd.  With color grading, sound design, and music likely being the later stages, this film was probably edited somewhere between January and June of this year. Adobe hadn't even released Premiere 8.0.1 by the end of June.  Gone Girl was probably edited mostly on a version of Premiere that was released late last year.... unless Adobe was giving Fincher direct access to beta versions... which would be risky for his team of editors.... and wouldn't those beta versions be for pre-8.1 versions anyways?

Yes, I filed a bug report for my Prelude issues.... but I'm not sure where the report went and haven't gotten any feedback... which kinda discourages one from again spending time filing a thorough report on any other problems.  Please let me know where I can review bugs I've posted and their status. 

And back to the topic of this thread: Surprisingly, this UI slugginess in Premiere 8.1 seems intermittent and is not consistent for me.... so my frustration level with the new build is reduced.  I haven't noticed any pattern as to what causes this UI slowdown though.

Regards,

Michael

Dynamic Link?  Dunno.  I don't use it much.  I usually render out of Ae and import files into Pr.  I'm also sticking to the 13.0 version of Ae until they change those dumb dark keyframes.  This latest update to the interface isn't Adobe's best work.  I don't recall anybody asking for a GUI that gave us eyestrain.

Hi Michael,

vanlazarus2013 wrote:

 

Hi Kevin,

 

Thanks for your response and detail in answering my questions.  Yes, my tone was accusatory because within 20 minutes of using the new version I encountered the problems described by the poster of this thread.... and work was lost, and time wasted looking for solutions.

Sorry about that. Did you update an existing project? Or was this a brand new project?

vanlazarus2013 wrote:

 

I don't understand how a build can be tested for months with the release schedule of the last 2 builds.  A build (8.0.1) was released in late July, then the latest (8.1) in early October.  That's 2.5 months between releases.

Work on releases overlap greatly. Planning for releases happens even earlier. Actual work on this release began long ago.

vanlazarus2013 wrote:

 

1) Was all the coding on the latest build done in 2 weeks, and then tested for 2 months?  I highly doubt this.

Again, we do not wait for software to be released to begin building our next version. Hope that makes sense.

Lots of things happen behind the scenes at a software manufacturer that a typical video editor might not know about. It was very interesting for me to come into the software business from the stance of a video editor, actually.

vanlazarus2013 wrote:

 

2) If new feature coding is happening concurrently with testing, how can quality be assured?

Refer to my first answer. Coding began long ago. We tested it thoroughly. Then we gave it to prerelease users and get their feedback. Then we refine, refine, refine, until we have a candidate for ship. Quality is tested the whole way.

vanlazarus2013 wrote:

 

Coding during testing should only be done to fix problems found... and if significant code needs to be changed to fix a bug, the test schedule needs to be reset to the beginning.

You'd have to talk to our engineering manager to get the specifics, but believe me, they know what they are doing regarding testing for quality. Were you in the QA field before or something?

vanlazarus2013 wrote:

 

3) How could Gone Girl have been edited on Premiere 8.1?  The movie was released on October 3rd.  With color grading, sound design, and music likely being the later stages, this film was probably edited somewhere between January and June of this year. Adobe hadn't even released Premiere 8.0.1 by the end of June.  Gone Girl was probably edited mostly on a version of Premiere that was released late last year.... unless Adobe was giving Fincher direct access to beta versions... which would be risky for his team of editors.... and wouldn't those beta versions be for pre-8.1 versions anyways?

Read this: http://blogs.adobe.com/premierepro/2014/10/gone-girl-marks-yet-another-milestone-for-adobe -premiere-pro-cc.html

Fincher worked with 6K RED Dragon, which is a feature of 8.1. This tells you that, yes, he and his editorial staff was working with a prerelease version of the software.

vanlazarus2013 wrote:

 

Yes, I filed a bug report for my Prelude issues.... but I'm not sure where the report went and haven't gotten any feedback... which kinda discourages one from again spending time filing a thorough report on any other problems.  Please let me know where I can review bugs I've posted and their status.

We don't always contact customers for feedback. There is no place to review bugs you've posted or their status. Sorry, I know that can be somewhat unsettling. Feel free to also make a post in the Prelude forum. That may help.

vanlazarus2013 wrote:

 

And back to the topic of this thread:

Thank you.

vanlazarus2013 wrote:

 

And back to the topic of this thread: Surprisingly, this UI slugginess in Premiere 8.1 seems intermittent and is not consistent for me.... so my frustration level with the new build is reduced.  I haven't noticed any pattern as to what causes this UI slowdown though.

Have you tried all the suggestions I made earlier on this thread? Try those.

Thanks,

Kevin

Hi Kevin,

I updated an existing feature film project.  This UI sluggishness comes and goes.  I don't see a pattern yet.... and I don't have time to troubleshoot.  If the problem returns and stays, I'll be forced to troubleshoot and try your suggestions.  Until then I'm hoping Adobe QA can troubleshoot this problem, find it, and fix it.  As I'm sure you're aware, most customers of the Adobe Creative Cloud want to use the software, not debug it, or spend time like I'm doing right now posting on Adobe forums.... although this can be a way to procrastinate tedious tasks in editing.

It really surprises me that your Premiere version development overlaps.  I don't even see how this could work unless the versions updated completely different sections of the code base.... And even then, you'd have to merge features from one version into the next, just before release, so that each version had all the features of the previous.  Overlapping version development doesn't seem a like a process that contributes to simplicity.  I can see that there might be a development speed increase but at what cost?

I worked in the video game field for 10 years. First as a programmer, then a designer, and then as a producer.  We never had 'versions' because once you released a game for a console, that was it... no chance to patch your errors (at least back in the day when I was in the field).  So the code had to be bullet-proof before it was released.  Software updates in the computer world are the bane of stable software.

Regarding my Prelude issues:  I have also posted to the Prelude forums and got no help.  Rather than spend more time posting, I bit the bullet and imported all the film media into Premiere directly, which sucked because Premiere doesn't import nested media very well at all... and rather than spend time reporting that bug, I just spent 5 or 6 hours organizing the media by hand.... which probably still saved me time compared to debugging the software for Adobe.

Hi Kevin,

I have tried all the suggestions on this list and I am yet to find a solution. The main area that I am noticing the lag is in RGB Curves. Premiere Pro CC v7.2.2 is buttery smooth, but Premiere Pro CC (2014) v8.1 takes a couple seconds with every click and occasionally causes everything to freeze up so I have to restart my system. I'm wondering if it has anything to do with the new version not talking to my Quadro 4000 graphics card… I have updated the CUDA driver to the newest version, but still no luck.

Please take a moment to view this comparison:

Best,

Dustin

Howdy Kevin. Thanks as always for your responses. I know you mean well.

I've just spent 12+ hours finsihing a job that should've taken me far less time. As I mentioned earlier, my new Mac Pro is in the shop getting more parts replaced for my phantom render lines issue you're very familiar with. This Premiere 8.1 issue, however, has taken me to a whole new level of frustration with Adobe.

After upgrading to 8.1 earlier this week on my new Mac Pro, I started suffering lags, lock ups, and more crashes than ever... even for Premiere, which has been crashing on me every couple of hours since version 5.5.

With my Mac Pro in the shop, I've had to work on my laptop. Like my tower, it's "top of the line". Recently purchased. The newest macbook pro Apple makes because I often do mobile edits for clients. Thank God I didn't have a mobile edit this week. It would've been embarrassing....

Because my project was created in 8.1, and I could not open it in 8 after rolling back (that stings), I had to continue on with what I had. Here is a nutshell bug report from just ONE DAY on 8.1, on a totally different machine than before mind you. And the project is mostly DSLR and Gopro. Not exactly the most demanding material...

ISSUES

- sluggish performance, including program locking up.

- Loss of ability to play back simple photo animations. So I restart the app, which causes it to crash every single time and recover the "copy of" version.

- crashes ALL THE TIME. can rarely quit without premiere making it into a crash. At one point I had a "copy of copy of copy of copy of" my project.

-  when a project is restored after a crash, all but one of the sequences is closed when the project comes back up. This was annoying at times.

- cannot import other projects, or even selected sequences, using dynamic link server. Kiiiiind of a major thing...

- warp stabilizer ceased to render properly after a while, leaving me with fragmented versions of the clip onscreen every time, no matter what the method (native nesting, etc).

- random green frames when playing back or rendering certain clips.

- while color correcting over the past couple of hours, I nearly punched my screen in over the super tiny slider handles in fast color corrector, which I had to carefully click twice just to grab onto every time. MADDENING and time consuming. Why in God's green goodness did you guys do this? It's one of the most blatantly foolish design changes I've ever encountered.

FIXES (?)

I've been using your list of "dos" every few hours to buy myself more temporary functionality, but in the end the app became so unstable I decided to switch off open CL and everything started working over the past couple of hours, albeit slowly (I'm typing all this as I render 17 minutes of color correction filters).

IN SUMMARY

8.1 is hands down the worst piece of software I've ever been forced to work on. And I'm paying Adobe monthly for this service (?)

Tomorrow I'm rolling back to version 8 and not touching any more versions with a 10 foot pole until I know for sure they're solid.

Apple handed Adobe an entire legion of dissatisfied editors after the release of FCPX, and ever since then Premiere has been my best friend and worst enemy. The regular crashing issue alone boggles my mind. This issue is never addressed, never fixed, and Premier's most consistent bug. Thank God you guys don't make cars or we'd all be dead!

My patience with Adobe is razor-thin at this point, and if another NLE came up that started being embraced by my colleagues, I'd be overjoyed to jump off the occasional Titanic that is Adobe Premiere Pro.

I'm hoping you guys make me eat my words by finally getting your Mac act together. Until then I'm feeling like Adobe's battered wife, having no where else to go...

thanks for listening. I hope Adobe really hears me (and other) on this fiasco.

jesse

I have a little info that may help narrow down this sluggishness.  I recently had another spat of extreme UI slowness, and noticed that my project hard drives were chugging.  Opened the Windows task manager and noticed that Premiere was incurring a 36mb/s data transfer hit on my project hard drive for over a few minutes, even when I was doing nothing.  The new version of Premiere seems to be doing some background task that lobotomizes the UI refresh rate.  I don't know what it's doing and it just stopped.  Does anyone have any ideas what Premiere is doing in the background?

Hi Vanlazarus2013,

For that, I'd file a bug report.

I did find out some interesting issues that may be affecting performance, please check out the following.

• Turn off Show Duplicate Frame Markers in the Settings menu (wrench menu)
• Disable "Show FX Badges” in the Settings menu (wrench menu)
• Disable "Display out of sync indicators for unlinked clips" in General Preferences

Also note an additional folder that you must check the permissions for has been added to my blog post: Library > Application Support > Adobe: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)

Please check that, as well.

Thanks,
Kevin

Hi Kevin,

Ok, I've filed a bug report with the info that I have.

I disabled all the things you've mentioned and will see if this sluggishness goes away.

I'm on a PC, so I don't think those MAC folder permissions are relevant to my setup.

Do all the people reporting this problem use multiple displays or multiple GPUs?  I have a 3 display setup with 2 GPUs.

Michael

Just confirmed this again.  Premiere is doing some massive file transfer read/write in the background every time my UI becomes super slow!  This is definitely the problem.  I can't tell what Premiere is doing in the background though.  As soon as the Task Manager reports that this transfer is over, the UI returns to normal.

What also sucks about this is that my project hard drives seem very hot.  If Premiere is constantly doing something with the 8tb of Red media my project has, then I can see why.

Do you by chance have the "Automatically Refresh Growing Files" checkbox checked in the Preferences > Media dialog?

Unless you have a specific need for them, I suggest leaving all five of those bottom preferences unchecked.

Another thought:  By chance is your boot disk almost full?  If so, you may be getting continuous VM swaps on a fragmented disk; and that would certainly tend to bog a system down, and account for heavy disk activity.  I suggest you leave 100 GB free on your boot disk, especially if it's a spinning disk (non-SSD).

I turned that off (Auto Refresh Growing Files) and it made no difference.

My OS drive is a 240gb SSD drive with 25gb left, but any OS issue can't be the cause because the task that is initiating this massive and near continuous file transfer is Premiere!  Premiere reports that it has 10.9gb of RAM to itself.  Is this not enough?  Is it swapping RAM continuously to my hard drive.  Others have reported weird memory usage with Premiere 8.1.

This project worked fine on Premiere 8.0.1.  It now it does not... the only thing changed was Premiere... 'upgraded' to Premiere 8.1.  Logic would indicate that this is not a system problem, but a Premiere problem.  The task manager is reporting a near continuous massive file transfer taking place whenever my UI chugs.  When the transfer is gone, the UI is fine... normal... like it was in version 8.0.1.

I'm 100% certain that Premiere feels it needs to do some kind of processing to/for my media, and while it's doing this, UI performance takes a massive hit.

I appreciate the suggestions everyone, but I strongly doubt my system, is the culprit here.

But just to be 100% sure that program hard drive space is not the problem, I removed some content off of my SSD drive.  Now there is 80gb free on my 240gb drive.  That is 33% available space.

Went back into Premiere, and within 2 minutes Premiere started it's 35 mb/s+ file transfer and my UI chugs horribly.

I'm not editing on an external drive, so a Thunderbolt 2 connection would have no impact.  I'm using an internal hardware SATA RAID 0 setup... which should be plenty fast.  The problem is that Premiere is trying to do some major file management task AT THE SAME TIME I'M EDITING..... Imagine how your editing experience manipulating Red media would be on ANY computer if the editing program was loading terabytes of media in the background and doing some task with it continuously?....  Or try running an AME render task in the background AND edit a feature film shot in 5k RAW video on almost any computer and you will experience problems.  This is the performance hit that I'm seeing in Premiere 8.1.

Premiere 8.1 has lost it's mind and is doing some major process on my project media.... perhaps over and over again.... I've certainly seen both Premiere and Prelude lose it's mind and generate audio peak files OVER and OVER again, so this wouldn't be surprising.

Unfortunately, this is costing me a lot of time and truly reducing my Premiere editing experience.

Could this sluggishness have something to do with Premiere endlessly regenerating thumbnails for video clips in bins?  Premiere 2014.1 never remembers thumbnails for my video files and constantly has to reload the thumbnails every time I scroll through bins.  Shouldn't these thumbnails be cached somewhere?

It would be great to get some kind of status from Adobe about this horrible problem in Premiere!  Daily! Has anyone there been able to recreate this problem yet???

It's gotten so bad that I don't even get preview display.  I move the cursor to anywhere on the timeline and nothing is shown in the Program Monitor.  Blackness.  Yet Premiere is still slamming my Raid 0 project drive with 35mb/s+ transfers.  I have to restart Premiere (and wait 5 minutes for the project to load) in order to be able to see what I'm editing! 

This is intolerable, yet I have no options.  I can't redo hundreds of hours of work and recreate the film in an old version of Premiere.  I'm trying to deliver content for the American Film Market tomorrow.  ARGH!

I'm demanding a few months of Creative Cloud free for this complete disaster of a version.  Surely some software standard must be achieved for Adobe to legally charge for a product.

..try visiting the PPBM7 website and test your machine on the video benchmark for PPro.

Sometimes its a hardware issue...

How can it be a hardware issue if;

Same computer + same project + Premiere 8.0.1 = smooth UI experience

Same computer + same project + Premiere 8.1 = terrible UI experience

The only variable that changed is Premiere.  Therefore, the problem is Premiere.

I'm now getting a weird render slowdown.  Just rendered 2 1080p versions of a sequence in about 15min each.  A lower res version of the same sequence is now taking over 90minutes?!?!??!  Both using AME and both using software (cause GPU crashes).  I restarted Premiere and restarted my machine.  No difference.

I feel like I'm taking crazy pills!

vanlazarus2013 wrote:

 

How can it be a hardware issue if;

 

Same computer + same project + Premiere 8.0.1 = smooth UI experience

Same computer + same project + Premiere 8.1 = terrible UI experience

 

The only variable that changed is Premiere.  Therefore, the problem is Premiere.

 

Most likely, but not necessarily.  The configurations, software and hardware up and down the stack are increasingly complex and varied – so it's possible that a correct change at the Premiere application layer is tickling an esoteric bug further down in at the driver, o/s, or hardware/firmware level (which only some customers are experiencing on particular rigs).

Yes, this is true.  In an effort to test your theory, I reset my bios overclock to defaults, thinking my overclock was failing and causing the extreme render slowdown that started yesterday.  Unfortunately this reset my sata controller back to AHCI and invalidated my 12tb RAID 0 drive on which my feature film project was located.  I was able to recover my recent project files and all the data exists on backups but I just spent 6 hours trying to restore this raid... in vain....  Preventing me from rendering one scene we were going to show at the american film market today.  I fly to LA in a few hours, leaving my computer and project in disarray.

I can't know 100% if my hardware setup is not to blame but there is a 99% chance that it is an Adobe bug that has caused me all this grief this past week. I wish I was a David Fincher and had some actual leverage to get this issue fixed right away. 

I guess the most frustrating aspect of this is that I have no idea what Adobe is doing to try and find the problem some of us are having with the latest Premiere.  Could it be months before Premiere is usable again for me?

Sorry to hear of your troubles.  I've been there (except for "invalidating" a big RAID - that sounds terrible). 

The first time I loaded the current rev of Pr 8.1.0, it didn't respond on quite a few features (such as: tweaking Motion tab position didn't do anything, effects didn't have any effect).  I blamed Pr for having "major" bugs.  But, since then, I uninstalled, reinstalled, reinstalled my graphics and GPU drivers, io card drivers, and then Pr started working.  I've done a few projects on it since, and have only noticed a few bugs, none of which are show-stoppers.  Like you, the previous build 8.0.0 was working fine, so I came to the same conclusion about 8.1.0.  What eventually fixed it for me was reinstalling my OS.  That sounds drastic, but on OSX, you can reinstall the OS without wiping out your applications and User folder documents and libraries.  It took me about an hour (I have an SSD boot disk.).  Many people that say "I've tried everything" haven't.  Or, they don't include an OS or drivers reinstall as "everything."  My point is if there was something wrong with the software, it would likely affect everybody.  Everybody would be making the same complaint as you.

BTW, there used to be a hack to open Pr Project in a previous version that involved opening the Project file in a text editor or Text Wrangler, and changing some code at the top of the document, then Saving As.  This was a way of getting around Pr not having a Save As Previous Version function.  It worked!  I can't remember how, or if this is even possible with the current build.  But, maybe some smart person could dig in and see if this is possible with the new build.

I'm still on 10.8.5.  Maybe that's the difference.

Jim Curtis wrote:

 

BTW, there used to be a hack to open Pr Project in a previous version that involved opening the Project file in a text editor or Text Wrangler, and changing some code at the top of the document, then Saving As.  This was a way of getting around Pr not having a Save As Previous Version function.  It worked!  I can't remember how, or if this is even possible with the current build.  But, maybe some smart person could dig in and see if this is possible with the new build.

That's a good question but Adobe made some changes in the file format between CS6 and CC, so that downsaving doesn't work quite the same way now as before.

Yes, but I seem to recall the hack worked between CS6 and CS5.5 or CS5.  So, it might not be out of the question to go from 8.1 to 8.0.

For grins, I did open a Pr 8.1 project in TextWrangler, and nothing was blindingly obvious about which project version was tagged.

But, coding isn't my thing, which is why I suggested somebody with those skills take a look.

I've got the same issue. Editing a feature shot on Red Epic Dragon 6k.  It was screaming fast and handling the raw footage and the timeline was buttery until I updated 2 days ago.

Interesting things to add:

I switched from the feature to edit a corporate video that had very little footage but lots of titles and graphics, and the performance on 8.1 was excellent. No trouble at all.

Now I'm back on the feature and it's unworkably slow. vanlazarus2013 mentioned that it seems like a huge data transfer is going on in the background, and I can tell that I'm having the same issue.  My RAID drives are chugging HARD at something when I'm not doing anything. Interestingly, playback is fine for me, it's just timeline work is intolerable.

I did notice on a couple bins that were open a little indicator that said (indexing __%) flash by.  Is premiere trying to index my 22TB of material?

I should add that I have tried all of the suggested remedies here to no avail.

Anyway, kudos to Adobe for having such an easy way to roll back to the previous version. I'm all good now on 8.0, but I'm looking forward to a fix for this. I like the new blue colour.

Kevin,

I'm sure I speak for everyone here when I say that I appreciate your being very proactive on this issue.

I'm a freelancer, and I do consider regular software checks and troubleshooting to be vital to the profession. But what was an occasional run through is now a daily, if not multiple times daily task. Like RedDirt, I'm inclined to suss out the cause of a problem and solve it. I have followed every suggestion in this thread, some many times. I've had no success. I've tried a version rollback, exporting and then importing EDLs and it proved only a partial fix as many cuts proved to be inaccurate, and random spaces between clips would appear. Never mind sound, keyframes, or any other adjustment I'd made.

Since the most recent update my experience has been:

-Render time is inconsistent, regardless of GPU status. "Software only" works for a bit, but it'll eventually either crash or grind to a crawl. Besides, what do I have a souped MacBook Pro for?

-Dynamic Link regularly bogs down or crashes PP.

-Plugins (third party and bundled) bog down, crash PP, or barely work at all (Warp Stabilizer is a headache).

-Playback will freeze up in various states (won't play / won't stop playing even though the frame is frozen and doesn't respond to keyboard commands / crashes during playback).

-Different video codecs in the timeline (the first reason I purchased CC) renders the program unusable.

-Exporting media is inconsistent. Some days good. Some days I might get fired because I don't deliver until 7:30pm.

Just today I've force PP to quit a dozen times. Even if I don't force quit I get a crash report 9 out of 10 times.

My computer:

2014 MacBook Pro Retina

OSX 10.9.5

2.3 GHz Intel Core i7

NVIDIA GeForce GT 750M 2048 MB

16 GB RAM

I read that you should make sure your computer can handle an update. I thought it could.

My question is this: Can we expect an update in the near future?

With other software companies, if an update is released and within days a bug is discovered, it's a big deal, and usually patched within days. This has been my life (and judging by the forum, many other people's lives) for over a month now. You, Kevin, and you alone seem to be the sole voice addressing this from the company.

For that I thank you.

Kevin Monahan kirjoitti:

 

Hi Sakari,

What happens if you choose Project Settings > General > Renderer > Mercury Playback Engine Software Only?

If exporting, can you also see if you have problems after setting to Software Only?

 

Thanks,

Kevin

Hi Kevin and sorry for late answer - due to my work and deadlines I had the time to test only the rendering with Software Only - it resolved the rendering issues (parts with blur effect rendered wrong with GPU on), now all the parts of the video exported correctly. Unfortunately I did not have time to test more of 8.1.0 problems, instad I rolled back to 8.0.1.