using CS5 on windows 7 64bit and trying to convert from mpeg2 files, Green square pixalation blocks apearing randomly but alway in the same spots after a re-encode on output files regardless of output settings
has anyone seen this before and how can I resolve it?
Encoding the same mpeg2 file on windows 7, 64 bit with CS5 media encoder - Green square pixalation blocks apear
Encoding the same mpeg2 file on windows server 2003, 32 bit with CS4 media encoder - Green square pixalation blocks apear
Encoding the same mpeg2 file on windows XP, 32 bit with CS4 media encoder - file has no error.
Encoding the same mpeg2 file on a 2nd windows XP, 32 bit with CS4 media encoder - file has no error.
I hope this helps you help me find a solution to use CS5 effectivly
someone had it on there laptop but he is on holidays this week so i cant tell you till then.
it only had single pass and it didnt look the best.
besides i managed to ge good results on XP with CS4, i just need it to work on W7 with CS5 so i can get the best quality and automate the process
What's the source of these files?
the source are suplied direct from the record company, this is the largest quality file they will supply for broadcast and re-encoder for my internet broadcast.
What application encoded them? With what settings?
i do not have this info. but AME 4.0 has no issue reading them and encoding them.
Can you post a sample that causes the problem so other people can look at it?
you can find a sample here;
ftp.sma.net.au
user: smaftp
pass: sma777
Your last message wasn't wholly clear, John. I did download the file, as opposed to trying to read it from the server. The file size of my downloaded copy matches what is shown on the FTP server, so it appears that the download was successful.
When you re-post the clip or post a different one, I'll try downloading again.
The files downloaded OK. It's got some black frames on the front but @ 1:20 the floating burger box and music start. I can see the problem with the green blocks in AME, After Effects, and Premiere Pro CS5 (which all use the same MPEG decoders).
Clearly there's a bug here, so I've filed that on your behalf. The good news is that, with the help of one of our big-brained software engineers, I've identified a workaround you can use.
You can make this file work as expected in AME, Premiere Pro, or After Effects CS5 by removing the ImporterFastMPEG.prm plug-in.
For AME, this can be found at:
C:\Program Files\Adobe\Adobe Media Encoder CS5\Plug-ins\common
(similar locations on Mac or for Premiere Pro and After Effects)
Drag the file out to your desktop, launch AME, add the file. It should play without the green blocks. When you're done using the MPEG file, don't forget to put the ImporterFastMPEG.prm file back. You want it there.
The bug here is that ImporterFastMPEG doesn't recognize that it's failing to decode the file, and should be passing it to our other (slower) ImporterMPEG decoder. A little background on why we even have two decoders: MPEG encoding and decoding is a wild, hairy bit of business that by definition doesn't wholly specify how a file is supposed to be encoded. Thus it's very easy to write a decoder that may not work with certain encoders. I recommend starting with the Wikipedia article if you want to learn more.
=====
Now, I really really really would like to know where this file came from. What software or hardware encoded it? What settings? If you can find that out, I'd be most grateful, and can add it to our bug records.
Thanks for posting the files.
Don't think of ImporterFastMPEG as an enhancement; it's the primary MPEG decoder. (The "Fast" part of the name misrepresents the purpose of the plug-in. The name is an archaic remnant of the plug-in's original design as a faster decoding algorithm. Today it does much, much more than that.)
Please believe me when I tell you that this plug-in is not optional. You want it there. You should put it back when you're not dealing with files that it's not handling correctly. The only reason for removing it is for cases like the one you're dealing with. Specifically, it doesn't know that it's failing to decode the file correctly and isn't automatically passing the decode to ImporterMPEG.
Thanks for looking into the source details.
North America
Europe, Middle East and Africa
Asia Pacific