Recherche avancée

Sur d’autres sites (11989)

• avformat/rtsp : Fix timeout option

  30 mai 2021, par Andriy Gelman

  avformat/rtsp : Fix timeout option
  92c40ef882be115e72d2aa02f9032b7ce88f8537 added a listen_timeout option
  
  for sdp. This allowed a user to set variable timeout which was
  
  originally hard coded to 10 seconds.
  The commit used the initial_timeout variable to store the value. But
  
  this variable is shared with rtsp where it's used to infer a "listen"
  
  mode. Thus, the timeout value could not be set in rtsp, and the default
  
  value (initial_timeout = -1) would give 100ms timeout.
  This was attempted to be fixed in c8101aabee654f6d147a4d89f77fa73e18908610,
  
  which changed the meaning of initial_timeout = -1 to be an infinite
  
  timeout. However, it did not address the issue that the timeout could
  
  still not be set. Being able to set the timeout is useful because it
  
  allows to automatically reconfigure from a udp to tcp connection in the
  
  lower transport.
  In this commit this is fixed by using the stimeout variable to
  
  store the timeout value.
  Signed-off-by : Andriy Gelman <andriy.gelman@gmail.com>
  

  • [DH] libavformat/rtsp.c
  • [DH] libavformat/rtsp.h

• cbs_mpeg2 : Improve checks for invalid values

  22 mai 2019, par Andreas Rheinhardt

  cbs_mpeg2 : Improve checks for invalid values
  MPEG-2 contains several elements that mustn't be zero according to the
  
  specifications : horizontal/vertical_size_value, aspect_ratio_information,
  
  frame_rate_code, the quantiser matrices, the colour_description
  
  elements, picture_coding_type, the f_code[r][s] values and
  
  quantiser_scale_code. It is now checked that the invalid values don't
  
  occur.
  The colour_description elements are treated specially in this regard :
  
  Given that there are files in the wild which use illegal values for the
  
  colour_description elements (some of them created by mpeg2_metadata),
  
  they will be corrected to the value meaning "unknown" (namely 2) during
  
  reading. This has been done in such a way that trace_headers will
  
  nevertheless report the original value, together with a message about
  
  the fixup.
  Furthermore, the trace_headers output of user_data has been beautified.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavcodec/cbs_mpeg2.c
  • [DH] libavcodec/cbs_mpeg2_syntax_template.c

• How to convert from .h264 to .ts using FFmpeg wrapper for C#/.NET ?

  9 décembre 2020, par juan_marti

  Context

  


  I'm using FFMpegCore in my .NET Core API project that receives a .h264 file (sent in a binary format that is received and converted into a byte array) to be converted to a .ts.

  


  I want to convert a .h264 stream into a .ts output stream using FFmpeg.

  


  Current Approach

  


  (...)

byte[] body;
using ( var ms = new MemoryStream() )
{
    await request.Body.CopyToAsync( ms ); // read sent .h264 data
    body = ms.ToArray();
}

var outputStream = new MemoryStream();

// FFMpegCore
await FFMpegArguments
                .FromPipeInput( new StreamPipeSource( new MemoryStream( body ) ) )
                .OutputToPipe( new StreamPipeSink( outputStream ), options => options
                .ForceFormat( VideoType.MpegTs ) )
                .ProcessAsynchronously();

// view converted ts file
await File.WriteAllBytesAsync( "output.ts", outputStream.ToArray() );

(...)


  


  Problem

  


  I'm not getting a working .ts file. What I'm a doing wrong ? Could you please give some hint or help me with this ? Even if you have other FFmpeg wrappers that you consider more suitable for this problem.

  


  Notes :

  


  

  • I don't have the physical location of the files since this will receive the content of the files over HTTP. So, I will only have the byte array meaning that I need to use the input stream to convert to another format.

  


  • FFmpeg command used to test the conversion from .h264 to .ts (using files) : ffmpeg -i file.h264 -an -vcodec copy -f mpegts output.ts