Recherche avancée

Sur d’autres sites (12628)

• Video length missing in FLV converted by ffmpeg-php

  19 janvier 2013, par Andrew

  I'm converting MP4 videos to FLV using ffmpeg-php on my CentOS server (without intervention from flvtool2 because it's not installed).

  The FLV videos are created, but no player is capable of retrieving the video duration, this creates serious issues when trying to seek the video. I'm using the player created by Moyea's Flash Video MX Pro, but the problem also happens with other FLV players as well, so I'm sure that ffmpeg-php is not createing the FLV with the proper length data.

  My MP4 videos are compatible because ffmpeg-php CAN get the video length properly from then, yet it does not apply that length information into the FLV file. I assume flvtool2 is ONLY to retrieve meta-data and has nothing to do with the output FLV video length, let me know if this is correct.

  This command I use for conversion :

  $command = "ffmpeg -i myvideo.mp4 -ar 22050 -ab 64k -f flv -s 320x240 -y myvideo.flv";
  
  $result = @shell_exec($command);

  This is my ffmpeg-php version :

  FFmpeg version 0.5, Copyright (c) 2000-2009 Fabrice Bellard, et al.
  
    configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --mandir=/usr/share/man --incdir=/usr/include --extra-cflags=-fPIC --enable-libamr-nb --enable-libamr-wb --enable-libdirac --enable-libfaac --enable-libfaad --enable-libmp3lame --enable-libtheora --enable-libx264 --enable-gpl --enable-nonfree --enable-postproc --enable-pthreads --enable-shared --enable-swscale --enable-x11grab
  
    libavutil     49.15. 0 / 49.15. 0
  
    libavcodec    52.20. 0 / 52.20. 0
  
    libavformat   52.31. 0 / 52.31. 0
  
    libavdevice   52. 1. 0 / 52. 1. 0
  
    libswscale     0. 7. 1 /  0. 7. 1
  
    libpostproc   51. 2. 0 / 51. 2. 0
  
    built on Jul 24 2009 01:40:27, gcc: 4.1.2 20080704 (Red Hat 4.1.2-44)

  Any help on this issue will be greatly appreciated.

• Revision fb1f6f1db4 : Fix segment feature data type. It has a range of -255,255, so should be int16_t

  7 juin 2013, par Ronald S. Bultje

  Changed Paths :
   Modify /vp9/common/vp9_blockd.h

  
  
  Fix segment feature data type.

  It has a range of -255,255, so should be int16_t, not int8_t.

  Change-Id : I5ef4b6aefb6212b0f35f4754f3c4d73fddbc52a0

• FFmpeg Not Transcoding In Real Time

  2 décembre 2018, par Nimble

  Been setting up a recording build for a friend to resemble mine, but I can’t seem to get things to work in real-time despite sufficient (as far as I can tell) hardware.

  System specs : 8600K, GTX 1050ti, 16Gb RAM, 1tb 860 EVO

  Test command :

  ffmpeg -y -hide_banner -thread_queue_size 9999 -indexmem 9999 -guess_layout_max 0 -f dshow -rtbufsize 2147.48M `
  
  -video_size 1920x1080 -framerate 60 `
  
  -i video="@device_pnp_\\?\usb#vid_07ca&pid_0570&mi_00#7&3886ab1a&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global":audio="@device_cm_{33D9A762-90C8-11D0-BD43-00A0C911CE86}\wave_{0A494693-5F33-4304-88D7-394757E09648}" `
  
  -thread_queue_size 9999 -indexmem 9999 -guess_layout_max 0 -f dshow -rtbufsize 2147.48M `
  
  -video_size 1920x1080 -framerate 60 `
  
  -i video="@device_pnp_\\?\usb#vid_07ca&pid_0570&mi_00#7&24df76f&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global":audio="@device_cm_{33D9A762-90C8-11D0-BD43-00A0C911CE86}\wave_{0E6F0DEF-2B29-4117-8D30-13F01160AC5B}" `
  
  -map 0:0,0:1 -map 0:1 -c:v h264_nvenc -r 60 -rc-lookahead 120 -forced-idr 1 -strict_gop 1 -sc_threshold 0 -flags +cgop `
  
  -force_key_frames "expr:gte(t,n_forced*2)" -preset: llhp -pix_fmt nv12 -b:v 250M -minrate 250M -maxrate 250M `
  
  -bufsize 250M -c:a aac -ar 44100 -b:a 384k -ac 2 -af "aresample=async=250" -vsync 1 -ss 00:00:00.000 `
  
  -max_muxing_queue_size 9999 -f segment -segment_time 600 -segment_wrap 9 -reset_timestamps 1 `
  
  -segment_format_options max_delay=0 C:\Users\Jordan\Videos\FFmpeg\Left\Left%02d.ts `
  
  -map 1:0,1:1 -map 1:1 -c:v h264_nvenc -r 60 -rc-lookahead 120 -forced-idr 1 -strict_gop 1 -sc_threshold 0 -flags +cgop `
  
  -force_key_frames "expr:gte(t,n_forced*2)" -preset: llhp -pix_fmt nv12 -b:v 250M -minrate 250M -maxrate 250M `
  
  -bufsize 250M -c:a aac -ar 44100 -b:a 384k -ac 2 -af "aresample=async=250" -vsync 1 -ss 00:00:00.000 `
  
  -max_muxing_queue_size 9999 -f segment -segment_time 600 -segment_wrap 9 -reset_timestamps 1 `
  
  -segment_format_options max_delay=0 C:\Users\Jordan\Videos\FFmpeg\Right\Right%02d.ts

  For one reason or another this command is not transcoding video in real-time, which is a big issue when you’re trying to record not simply convert a file. When I omit one of the two outputs or if I halve the resolution of each input / output everything works in real-time. This would make me believe there is a bottleneck in the system somewhere but when monitoring everything in task manager nothing is even close to capping out (GPU encoder, cpu, ram, and SSD below 30% usage).

  Furthermore when I try recording both streams in one 4K60 video via OBS things work perfectly fine, as in real-time. So I don’t understand how transcoding two 1080p60 streams in FFmpeg would be anymore intensive than one 4K60 stream in OBS... When looking at the GPUs encoding chip usage it shows about 30% for the two 1080p60 streams on FFmpeg and 80% usage for single 4K60 stream in OBS, yet the OBS recording is real-time while the FFmpeg recording is at .6x speed.

  Lastly I run a very similar command at home but instead of two 1080p60 streams I’m doing 2 4K60 streams, a 1080p60 stream, and another 2 audio streams without issue. I do have a GTX 1080 though... however when monitoring usage for the 1050 TI being used in this situation nothing points to a GPU bottlecap.

  Any insight would be greatly appreciated, been going at this for hours now with no clue as to what could be causing this.