Skip navigation
Kombi_914
Currently Being Moderated

Green square pixalation blocks apearing on output files

Jan 18, 2011 8:57 PM

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?

 
Replies 1 2 Previous Next
  • Currently Being Moderated
    Jan 18, 2011 9:22 PM   in reply to Kombi_914

    I have not seen this myself, but then I do not use MPEG as source material.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 21, 2011 2:07 PM   in reply to Kombi_914

    "This video is not available in your country."


     
    |
    Mark as:
  • Currently Being Moderated
    Jan 21, 2011 6:42 PM   in reply to Kombi_914

    This:

     

    notavailable.png

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 23, 2011 7:08 PM   in reply to Kombi_914

    the free encode isnt up to scratch.

     

    Which one?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 26, 2011 4:36 PM   in reply to Kombi_914

    > What is the best proccess to take this case to the Adobe support where someone can look at solving my problem?

     

    http://www.adobe.com/support/contact/

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 28, 2011 10:36 AM   in reply to Kombi_914

    What's the source of these files?  What application encoded them?  With what settings?

     

    Can you post a sample that causes the problem so other people can look at it?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 28, 2011 2:50 PM   in reply to Kombi_914

    Thanks for posting the file.  Unfortunately all I see in it is 4 all-black frames.  What should I see?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 28, 2011 3:09 PM   in reply to Kombi_914

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 28, 2011 4:39 PM   in reply to Kombi_914

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 28, 2011 4:55 PM   in reply to Tim Kurkoski

    OK, I just read your previous posts and realized that you're using Adobe Media Encoder CS4, not CS5.  Everything in my last message still applies, just use the correct path to the AME CS4 application directory so you can find that version's ImporterFastMPEG file.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 31, 2011 9:43 AM   in reply to Kombi_914

    Only pull the ImporterFastMPEG file when you have a problem file.  Put it back for all other cases.

     

    Did you get information about the source of the MPEG file?  My engineer friends are hungry for more data about the problem.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 31, 2011 2:15 PM   in reply to Kombi_914

    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.

     
    |
    Mark as:
1 2 Previous Next

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points