H.263 Encoder

Hi,
Is anyone aware of a third party (either open-source or commercial) H.263 encoder? I'd prefer one that is independent from JMF if possible.
All recommendations will be welcomed!

hi....im looking the same thing....please help me....well in fact i'm a beginner...so i need help actually saving the video data to a file...any type of file...and then i can move on a do the thing for save it in 3gpp....any source code example...any help is welcome.....hoping that some one respond
see ya

Similar Messages

  • H.263 avi encoding - possible?

    I have a need to create a h.263 encoded AVI video file... (For a video IVR platform). I purchased Quicktime Pro, hoping it would be able to create these files for me, but it's not as obvious as I hoped.
    I see I can create an h.263 encoded .mov file, but I need this to be in a .avi container. When I select .avi file, I only get 5 or 6 different encoders I can use, and h.263 isn't one of them.
    The g3 format or whatever has h.263 support, but again that's not .avi ..
    I looked at ffmpegx too, but again - not too obvious.
    Can anyone help??? Thanks
    24" iMac   Mac OS X (10.4.9)  

    It's 2007 and even Microsoft dumped the AVI container years ago.
    Ask them first why they need AVI and then explain your export options.
    They seem to be locked into the early 90's.

  • Re: Multiple Processor-Objects

    I found some h263 encoded media files on http://samples.mplayerhq.hu/V-codecs/h263/
    and even used the exact same file for the concat-sample - with the following result:
    - Create processor for: file://XXX/movies/movie10.mov
    - Create processor for: file://XXX/movies/movie10.mov
    - Cannot transcode the tracks to a common format for concatenation!  Sorry.
    Failed to match the tracks.
    Failed to concatenate the inputs
    Could someone perhaps offer media-sample that are guaranteed to work with at least that concat-example?
    Edited by: Yppolitia on Feb 4, 2010 8:13 AM

    H.263 encoding is only supposed by the performance packs, so if you're using the cross-platform pack you won't be able to encode H.263.
    For samples, I generally use these:
    [http://www.cs.odu.edu/~cs778/spring04/lectures/jmfsolutions/clips/]

  • Multiple Processor

    I have installed oracle report server on a machine having 4 processor's. how can i benefit from all of these processors to finish the job fast.

    H.263 encoding is only supposed by the performance packs, so if you're using the cross-platform pack you won't be able to encode H.263.
    For samples, I generally use these:
    [http://www.cs.odu.edu/~cs778/spring04/lectures/jmfsolutions/clips/]

  • How to compile JMF source code

    Hello,
    Im working in an application which uses Java Media Framework to code/decode and transmit/receive the video and audio. I need to modify the h.263 codec in order to get an especial issue related to video.
    I download the source code of jmf I found in this topic: http://ohmydear.tistory.com/attachment/48fd0e73b49f9C0.zip. But I dont know how to compile the jmf in eclipse tool. Does anybody know?
    If anybody doesn't, would anybody know how to modify the coding and decoding of h.263 in JMF. I have no idea how to get that?
    Thanks a lot and best regards.
    Pedro

    pedritomoreno wrote:
    I download the source code of jmf I found in this topic: http://ohmydear.tistory.com/attachment/48fd0e73b49f9C0.zip. But I dont know how to compile the jmf in eclipse tool. Does anybody know?
    If it's not just a straightforward build, then I doubt anyone has instructions on how to do it...
    If anybody doesn't, would anybody know how to modify the coding and decoding of h.263 in JMF. I have no idea how to get that?Well, if you look at the following link...
    [http://java.sun.com/javase/technologies/desktop/media/jmf/2.1.1/formats.html]
    You'll see that for h.263, decryption is the only thing that's implemented in Java (the things that are in the windows pack but not in the cross platform pack are implemented in native code)... so if you're wanting to do h.263 encoding, you'll have to code that from the ground up...
    Read the following post for more information about writing your own codecs...
    [http://forums.sun.com/thread.jspa?messageID=10725041#10725041]

  • How to encode MOV files in H.263-basic

    Hi,
    I need to create a .mov file encoded in h.263-basic , Can QuickTime or any other tool do this ?
    Thanks
    -Chatura

    Hi,
    Thanks for the reply, I have a radvision 3G gateway which needs the mov file to be encoded in the native H.263 format (i.e. without any annexes).
    It also supports the following,
    -H.263
    -H.263+ (Annexes F, I,J, K, T)
    -H.264 baseline profile level 1
    Can QT pro save files specifically in these formats ?
    Thanks
    -Chatura

  • H.263/H.264 3GP Mobile encoding errors

    Gotta say that I'm sharing the frustration of others w.r.t. Quicktime Pro on Windows ... any who ...
    I have some v. strange errors when encoding some mobile media. I'm going from a quicktime mov to
    a) H.263 + AMR NB 3GP contained
    b) H.264 + AMR NB 3GP contained.
    On the first instance, if I try and transcode using the following settings
    H.263, 32kbits/sec data rate, QCIF size, 15 FPS, with key frame at every 24 frames, the video is truncated, but if I then set it to 33KBits/sec things are fine. Has anyone else come across this?
    When doing the same for H.264 I get an error -48: Can't resize to ... The input is already at QCIF size, and even specifying Current as an option doesn't help.
    AFAIK this looks like a bug. Has anyone got any ideas etc that might help me out of this hole?
    Many thanks in advance.

    Try enabling "Show legacy encoders" in the "Advanced" tab of "QuickTime" system preferences (not the QuickTime Player preferences).

  • Encoding in H.263, not H.264

    I want to encode a short video in a variety of codecs to let my students figure out which ones they can view on their computers. (In particular, I need to find out how many of my students can view H.263 but not H.264.) I thought I knew how to do this in Quicktime Player... just choose Export, popup "Movie to Quicktime Movie", Options, [Video] Settings, and H.263 from the "Compression type" popup. But it's not there... just H.264! (Also missing are H.261 and Cinepak, which I sometimes found was necessary for running Quicktime movies on my older iBook since H.264 was too processor intensive during decoding.)
    Has this codec been removed by Apple? It is still listed as a supported codec on Apple's Quicktime page. I have the Quicktime Player version 7.4.5 (25).

    Try enabling "Show legacy encoders" in the "Advanced" tab of "QuickTime" system preferences (not the QuickTime Player preferences).

  • UTF-8 encoding in J2ME

    Hello,
    I'm currently developing J2ME application for downloading bus schedules.
    The data that I download is in polish language (eg. bus directions, stop names etc). These are xml files generated by a php script encoded in UTF-8.
    The problem is that I don't know how to display that properly, so that all the polish characters are what they're supposed to be.
    Some of my code for downloading content:
    String getXML(String url)
            HttpConnection cn = null;
            InputStream str = null;
            //DataInputStream strd = null;
            StringBuffer sb = null;
            try
                int code;
                cn = (HttpConnection) Connector.open(url);
                code = cn.getResponseCode();
                if (code == HttpConnection.HTTP_OK)
                    str = cn.openInputStream();
                    // strd = new DataInputStream(str);
                    sb = new StringBuffer();
                    InputStreamReader r = new InputStreamReader(str, "UTF-8");
                    int total = 0;
                    int read = 0;
                    while ((read = r.read()) >= 0)
                        total++;
                        sb.append((char) read);
                    return sb.toString();
                else
                    throw new Exception("Nie udało się połączyć z serwerem");
            catch (Exception e)
                return null;
            finally
                try
                    if (str != null)
                        str.close();
                    if (cn != null)
                        cn.close();
                catch (Exception e)
        }And parsing it:
    InputStreamReader reader = null;
                    String xml = getScheduleXML(getSel_Line(), null, null);
                    ByteArrayInputStream stream = new ByteArrayInputStream(xml.getBytes());
                    reader = new InputStreamReader(stream, "UTF-8");
                    parser.setInput(reader);
                    while (parser.next() != KXmlParser.END_DOCUMENT)
                        if ((parser.getEventType() == KXmlParser.START_TAG) && (parser.getName().equalsIgnoreCase("direction")))
                                String d = (String) parser.getAttributeValue(0);
                                v.addElement(d);
                                String d2 = (String) parser.getAttributeValue(1);
                                v2.addElement(d2);
                    }What do I do wrong? What is missing?

    Problem solved. I had to add "UTF-8" parameter to getBytes method.

  • H264 stream is not encoded properly in AIR 3.2

    Hi all,
    I'm running latest AIR runtime on my desktop: 3.2.0.2070
    My air appliation is compiled with latest air sdk also: 3.2.0.2070
    Platform is Windows XP.
    The application is aka Cirrus Video Phone Lab app, where streaming is done to another instance of the AIR application.
    I do use this code to enable H264 encoding on the outgoing stream:
         var h264Settings:H264VideoStreamSettings = new H264VideoStreamSettings();
         h264Settings.setProfileLevel(H264Profile.MAIN, H264Level.LEVEL_3_2);
         outgoingStream.videoStreamSettings = h264Settings;
    Once my app is running i do check the VideoStreamSettings.codec on both outgoing and incoming streams:
         trace("outStream codec: "+outgoingStream.videoStreamSettings.codec+"\n");
         trace("inStream codec: "+incomingStream.videoStreamSettings.codec+"\n");
    Here is the output:
         outStream codec: H264Avc
         inStream codec: Sorenson
    So it appears that incomingStream is using Sorenson?! How is this possible to encode in H264 and decode using Sorenson and see the video?
    Or really it is Sorenson which is used for encoing irrelevant of what videoStreamSettings is set to? How about Adobe's claim they support H264 on the Air web page?
    Or am I missing something completely?
    Thanks,
    Sd.
    An update:
    I've recompiled my test project to use web application and run it on a standalone flashplayer11_2r202_228_win_sa_debug_32bit.exe
    Result is the same: outgoing stream prints H264Avc, while incoming does Sorenson.
    So, I'm not really sure what's the deal about Adobe's claim about H264 support in AIR3 and FP 11.2? There are no H264 support in both. Period.
    Too bad Adobe, too bad... Sorenson has been since FP6 right? It's year 2012 now. I just want to remind you if you forgot about this.
    I undersdtand making creative art on the web page with useless claims (http://www.adobe.com/products/air/features.html) is much easier then making
    a product which stands for them, but with bugs like that it's better to keep the mouth shut then claim non-existent "features". Please also explain to us
    how are we suppose building that "cutting-edge" application running on "billions" of devices? Anyone?

    When I try this on a MacBook I observe incomingStream.videoCodec=2048. What does 2048 mean? It's not in the referenced document.
    When I try this on iOS and Android, assigning a value to outgoingStream.videoStreamSettings does not work. The value of outgoingStream.videoStreamSettings is null after assignment. When I look at the value of incomingStream.videoCodec on the decoding side I see a value of 2 which I understand to mean Sorenson H.263. So it doesn't look like H264 encoding works on iOS or Android. My code is simple.
    outgoingStream = new NetStream(connection);
    outgoingStream.client = this;
    outgoingStream.addEventListener(NetStatusEvent.NET_STATUS, outputNetStatusHandler);
    outgoingStream.addEventListener(NetDataEvent.MEDIA_TYPE_DATA, outputNetDataHandler);
    outgoingStream.attachCamera(camera);
    var h264Settings:H264VideoStreamSettings = new H264VideoStreamSettings();
    h264Settings.setProfileLevel(H264Profile.BASELINE, H264Level.LEVEL_3_1);
    outgoingStream.videoStreamSettings = h264Settings;
    trace("outgoingStream.videoStreamSettings=" + outgoingStream.videoStreamSettings + " " + describeType(outgoingStream.videoStreamSettings));
    outgoingStream.publish("test");

  • Improper decoding of base64 encoded attachment on Exchange 2007 SP1

    I'm using Exchange 2007 SP1. My java application sends email to users of exchange 2007 SP1. The email contains an email as an attachment which is base64 encoded . This email when sent to users on exchange 2007 SP1 shows blank attachment. The same email when sent to users on different exchange (e.g. Exchange 2003) shows the correct attachment i.e. the attachments are not blank. While sending the mail i'm setting name of the attachment in Content-Type header but it is not there when we look at the rfc contents of the mail received on ex 2007 SP1.  It seems exchange 2007 is not able to decode the base 64 contents properly. Below are the rfc contents of the mail which show few headers in the attachment part instead of the base64 content. Please suggest some solution to it. It's urgent.
    Received: from test80.psjpr.com (192.168.0.243) by exchange01.psjpr.com
     (192.168.0.138) with Microsoft SMTP Server id 8.1.263.0; Fri, 11 Apr 2008
     18:53:12 +0530
    From: Admin <[email protected]>
    To: test test1 <[email protected]>
    Date: Fri, 11 Apr 2008 18:53:12 +0530
    Subject: Retrieved from : testingggggg
    Thread-Topic: Retrieved from : testingggggg
    Thread-Index: Acib1zFeboxSL6S4RuaeI0AaCou0pQ==
    Message-ID: <[email protected]>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Exchange-Organization-AuthAs: Anonymous
    X-MS-Exchange-Organization-AuthSource: exchange01.psjpr.com
    X-MS-Has-Attach: yes
    X-MS-TNEF-Correlator:
    Content-Type: multipart/mixed;
     boundary="_002_9c2e5956bc9b49efbbc61a358f61698bexchange01psjprcom_"
    MIME-Version: 1.0
    --_002_9c2e5956bc9b49efbbc61a358f61698bexchange01psjprcom_
    Content-Type: text/plain; charset="iso-8859-1"
    Content-Transfer-Encoding: quoted-printable
    The message you requested is attached.
    --_002_9c2e5956bc9b49efbbc61a358f61698bexchange01psjprcom_
    Content-Type: message/rfc822
    Subject:
    Thread-Index: Acib1zFexS+KMQAOSD+lcMut076Wyg==
    Accept-Language: en-US
    X-MS-Has-Attach:
    X-MS-TNEF-Correlator:
    Content-Type: text/plain; charset="us-ascii"
    Content-Transfer-Encoding: quoted-printable
    MIME-Version: 1.0
    --_002_9c2e5956bc9b49efbbc61a358f61698bexchange01psjprcom_--

    Did you ever this to work ?

  • 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?

  • H.263/RTP payload

    As we know jmf can stream in h.263/rtp with payload 34. i am streaming h.263/rtp to a device which does not understand payload 34 rather payload 96 whihc is used by h.263-1998 and 2000 updated versions.
    Do anyone has any idea how can change payload from 34 to compatible with 96.
    Sorry if it is not the right place/forum to ask this question. But if any one has any idea where i can ask question regarding transcoding h.263/rtp packets from the one compatible with rfc 2190 (which is supported by jmf and is almost outdated) to packets compatible with rfc 2429.

    Sorry captfoss i was on leave for some time so could not respond to your reply on time.
    While working today i found that JMF has a videoformat :-VideoFormat.H263_1998_RTP which is compaitable with RFC 2429. But there is a problem - i tried several times to transcode my h263 file i am reading from local computer to h263_1998_RTP format but it fails giving following error:-
    Failed to realize: com.sun.media.ProcessEngine@19209ea
      Cannot build a flow graph with the customized options:
        Unable to transcode format: H263, 176x144, FrameRate=15.0, Length=76032 0 extra bytes
          to: H263-1998/RTP
          outputting to: RAW/RTP
    Error: Unable to realize com.sun.media.ProcessEngine@19209eathen i checked in jmf registery i found a codec -com.sun.media.codec.video.vh263.Native Decoder -This Decoder converts h263,h263/rtp as well as h263-1998/rtp into yuv format. but i could not found any encoder which converts any format(yuv or rgb or h263 or any other) to h263-1998/rtp.
    Is there any way by which i can transcode to h263-1998/rtp???

  • H.263 Dimensions are Wrong

    Hi folks. I am implementing a system which translates exported iMovie videos to Flash FLV files for Internet placement. Fun stuff.
    I've been having some issues with files not having the right dimensions. I export from iMovie at 320x240. CD_ROM as a quick choice for export, as well as Expert Settings, set to H.263, same resolution. All things fine. I play in QuickTime, and the info window says it's 320x240. I play in VLC Player, and its info window also reports 320x240.
    Now, the software that translates (ffmpeg) reports that the source file (my exported file) has dimensions of 352x288. So it has a right black border of 32pixels, and a bottom border of 48 pixels, which is about right to my eyeball.
    So the output video is a problem. I'm exporting, as any consumer would, from their iMovie, to 320x240, and it is adding fudge to the video stream.
    Will this be fixed in better versions than 3.0.3? Or is this type of output going to remain?
    I'm trying to leverage the Mac as a valid business platform. If iMovie exports won't take video footage and export them accordingly, then that is creating a problem for my potential customers that need a surefire way of getting video footage to me. Naturally I would want to push the iMovie platform, as it's as friendly as you can get, and therefore it's a natural for clients to choose, and for me to recommend.
    Any advice/comments welcome.
    Cheers

    Hi there. That's what I thought. So I tested and tested, then posted in the ffmpeg list and got some lovely reply:
    | Now, some details. Source file was exported at 320x240. ffmpeg
    | reports it as 352x288. Quicktime reports it as 320x240. VLC Player
    It is actually 352x288. Quicktime is lying to you. I could have told
    you this right away if it were in your original report -- Quicktime
    files contain fake dimensions as a 'crop directive' the the player,
    allowing part of the video to be hidden. FFmpeg ignores this and gives
    you your whole video. You need to crop it if you want it cropped.
    | reports it as 320x240. I have asked it to output to 320x240 but the
    | sizing is smaller, putting black to the bottom and to the right.
    Blame the XXXXXX at Apple or whoever wrote the software that generated
    the mov file -- they're the ones who actually encoded 352x288 h263
    video and put it in a Quicktime container with a false "320x240" label
    on it."
    Having exported from iMovie in H.264, the video corrected itself, with the very same instructions that I used for the H.263 file.
    Second, that converter won't work. This is a web app that behaves like YouTube, so incoming videos have to be translated on the fly, and I can't hire someone 24/7 to click buttons on this stuff. And like I said, this will do it automatically in the workflow for H.264 files.
    I am also making sure that there is a proper workflow as well, as I want to give advice about minimizing the size of exported files while maintaining quality. Having mega MB files to upload will take bandwidth and have users cancelling. Second, Safari already has a 1 minute page timeout, reintroduced with version 3 that I have to code around, so it's already feeling the crunch. Users will need to export some way, and currently H.264 is the only way I can give that advice. And that has audio issues in the web translate.

  • H.263 vs h.264

    does h.263 provide better compression than h.264?
    also, why does a .flv file exported as h.264 (all things being equal) result in larger file?

    does h.263 provide better compression than h.264?
    No, but being older is probably more compatible system/platform wise.
    "H.263 was developed as an evolutionary improvement based on experience from H.261, the previous ITU-T standard for video compression, and the MPEG-1 and MPEG-2 standards. Its first version was completed in 1995 and provided a suitable replacement for H.261 at all bitrates. It was further enhanced in projects known as H.263v2 (also known as H.263+ or H.263 1998) and H.263v3 (also known as H.263++ or H.263 2000)." —Wikipedia
    "The next enhanced codec developed by ITU-T VCEG (in partnership with MPEG) after H.263 is the H.264 standard, also known as AVC and MPEG-4 part 10. As H.264 provides a significant improvement in capability beyond H.263, the H.263 standard is now considered primarily a legacy design (although this is a recent development). Most new videoconferencing products now include H.264 as well as H.263 and H.261 capabilities." —Wikipedia
    also, why does a .flv file exported as h.264 (all things being equal) result in larger file?
    If you are asking about the same content being converted to a target format using differing intermediate compression formats, then generally speaking, if all encoding settings -- especially the data rate, mode, quality, and frame type -- are exactly the same, the files should come out roughly the same with only minor differences reflecting differences in the intermediate files themselves. Quality, however, can vary drastically. If you are asking about a single source file being converted to 2 different codecs (e.g., FLV to H.263 and H.264), then differences are to be expected since each codec has its own unique characteristics and peculiarities -- e.g., how each codec reacts to vector motion, levels of brightness and/or contrast, how fast the codecs adjusts for changes in data rate requirements based on scene complexity, etc.

Maybe you are looking for

  • How to connect macbook to HD TV?

    I would like to watch my pictures from Iphoto to my HD TV and stream some movies from the mac to tv, how do I do that?

  • Is it possible to have 2 icloud (from 2 different iphones with different apple ids) on the same computer?

    I am inquiring as to if you can 2 different icloud accounts (that come from 2 different iphones with different apple ids) on the same computer. I would like both iphones to be able to back up to the same computer since we have different accounts/pict

  • Group by trunc(date)

    Hi, lets say I have a source table like this Customer _ TimeStamp ________ BillAmount 001 ______ 01/01/2012 11:00 __ 100,00 001 ______ 01/01/2012 17:00 __ 150,00 I want to load a destination table like this Customer _ Date ________ BillAmount 001 ___

  • Can I run Firefox in chromeless mode (ie. with no Windows borders etc)

    I think chromeless mode is the correct term to use. Basically I want to run Firefox 8 without the usual Windows borders. For example to run it un-maximised but looking just as it does when maximised. If I'm not being clear please ask questions. Thank

  • Setting up Ipad in Russian language

    Hello, my friend wants to buy an IPad2 in England  and take it back to Russia.My question is...is this possible and does he need a Apple expert to show him when he buys it? Any advice would be greatly appreciated..many thanks.