Recherche avancée

Sur d’autres sites (9675)

• ffmpeg Invalid data found when processing input h264 to h265

  8 mars 2016, par ddio

  I want to convert video files from h264 to h265.

  The command I use worked for many files so far, but now I get an error for some files :

   # ffmpeg -i rst.mkv -vcodec hevc -x265-params crf=28 -sn -acodec copy -map 0  out.mkv
  
  ffmpeg version 2.8.6 Copyright (c) 2000-2016 the FFmpeg developers
  
    built with gcc 4.8.5 (Gentoo 4.8.5 p1.3, pie-0.6.2)
  
    configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --mandir=/usr/share/man --enable-shared --cc=x86_64-pc-linux-gnu-gcc --cxx=x86_64-pc-linux-gnu-g++ --ar=x86_64-pc-linux-gnu-ar --optflags='-O2 -pipe -march=core2' --disable-static --enable-avfilter --enable-avresample --disable-stripping --disable-indev=v4l2 --disable-outdev=v4l2 --disable-indev=alsa --disable-indev=oss --disable-indev=jack --disable-outdev=alsa --disable-outdev=oss --disable-outdev=sdl --enable-bzlib --disable-runtime-cpudetect --disable-debug --disable-doc --disable-gnutls --enable-gpl --enable-hardcoded-tables --enable-iconv --disable-lzma --enable-network --disable-openssl --enable-postproc --disable-libsmbclient --disable-ffplay --disable-sdl --disable-vaapi --disable-vdpau --disable-xlib --disable-libxcb --disable-libxcb-shm --disable-libxcb-xfixes --enable-zlib --disable-libcdio --disable-libiec61883 --disable-libdc1394 --disable-libcaca --disable-openal --disable-opengl --disable-libv4l2 --disable-libpulse --disable-libopencore-amrwb --disable-libopencore-amrnb --disable-libfdk-aac --disable-libopenjpeg --disable-libbluray --disable-libcelt --disable-libgme --disable-libgsm --disable-libmodplug --disable-libopus --disable-libquvi --disable-librtmp --disable-libssh --disable-libschroedinger --disable-libspeex --enable-libvorbis --enable-libvpx --disable-libzvbi --disable-libbs2b --disable-libflite --disable-frei0r --disable-libfribidi --disable-fontconfig --disable-ladspa --disable-libass --disable-libfreetype --disable-libsoxr --enable-pthreads --disable-libvo-aacenc --disable-libvo-amrwbenc --disable-libmp3lame --disable-libaacplus --disable-libfaac --disable-libsnappy --enable-libtheora --disable-libtwolame --disable-libwavpack --disable-libwebp --enable-libx264 --enable-libx265 --disable-libxvid --disable-x11grab --disable-amd3dnow --disable-amd3dnowext --disable-avx --disable-avx2 --disable-fma3 --disable-fma4 --disable-sse3 --disable-ssse3 --disable-sse4 --disable-sse42 --disable-xop --cpu=core2
  
    libavutil      54. 31.100 / 54. 31.100
  
    libavcodec     56. 60.100 / 56. 60.100
  
    libavformat    56. 40.101 / 56. 40.101
  
    libavdevice    56.  4.100 / 56.  4.100
  
    libavfilter     5. 40.101 /  5. 40.101
  
    libavresample   2.  1.  0 /  2.  1.  0
  
    libswscale      3.  1.101 /  3.  1.101
  
    libswresample   1.  2.101 /  1.  2.101
  
    libpostproc    53.  3.100 / 53.  3.100
  
  Input #0, matroska,webm, from 'rst.mkv':
  
    Metadata:
  
      encoder         : libebml v1.0.0 + libmatroska v1.0
  
    Duration: 00:21:22.28, start: 0.000000, bitrate: 11533 kb/s
  
      Chapter #0:0: start 0.000000, end 159.784000
  
      Metadata:
  
        title           : 00:00:00.000
  
      Chapter #0:1: start 159.784000, end 642.266000
  
      Metadata:
  
        title           : 00:02:39.784
  
      Chapter #0:2: start 642.266000, end 1225.641000
  
      Metadata:
  
        title           : 00:10:42.266
  
      Chapter #0:3: start 1225.641000, end 1254.878000
  
      Metadata:
  
        title           : 00:20:25.641
  
      Chapter #0:4: start 1254.878000, end 1282.281000
  
      Metadata:
  
        title           : 00:20:54.878
  
      Chapter #0:5: start 1282.364000, end 1282.281000
  
      Metadata:
  
        title           : 00:21:22.364
  
      Stream #0:0(eng): Video: h264 (High), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)
  
      Stream #0:1(ger): Audio: ac3, 48000 Hz, 5.1(side), fltp, 384 kb/s (default)
  
      Stream #0:2(eng): Audio: dts (DTS), 48000 Hz, 5.1(side), fltp, 1536 kb/s
  
  File 'tbbt-s07e02.mkv' already exists. Overwrite ? [y/N] y
  
  x265 [info]: HEVC encoder version 1.9
  
  x265 [info]: build info [Linux][GCC 4.8.5][64 bit] 8bit+10bit+12bit
  
  x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.1 Cache64
  
  x265 [info]: Main profile, Level-4 (Main tier)
  
  x265 [info]: Thread pool created using 4 threads
  
  x265 [info]: frame threads / pool features       : 2 / wpp(17 rows)
  
  x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
  
  x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
  
  x265 [info]: ME / range / subpel / merge         : hex / 57 / 2 / 2
  
  x265 [info]: Keyframe min / max / scenecut       : 23 / 250 / 40
  
  x265 [info]: Lookahead / bframes / badapt        : 20 / 4 / 2
  
  x265 [info]: b-pyramid / weightp / weightb       : 1 / 1 / 0
  
  x265 [info]: References / ref-limit  cu / depth  : 3 / 1 / 1
  
  x265 [info]: AQ: mode / str / qg-size / cu-tree  : 1 / 1.0 / 32 / 1
  
  x265 [info]: Rate Control / qCompress            : CRF-28.0 / 0.60
  
  x265 [info]: tools: rd=3 psy-rd=2.00 signhide tmvp strong-intra-smoothing
  
  x265 [info]: tools: lslices=6 deblock sao
  
  [matroska @ 0x1b09450] Codec for stream 1 does not use global headers but container format requires global headers
  
  [matroska @ 0x1b09450] Codec for stream 2 does not use global headers but container format requires global headers
  
  [matroska @ 0x1b09450] Invalid chapter start (1282364000000) or end (1282281000000).
  
  Output #0, matroska, to 'out.mkv':
  
    Metadata:
  
      encoder         : Lavf56.40.101
  
      Chapter #0:0: start 0.000000, end 159.784000
  
      Metadata:
  
        title           : 00:00:00.000
  
      Chapter #0:1: start 159.784000, end 642.266000
  
      Metadata:
  
        title           : 00:02:39.784
  
      Chapter #0:2: start 642.266000, end 1225.641000
  
      Metadata:
  
        title           : 00:10:42.266
  
      Chapter #0:3: start 1225.641000, end 1254.878000
  
      Metadata:
  
        title           : 00:20:25.641
  
      Chapter #0:4: start 1254.878000, end 1282.281000
  
      Metadata:
  
        title           : 00:20:54.878
  
      Chapter #0:5: start 1282.364000, end 1282.281000
  
      Metadata:
  
        title           : 00:21:22.364
  
      Stream #0:0(eng): Video: hevc (libx265), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 23.98 fps, 1k tbn, 23.98 tbc (default)
  
      Metadata:
  
        encoder         : Lavc56.60.100 libx265
  
      Stream #0:1(ger): Audio: ac3 ([0] [0][0] / 0x2000), 48000 Hz, 5.1(side), 384 kb/s (default)
  
      Stream #0:2(eng): Audio: dts ([1] [0][0] / 0x2001), 48000 Hz, 5.1(side), 1536 kb/s
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> hevc (libx265))
  
    Stream #0:1 -> #0:1 (copy)
  
    Stream #0:2 -> #0:2 (copy)
  
  Could not write header for output file #0 (incorrect codec parameters ?): Invalid data found when processing input
  
  
  
  encoded 0 frames

  The files in question are playable by for example mpv, so they are not corrupt.

• WebRTC predictions for 2016

  17 février 2016, par silvia

  I wrote these predictions in the first week of January and meant to publish them as encouragement to think about where WebRTC still needs some work. I’d like to be able to compare the state of WebRTC in the browser a year from now. Therefore, without further ado, here are my thoughts.

  WebRTC Browser support

  I’m quite optimistic when it comes to browser support for WebRTC. We have seen Edge bring in initial support last year and Apple looking to hire engineers to implement WebRTC. My prediction is that we will see the following developments in 2016 :

  • Edge will become interoperable with Chrome and Firefox, i.e. it will publish VP8/VP9 and H.264/H.265 support
  • Firefox of course continues to support both VP8/VP9 and H.264/H.265
  • Chrome will follow the spec and implement H.264/H.265 support (to add to their already existing VP8/VP9 support)
  • Safari will enter the WebRTC space but only with H.264/H.265 support

  Codec Observations

  With Edge and Safari entering the WebRTC space, there will be a larger focus on H.264/H.265. It will help with creating interoperability between the browsers.

  However, since there are so many flavours of H.264/H.265, I expect that when different browsers are used at different endpoints, we will get poor quality video calls because of having to negotiate a common denominator. Certainly, baseline will work interoperably, but better encoding quality and lower bandwidth will only be achieved if all endpoints use the same browser.

  Thus, we will get to the funny situation where we buy ourselves interoperability at the cost of video quality and bandwidth. I’d call that a “degree of interoperability” and not the best possible outcome.

  I’m going to go out on a limb and say that at this stage, Google is going to consider strongly to improve the case of VP8/VP9 by improving its bandwidth adaptability : I think they will buy themselves some SVC capability and make VP9 the best quality codec for live video conferencing. Thus, when Safari eventually follows the standard and also implements VP8/VP9 support, the interoperability win of H.264/H.265 will become only temporary overshadowed by a vastly better video quality when using VP9.

  The Enterprise Boundary

  Like all video conferencing technology, WebRTC is having a hard time dealing with the corporate boundary : firewalls and proxies get in the way of setting up video connections from within an enterprise to people outside.

  The telco world has come up with the concept of SBCs (session border controller). SBCs come packed with functionality to deal with security, signalling protocol translation, Quality of Service policing, regulatory requirements, statistics, billing, and even media service like transcoding.

  SBCs are a total overkill for a world where a large number of Web applications simply want to add a WebRTC feature – probably mostly to provide a video or audio customer support service, but it could be a live training session with call-in, or an interest group conference all.

  We cannot install a custom SBC solution for every WebRTC service provider in every enterprise. That’s like saying we need a custom Web proxy for every Web server. It doesn’t scale.

  Cloud services thrive on their ability to sell directly to an individual in an organisation on their credit card without that individual having to ask their IT department to put special rules in place. WebRTC will not make progress in the corporate environment unless this is fixed.

  We need a solution that allows all WebRTC services to get through an enterprise firewall and enterprise proxy. I think the WebRTC standards have done pretty well with firewalls and connecting to a TURN server on port 443 will do the trick most of the time. But enterprise proxies are the next frontier.

  What it takes is some kind of media packet forwarding service that sits on the firewall or in a proxy and allows WebRTC media packets through – maybe with some configuration that is necessary in the browsers or the Web app to add this service as another type of TURN server.

  I don’t have a full understanding of the problems involved, but I think such a solution is vital before WebRTC can go mainstream. I expect that this year we will see some clever people coming up with a solution for this and a new type of product will be born and rolled out to enterprises around the world.

  Summary

  So these are my predictions. In summary, they address the key areas where I think WebRTC still has to make progress : interoperability between browsers, video quality at low bitrates, and the enterprise boundary. I’m really curious to see where we stand with these a year from now.

  —

  It’s worth mentioning Philipp Hancke’s tweet reply to my post :

  https://datatracker.ietf.org/doc/draft-ietf-rtcweb-return/ … — we saw some clever people come up with a solution already. Now it needs to be implemented

• Combine images to video stream

  8 mars 2016, par idementia

  Can anyone please tell what is the easiest way to complete topic task in android studio ?
  I found some solutions but was unable to set to work any of them.

  1. One suggestion was to use FFmpeg recorder like it’s described here. Problem is recorder takes only IplImage type. I tried to create IplImage with javacv.cpp.opencv_core, but it refers to java.awt.* stuff, which is not supported by android, so i catch crash. Moreover, using IplImage is highly unlikely because it is old format and because transformations of Mat (that’s type that i have) to IplImage takes a lot of formating steps with byte[], BufferedImage and other types of one to another.

  2. Another way i tried from here. It looked acceptable - to process multiple .jpeg to video stream with codecs. But as far as i understand problem is that FFmpeg is not provided as complete stand-alone SDK lib for android. And almost all web-links to source FFmpeg-files which could contain methods (like execFFMPEG) are already dead.

  In general, topic task must not be hard : to combine simple video stream with given set of images, fixed fps and video coder (i don’t even need audio stream). In practice, i’m already overheaded with tones of infos and still not a step closer to solution.
  Thanks in advance.