Adobe Community: Message List - Walking yesterday. Crawling today.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Thu, 06 Nov 2014 18:49:13 GMT

I think Adobe needs to lock their project file format. Changing it every CC version is really a big drawback to the whole CC 'get the latest version easily' system. And if changing it every release is a must, then a 'retrograde' conversion option is also a must. On a side note, it also sucked that I lost all my presets when upgrading to the 2014 versions of every app.

I think there needs to be a project cleaner tool as well. When importing sequences from other projects, my project file has ballooned in size. It went from 6mb to 17mb by just importing a few sequences from a colleague's project file (with identical media). I'm not sure how the file structure is organized, but it shouldn't need 17mb to store locations for 8000 media files and a few hundred in and out points for the sequences. Some kind of data duplication is taking place when importing sequences from another project.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Thu, 06 Nov 2014 16:25:39 GMT

Unfortunately, we don't have a 'retrograde conversion tool' for projects.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Thu, 06 Nov 2014 00:56:59 GMT

Vanlaz, your situation sounds like an effing nightmare. Have you ever tried exporting the film to XML, and then reverting back to 8.01 in order to finish up? 8.01 still works great for me -- sounds like we are in identical situations, except I didn't have the fortitude to stick with 8.1 for more than a few minutes. You might also be able to import the 8.1 project back into 8.01?

Or Bruce -- maybe someone at Adobe can help to convert his project file back to 8.01 compatible for him, if the above are not viable?

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Thu, 06 Nov 2014 00:54:30 GMT

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.

From this thread, and regardless of how much my family enjoyed visiting Vancouver last summer (particularly Honey's Doughnuts in North Van), it seems like we should be able to repro the behavior without the travel; you're not alone. We've already been sent multiple hefty(!) project/footage bundles, so it's not for lack of source material. There is some key difference between the configs we're testing, and the terribly-performing machines noted in this thread. We are actively searching for it.

Kevin's list of things to check/change/confirm [previously, in thread] is the best place to start, for troubleshooting most performance problems.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Thu, 06 Nov 2014 00:36:27 GMT

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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Thu, 06 Nov 2014 00:26:42 GMT

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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Wed, 05 Nov 2014 23:55:49 GMT

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

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Wed, 05 Nov 2014 22:03:00 GMT

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!

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Wed, 05 Nov 2014 21:40:40 GMT

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

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Wed, 05 Nov 2014 21:37:17 GMT

+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?

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Thu, 30 Oct 2014 18:31:01 GMT

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.

>Sigh<

Yeah no. Obsolete means "no longer in use" - To the contrary 8.0 is heavily in use. If I were in a position of customer relations, I'd consider quickly giving up on defending the "obsolete" comment, it's a no win and the remark was out of place for such a new release and in an environment where a CS4 forum is violently active.

Thanks cscooper2013, I rarely buy into the "wow you are the only one experiencing these issues" spiel - it's just sometimes disheartening where I encounter it.

Moving on... I haven't seen any, out of the dozens and dozens of posts with similar issues, where the customers haven't been responsive to the barrages of scripted questions so I hope everyone is helping the greater good towards getting a nice solid release. No one asked me for project files, not that I'd have time to do that dance, but DVAGold support also hasn't gotten back to me in a week so that's neither here no there.

Rolling back literally saved my life, and as I've said before one of the nosiest releases i have seen around these parts in some time. If I spent my time piling onto every post I see come through so I could write "similar issues here" I would never get any work done. But then again I think I'm rather lucky that I am back up and working at all. Thank goodness Adobe provides a newly streamlined 2-click way to go back to those obsolete versions from oh so many hours ago.

I hear the 8.2 a comin'... comin' round the bend...

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Thu, 30 Oct 2014 13:20:06 GMT

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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Thu, 30 Oct 2014 12:18:58 GMT

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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Thu, 30 Oct 2014 09:01:10 GMT

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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Wed, 29 Oct 2014 17:11:59 GMT

OP monitors are standard Dell 2209WA at 1920 x 1080

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Wed, 29 Oct 2014 05:23:08 GMT

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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Wed, 29 Oct 2014 05:06:02 GMT

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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Wed, 29 Oct 2014 04:53:53 GMT

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).

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 27 Oct 2014 23:33:54 GMT

Should 5TB free be enough?

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 27 Oct 2014 23:13:51 GMT

This theory of course works perfectly the other way around as well...

"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 companies are not always as ready as they think they might be when releasing an update for an application, OS, or both."

Also...

Rolled back version still functioning well as far as responsiveness (thank goodness for my project) -- however I did isolate a very specific bug that I can replicate which I'll bring up in a separate post concerning using adjustment layers with the power masks.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 27 Oct 2014 23:01:53 GMT

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!!!

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 27 Oct 2014 22:39:48 GMT

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)

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 27 Oct 2014 22:37:30 GMT

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

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 27 Oct 2014 22:27:00 GMT

Appreciated RedDirt... however I was just asking that you put the single link to your original problem post inside my post here: List of Posts concerning performance issues after Premiere Pro CC 2014.1 8.1 Update

I also have been in touch with Adobe DVAGold... so far its gone something like this via email...

ADOBE: "Hello can we help you?"

10 minutes later

ME: "Yes can you work weekends and nights?"

1 week later...

ADOBE: "Yes what times in the evening are best?"

10 minutes later...

ME: "Anytime after 7:00 PM PST would be wonderful"

1 week later....

(Looks like I'm in for a long haul... but I'll keep you posted...)

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 27 Oct 2014 22:17:31 GMT

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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 27 Oct 2014 22:16:29 GMT

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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 27 Oct 2014 21:45:36 GMT

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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Tue, 21 Oct 2014 18:25:37 GMT

RedDirt... show me some love: List of Posts concerning performance issues after Premiere Pro CC 2014.1 8.1 Update

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Tue, 21 Oct 2014 18:21:50 GMT

Easy now big shooter...

The conclusion of my particular thread is specifically that I no longer have to question my hardware. Quite simply put 8.1 crippled me and 8.0 works like a charm - actually slightly faster than i remembered. Same machine. Done and done. I'm back in the game and cranking dual Nvidia CUDA's like there is no tomorrow.

Now if Adobe wants to push a future upgrade and update their minimum requirements documentation... I'd be happy to consider how thin I am at that time before upgrading, however that was not the case with this most recent push.

Honestly I think you'd be amazed at how well a working Premiere Pro (unequivocally all the way up to one version ago even) can sing on certain configs. And it's rare for a company to release a ".1" update that suddenly renders systems obsolete, if anything that would have happened on the big 2014 update and with lots of warning and documentation, not the point one.

So I'm inclined to agree with RedDirt on the type of issue we are dealing with here. I keep watching the posts on this subject come in to reinforce this. This is the noisiest release I've seen in quite awhile. Maybe a hasty .2 is around the corner.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Tue, 21 Oct 2014 16:11:35 GMT

....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 !!!

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Tue, 21 Oct 2014 15:59:35 GMT

WHY are you YELLING

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Tue, 21 Oct 2014 15:55:37 GMT

...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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Tue, 21 Oct 2014 15:14:01 GMT

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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Tue, 21 Oct 2014 15:10:18 GMT

...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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Tue, 21 Oct 2014 12:47:43 GMT

thank you, RedDirt.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Tue, 21 Oct 2014 11:38:37 GMT

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

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Tue, 21 Oct 2014 09:38:38 GMT

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...

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 20 Oct 2014 14:52:49 GMT

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

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 20 Oct 2014 18:28:16 GMT

Apparently Adobe Forum Admin disagreed with my choice as the correct answer to my own post and reversed my marking of post #33 as the correct answer. However I am now unable to go back in and edit that post to emphasize how crucially and financially important rolling back away from update 8.1 was to me personally. How it absolutely fixed my problems, and how it may keep others from missing deadlines and losing clients.

With post #33 no longer being marked as the Correct Answer it is now lost in the mix. Previous to rolling back and solving my issues I scoured the forums to see if rolling back versions had helped anyone out before blindly trying it myself, but i found no insight. Therefore I considered post #33 a very valid solution midst a world of update pain. Yes rolling back is not ideal. But neither is an update that put me out of business.

So in light (fire light?) of these Fahrenheit 451 circumstances, this is my post to sort of cap-off my OP and re-emphasize what worked for me - what correctly answered my own posted question - until I am offered a better working solution.

Rolling Back Fixed All Of My Sluggish/Crashing Problems

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 20 Oct 2014 17:29:34 GMT

bbb_999 -- I probably overreacted. Frustrated at my "reluctant fix" and sleep deprived. But FWIW it's probably not a bad idea to keep in mind that when working/paying customers reach out to these forums about an update destroying their perfect previous world - especially if their post has been around a bit - they are probably desperate - so every response or perceived attitude carries great weight.

RedDirt - I marked it as answered, probably out of spite, but also because my fix really did pull me out of two weeks of hell. I personally searched the forums to see if something as ludicrous as rolling back actually fixed this so that people could at least function and couldn't find the answer. So when i tried it and it worked i was both overjoyed at my present situation and angered that this is what i had to resort to (I just don't have another 2 weeks to troubleshoot this) and Embittered Temporary Fix wasn't a choice.

All - I have no idea if this will help Adobe, but I am going to start a new post to try and connect all of these similar issues. Every time I look at the forums there is at least one new similar situation in the top ten posts.

Here: List of Posts concerning performance issues after Premiere Pro CC 2014.1 8.1 Update

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 20 Oct 2014 14:05:25 GMT

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

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 20 Oct 2014 11:20:34 GMT

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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 20 Oct 2014 11:04:21 GMT

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

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 20 Oct 2014 08:59:04 GMT

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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 20 Oct 2014 07:35:20 GMT

bbb_999 and Adobe-Team,

I am having exactly the same issues (however, I stated it with "video freezes"). If I click some timepoint in a sequence, it takes up to 60 seconds until the program-window "reacts". If I add an effect, it takes about 1-2 minutes until I see changes of this effect in the program-window. If I press the play button the video plays choppy...This happend after I had to install (yes, a must, as I need dynamic link to Speedgrade) the new Premiere Version. Everything is still fine in the old version of Premiere.

I am so disappointed and frustrated about a service I have to pay for, which does not work properly and I spent hours of error-solving...really Adobe?!?

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Mon, 20 Oct 2014 00:19:03 GMT

Cadillac, I hear you. BTW, not sure who noted your answer there as "Correct Answer" -- but I think that's deceiving. "Workaround" might be right, but reverting to 8.0.1 is not a fix. 8.1 update delivers other enhancements which we should be able to benefit from, based on paying a monthly fee for the latest updates. I recommend (to whomever marked it "correct") to unmark it as such -- this ain't fixed.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Sun, 19 Oct 2014 22:43:17 GMT

I'm having the EXACT same issues. In fact, I posted a thread prior to seeing this one:

https://forums.adobe.com/thread/1611940?sr=stream

I did a fresh install of Windows and started everything from scratch. Notta. The problems still persist. The same issues the posters above me are having.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Sun, 19 Oct 2014 19:05:25 GMT

Sorry if I rubbed you the wrong way; any guilt was unintentional.

Mine wasn't, strictly speaking, a customer service response; it was an offer to have you work directly with PPro team members in an attempt to resolve your issue.

If you have a working setup, great. If you'd like our help, let me know.

-bbb

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Sun, 19 Oct 2014 17:54:29 GMT

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.

Re: Walking yesterday. Crawling today.

forums_noreply@adobe.com — Sun, 19 Oct 2014 13:59:52 GMT

Glad you have something working; still, staying on obsolete versions rather than figuring out the actual issue is a solution without a future.

We've offered to work with you to find a solution to the problems you've encountered; let us know if you're interested in resolving the issue.

-bbb