Premier pro cs 5.5 program monitor freezing cronically

[Petros Kolyvas]

Are you using any external/boradcast monitoring?

We had lots of trouble like this when using the MXO2. We’ve since switched, but the program window continues to freeze periodically although with our non-Matrox hardware, the broadcast out continues to work during timeline/sequence playback even if the program window isn’t updating.

You could try clearing out the media cache as well as the previews.

Hopefully someone else has more constructive comments for you – I know how frustrating it can be. It’s definitely an area where Premiere isn’t yet as realible as other alternatives.

—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

[Toby Wilson]

Hey amazed at the quickness of the response!
Yes i do use a external monitor but just a lcd not a broadcast one. I also thought that this may be the case so i did a full shutdown and then started up with no monitor connected. No luck.
maybe there are conflicting .xmp files that are messing with the media. i will clear the entire preview cache soon so im hoping that will work.

[Gerry Curtis]

I’ve found that large stills will cause this behavior, over 3K, so perhaps one of your graphics is causing the problem? What kind of media are you working with and does it happen on a particular clip?

Cheers,

Gerry

http://www.digitalkilnstudios.com
Color Reel

[Toby Wilson]

yes! did not think about this. i am working with a 2k painting with light sequence so that could possibly be the issue. i will report back

[Toby Wilson]

so i tried these things to try fix it with no results.

Exported any sequence over 1080 as a prores file and then removed all associated files and sequences:still have the freeze
I also opened old projects that were all 1080 native and they worked fine so it is definatly project specific i just cannot nail down the problem which is super frustrating as i only need to make seven changes before export but cannot edit and grade blind as it will not even render a frame for magic bullet looks.

[Petros Kolyvas]

I suggested this in an unrelated issue thread, but have you tried importing the sequence into a clean, new project? It’s my go-to solution with the occasional problematic sequence.

—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

[Corey Sullivan]

I have 4 NLE’s set up, all in the same configuration, but I’m having that issue on just one system. I’ve checked the drivers, cleared the cache, and even swapped video cards, but this one system continues to have the problem. The other three systems are fine, so I guess I need to dig in and figure out what’s different with the one that’s sick.

[Toby Wilson]

hey i did get mine working eventually. i think its either a .xmf file issue or a issue with over 2k resolutions that are jpegs.

What i did:
cleared cache.
cleared preferences
exported any jpeg sequence as a prores 422
deleted all jpeg files from the import bins
deleted all rendered previews
closed project and force quited all premier related processes such as pproheadless and adobe server
re-opened project and then replaced the jpeg sequences with the prores files.
rendered entire preview sequence

has been working fine ever since then.

There it is
https://vimeo.com/37939248

cheers
Toby Wilson

[Greg Laff]

I am having this issue now. I can scrub through the timeline, save, and other stuff but it wont change frames in the monitor or playback at all. Its so annoying! 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

[Toby Wilson]

Hi Greg,

I think this issue could be directly related to hard drive speed, i am running raided drives now and have no issue.

If you download black magic disk test and run it from your raw drive and scratch drive i think you might find they are the problem.

My raw drive is around 80-90 write and 90-100 read and i have no issues on that.

Editing HD and higher is almost impossible without a fast drive going through a fast connection like esata or thunderbolt.

Cheers