Mpeg2 encoding problems, compressor 4

When I compress any Quicktime file to mpeg2 using compressor 4.0.7 and/or 3.5 I get intermittent digitially distorted (square pixels) frames. Usually 1-2 frames per location.
I've done multiple Quicktime exports from FCP (all 1920x1080 30P) with the same results.

Trailpro wrote:
FYI, I had the same problem originally with the 1080i export using compressor 4. It was a while ago and I believe I resolved the problem by using compressor 3.5. However that isn't working this time.
AFAIK, 3.5 amd 4.x encode for DVD MPEG the same.
Sounds like you used QuickTime Conversion to go out from FCP7? Generally, the preferred route is to do as little as possible to the sequence in exporting from FCP; which would mean, Export QT Current Settings.
Another general comment: Interlaced material never looks great on a computer display, and if there is much motion, including pans and zooms, it can really look awful. But that doesn't mean you should de-interlace in FCP. A DVD player and/or the TV should be able to handle interlaced perfectly well. In that case, you would not do any software de-interlacing. Other times, one might decide it was still desirable to de-interlace; and in that case, Compressor will d a better job than FCP.
It's also possible that what you're seeing is just artifacts that were introduced in down-scaling (amd changing pixel shape) from 1080 to 480 anamorphic. Setting he Resize Filter in Frame Controls to Best may cure that problem. In the preview window, mark a short section (that you know contains problem frames) with in and out point as a test and see whether that clears up the problem.
Good luck.
Russ

Similar Messages

  • MPEG2 Asset from Compressor is blank/black

    Hi Mac fans,
    I have a horrible problem with DVD Studio Pro 4 (DSP4 hereafter). After I encode a Final Cut Pro sequence with Compressor using the 90 mins best DVD preset, I import it into DSP4 via the Assets tab. The audio ac3 file works fine but the video m2v file comes out black. I have tried doing this twice now. I can play the file in Quicktime (although it takes a while to load for some reason unknown to me).
    There are some other sequences using shorter portions of the same footage that have successfully imported (only on the third attempt at encoding in Compressor) after some color correction in Color. Problems I had during the failed attempts include: the black screen, a green screen, files not even being allowed to import.
    I have tried, to make sure the file opens with Quicktime by default and this has not changed my problem.
    I can't seem to figure this one out and can't complete this DVD until this problem is solved. I have spent many many days reencoding the same sequences. It's crazy.
    Hope someone has a clue,
    Many thanks,
    Bob
    (ps the dsp4 project is SD. I filmed in HDV.)

    Oh my,
    even the file without the in and out points seems to be working.
    The only thing I can think of is that under the "General" tab in Preferences, I switched the "Display Mode" to 16:9 pan and scan but I have changed it back to 16:9 letterbox and all seems to be working.
    DVDSP is seeming pretty volatile and unreliable unless I am missing something (which is very possible).

  • AC3 audio encoding problems

    Have been encoding ac3 without any problems until recently. Now all ac3 encodes just play back as digital "noise", and the problems exists with default as well as modified versions of the standard ac3 preset.
    I'm using latest versions of Compressor and Quicktime. Anyone seen this issue and know how to solve? I'm considering reinstalling Compressor, but that seems to entail a complete FCS2 reinstall...

    UPDATE: I rebooted my mac using my backup system disk, which has quicktime 7.1.6 installed. I found that under this configuration my ac3 files could be played back. So it's NOT an encoding problem after all. It seems to be a decoding problem. So next up I'll try reinstalling my current version of Quicktime on the main system disk (that's QT 7.2 of course.) If that doesn't work, I'll have to try reverting to Quictime 7.1.6 I guess...

  • Third Party MPEG2 encoder - Suggestions

    So I recently upgraded to a new MacBook Pro. Everything's great except that the version of DVDSP 3 that I have won't work with it and neither will the version of Compressor that came along with it. (I upgraded from a G4 iMac.)
    Can anyone suggest a good third party MPEG2 encoder? My budget is $100 - $200 (or less if possible). I just don't have enough control with the iDVD encoder (even with the new iLife '08). I'm not looking for anything real fancy, just something that will let me have a bit more control over the bitrate, etc . . . And, if it can handle DVD markers from FCE3.5 even better.
    Many thanks for any thoughts.

    Tom,
    Thanks for your question. I didn't try because from what I've read on the forums DVDSP 3, the version that I have, is NOT universal. Not only that, it won't work with Intel Macs under Rosetta. Check the following URL for more information:
    http://www.apple.com/rosetta/
    "Pro applications from Apple — including Final Cut Pro, Motion, Soundtrack Pro, DVD Studio Pro, Aperture, Logic Pro, Logic Express, Shake and Final Cut Express — are not supported by Rosetta. For most applications, you can upgrade to the Universal version for minimal cost (see “Apple Applications” to right)."
    Does this sound correct to you? I'd love to keep DVDSP and Compressor, but it doesn't look possible. Are you using them with your Intel set up?
    Many thanks for any thoughts.
    Jason Morris

  • QuickTime MPEG2 Encoding Cause Kernel Panic

    Does anyone know why I would suddenly be getting kernel panics when encoding to MPEG2 using the QT MPEG2 Encoder.
    I has been exporting using QT Conversion to MPEG2 form FCP for Months, but now I am getting kernel panics and program crashes everytime I attempt to export.
    Any suggestions would be great.
    Dual 1.8 GHz PowerPC G5   Mac OS X (10.3.9)   1.25 GB Ram

    Are you still using QuickTime version 6 or have you moved up to version 7?
    Double check the version number (Get Info window) of the MPEG-2 Playback Component. It should be 6.4.
    The MPEG-2 exports should now be handled using Compressor.

  • MPEG2 Encoder

    What is the best MPEG2 Encoded available for the Mac? I'd be encoding at 1920*1080 and 1280*720.

    Bit Vice, Compressor, Sorenson Squeeze, Cleaner are among the best. There's also iDVD, DVD-SP and Toast.
    -DH

  • Hardware MPEG2 Encoder

    According to Apple and Google, there is NO Hardware MPEG2 encoder available for Apple's Quad G5. I am on the hunt for a solid MPEG2 encoder after countless Compressor letdowns both in performance and actually getting the program to work.
    http://www.apple.com/finalcutstudio/dvdstudiopro/partners.html
    Optibase, among others, have not yet adopted the PCI Express compatibility which has painted us in a corner to deal with the software encoding process that takes hours. Yes, HOURS. I'm not talking about 2-3 hours for a 20 minute video. I'm talking about 10, 15, 20 hours for Compressor to make the MPEG2 and AIF, and once it does, the quality is good, not great.
    Please someone at Apple or one of these third party companies (Optibase, Wired) throw a pizza party for the engineering staff and let's get the ball rolling on a PCI Express techology that we can use before the PowerIntel MacPro G6 comes out.
    (Or at least make Compressor utilize all four chips in the Quad)
    Thanks,
    Dan
    Quad G5, 8GB RAM   Mac OS X (10.4.5)  

    I use an SD-2000 on Windows. The Creator encoder is still part of a OS9 G4 system but they're not not updating it. They've (Sonic) flat out stopped developing Creator/Fusion. We also have a Wired Inc. board which I've not sorted out yet. The windows CCE SP (software) option is a very good app but hardware is hardware. Two or three copies, Procoder and some PCs still works out a lot cheaper than some hardware encoders though...
    I'd say it's aways good to have options cause there are lots of times where the SD-2000 doesn't cut it and I encode with something else...
    -Jake

  • Encoding problems in email while on Windows Mail app

    Hello.
    I have a question concerning email and encoding problems in the Windows Mail App in Windows 8.1.  I have encountered a problem with an email I received, while reading, I see strange ASCII characters in one email.  I have never encountered it in
    my web browsers nor Gmail, just the Mail App.
    I was referred to come here when I had asked a similar question there:
    http://answers.microsoft.com/en-us/windows/forum/windows8_1-ecoms/strange-foreign-ascii-characters-appearing-in/911f8a44-c302-4fa1-bcaa-3297b32d9120
    I don't know which forum to go to so I picked here.
    Is there any way that it can be resolved.  I tried to troubleshoot, nothing worked; I even synched, to no avail.
    I look forward to a response.
    JB

    Hi JB,
    The responder on answers was a bit confused. The MSDN forums are for developers to discuss writing their own apps. We cannot help with problems using Windows or its built-in apps.
    If the folks on answers cannot help then you may need to open a support incident. See
    http://support.microsoft.com , or the folks on answers may be able to direct you to the specific page for the Windows Mail app.
    --Rob

  • Encoding problem while reading binary data from MQ-series

    Dear all,
    we are running on 7.0 and we have an encoding problem while reading binary data from MQ-series. Because we are getting flat strings from queue we use module "Plain2ML" (MessageTransformBean) for wrapping xml-elements around the incoming data.
    The MQ-Series-Server is using CCSID 850, which we configured in connection parameters in communication channel (both parameters for Queuemanager CCSID and also CCSID of target).If there are special characters in the message (which HEX-values differ from codepage to codepage) we get errors in our adapter while executing, please see stack-trace for further analysis below.
    It seems to us that
    1. method ByteToCharUTF8.convert() expects UTF-8 in binary data
    2. Both CCSID parameters are not used anyway in JMS-adapter
    How can we solve this problem without changing anything on MQ-site?
    Here is the stack-trace:
    Catching com.sap.aii.af.mp.module.ModuleException: Transform: failed to execute the transformation: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
        at com.sap.aii.af.modules.trans.MessageTransformBean.throwModuleException(MessageTransformBean.java:453)
        at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:387)
        at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)
        at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:292)
        at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
        at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:84)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.ConvertBinaryToXiMessageFilter.filter(ConvertBinaryToXiMessageFilter.java:304)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.ConvertJmsMessageToBinaryFilter.filter(ConvertJmsMessageToBinaryFilter.java:112)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.InboundDuplicateCheckFilter.filter(InboundDuplicateCheckFilter.java:87)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:123)
        at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filter(TxManagerFilter.java:59)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.DynamicConfigurationFilter.filter(DynamicConfigurationFilter.java:72)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.PmiAgentFilter.filter(PmiAgentFilter.java:66)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.InboundCorrelationFilter.filter(InboundCorrelationFilter.java:60)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.JmsHeadersProfileFilter.filter(JmsHeadersProfileFilter.java:59)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageInvocationsFilter.filter(MessageInvocationsFilter.java:89)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.JarmMonitorFilter.filter(JarmMonitorFilter.java:57)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.ThreadNamingFilter.filter(ThreadNamingFilter.java:62)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.SenderChannelImpl.doReceive(SenderChannelImpl.java:263)
        at com.sap.aii.adapter.jms.core.channel.ChannelImpl.receive(ChannelImpl.java:437)
        at com.sap.aii.adapter.jms.core.connector.MessageListenerImpl.onMessage(MessageListenerImpl.java:36)
        at com.ibm.mq.jms.MQMessageConsumer$FacadeMessageListener.onMessage(MQMessageConsumer.java:399)
        at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl$JmsProviderMessageListener.onMessage(JmsMessageConsumerImpl.java:904)
        at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:4249)
        at com.ibm.msg.client.wmq.v6.jms.internal.SessionAsyncHelper.run(SessionAsyncHelper.java:537)
        at java.lang.Thread.run(Thread.java:770)
    Caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
        at com.sap.aii.messaging.adapter.Conversion.service(Conversion.java:714)
        at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:538)
        at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:528)
        at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:471)
        at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:364)
        ... 36 more
    Caused by: sun.io.MalformedInputException
        at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java:270)
        at sun.nio.cs.StreamDecoder$ConverterSD.convertInto(StreamDecoder.java:287)
        at sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java:337)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:223)
        at java.io.InputStreamReader.read(InputStreamReader.java:208)
        at java.io.BufferedReader.fill(BufferedReader.java:153)
        at java.io.BufferedReader.readLine(BufferedReader.java:316)
        at java.io.LineNumberReader.readLine(LineNumberReader.java:176)
        at com.sap.aii.messaging.adapter.Conversion.convertPlain2XML(Conversion.java:310)
        at com.sap.aii.messaging.adapter.Conversion.service(Conversion.java:709)
        ... 40 more
    Any ideas?
    Kind regards, Stefan

    Hi Stefan,
    for the first MTB now we are using only one parameter: Transform.ContentType = text/plain;charset="ISO-8859-1"
    The second MTB, which does the XML-Wrapping, is configured like this:
    Transform.Class = com.sap.aii.messaging.adapter.Conversion
    Transform.ContentType = application/xml
    xml.conversionType = SimplePlain2XML
    xml.fieldNames = value
    xml.fieldSeparator = §%zulu§%
    xml.processFieldNames = fromConfiguration
    xml.structureTitle = payload
    Both CCSID configuration parameters from the "Source"-Tab we've set to 850.
    Now, we don't get an error anymore - sun.io.malformedInputException - , but, unfortunately, now special character conversion succeeded (we need an "ß" and we get an ISO-HEX-E1 -> á).  E1 is (different from ISO) an "ß" in 850.
    Any ideas?

  • Encoding problem in call-back to hook URL (post parameters)

    Hello all,
    I'm encountering a character encoding problem while retrieving the content of the shopping basket from one of our provider.
    After the POST request is made by the provider to our system using the hook url, when debbuging I can see that some special characters are represented with the sign '#' (after the call the ITS_IMPORT_CONTEXT).
    In our case using the parameter http_content_charset with various values, including UTF-8, did not change the result.
    Inspecting the HTTP traffic has highlighted the following: the encoding received from the provider is related to UTF-8, but while we are expecting the hexadecimal values, we are receiving the "Unicode code points", which are not recognized by our SAP system. For more details look at the UTF-8 encoding table found here and compare the values under column "Unicode code point" with the one under column "UTF-8 (hex.)".
    As an example, for the character 'é', we are receiving the value "%E9" (the code point) instead of receiving the the hexa value : "%C3%A9".
    Do you have any idee if this can be corrected on our side or if the provider must addapt the way it's sending the POST parameters?
    Many thanks in advance for you help.
    Best regards,
    Jerome.

    Hi Jason,
    Indeed I had contacted the provider and informed them about the encoding problem and the fact that passing the parameter http_content_charset had no effect on the sent back encoding.
    They have taken into account my request and have changed the encoding used during the request to the HOOK_URL.
    Thanks to all of your for your help.
    Regards,
    Jerome.

  • Character encoding problem using XSLT and Tomcat on Linux

    Hi,
    I have an application running on a Tomcat 4.1.18 application server that applies XSLT transformations to DOM objects using standard calls to javax.xml.transform API. The JDK is J2SE 1.4.1_01.
    It is all OK while running on a development enviroment (which is Windows NT 4.0 work station), but when I put it in the production enviroment (which is a red hat linux 8.0), it comes up with some kind of encoding problem: the extended characters (in spanish) are not shown as they should.
    The XSL stylesheets are using the ISO-8859-1 encoding, but I have also tried with UTF-8.
    These stylesheets are dynamicly generated from a JSP:
    // opens a connection to a JSP that generates the XSL
    URLConnection urlConn = (new URL( xxxxxx )).openConnection();
    Reader readerJsp = new BufferedReader(new InputStreamReader( urlConn.getInputStream() ));
    // Gets the object that represents the XSL
    Templates translet = tFactory.newTemplates( new StreamSource( readerJsp ));
    Transformer transformer = translet.newTransformer();
    // applies transformations
    // the output is sent to the HttpServletResponse's outputStream object
    transformer.transform(myDOMObject, new StreamResult(response.getOutputStream()) );Any help would be appreciated.

    Probably you need to set your LANG OS especific environment variable to spanish.
    Try adding this line:
    export LANG=es_ES
    to your tomcat/bin/catalina.sh, and restart tomcat.
    It should look like this:
    # OS specific support.  $var _must_ be set to either true or false.
    cygwin=false
    case "`uname`" in
    CYGWIN*) cygwin=true;;
    esac
    export LANG=es_ES
    # resolve links - $0 may be a softlink
    PRG="$0"
    .(BTW, keep using ISO-8859-1 encoding for your XSL)
    HTH
    Un Saludo!

  • C# GWTypeLibrary - AddressBook Entry encoding problem

    Hello.
    I am using C#(Visual Studio 2005) and GroupWareTypeLibrary to develop for
    GroupWise Client 7.0.
    Working with AddressBook I have faced some problems.
    I am getting display name (AddressBookEntry.DisplayName) for all entries
    of AddressBook. Almost all DisplayNames are correct but there are some
    problems with two or three of them (there are some illegal char displayed
    instead of some char of real user DisplayName). I think it is local
    encoding problem bekause I see the same problem with the same users in
    GroupWise Client AddressBook.
    I thought display name is building not correctly but when I tried to get
    these users first and last name I have got the same problem with encoding
    in them.
    Please advice how to decide this problem.
    Regards,
    Alex.

    Sounds like a GW Client problem and not an API problem if you see it in the client address book. Technical Support should be able to help you.
    Glade,
    Novell Developer Support

  • Encoding Problems with WRT300N V2

    Hello guys,
    i have following problem:
    I have a WRT300n Router and it seems to have problems with WPA2 encoding. I have 2 different deviceses (a SMC Ethernet Bridge and a PS3) trying to connect to my Linksys wireless router. No chance in WPA2 mode but when I try in WEP-Mode, both devicec can connect to it.
    Are there known encoding problems?
    Any idea what i can do?

    It is able to use. But my router always drops the connection. WEP is no problem, but ... what about low security and Wirless N is not enabled ??

  • Encoding problem (via ORB)

    Hello,
    I posted this problem few months ago, but still havent been able to solve this.
    I have a Client Server program which communicates via ORB, i.e. using CORBA, with server running on Solaris OS and Client running on windows.
    The server returns string containing chinese characters to the client.
    However, my chinese characters dont appear properly on the client side.
    If i run the client on the Solaris OS there is no problem with it.
    I tried converting the encode of the string by getting its byte and creating
    a new string with encoding parameter. None of this seems to work.
    I can see the chinese character when the server is writing to OutputStream of CORBA, but on the InputStream of CORBA it does not
    show properly.
    Any ideas on how i can overcome this encoding problem where the C/S is
    communicating via CORBA (ORB)?
    Thanks in advance.

    Thanks for your reply
    Yes, i know the BIG5 is for Traditional Chinese and japansese is using like Shift-JIS or EUC.
    So when i try to post japanese in a BIg5 web page, i think it's normal that i can't see it in BIG5 encoding.
    But then i change the Safari default decoding to BIG5 HKSCS, the japanese appers! At the same time i can see the traditional chinese too!
    And if i use Firefox, i can both see the japanese and chinese at the default BIG5 encoding.
    So i simple think maybe safari translate my japanese into BIG5 HKSCS,not Shift-JIS. But if i use Firefox, i can get the same result with only BIG5 encoding, not BIG5 HKSCS. So i am just wondering why it's different between Safari and Firefox with the same BIG5 encoding.
    Following is a example URL
    It's a MAC discussing froum with BIG5 encoding in Taiwan.
    http://ubb.frostyplace.com.tw/viewtopic.php?t=19162
    It's a froum topic posted by me. I input some japanese into this topic
    If you browse this page with Safari BIG5 encoding, you can see a lot of question mark instead of the original japanese word that i and other people posted.
    But if you change the encoding to BIG5 HKSCS, the japanese appears. And if you using Firefox with BIG5 encoding, the japanese appears too.
    So is it someing wrong with Safari's BIG5 encoding or some other reason makes this happen?

  • View Object Encoding problem

    I'm using Jdeveloper version 11.1.2.1. I have a encoding problem when creating View Object based on a query. This is my query:
    select id, DECODE(id,'11','Индивидуално,'13','Semejno','14','Grupno') naziv
    from ins_type
    where class_id = '14' and id in ('11', '13', '14')
    It is a simple LOV query with cyrilic letters. When I save the ViewObject and re-open it im getting question marks(???????) instead of the cyrilic letters. This only happens in the view object. I dont have other encoding issues when working with cyrilic letters only when im trying to build a View Object based on a query that has cyrilic letters. If i read those values from the database everything is fine
    Thanks,

    Change the encoding of your application to UTF-8 which appears to be sufficient for cyrilic chars. Here is a quick guide on how to do this http://docs.oracle.com/cd/E17984_01/doc.898/e14693/appa_configuring_jdev.htm
    You may also need to update any pages that have encoding explicitly set

Maybe you are looking for