Announcement

Collapse
No announcement yet.

FFmpeg 1.1 Brings New Support, Encoders/Decoders

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Originally posted by tuke81 View Post
    Well yeah I could have been more precise. I did not suggest you to use .srt just try the ffmpeg command if it recognize at all your subtitle file.
    No its not Working

    Code:
    subtitle.ass: Invalid data found when processing input
    But the ass filter is happy with this files and aegisub too.

    Comment


    • #17
      Hmm odd. Does any other .ass subtitle work? I.e. this(I can't find a good example file with google):
      http://code.ohloh.net/file?fid=m75vO...ser=Default#L0

      When I convert it to .srt with my comp(well it's .ssa but it's the same with any .ass file):
      Code:
      $ ffmpeg -i subtitle.ssa subtitle.srt
      ffmpeg version 1.1-1.1-0ubuntu0~precise1 Copyright (c) 2000-2013 the FFmpeg developers
        built on Jan  8 2013 18:46:24 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5)
        configuration: --enable-libass --arch=amd64 --enable-pthreads --enable-runtime-cpudetect --extra-version='1.1-0ubuntu0~precise1' --libdir=/usr/lib/x86_64-linux-gnu --disable-stripping --prefix=/usr --enable-bzlib --enable-libdc1394 --enable-libfreetype --enable-frei0r --enable-gnutls --enable-libgsm --enable-libmp3lame --enable-librtmp --enable-libopencv --enable-libopenjpeg --enable-libpulse --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-vaapi --enable-vdpau --enable-libvorbis --enable-libvpx --enable-zlib --enable-gpl --enable-postproc --enable-libcdio --enable-x11grab --enable-libx264 --shlibdir=/usr/lib/x86_64-linux-gnu --enable-shared --disable-static --enable-libxvid
        libavutil      52. 13.100 / 52. 13.100
        libavcodec     54. 86.100 / 54. 86.100
        libavformat    54. 59.106 / 54. 59.106
        libavdevice    54.  3.102 / 54.  3.102
        libavfilter     3. 32.100 /  3. 32.100
        libswscale      2.  1.103 /  2.  1.103
        libswresample   0. 17.102 /  0. 17.102
        libpostproc    52.  2.100 / 52.  2.100
      [ass @ 0x793560] Estimating duration from bitrate, this may be inaccurate
      Input #0, ass, from 'subtitle.ssa':
        Duration: N/A, bitrate: N/A
          Stream #0:0: Subtitle: ssa
      Output #0, srt, to 'subtitle.srt':
        Metadata:
          encoder         : Lavf54.59.106
          Stream #0:0: Subtitle: subrip
      Stream mapping:
        Stream #0:0 -> #0:0 (ass -> subrip)
      Press [q] to stop, [?] for help
      size=       0kB time=00:00:01.18 bitrate=   0.8kbits/s    
      video:0kB audio:0kB subtitle:0 global headers:0kB muxing overhead 43.037975%

      Comment


      • #18
        Mh ok now i found the issue.

        Aegisub don't write to the first line
        Code:
        [Script Info]
        If i Add this to my sub it work. Without this ffmpeg cant detect it. curious is that the filters work without an problem and don't write any message about this in the log.

        Thx tuke81


        EDIT: The new Aegisub Versions.
        Last edited by Nille; 01-08-2013, 03:06 PM.

        Comment


        • #19
          I find it quite odd too, line [Script Info] should be there by the ssa specs. I'm not familiar with Aegisub, but if filter does not even throw warnings about missing line that spec requires it is bad filter.

          Comment


          • #20
            Originally posted by tuke81 View Post
            I find it quite odd too, line [Script Info] should be there by the ssa specs. I'm not familiar with Aegisub, but if filter does not even throw warnings about missing line that spec requires it is bad filter.
            xvfilters and libass say nothing agains this. and i dont know if there is an other library for ass.

            Comment


            • #21
              Still no H.264 MVC (multiview video coding) support. Is anybody working on this at all?

              Comment


              • #22
                Originally posted by arokh View Post
                Still no H.264 MVC (multiview video coding) support. Is anybody working on this at all?
                Well I think it was part of ESA:s summer of code 2012, which had deadline 28.10.2012:
                http://wiki.multimedia.cx/index.php?...2012#H.264_MVC
                http://wiki.multimedia.cx/index.php?..._In_Space_2012

                But I don't know did they find anyone to code it.

                Edit: I think it failed, but it have started(kind of):
                [00:35] <canbal> hi, does anyone know if there are any plans or working progress on supporting H.264/MVC decoding in ffmpeg?
                [00:36] <michaelni> why do you ask ?
                [00:37] <michaelni> do you want to work on that ?
                [00:46] <canbal> i work on H.264/MVC and Video+Depth compression in my research
                [00:46] <canbal> and I rely on ffmpeg constantly to do frame extraction etc
                [00:47] <canbal> i recently encountered a consumer level camera that encodes MVC and i tried to extract frames from it
                [00:47] <canbal> ffmpeg obviously doesn't support it, so i was wondering if i could be any help for the implementation
                [00:47] <canbal> i don't have the time to take the lead, but i would like to contribute if there is any working progress or any intentions
                [00:49] <gnafu> Ooh, which camera?
                [00:52] <canbal> http://amzn.to/IqAGL7
                [00:52] <canbal> sony td20 3d camera
                [00:53] <gnafu> Cool, thanks.
                [00:53] <canbal> np, so any ideas if anyone is working on this and looking for some help?
                [00:53] <michaelni> canbal, there definitly is interrest in a MVC implementation and i had considered to work on it myself
                [00:53] <michaelni> but iam too busy
                [00:54] <michaelni> with other open source things ...
                [00:56] <canbal> i see
                [00:56] <canbal> i am quite busy too - working part time and doing a phd at the same time
                [00:56] <canbal> that's why i can't dare to start on my own
                [01:08] <Compn> canbal : ask on the list
                [01:08] <Compn> i think there are some interested parties who may want to join up
                [01:09] <canbal> ok i will do that
                [01:09] <canbal> thank you for the info
                [01:09] <Compn> at least michael said he would mentor , in our failed bid for summer of code project
                [01:10] <Compn> so there will be help, if you want to start
                [01:10] <Compn> i think a good place to start is just to start a discussion on how to work the api
                [01:10] <Compn> e.g. how to demux it and pass to decoder
                [01:12] <Compn> seems like a difficult thing to do
                [01:12] <Compn> well maybe not
                [01:12] <Compn> wonder how optimizing would go , can motion vectors be reused? :P
                [01:31] <canbal> for decode process, the MVC stream macroblocks have their own motion vectors
                Last edited by tuke81; 01-09-2013, 10:31 AM.

                Comment


                • #23
                  It's all wrong that article

                  Except that most of that article is just plain wrong.

                  FFmpeg 1.1 is a bug fix release of the release/1.0 branch.

                  There's nothing new since ffmpeg 1.0 ; just bug fixes.

                  Most of the changes listed are only in the current FFmpeg master.

                  Comment


                  • #24
                    Originally posted by jyavenard View Post
                    Except that most of that article is just plain wrong.

                    FFmpeg 1.1 is a bug fix release of the release/1.0 branch.

                    There's nothing new since ffmpeg 1.0 ; just bug fixes.

                    Most of the changes listed are only in the current FFmpeg master.
                    No, you are wrong. Bug fix releases for the 1.0 branch are released as 1.0.x.

                    1.1 is a feature release. Try actually reading the ChangeLog.

                    Comment

                    Working...
                    X