XDCAM EX playback issues

[Bob Ramage]

I’m having a similar problem with EX1 footage using PPro CS4 on Mac OS X (on a Mac Pro workstation). I can edit for a while, but eventually the program locks up. I started watching the OS X Activity Monitor while editing and noticed that a CS4 application that loads with PPro called “ImporterProcessServer” seemed to be the culprit. When PPro locked up the ImporterProcessServer suddenly spiked in both CPU (to 100%) and RAM usage. You might want to check the Task Manager in Windows and see if the ImporterProcessServer is doing the same for you.

For me, the problem seemed to crop up after I updated After Effects to 9.0.1. Prior to that PPro had been solid.

[Marc Bauwens]

Hay Bob,

I’m having a similar problem in that the CPU activity is at 40% for a while and then the activity of ALL 4 cores spikes to 100%!

I’m not aware of the software process that you mention, but I see a clear pattern here.
I definitely think that it is a software issue. I have to admit that I have no experience prior to the update, as I updated to 4.0.1 immediately after installing.

Could it be memory leakage or something along those lines?

Adobe, get your act together please …

[Marc Bauwens]

Under Windows it doesn’t seem to be the application you mentioned because with me it remains stable at between 20 and 25% CPU charge.

What happens it that PPro goes from 23% under normal conditions to about 80% CPU charge when playback starts to get choppy and then all 4 CPU’s go thru the roof and flatline at 100%.

I have one wicked system so playing back EX1 footage isn’t an issue, proof being that the Sony mediabrowser handles it without any issues at all.

My feeling is that Adobe flunked it on this one and that the code is not ok in regard to playback of these new formats.
I’ve read a lot of grief about users trying to play back AVCHD footage and man, are they angry…

I can legitimatelly understand that when you hand over a wad of money it’s supposed to be working and what also intrigues me is that there is no response whatsoever from Adobe.
For now I’ll try to live with the issues on playback and try to find a workaround.

I already tried a conversion to MXF from within the Sony Mediabrowser with the same results so my best guess is that Ppro is messing it up.
Hopefully there will be a fix for that soon.

If you find any workaround please let me know.

[Bob Ramage]

I think the problem is a memory leak in Premiere Pro. I tested my RAM (I have 16 GB) and it was fine. I’ve got CS3 on the same system and it works great with EX1 footage. My interim workaround will be to revert to editing with CS3.

[Mike Cohen]

there are many threads further down the board about CS4 “issues”. Adobe must test the new software on the WOPR.

Growing pains.

[Bob Ramage]

I found the solution in my case. It seems that Premiere Pro doesn’t like having the default BPAV folder for EX1 footage named anything but BPAV. I had used the names BPAV1 and BPAV2. I noticed that PPro CS3 wouldn’t import the BPAV1 footage (declaring mp4 footage as “not supported”). When I renamed the BPAV1 folder to “BPAV” the footage imported correctly to CS3.

Suspecting a similar problem in CS4, I opened up the project that had been causing the “ImporterProcessServer” freezes/crashes. Since the source folder had been renamed from BPAV1 to BPAV I had to manually relink all of the EX1 footage – a royal pain. It was worth it in the end though, as it appears to have solved the problem. Footage plays very smoothly and despite my best efforts I haven’t been able to provoke a freeze or crash.

Seems like the “ImporterProcessServer” is somewhat fragile. I would recommend making sure you use the default folder structure as originally transferred from the SxS cards.

[Bob Ramage]

Another thought. The project I had been working on originated in CS3. When I upgraded, I opened it in CS4 to continue work. I did the same with another DV project. in both cases, I noticed that performance seemed sluggish compared to CS3. And of course eventually I started getting the “ImporterProcessServer” freezes/crashes with the EX1 project.

As I mentioned, when I renamed the “BPAV1” folder to “BPAV”, I had to manually re-import and link all of the EX1 footage. It’s possible that it was this process which inadvertently solved my problem, and that it was the translation from CS3 to CS4 which caused it.

After I had reimported the footage, the freezes/crashes stopped and CS4’s performance became fast and smooth. I noticed however, that two previously edited multi-cam sequences were screwed up. Edit points no longer made sense and clips had shifted mysteriously.

Bottom line: it’s possible that the conversion process from projects created in older versions of PPro to CS4 doesn’t work correctly, and can lead to the “ImporterProcessServer” problem.

[Marc Bauwens]

Bob,

I tried the proposed solution, but no joy…
It plays and then stutters, before playing again.
It doesn’t lock up any more, but performance is just terrible!
Also I have the impression that when it plays smoothly, it is not real time.

Any further thoughts?
Thanks,

Marc Bauwens

[Bob Ramage]

Sorry Marc, but I don’t have any more ideas. As I noted, my project was started in CS3 before I opened it in CS4 and started editing. Performance was sluggish and I soon started getting the “ImporterProcessServer” freezes/crashes.

The steps that worked for me were to rename the source folder holding the EX1 clips, then manually relink all of the footage in the PPro CS4 project. The difference in performance has been amazing. Response is very fast and smooth, with no hesitation whatsover when scrubbing or playing at various speeds.

Did you start your project in CS3 or was it CS4 from the start?

[Marc Bauwens]

Bob,

My project was started in CS4, and so far the problem remains.

Thanks for your help anyway, I’ll try to find something else.