Recherche avancée

Sur d’autres sites (7180)

• Libavformat records RTP stream too fast (too high FPS)

  14 avril 2022, par cydonia

  I am trying to record an RTP stream using libavformat, however the FPS of recorded videos are ridiculously high, I get thousands of FPS, if not ten thousands. I tried to set the FPS to 30 making the following modifications :

  


  AVFormatContext *src; // Assume src is set here to demuxer's context
AVStream *source_stream = src->streams[i];
AVStream *dest_stream = avformat_new_stream(dest, NULL); // dest is muxer's context here
const AVCodec *pCodec = avcodec_find_decoder(source_stream->codecpar->codec_id);
AVCodecContext *avctx = avcodec_alloc_context3(pCodec);
avctx->time_base = av_make_q(1, 30000);
avcodec_parameters_to_context(avctx, source_stream->codecpar);
avcodec_parameters_from_context(dest_stream->codecpar, avctx);
dest_stream->sample_aspect_ratio = source_stream->sample_aspect_ratio;
dest_stream->time_base = avctx->time_base;
dest_stream->avg_frame_rate = av_make_q(30, 1);
dest_stream->r_frame_rate = source_stream->r_frame_rate;
dest_stream->disposition = source_stream->disposition;


  


  Then, during the recording phase, I do the following as I read a new packet :

  


  packet->pts = av_rescale_q(packet->pts, src_stream->time_base, dest_stream->time_base);
packet->dts = av_rescale_q(packet->dts, src_stream->time_base, dest_stream->time_base);
packet->duration = dest_stream->time_base.den / dest_stream->time_base.num / dest_stream->avg_frame_rate.num * dest_stream->avg_frame_rate.den;
av_interleaved_write_frame(dest, packet);


  


  The error log I get is the following, in a repeated manner :

  


  [mp4 @ 0x7fc514001d00] Application provided duration: ... / timestamp: ... is out of range for mov/mp4 format
[mp4 @ 0x7fc514001d00] pts has no value


  


  The libav version I am using is the following :

  


  ffmpeg version 4.3.3 Copyright (c) 2000-2021 the FFmpeg developers
  built with gcc 7 (Ubuntu 7.2.0-8ubuntu3)
  configuration:
  libavutil      56. 51.100 / 56. 51.100
  libavcodec     58. 91.100 / 58. 91.100
  libavformat    58. 45.100 / 58. 45.100
  libavdevice    58. 10.100 / 58. 10.100
  libavfilter     7. 85.100 /  7. 85.100
  libswscale      5.  7.100 /  5.  7.100
  libswresample   3.  7.100 /  3.  7.100


  


  P.S : Upgrading ffmpeg version won't work.

  


• High Quality Screen Capture with FFmpeg

  18 novembre 2015, par plumzl

  I’m trying to figure out a command for high quality screen capture on REHL.

  I have tried various options, but none really worked. The quality is not good enough. I’m quite new to ffmpeg and doesn’t quite understand all the different flags. So any help would be appreciated !

  The commands I have tried :

  ffmpeg -y -f x11grab -r 30 -s 1920x1080 -i :0.0+0,0 -vcodec libx264 -strict -2 -b:v 16M output.mov

  The first command I tried. The weird thing is it doesn’t seem to preserve the bitrate specified -b:v 16M. The output video’s bitrate is only 2mb/s. Is that not the correct way to specify bitrate when doing screen capture ?

  ffmpeg -f x11grab -s 1920x1080 -r 30 -i :0.0 -qscale 0 -vcodec huffyuv output.mov

  The huffyuv codec is supposed to be lossless, but the quality doesn’t seem to be any better than the libx264 output.

  ffmpeg -f x11grab -r 30 -s 1920x1080 -i :0.0+0,0 -vcodec copy -pix_fmt yuv420p -qscale 0 -an output.mkv
  
  ffmpeg -f rawvideo -pix_fmt yuv420p -s:v 1920x1080 -r 30 -i output.mkv -an -c:v libx264 -qscale 0 result.mov 

  I’m even trying to capture rawvideo and then convert it to libx264 codec viedeo. But the output is corrupted.

  I’m using the version of ffmpeg that’s built on April 23rd this year. It doesn’t have the preset like -vpre lossless_ultrafast which I see mentioned in a lot posts.

  Edit :

  After more research, this is the command I end up using. I have to use h264 codec and yuv420p as pixel_fmt since I need to be able to play the quicktimes using quicktime.

  ffmpeg -y -f x11grab -framerate 30 -video_size 1920x1080 -i :0.0+0,0 -c:v libx264 -pix_fmt yuv420p -qp 0 -preset ultrafast output.mov

  The quality doesn’t seem to be much improved even though -qp is set to 0. But it could also because of the rgb conversion to yuv color space according to this post.

  https://trac.ffmpeg.org/wiki/Encode/H.264

• High Quality Screen Capture with FFmpeg

  18 novembre 2015, par plumzl

  I’m trying to figure out a command for high quality screen capture on REHL.

  I have tried various options, but none really worked. The quality is not good enough. I’m quite new to ffmpeg and doesn’t quite understand all the different flags. So any help would be appreciated !

  The commands I have tried :

  ffmpeg -y -f x11grab -r 30 -s 1920x1080 -i :0.0+0,0 -vcodec libx264 -strict -2 -b:v 16M output.mov

  The first command I tried. The weird thing is it doesn’t seem to preserve the bitrate specified -b:v 16M. The output video’s bitrate is only 2mb/s. Is that not the correct way to specify bitrate when doing screen capture ?

  ffmpeg -f x11grab -s 1920x1080 -r 30 -i :0.0 -qscale 0 -vcodec huffyuv output.mov

  The huffyuv codec is supposed to be lossless, but the quality doesn’t seem to be any better than the libx264 output.

  ffmpeg -f x11grab -r 30 -s 1920x1080 -i :0.0+0,0 -vcodec copy -pix_fmt yuv420p -qscale 0 -an output.mkv
  
  ffmpeg -f rawvideo -pix_fmt yuv420p -s:v 1920x1080 -r 30 -i output.mkv -an -c:v libx264 -qscale 0 result.mov 

  I’m even trying to capture rawvideo and then convert it to libx264 codec viedeo. But the output is corrupted.

  I’m using the version of ffmpeg that’s built on April 23rd this year. It doesn’t have the preset like -vpre lossless_ultrafast which I see mentioned in a lot posts.

  Edit :

  After more research, this is the command I end up using. I have to use h264 codec and yuv420p as pixel_fmt since I need to be able to play the quicktimes using quicktime.

  ffmpeg -y -f x11grab -framerate 30 -video_size 1920x1080 -i :0.0+0,0 -c:v libx264 -pix_fmt yuv420p -qp 0 -preset ultrafast output.mov

  The quality doesn’t seem to be much improved even though -qp is set to 0. But it could also because of the rgb conversion to yuv color space according to this post.

  https://trac.ffmpeg.org/wiki/Encode/H.264