Walking yesterday. Crawling today.

Formats?

Editing footage directly from Canon 5D MKIII if that helps.

Fairly smooth 24 hours ago, not so much now.

No - the footage is in the file structure I described in my OP. I just meant as far as file type its the footage right out of the camera.

Hoping someone else sensed a change with the update.

This thread also describes what i am experiencing: How do I roll back the 8.1 update back to PP 2014 8.0?

Again I don't see how your recommendation can be anything more than rollback, wait for the fix, or get a new computer based on the main theme of my issue - everything worked before the update.

However I will provide as soon as I'm at my system, thanks.

You are one lucky b*st*rd shooternz - but please don't rub it in -- A quick scan of the forums shows I'm not alone on this one -- annoying at best.

OK Kevin Monahan here we go:

Windows 7 Home Premium 64bit

Alienware Area 51

i7 CPU 930 @2.80 GHz 2.80 GHz

12 GB Ram

Dual (2) NVIDIA GeForce GTX 680

Anything for me Kevin Monahan?

OK assuming you mean this specific bit:

go to c:-program files*86-common-Adobe-SLCache, rename the SL Cache to old SL cache

go to c:-Program Data-Adobe-SLStore and rename the Sl store to old SL Store.

Program Data is a hidden folder so have to change the view option in order to find the folder.

There was no effect.

Additional insight for you/the group:

• I had none of these "specific" issues pre-update. (Have I mentioned that yet?)

• Everything is painfully sluggish like never before, the UI sort of loads one panel at a time.

• When I double click on one of the source ".MOV" files (vs a sequence) in the timeline I get faded white screen and she locks up and spins until I force close.

• I have not yet tried a new project from scratch - all of my tests are on projects I've had to "convert" to the new version upon opening them - because i was mid project when i stupidly decided to update... of course.

Yeah you would think a version update wouldn't be violent enough to render a project from the very previous version unusable.

Alas...

So wait... are you saying if i start a fresh project from scratch from right within the 8.0.1 environment there is some percentage chance I will not have these issues?

Hundreds of thousands of Creative Cloud users? Or Adobe Premiere specifically?

OK I'm game - I don't have much more I can lose at this point. New project from scratch - I'll load it up with all my normal tabs of sequences and effects and see if she holds water any better.

Talk soon...

OK so I not only started a new project from within 8.0.1 I also ran over to RedDirt's post and followed the non-Mac-specific steps.

I feel like things generally became more stable - but as many report - after an hour or two of working and piling on top of the footage things more or less return to a sluggish state - kind of like you are afraid to click anywhere or drag the timeline bar for fear of sitting and spinning.

That being said there is one specific set of circumstances, that unfortunately I use in my day to day, that is a showstopper. I was able to more specifically nail down this very bad issue... and recreate it at will.

I have one sequence tab open (Scene 1) that has several sequences within it (Shots (sequences made from original source camera clips))... then I do a subsequent tab/sequence that sucks in the "Scene 1" sequence (lets say Vignette). Then I have a subsequent sequence/tab that sucks in "Vignette" sequence, and so on for about a half dozen tab/sequences or so, each sucking in the previous sequence. Now, if I have all those tabs open, generally speaking, I can move about amongst the tabs pretty freely, better than when i first posted for sure, but yes noticeably "different" and clunky from time to time. Now if I go back to my first "Scene 1" sequence and double click one of the "Shots" sequences it contains (which would take me to the original camera footage clip) everything goes bad. Back in the day (Yesterday) before I made the suggested changes it would white screen overlay and spin until I force closed it. Now it white screen overlays and spins but after a long minute or so it will come back and finally pop that original camera clip (for example 2A0B2218.MOV) as a tab as expected, although it takes far to long to be acceptable. Anyway, wow that the 2A0B2218.MOV tab is finally open if I then go to click back on the original "Scene 1" tab everything freezes once again, white screen, timer, wait a couple minutes and so on. However oddly, I can click on any of the interstitial tabs (like Vignette or Color Grading) at this time and those behave as expected. But as soon as I go to click back on the "Scene 1" sequence tab or the now open 2A0B2218.MOV tab everything again goes sideways.

So in a nutshell, as of now anyway, when the "Scene 1" tab is open at the same time the original footage tab (2A0B2218.MOV) is showing on the timeline - if I so much as click to switch back and forth between those tabs, or if I dare to scrub along or click into either of those sequences it will freeze - white screen/timer spinning... sometimes it comes back, sometimes I have to force close. When I close the original footage tab things generally come back to normal new 8.0.1 sluggish vs completely unusable sluggish.

I am only using 2A0B2218.MOV as one example - it happens with any of the sequences made from source clips within the Scene 1 tab.

I hope I am explaining this correctly as its very specific and recreate-able. Screenshots attached.

Hoping my overly detailed explanation helps?

I am also starting to wonder if the pseudo-crash is related to clicking on clips with the power mask(s) - but haven't had the chance to verify yet.

No effect except my playback becomes choppy/non-existent on sequences with heavier effects.

I have to say "playback" is still about the only thing keeping me in the game - its not choppy and generally pretty smooth.

But doing something non-playback related - like trimming a clip, or sliding a clip a little up or down the timeline, causes a total delayed reaction where nothing happens, everything kind of freezes for a few moments and then suddenly the clip blinks to roughly where I let go of the mouse when things froze.... never experienced this prior to 8.0.1

Help?

Also the more I work the worse it gets. Dragging an RGB curves effect on to a sequence takes around 60 seconds or so to finally "pop".

Switching between sequences by clicking a new tab takes at least a minute to finally switch to the tab I selecetd.

Exporting is lightning fast.

manfredhaider...

Playback does not freeze for me normally - unless I turn off MPE Hardware Accelerate as instructed for troubleshooting here.

It is manipulating the sequences in any way that causes huge pauses and lag... and anger.

The mystery of the re-arranging disappearing sequence tabs is allegedly fixed in some future update, as adobe support mentions towards the very top of this thread.

None-the-less yes very frustrating... crippling actually. An unshakable feeling off here yesterday gone today.

Seems different.

All of my exporting, playback and rendering functions have remained unscathed - still very good.

All of my showstopping experiences seem to be 8.0.1 UI related, unacceptable unresponsiveness, sliding things around the timeline, adding effects, even right clicking on a clip to get the pop up menu now takes forever.

So you aren't buying that you and i are the only two of hundreds of thousands experiencing this

My main question to you is... were you fine the hours before D-day?

OK... I have the exact same sequence config you describe plus a bit more - so several scene sequences (which themselves contain many small clips (shots)) that are pieced together in a master sequence. However then I take that master sequence and pull it into say a vignette sequence and then i pull that one into a color grading sequence and so on until I get to what I call the final sequence which is where I add letterbox and export. So yes lots of nesting - which has always helped my workflow - as taught to me by one of the masters on this very forum - and of course has always worked until that fateful update.

1) In a nutshell I have some masking and lots of RGB curves. More than this of course but that's the basics. I cant pinpoint yet if the issues are effects-centric or not. Canon 5D MKiii footage as mentioned.

2) If you look in my effects tree there is an old red giant that I haven't opened and applied to anything in years and my 3rd party noise reduction software which I am also not employing. These things just keep finding themselves into my effects tree when i upgrade but I never open the folder and use any of the effects on any of the clips - so I am assuming this is a non issue. Unless merely having them be "available" could cause issues like this? I also use LookLabs Speed Looks on the later sequences - these have always slowed down my playback - but never on the prior sequences or heavens forbid caused clunky pauses on the raw scene building sequences where nothing intensive is going on yet. I also dont consider those third party since they are available in Speedgrade.

3) I use Harm's recommendation for a 3 drive set up on the drive assignments. (dont know it by heart and the forum link escapes me atm)

4) No RAIDS (had a tragic tragic experience with RAIDS once that we shall not speak of - so no longer worth the perks to me)

5) Nothing fancy here. Just running dual Dell HD monitors out of my card.

6) Per supports recommendation in this thread I tried a project from scratch. No change in the symptoms.

I just received my Adobe "thank you for paying us this month" email and it suddenly hit me... I am very pissed off here.

If I drag RGB curves effect for example onto a sequence I have to sit there and watch a static screen for 120 seconds before it actually appears.

And now my situation has worsened. If I start sliding enough clips around on the timeline after the sluggish unresponsiveness finally gives way I am actually getting the intermittent "Adobe Premiere CC has stopped working".

Are there any solutions or actions left for me to take? I feel I have overly described my situation in great detail to no avail.

If I have officially been filed under some one percenter customer support lost cause I believe I need to at the very least roll back to the previous version.

I am stressing about losing clients and missing deadlines now -- and yet I am still merrily getting charged for my pain. Ouch guys.

Where are we at?

I rolled back to the previous version, rebuilt a project from scratch, set it up with all of my sequential sequences, loaded it with effects and power masks and worked with it for a couple of days.

100% back to normal with no issues whatsoever.

On the old 2014.0 single barrel version I stay.

Adobe, if I had a second machine, no cash related deadlines, any sort of downtime, and if I wasn't paying for your product (or you decided to pay me) I would be happy to troubleshoot this with you for another 2 weeks of my life. However that is not my reality at this point in time.

Wow. Very interesting "customer service" response.

Oh my I hope a version from a few weeks ago isn't "obsolete" in an environment where there are still forums dedicated to Premier Pro CS4 and earlier.

>> We've offered to work with you to find a solution to the problems you've encountered
I believe I've more than adequately described the criteria necessary for me to continue working for Adobe instead of myself. Please note the start date of my post, and then today's date, and then google the most popular adages/idioms of all time. Figuring out solutions with a future is something I admire but choose to leave to the "professionals" who have specifically chosen to spend the invaluable hours of their day on. I've been more than accommodating.

Here's to hoping your next release is compatible and complete.

My advice? Why sure. Instead of using energy to make me feel guilty for needing to avoid something broken so that I can put groceries on the table (and cover my Adobe subscription fee), I would instead focus on scouring the forum and connecting the dozens of similar posts concerning sluggish performance on this release. Then I would carefully browse the thread I've created right here to eliminate all of the "check your system, it's your hardware, what has the user changed" questions from the script and embrace the scientific method handed to you, with zero variables. Unequivocally the old version works for me and the new one doesn't. I am the perfect litmus. I'm no expert - but I would get the lab to test on those cards I am running in crossfire.

I'll check back after I've made up for my 2 week loss.

Emotionally drained, but by golly I will not be made to feel dirty for doing what I had to do to have software that I pay for, and therefore an editor (me), that is finally working once again.