Adobe Premiere Pro CC 2015 won’t play after pressing space bar or play

[Ken Cooper]

This is happening in non multi cam projects….I am shuttering…ready to move to the multi cams very soon with tons more footage.

Best regards,

Ken Cooper

[Mike Postupak]

Apparently something with the footage maybe or Premiere reading of footage (although Premiere handles codecs better than most other NLEs)

Some other people have seemed to have this problem a while ago.
https://forums.adobe.com/message/6515636

Spending some time Googling on this error might help. It comes up with a few hits.
Apparently people have gotten this error with FCP also. Seems like a uninstall and reinstallation of Premiere fixed it for many.
Maybe try posting your question as a new thread more eyes will see it. Actually I think there already is a thread on the ” low-level exception” https://forums.creativecow.net/thread/3/942816

[Ken Cooper]

Mike,

Thank you so much for your kind help. Maybe I’ll try the uninstall…reinstall. Again thanks very much for trying to help.

Best regards,

Ken Cooper

[Brian Gilbert]

I just ran into a similar problem. User had a year-old project wrapping up, but it refused to play the sequence. Also refused to render anything, “unknown error”. We tried many of the suggestions; deleting cache, deleting renders, turn off GPU rendering, blow prefs with shift-option when opening Premiere, copy/paste to new timeline. Nothing did the trick. Couldn’t use 2014 Premiere, the project wouldn’t open there. (We’re on 2015.0, build 9.0.0 (247))

I discovered Premiere would play another seq just fine, but if I tried to play the problem seq, nothing would play anywhere until I restarted Premiere.

What DID fix the problem (thanks Ben!): Started a new, blank project, and imported just the final master seq from the problem project. Boom, it plays and renders.

Hope this helps someone, it’s sure frustrating until you find an answer that works for you.

[Olivier Aubut]

We had that happen on one of our iMac with Nvidia GeForce GPU. Installing the latest Nvidia Web driver seems to have fixed the issue for now.

Hope this helps.
Olivier

[Drew Lahat]

So basically this error can be caused by anything the sun. 🙂 About as specific as Avid’s “Bus Error in Main Thread at address 0x0″…

[Greg Hughs]

I am having the same problem. Managed to snatch this error message before getting the dreaded “General Error” message. Any idea what this means, Adobe?

[Bayard Stryker]

I had this problem with Premiere Pro CC 2015. I changed the audio hardware settings and it worked! Finally it plays back. All I did was change the default audio input from Apollo (a usb audio device) to default mic input. My guess is that the audio settings get corrupted and caused the error. Premiere rebuilds this setting when you change the inputs or outputs. Hope this helps for other users.

[Ahmed Elshabrawishy]

Yes, same thing here. I would also like to add that this is happening with my dual processor quad core intel xeon 32 GB RAM mac pro, while none of this is happening on my 6 GB RAM core I3 sony vaio running on windows. It is also worth mentioning that I’m using a Black Magic 4K SDI card on my mac pro and seems it could be the problem since I’ve read a lot of complains about that, but I’m still looking into it.

Have you found any other solution?

[Julian Poon]

An AE in my studio was having problems getting multi cam footage to play after being added to a sequence in Premiere 2014 version 8.2.0 on OS X Yosemite 10.10.5 (141F1808) on an Ultimate iMac 14,2. The AE was able to scrub through the sequence and see in the viewport the reflection of that scrubbing in real time, but using the spacebar / clicking on the play button in the viewport had no affect.

Oddly enough, if one just dragged the multi cam footage from the asset / file browser back to the sequence it resolves the behavior of the spacebar / viewport play button from not working. We have no idea why, but I thought that I’d mention it here since so many others don’t have a fix.

I didn’t necessarily have the time to sit down and see if this was someone else’s workflow to get it working again, so apologies in advance if this has already been mentioned.

Happy editing!