[Bill Boyer]

Well, I gave that a try and it does work. However, it’s an extra step that should not be necessary. My point is Adobe/Microsoft should do something about the situation. I can sort of understand why Adobe has neglected the situation because all the MPEGs playback fine when they’re brought back into PPro CS5.5. It’s Microsoft’s Window Media Player that seems to be the bad guy here. At my TV station, the Tightrope SXLE server, which plays the MPEG files into the SX encoder for broadcast, uses the Windows Media Player for the file playback. That’s why everybody watching the channel sees freeze-frames. It’s the pits! My work around is that I kept PPro CS2 on my system along with the new PPro CS5.5. So instead of using CS5.5, I use CS2 for TV stuff and there is no problem. Really a shame to have to use a program that is 3½ versions down from the latest to obtain a perfect MPEG2 output file.

I’m going to throw this CS5.5 issue to Tightrope and see what they can suggest. Maybe there is an upgrade they have developed to correct the problem with Microsoft’s Windows Media Player.

Thanks for your reply and suggestion. It does work and very well!
Bill

[Bill Boyer]

Hello – I was browsing trying to find this MPEG2 freezing issue and I came across your Creative Cow post. I am currently having the exact same issues with PPro CS5.5. Every created MPEG2 file (using AME) has a momentary (½ to 1 sec) freezing. Yet, if I import the MPEG2 back into PPro CS5.5 it plays perfectly. The freezing seems to only occur when MPEG2 is played back in the Windows Media Encoder and the Tightrope TV system SX encoder at the TV station. Did you ever find a non-complex way of stopping this problem and being able to use the Adobe Media Encoder CS5.5 for all your encoding?

My system is:
Motherboard=ASUS P7P55D-E LX Xtreme Design
CPU=Intel I3 @ 3.2 Ghz
RAM=16 BG DDR3
Display Adapter=EVGA GeForce GTX 550Ti with 1 GIG DDR5 on board
HDD=Two (2) internal 1 TB capacity @ 7200 rpm and 1 exteranl 1 TB

Thanks for any information you have that corrected this problem for you,
Bill