Thanks for the quick response, Kevin. But sadly, that plist file doesn't even exist on our machines. Besides, we don't seem to have issues with looping or stopping playback early. It's more about the playback stopping the moment we hit the spacebar...instead of "getting around to stopping when it feels like it" a few seconds later.
Try a test without the SAN or eSATA drives. Try a second internal drive or FireWire 800 drive.
Our GLYPH's run on eSATA and FW800 which gives us the same, intermittent problem. Using an internal drive is unrealistic because of all the sharing we do in the office. Also, the sheer volume of footage we're using would fill up a 2TB internal quickly. We've got 80TB of SAN storage as it is...and it's filling up fast.
With two shows currently in production and two more on the way, we've got to figure this out soon!
One of the things that I've read about and been told about is the Media Cache. Our editors have shown impatience waiting for Peak Files to generate or Conforming Video to complete. Sometimes (usually) they'll start working with Premiere before it's done conforming or generating. I'm told this can create problems with Premiere at their station not just while the files are generating but from that point on, and also that these files will have to generate AGAIN when the project is taken to another station.
I'm wondering if setting the media cache to be in the same folder as the footage will help prevent generating these files each time a new editor is working on a project. in fact, there is a setting for "save media cache files next to originals when possible". if our cache files lived with the footage, presumably, no one would have to wait to generate them. however, i'm ALSO told that cleaning your cache every 3-4 weeks is important and i am not sure how we'd clean the cache if the files are spread all over the SAN system in footage folders.
My head is spinning.
Eric, I have nothing to offer, sorry.
As my shop migrates from Final Cut Pro to CC we're shopping for a shared media storage system for two seats of Premiere. I'm reading every post I can find on this topic.
The advice I have located, from advanced users and some Adobe people who participate on the forums, is that Premiere is not designed for networked operations. End of story. Everything else is a hack.
Shared read/write access to a single media library is a touted feature of several mfrs' SAN and NAS products. I have no idea if any of those devices actually work, that's what I'm trying to find out. Was multiple user-access in Premiere a feature that your SAN provider promised? Maybe your problem is with them, not with Adobe since, as I've been told, Premiere simply does not function well on a network.
Hope you get it figured out.
Message was edited by: bogiesan
We have multiple user READ access but single user WRITE access which makes the whole thing difficult. We hope to find a solution with the loggers and assistant editors and start with them on their end, but it's proving a major headache.
Our software for the SAN is FibreJet. Seems really stable. We've been using it for as long as we've been using PrePro (3 months) and it's been great...only problem is...Premiere seems to be having the problems you talked about. Maybe it's just not ready for teams/networks. This is bad news for us and for any major production company trying to get their product out there quickly.
I just had a similar issue after upgrading to Premiere Pro CC 2014 - had all the performance issues described and working with an external (LaCie Thunderbolt) drive.
What I tried was opening a new project in PP CC 2014, and importing the old project via File > Import and saving it as a PP CC 2014 file.
The program then indexed the file over again, and the whole thing seems to be playing back great - no lags or whatnot thus far. The fresh new file and re-indexing all the material seemed to be key in getting performance back to normal. Hope it helps!
MacBook Pro Retina, Mid 2012
OS X 10.9.3
2.7 GHz i7
NVIDIA GeForce GT 650M 1024 MB