> so ImporterFastMPEG decodes the files better than ImporterMPEG, giving you a higher quality output file?
It's not relevant to compare the two plug-ins. Don't think about it in either/or terms. Both are used by the application. I can't stress enough how removing ImporterFastMPEG is only a workaround for a bug. Both plug-ins should be left in place if you desire normal operation of the application.
> they are use the MainConcept encoder for the mpeg-2 files
Correct, there is code from MainConcept that is used by both plug-ins which runs the internal mechanisms of decoding the MPEG data.
> So might this be also related to the issues with h.264 which also uses MainConcept?
No. This thread is about a specific issue with a specific aspect of the MPEG-2 files which aren't getting decoded correctly. The path for decoding H.264 files is completely different. The same plug-in files might be involved (depending on the given situation), but that doesn't necessarily mean the same code is relevant to the problem.
I have this problem on some footage when both "Render at Maximum Depth" and "Use Maximum Render Quality" are selected. Selecting just one of them or neither results with no green blocks. Can't figure out why. Using AME 5.5
I just posted almost the same problem when exporting H.264 files from Premiere 5.5 with AME and when I UNCHECKED render at maximum depth the green blocks went away from my shadow areas... Use Maximum Render Quality had no effect in my situation. Here is the intesting part - When I took off my color correction effects, The video files were fine with both of the boxes checked.
At least this fixed my sitaution! Thank you for the hard work and ubi_tech's response...
I'm experiencing the same issue - the entire screen just goes to green (and sometimes black) pixelation. I've tried removing the ImporterFastMPEG file from the plugin folder as you described but it hasn't fixed the problem.
I'm hoping, seeing as this is 1.5yrs since you originally identified the bug in your post, that your dev team may have more thoughts on the bug? Do you have any other suggestions re how to deal with this?
I'm using CS5 on a 64-bit PC. The footage was supplied by an external production company (so no chance of getting a different version). I know all footage was XDCAM compressed from FCP7 as .movs