Copy link to clipboard
Copied
Production Premium CS5 has always worked fine for editing DV content. But I've just graduated to AVCHD format (from and Olympus OM-D E-M5), and have problems with scrubbing and been unable export reliably. The common thread seems to be that, when things go awry, the "Adobe QT32 Server.exe" is chewing large amounts of CPU and never exits. Sometimes Premiere crashes, sometimes it just hangs (Not Responsive) and I have to kill it.
It's a pretty simple experiment: I have about 35 minutes of clips. I automate them to the timeline. Problem 1:
Problem 2:
Problem 3, Exporting via the media encoder:
The machine is an i7-960 with 24G of RAM, and an Nvidia GeForce 560 Ti. Lots of RAM and CPU. Several disks, but no RAID. I've tried moving the media cache to SSD - no change.
As I say, I've turned Mercury on/off, with no effect.
I've completely deregistered, uninstalled, restarted computer, reinstalled, reregistered CS5. No effect.
Aaargh!
Although that camera records to H.264, it's not AVCHD, which is a very specific subset of the H.264 spec. Further, it records H.264 to MOV files, which forces Pr to use its own Quicktime importer in a 64-bit environment. Apple's Quicktime is still 32-bit, which is why Adobe had to come up with their own 64-bit importer for some QT codecs. NB: I'm assuming you're using Windows 7 64-bit based on clues that you left in your post, but you didn't say. If you're using another operating system, the
...Copy link to clipboard
Copied
Although that camera records to H.264, it's not AVCHD, which is a very specific subset of the H.264 spec. Further, it records H.264 to MOV files, which forces Pr to use its own Quicktime importer in a 64-bit environment. Apple's Quicktime is still 32-bit, which is why Adobe had to come up with their own 64-bit importer for some QT codecs. NB: I'm assuming you're using Windows 7 64-bit based on clues that you left in your post, but you didn't say. If you're using another operating system, then my advice may change.
Try changing the file extension of the .mov files to .mp4. You might be able to get Pr to use its H.264 importer instead of the Quicktime importer, which should give you better results.
Jeff
Copy link to clipboard
Copied
Yes, Win 7 64. The camera manual isn't particularly helpful, wrt which formats the camera is generating. Which preset should I use?
Copy link to clipboard
Copied
I can quickly say that seems to have resolved problems 1 and 2. Will take awhile to test the export.
Copy link to clipboard
Copied
Good news.
Jeff
Copy link to clipboard
Copied
Exporting worked too. My faith in adobe is restored! Sure wish I'd asked, before fighting with it so much.
Thanks for the advice.
Copy link to clipboard
Copied
You're welcome.
Jeff
Copy link to clipboard
Copied
Just drag a clip from the Project Panel to the New Item icon at the bottom of the panel. It will automatically create a proper sequence for the clip.
Jeff
Copy link to clipboard
Copied
Hi Jeff,
I'm experiencing this issue as well. It just started happening recently as I've edited a few videos with Pr. I'm on a Mac (specs below):
Model Name: MacBook Pro
Model Identifier: MacBookPro9,1
Processor Name: Intel Core i7
Processor Speed: 2.7 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 8 GB
Any help would be greatly appreciated.
Copy link to clipboard
Copied
But why is this program is 32 bit instead of 64?
Can we avoid using 32 bit exporter buy installing QTlite codec for windows instead of regular QuickTime?
The problem I have is strange, but... All 32 bit apps hungs my system. And this server too. And the same time I can't refuse using mov.
Copy link to clipboard
Copied
"Adobe QT32 Server.exe" is an essential part for the Adobe applications to launch.
And there is a instance of it running for Premiere, AE and Media Encoder each.
Killing it is not the solution as it is used by all these applications.
Can try to reset the preferences and check if that works. Also right click on the application and choose" Run as administrator ".
Also can try to create a new user account t see if that works.
Copy link to clipboard
Copied
Killing it is not the solution as it is used by all these applications.
Unless you don't use QuiRcktime ever, then it can safely be killed. Who is interested in using SLOWtime or QuiRcktime when it destroys the 64 bit nature of PR, I wonder.
Copy link to clipboard
Copied
In my case, killing it was essential, as it was non-responsive. Often, it took Premiere with it. And it didn't shut down once Premiere closed down.
Following Jeff's recommendation and renaming the files .mov->.mp4 solved everything. "Adobe QT32 Server.exe" is still running, but it isn't doing anything.
Copy link to clipboard
Copied
Following Jeff's recommendation and renaming the files .mov->.mp4 solved everything. "Adobe QT32 Server.exe" is still running, but it isn't doing anything
apart from using CPU cycles and stealing memory.