Recherche avancée

Sur d’autres sites (14565)

• capture my webcam and encode to mp4 with ffmpeg, but the x264 works bad

  17 septembre 2015, par zhangxm1991

  here is my version :
  ffmpeg version : 2.3.3
  libx264 version:142.x

  I wat to capture my video and use ffmpeg and x264 to a mp4 file. the solution is 320x240.
  But i found that the video file is so big. Then i found that the P frame and B frame is very big, even nearly equal to the I frame.I do not know why.

  here is my code :

      c->codec_id = codec_id;
  
      c->bit_rate = 400000;
  
      c->width    = 320;
  
      c->height   = 240;
  
      c->time_base.den = 10;
  
      c->time_base.num = 1;
  
      c->pix_fmt       = AV_PIX_FMT_YUV420P;

  Here is my program output :

  [libx264 @ 0xb6200fc0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX 
  
  
  
  [libx264 @ 0xb6200fc0] profile High, level 1.3
  
  
  
  [libx264 @ 0xb6200fc0] 264 - core 142 - H.264/MPEG-4 AVC codec - Copyleft 2003-2014 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=10 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=abr mbtree=1 bitrate=400 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  
  
  Output #0, mp4, to '/home/2014_09_12/0002b6429579/5/2014_09_12_18_39_12_600.mp4':
  
  
  
      Stream #0:0: Video: h264 (libx264), yuv420p, 320x240, q=-1--1, 400 kb/s, 10 tbc
  
  
  
      Stream #0:1: Audio: aac, 8000 Hz, mono, fltp, 32 kb/s
  
  
  
  [mp4 @ 0xb62005e0] Using AVStream.codec.time_base as a timebase hint to the muxer is deprecated. Set AVStream.time_base instead.
  
  
  
  [mp4 @ 0xb62005e0] Using AVStream.codec.time_base as a timebase hint to the muxer is deprecated. Set AVStream.time_base instead.
  
  
  
  [mp4 @ 0xb62005e0] Encoder did not produce proper pts, making some up.
  
  
  
  [libx264 @ 0xb6200fc0] frame I:3     Avg QP: 2.79  size: 72996
  
  
  
  [libx264 @ 0xb6200fc0] frame P:383   Avg QP: 0.14  size: 54075
  
  
  
  [libx264 @ 0xb6200fc0] frame B:216   Avg QP: 1.95  size: 64784
  
  
  
  [libx264 @ 0xb6200fc0] consecutive B-frames: 30.1% 63.2%  6.0%  0.7%
  
  
  
  [libx264 @ 0xb6200fc0] mb I  I16..4: 16.1% 12.7% 71.2%
  
  
  
  [libx264 @ 0xb6200fc0] mb P  I16..4:  3.5%  5.1% 15.9%  P16..4: 20.3% 22.8% 14.0%  0.0%  0.0%    skip:18.3%
  
  
  
  [libx264 @ 0xb6200fc0] mb B  I16..4:  0.4%  2.5%  8.2%  B16..8: 32.6% 19.8% 13.5%  
  
  direct:22.2%  skip: 0.8%  L0:25.5% L1:12.8% BI:61.6%
  
  
  
  [libx264 @ 0xb6200fc0] final ratefactor: -32.89
  
  
  
  [libx264 @ 0xb6200fc0] 8x8 transform intra:21.0% inter:29.6%
  
  
  
  [libx264 @ 0xb6200fc0] coded y,uvDC,uvAC intra: 100.0% 100.0% 100.0% inter: 83.3% 80.9% 80.9%
  
  
  
  [libx264 @ 0xb6200fc0] i16 v,h,dc,p:  5%  7% 42% 46%
  
  
  
  [libx264 @ 0xb6200fc0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 14% 12% 23%  8%  6%  6%  8%  9% 14%
  
  
  
  [libx264 @ 0xb6200fc0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 12% 11% 19% 10%  8%  8% 10% 10% 12%
  
  
  
  [libx264 @ 0xb6200fc0] i8c dc,h,v,p: 78%  3%  4% 15%
  
  
  
  [libx264 @ 0xb6200fc0] Weighted P-Frames: Y:0.5% UV:0.3%
  
  
  
  [libx264 @ 0xb6200fc0] ref P L0: 43.4% 14.6% 19.0% 22.9%  0.1%
  
  
  
  [libx264 @ 0xb6200fc0] ref B L0: 63.3% 35.7%  1.1%
  
  
  
  [libx264 @ 0xb6200fc0] ref B L1: 97.0%  3.0%
  
  
  
  [libx264 @ 0xb6200fc0] kb/s:4.53
  
  
  
  [aac @ 0xb6201ba0] 2 frames left in the queue on closing

• ffmpeg Streams mixed when using -filter_complex amerge

  25 août 2014, par BrainStone

  I am currently having issues with ffmpeg and one of its filters.

  I am trying to merge 2 audio streams of a video into one. for this purpose I tried this command :

  ffmpeg -i /home/maniaplanet/Videos/ManiaPlanet\ 2014-08-21\ 20-09-13-082.avi.output.mkv -filter_complex "[0:1][0:2] amerge=inputs=2"-c:v copy -c:a libvo_aacenc -b:a 256k /var/www/files/output.mp4

  But I get this output :

  ffmpeg version 1.0.10 Copyright (c) 2000-2014 the FFmpeg developers
  
    built on Jul 25 2014 07:50:40 with gcc 4.7 (Debian 4.7.2-5)
  
    configuration: --prefix=/usr --extra-cflags='-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security ' --extra-ldflags='-Wl,-z,relro' --cc='ccache cc' --enable-shared --enable-libmp3lame --enable-gpl --enable-nonfree --enable-libvorbis --enable-pthreads --enable-libfaac --enable-libxvid --enable-postproc --enable-x11grab --enable-libgsm --enable-libtheora --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libx264 --enable-libspeex --enable-nonfree --disable-stripping --enable-libvpx --enable-libschroedinger --disable-encoder=libschroedinger --enable-version3 --enable-libopenjpeg --enable-librtmp --enable-avfilter --enable-libfreetype --enable-libvo-aacenc --disable-decoder=amrnb --enable-libvo-amrwbenc --enable-libaacplus --libdir=/usr/lib/x86_64-linux-gnu --disable-vda --enable-libbluray --enable-libcdio --enable-gnutls --enable-frei0r --enable-openssl --enable-libass --enable-libopus --enable-fontconfig --enable-libfdk-aac --enable-libdc1394 --disable-altivec --dis  libavutil      51. 73.101 / 51. 73.101
  
    libavcodec     54. 59.100 / 54. 59.100
  
    libavformat    54. 29.104 / 54. 29.104
  
    libavdevice    54.  2.101 / 54.  2.101
  
    libavfilter     3. 17.100 /  3. 17.100
  
    libswscale      2.  1.101 /  2.  1.101
  
    libswresample   0. 15.100 /  0. 15.100
  
    libpostproc    52.  0.100 / 52.  0.100
  
  Input #0, matroska,webm, from '/home/maniaplanet/Videos/ManiaPlanet 2014-08-21 20-09-13-082.avi.output.mkv':
  
    Metadata:
  
      ISRC            : Video:RGB24 Audio0:Headset (2- Plantronics .Audio 655 DSP) Audio1:Headset (2- Plantronics .Audio 655 DSP)
  
      ENCODER         : Lavf55.37.100
  
    Duration: 01:49:48.47, start: 0.000000, bitrate: 3867 kb/s
  
      Stream #0:0: Video: h264 (High), yuv420p, 1280x1024, SAR 1:1 DAR 5:4, 30 fps, 30 tbr, 1k tbn, 60 tbc (default)
  
      Stream #0:1: Audio: mp3, 48000 Hz, stereo, s16, 320 kb/s (default)
  
      Stream #0:2: Audio: mp3, 48000 Hz, stereo, s16, 320 kb/s (default)
  
  File '/var/www/files/output.mp4' already exists. Overwrite ? [y/N] y
  
  Input channel layouts overlap: output layout will be determined by the number of distinct input channels
  
  [libvo_aacenc @ 0x7ae800] Unable to set encoding parameters
  
  Output #0, mp4, to '/var/www/files/output.mp4':
  
    Metadata:
  
      ISRC            : Video:RGB24 Audio0:Headset (2- Plantronics .Audio 655 DSP) Audio1:Headset (2- Plantronics .Audio 655 DSP)
  
      ENCODER         : Lavf55.37.100
  
      Stream #0:0: Audio: aac, 48000 Hz, 4.0, s16, 256 kb/s
  
      Stream #0:1: Video: h264, yuv420p, 1280x1024 [SAR 1:1 DAR 5:4], q=2-31, 30 fps, 90k tbn, 1k tbc (default)
  
  Stream mapping:
  
    Stream #0:1 (mp3) -> amerge:in0
  
    Stream #0:2 (mp3) -> amerge:in1
  
    amerge -> Stream #0:0 (libvo_aacenc)
  
    Stream #0:0 -> #0:1 (copy)
  
  Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

  I think the important part is at the bottom :

  Stream mapping:
  
    Stream #0:1 (mp3) -> amerge:in0
  
    Stream #0:2 (mp3) -> amerge:in1
  
    amerge -> Stream #0:0 (libvo_aacenc)
  
    Stream #0:0 -> #0:1 (copy)

  It maps the video stream as the second stream and the audio gets first. How do i resolve this ? -map did not help. (Maybe I just used it wrong)

• Announcing our latest open source project : DeviceDetector

  30 juillet 2014, par Stefan Giehl — Community, Development, Meta, DeviceDetector

  This blog post is an announcement for our latest open source project release : DeviceDetector ! The Universal Device Detection library will parse any User Agent and detect the browser, operating system, device used (desktop, tablet, mobile, tv, cars, console, etc.), brand and model.

  Read on to learn more about this exciting release.

  Why did we create DeviceDetector ?

  Our previous library UserAgentParser only had the possibility to detect operating systems and browsers. But as more and more traffic is coming from mobile devices like smartphones and tablets it is getting more and more important to know which devices are used by the websites visitors.

  To ensure that the device detection within Piwik will gain the required attention, so it will be as accurate as possible, we decided to move that part of Piwik into a separate project, that we will maintain separately. As an own project we hope the DeviceDetector will gain a better visibility as well as a better support by and for the community !

  DeviceDetector is hosted on GitHub at piwik/device-detector. It is also available as composer package through Packagist.

  How DeviceDetector works

  Every client requesting data from a webserver identifies itself by sending a so-called User-Agent within the request to the server. Those User Agents might contain several information such as :

  • client name and version (clients can be browsers or other software like feed readers, media players, apps,…)
  • operating system name and version
  • device identifier, which can be used to detect the brand and model.

  For Example :

  Mozilla/5.0 (Linux; Android 4.4.2; Nexus 5 Build/KOT49H) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.99 Mobile Safari/537.36

  This User Agent contains following information :

  Operating system is Android 4.4.2, client uses the browser Chrome Mobile 32.0.1700.99 and the device is a Google Nexus 5 smartphone.

  What DeviceDetector currently detects

  DeviceDetector is able to detect bots, like search engines, feed fetchers, site monitors and so on, five different client types, including around 100 browsers, 15 feed readers, some media players, personal information managers (like mail clients) and mobile apps using the AFNetworking framework, around 80 operating systems and nine different device types (smartphones, tablets, feature phones, consoles, tvs, car browsers, cameras, smart displays and desktop devices) from over 180 brands.

  Note : Piwik itself currently does not use the full feature set of DeviceDetector. Client detection is currently not implemented in Piwik (only detected browsers are reported, other clients are marked as Unknown). Client detection will be implemented into Piwik in the future, follow #5413 to stay updated.

  Performance of DeviceDetector

  Our detections are currently handled by an enormous number of regexes, that are defined in several .YML Files. As parsing these .YML files is a bit slow, DeviceDetector is able to cache the parsed .YML Files. By default DeviceDetector uses a static cache, which means that everything is cached in static variables. As that only improves speed for many detections within one process, there are also adapters to cache in files or memcache for speeding up detections across requests.

  How can users help contribute to DeviceDetector ?

  Submit your devices that are not detected yet

  If you own a device, that is currently not correctly detected by the DeviceDetector, please create a issue on GitHub
  In order to check if your device is detected correctly by the DeviceDetector go to your Piwik server, click on ‘Settings’ link, then click on ‘Device Detection’ under the Diagnostic menu. If the data does not match, please copy the displayed User Agent and use that and your device data to create a ticket.

  Submit a list of your User Agents

  In order to create new detections or improve the existing ones, it is necessary for us to have lists of User Agents. If you have a website used by mostly non desktop devices it would be useful if you send a list of the User Agents that visited your website. To do so you need access to your access logs. The following command will extract the User Agents :

  zcat ~/path/to/access/logs* | awk -F'"' '{print $6}' | sort | uniq -c | sort -rn | head -n20000 > /home/piwik/top-user-agents.txt

  If you want to help us with those data, please get in touch at devicedetector@piwik.org

  Submit improvements on GitHub

  As DeviceDetector is free/libre library, we invite you to help us improving the detections as well as the code. Please feel free to create tickets and pull requests on Github.

  What’s the next big thing for DeviceDetector ?

  Please check out the list of issues in device-detector issue tracker.

  We hope the community will answer our call for help. Together, we can build DeviceDetector as the most powerful device detection library !

  Happy Device Detection,