-
So what the heck is going on?
For about 2 years now I’ve been trying to give Premiere a chance. Both on my MacPro 1,1 system, and more recently on my i7 iMac. Both with 16gigs. I’ve tried CS5, 5.5, and now CS6.
This was happening with my Matrox mini and the old MacPro, but I assumed with CS6, and iMac, and Blackmagic Intensity Extreme, that it was a whole new set of gear, monitoring, and software. But no, it occurs on Both BMD and Matrox hooked up to the iMac on CS6…
After I dunno, 10 minutes of fooling around with Premiere, it just stops. Not a freeze mind you. The Program window goes blank. Not black, blank. I can move the playhead around the sequence, but it won’t play. If you go to the force quit panel it doesn’t say the app isn’t responding. It’s not beach balling. It’s not frozen. It’s just not DOING anything.
So, over the last 2 years every time I toy around with this thing it seems to happen. I can’t figure out the link. Different hardware. Difference Mac OS’s. Different PPro software. Perhaps it’s the ProRes files I’m playing with? I don’t’ know. There has to be some connection. But I figure it’s been happening to me for 2 years so the folks on the PPro forum should know what’s up. At this point it seems like such promising software but I can’t trust it and just put it in the “unstable” category and move on hoping for Smoke to come up with something that just works. Sad really because I use after effects, photoshop, illustrator, even dreamweaver, for the last 16 years and it’d be nice to bring it all together.
-
8 Replies
-
I don’t have experience with monitoring hardware like you’re using, but I can suggest a couple things:
– Did you download the 6.0.1 Premiere Pro update that just came out?
– Do you have cs6-specific drivers installed for your monitoring hardware? They changed the way this is set up in cs6, so you don’t need a sequence specific to your hardware.
______________________________________________
“THAT’S our fail-safe point. Up until here, we still have enough track to stop the locomotive before it plunges into the ravine… But after this windmill it’s the future or bust.” -
“hoping for Smoke to come up with something that just works”
After some personal experience with the 2012 linux build I really wouldn’t bet on that.
-
I’ve heard similar from 2012 users. But then they saw the 2013 demo and were like… OH! now that’s different!
So how do you feel after seeing the 2013 demo? It looks pretty capable, except it doesn’t have multi cam at the moment.
I’ve been kind of a final cut, after effects kinda guy so I figured CS6 would be the route. But I’m looking toward DaVinci too and Walter Biscardi’s notes about CS6 and DaVinci are disheartening.
-
Haven’t downloaded 6.0.1 yet.
And yeah, my drivers for hardware are all current. I’m monitoring via the playback options where BlackMagic and Matrox have their own particular settings.
Starting to think maybe it’s just ProRes sequences derived from FCP 7 XML exports. It’s amazing how that works. I need to keep track of what kind of project it is when it locks up. Maybe there’s just something wrong with the XML transfer.
-
CS 5 and CS6 are very smooth and fun to work with on PCs. May be it’s just the ProRes and XML export as you guessed.
-
Matrox JUST released a new set of drivers for CS6. Also update to premiere 6.01 and see where you stand.
-
I’ve had this problem before, but it usually comes after a couple hours of work. It happens to me so infrequently that it never disrupts my work too much, and I can’t reproduce it for the life of me.
It happened for me in CS5 and 5.5, has yet to happen in CS6.
Not using any I/O devices myself, so that’s not likely the problem. Especially if you’re experiencing it with both BMD and Matrox devices.
I’ve noticed this happening less often now that I’m getting more comfortable with native workflows, so maybe it is a ProRes thing?
For me it never disrupted any of the menu functions (just the timeline), so I’d save, quit, and relaunch. I thought it might be a problem with the cheap Firewire disks I was using at the time, so when it happened I’d remount the disk to be safe. Who knows if that actually did anything, though.
-
I am having this issue now and I find that it happens when I switch to other applications like an internet browser or an audio program like VLC or FL Studio. It seems to be related to audio playback devices and/or Premiere Pro Layout files(.xml).
I haven’t figured out a permanent fix yet but if you shut down and go to documents/adobe/premiere and delete the whole folder it will start working again until the next time i try to use another program with audio playback at the same time as Premiere Pro.
I had to share my story in hopes someone finds a solution. email me @ illestmindset@gmail.com
Reply to this Discussion! Login or Sign Up