Advanced search

On other websites (9645)

• My FFMPEG converter is not allowing mp4 to webm conversions.

  2 November 2016, by Fred Garbutt

  heres the command:

  ffmpeg -i videos/test.mp4 -c:v libvpx -level 216 -profile 0 -qmax 42 -qmin 10 -c:a libvorbis -f webm out.webm

  i keep getting this error:

  Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

  here is the full response

  # ffmpeg -i videos/test.mp4 -c:v libvpx -level 216 -profile 0 -qmax 42 -qmin 10 -c:a 
  
  
  
  libvorbis -f webm out.webm
  
  ffmpeg version N-49225-g7e059c9 Copyright (c) 2000-2013 the FFmpeg developers
  
    built on Jan 24 2013 05:14:06 with gcc 4.1.2 (GCC) 20080704 (Red Hat 4.1.2-54)
  
    configuration: --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvpx --enable-libfaac --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-gpl --enable-postproc --enable-nonfree
  
    libavutil      52. 15.101 / 52. 15.101
  
    libavcodec     54. 90.100 / 54. 90.100
  
    libavformat    54. 61.104 / 54. 61.104
  
    libavdevice    54.  3.102 / 54.  3.102
  
    libavfilter     3. 33.100 /  3. 33.100
  
    libswscale      2.  2.100 /  2.  2.100
  
    libswresample   0. 17.102 /  0. 17.102
  
    libpostproc    52.  2.100 / 52.  2.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'videos/test.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 1
  
      compatible_brands: mp42avc1
  
      creation_time   : 2010-08-12 15:42:21
  
    Duration: 00:00:34.20, start: 0.000000, bitrate: 358 kb/s
  
      Stream #0:0(eng): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 100 kb/s
  
      Metadata:
  
        creation_time   : 2010-08-12 15:42:21
  
        handler_name    : Apple Sound Media Handler
  
      Stream #0:1(eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 640x320, 251 kb/s, 29.97 fps, 29.97 tbr, 2997 tbn, 5994 tbc
  
      Metadata:
  
        creation_time   : 2010-08-12 15:42:21
  
        handler_name    : Apple Video Media Handler
  
  Please use -profile:a or -profile:v, -profile is ambiguous
  
  File 'out.webm' already exists. Overwrite ? [y/N] y
  
  v0.9.6
  
  [libvpx @ 0x7e38d20] Failed to initialize encoder: ABI version mismatch
  
  Output #0, webm, to 'out.webm':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 1
  
      compatible_brands: mp42avc1
  
      Stream #0:0(eng): Video: vp8, yuv420p, 640x320, q=10-42, 200 kb/s, 90k tbn, 29.97 tbc
  
      Metadata:
  
        creation_time   : 2010-08-12 15:42:21
  
        handler_name    : Apple Video Media Handler
  
      Stream #0:1(eng): Audio: none, 44100 Hz, stereo, fltp
  
      Metadata:
  
        creation_time   : 2010-08-12 15:42:21
  
        handler_name    : Apple Sound Media Handler
  
  Stream mapping:
  
    Stream #0:1 -> #0:0 (h264 -> libvpx)
  
    Stream #0:0 -> #0:1 (aac -> libvorbis)
  
  Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

  does anybody have any idea whats going on? I am completely lost. I have tried so many different commands. converting from mp4 to ogg works fine, and i have had mp4 to webm working before, but i reinstalled ffmpeg to get the mp4 to ogg working and now ive lost my mp4 to webm conversions. >.< this whole installation process is such a damn nightmare. does anyone havea good tutorial for centos installation of ffmpeg that will work for mp4 ogg and webm? I have used the centos tut that came off of the ffmpeg site, but it failed me. If anyone has any ideas that could point me in the right direction i would much appreciate it!

• How To Play Hardware Accelerated Video on A Mac

  28 May 2013, by Multimedia Mike — General

  I have a friend who was considering purchasing a Mac Mini recently. At the time of this writing, there are 3 desktop models (and 2 more “server” models).

  
  
  

  The cheapest one is a Core i5 2.5 GHz. Then there are 2 Core i7 models: 2.3 GHz and 2.6 GHz. The difference between the latter 2 is US$100. The only appreciable technical difference is the extra 0.3 GHz and the choice came down to those 2.

  He asked me which one would be able to play HD video at full frame rate. I found this query puzzling. But then, I have been “in the biz” for a bit too long. Whether or not a computer or device can play a video well depends on a lot of factors.

  Hardware Support
  First of all, looking at the raw speed of the general-purpose CPU inside of a computer as a gauge of video playback performance is generally misguided in this day and age. In general, we have a video standard (H.264, which I’ll focus on for this post) and many bits of hardware are able to accelerate decoding. So, the question is not whether the CPU can decode the data in real time, but can any other hardware in the device (likely the graphics hardware) handle it? These machines have Intel HD 4000 graphics and, per my reading of the literature, they are capable of accelerating H.264 video decoding.

  Great, so the hardware supports accelerated decoding. So it’s a done deal, right? Not quite…

  Operating System Support
  An application can’t do anything pertaining to hardware without permission from the operating system. So the next question is: Does Mac OS X allow an application to access accelerated video decoding hardware if it’s available? This used to be a contentious matter (notably, Adobe Flash Player was unable to accelerate H.264 playback on Mac in the absence of such an API) but then Apple released an official API detailed in Technical Note TN2267.

  So, does this mean that video is magically accelerated? Nope, we’re still not there yet…

  Application Support
  It’s great that all of these underlying pieces are in place, but if an individual application chooses to decode the video directly on the CPU, it’s all for naught. An application needs to query the facilities and direct data through the API if it wants to leverage the acceleration. Obviously, at this point it becomes a matter of “which application?”

  My friend eventually opted to get the pricier of the desktop Mac Mini models and we ran some ad-hoc tests since I was curious how widespread the acceleration support is among Mac multimedia players. Here are some programs I wanted to test, playing 1080p H.264:

  • Apple QuickTime Player
  • VLC
  • YouTube with Flash Player (any browser)
  • YouTube with Safari/HTML5
  • YouTube with Chrome/HTML5
  • YouTube with Firefox/HTML5
  • Netflix

  I didn’t take exhaustive notes but my impromptu tests revealed QuickTime Player was, far and away, the most performant player, occupying only around 5% of the CPU according to the Mac OS X System Profiler graph (which is likely largely spent on audio decoding).

  VLC consistently required 20-30% CPU, so it’s probably leveraging some acceleration facilities. I think that Flash Player and the various HTML5 elements performed similarly (their multi-process architectures can make such a trivial profiling test difficult).

  The outlier was Netflix running in Firefox via Microsoft’s Silverlight plugin. Of course, the inner workings of Netflix’s technology are opaque to outsiders and we don’t even know if it uses H.264. It may very well use Microsoft’s VC-1 which is not a capability provided by the Mac OS X acceleration API (it doesn’t look like the Intel HD 4000 chip can handle it either). I have never seen any data one way or another about how Netflix encodes video. However, I was able to see that Netflix required an enormous amount of CPU muscle on the Mac platform.

  Conclusion
  The foregoing is a slight simplification of the video playback pipeline. There are some other considerations, most notably how the video is displayed afterwards. To circle back around to the original question: Can the Mac Mini handle full HD video playback? As my friend found, the meager Mac Mini can do an admirable job at playing full HD video without loading down the CPU.

• Xcode with ffmpeg support

  5 October 2013, by user2741735

  I wanted to know the procedure for compiling the xcode project with ffmpeg with special ./configure options and the gas-processor. I'm using direct input from IP Camera and storing it on my hard drive. However I'm doing this on terminal with ffmpeg. I want to do the same operations using code on xcode. Need help for that.

  I have heard that Apple doesn't support ffmpeg for ios apps on AppStore. Is it true?