Recherche avancée

Sur d’autres sites (9909)

• Does ffmpeg rtp_mpegts muxer support setting DVB triplet ?

  19 février 2021, par drake7

  It seems ffmpeg lets you set the DVB triplet with UDP but not with RTP.

  


  FYI : This is a followup on my findings about the rtp_mpegts muxer compared to the mpegts muxer : Question

  


  In my tests I was using ffmpeg version 4.3.1-2021-01-01-full_build-www.gyan.dev on windows.

  


  findings

  


  I analyzed my streams with dectec's "StreamXpert" :

  


  


  • With UDP and it's mpegts muxer, the DVB triplet can be set (1)

    


  


  • With RTP and it's rtp_mpegts muxer, the DVB triplet is ignored (3) (Note that 3a and 3b create very similar results in "StreamXpert".)

    


  


  • Using UDP with DVB triplet as input and output with RTP ignores the DVB triplet (2)

    


  



  


  Interestingly, leaving out the following options...

  


  -pcr_period 20 -pat_period 0.10 -sdt_period 0.25 -metadata:s:a:0 language=nya \
-mpegts_flags +pat_pmt_at_frames -mpegts_flags system_b


  


  ... the rtp_mpegts muxer (3b) creates a valid DVB transport stream, while the the mpegts muxer (4) does not.

  


  ffmpeg params :

  


  



  


  muxer : mpegts (udp)

  


  ffmpeg -f lavfi -i testsrc -r 25 -c:v libx264 -pix_fmt yuv420p -profile:v main -level 3.1 -preset veryfast -vf scale=1280:720,setdar=dar=16/9 -an -bsf:v h264_mp4toannexb -b:v 4M -muxrate 8M \
-pcr_period 20 -pat_period 0.10 -sdt_period 0.25 -metadata:s:a:0 language=nya -mpegts_flags +pat_pmt_at_frames \
-mpegts_transport_stream_id 0x005A \
-mpegts_original_network_id 0x005B \
-mpegts_service_id 0x005C \
-mpegts_pmt_start_pid 0x005D -mpegts_start_pid 0x005E -mpegts_service_type advanced_codec_digital_hdtv \
-metadata service_provider="Provider foo" \
-metadata service_name="Service bar" \
-mpegts_flags system_b -flush_packets 0 \
-f mpegts "udp://239.10.33.10:1234?pkt_size=1316"


  


  



  


  muxer : rtp_mpegts (rtp)

  


  ffmpeg -i "udp://239.10.33.10:1234" -map 0 -c copy \
-f rtp_mpegts "rtp://239.10.33.11:1234?pkt_size=1316"


  


  



  


  a) muxer : rtp_mpegts (rtp)

  


  ffmpeg -f lavfi -i testsrc -r 25 -c:v libx264 -pix_fmt yuv420p -profile:v main -level 3.1 -preset veryfast -vf scale=1280:720,setdar=dar=16/9 -an -bsf:v h264_mp4toannexb -b:v 4M -muxrate 8M \
-pcr_period 20 -pat_period 0.10 -sdt_period 0.25 -metadata:s:a:0 language=nya -mpegts_flags +pat_pmt_at_frames \
-mpegts_transport_stream_id 0x005A \
-mpegts_original_network_id 0x005B \
-mpegts_service_id 0x005C \
-mpegts_pmt_start_pid 0x005D -mpegts_start_pid 0x005E -mpegts_service_type advanced_codec_digital_hdtv \
-metadata service_provider="Provider foo" \
-metadata service_name="Service bar" \
-mpegts_flags system_b -flush_packets 0 \
-f rtp_mpegts "rtp://239.10.33.10:1234?pkt_size=1316"


  


  b) muxer : rtp_mpegts (rtp) (omitting some options)

  


  ffmpeg -f lavfi -i testsrc -r 25 -c:v libx264 -vf scale=1280:720,setdar=dar=16/9 -b:v 4M -muxrate 8M \
-mpegts_transport_stream_id 0x005A \
-mpegts_original_network_id 0x005B \
-mpegts_service_id 0x005C -mpegts_pmt_start_pid 0x005D -mpegts_start_pid 0x005E \
-mpegts_service_type advanced_codec_digital_hdtv \
-metadata service_provider="Provider foo" \
-metadata service_name="Service bar" \
-f rtp_mpegts "rtp://239.10.33.10:1234"


  


  



  


  muxer : mpegts (udp) (omitting some options)

  


  ffmpeg -f lavfi -i testsrc -r 25 -c:v libx264 -vf scale=1280:720,setdar=dar=16/9 -b:v 4M -muxrate 8M \
-mpegts_transport_stream_id 0x005A \
-mpegts_original_network_id 0x005B \
-mpegts_service_id 0x005C -mpegts_pmt_start_pid 0x005D -mpegts_start_pid 0x005E \
-mpegts_service_type advanced_codec_digital_hdtv \
-metadata service_provider="Provider foo" \
-metadata service_name="Service bar" \
-f mpegts "udp://239.10.33.10:1234"


  


  Analyzing the transport stream

  


  

  


• passing additional values to s3 event notification for lambda consumption

  8 septembre 2017, par user1790300

  I have to write code in react-native that allows a user to upload videos to amazon s3 to be transcoded for consumption by various devices. For the processing after the upload occurs ; I am reviewing two approaches :

  1) I can use Lambda with ffmpeg to handle the transcoding immediately after the uploading occurs (my fear here would be the amount of time required to transcode the videos and the effect on pricing if it takes a considerable amount of time).

  2) I can have s3 pass an sns message to a rest api after the created event occurs and the rest api generate a rabbitmq message that will be processed by worker that will perform the transcoding using ffmpeg.

  Option 1) seems to be the preferable option based on a completion time perspective. How concerned should I be with using 1) considering how long video transcoding might take as opposed to option 2) ?

  Also, regardless, I need a way to pass additional parameters to lambda or along the sns messaging that would allow me to somehow associate the user who uploaded the video with their account. Is there a way to pass additional text-based values to s3 to pass along to lambda or along sns when the upload completes, as a caveat I plan to upload the video directly to s3 using the rest layer(found this answer here : http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPUT.html#RESTObjectPUT-responses-examples) ?

• Restream IP camera Feed [closed]

  4 janvier 2024, par Reenath Reddy Thummala

  I possess several IP cameras linked to a shared network. Although I intend to leverage each camera stream across multiple microservices, the network faces challenges in managing the bandwidth load. Unfortunately, I lack control over the network and cannot augment its bandwidth. Despite attempting to create a restreaming service using GStreamer, Live555, FFMPEG, and OpenCV, stability remains an issue. Are there any paid services accessible that can accept the source feed as input and provide scalable restream feed URLs ?