Recherche avancée

Sur d’autres sites (6276)

• Révision 18207 : Résoud #2025 (on va dire) :

  7 juillet 2011, par cedric -

  En l’absence de define(’_SURLIGNE_RECHERCHE_REFERERS’,true) on ne surligne qu’en présence de var_recherche ce qui a le merite d’accélerer le service des pages en évitant l’analyse de tous les referers connus, a chaque hit avec referer (soit presque (...)

• Anomalie #2025 : Surlignage intempestif

  20 septembre 2011, par tetue -

  Ceinture et bretelles : la classe pas_surlignable est passée par défaut sur toutes les balises de la dist depuis Changeset 50225 (c’est inutile, du coup ?)

• What are supported ffmpeg rtp_mpegts Muxer options ? (mpegts Muxer options are ignored)

  7 mars 2020, par drake7

  I created a UDP stream with -f mpegts and some options like -mpegts_transport_stream_id.

  I received the stream with "StreamXpert - Real-time stream analyzer" that shows all options are in the output. See my ffmpeg parameters and the StreamXpert at the end.

  The same Muxer options seem to be ignored with -f rtp_mpegts.

  I have tried to use -f mpegts and pipe it to -f rtp_mpegts like so :

  ffmpeg -i ... -f mpegts pipe: | ffmpeg pipe: -c copy -f rtp_mpegts "rtp://239.1.1.9:1234?pkt_size=1316"

  The options are still ignored.

  This ticket "support options for MPEGTS muxer when using RTP_MPEGTS" also notices the ignored option. Furthermore in this comment, "thovo" gives an analysis and suggests a solution.

  Obviously the problem still exists. Anybody found a workaround for this ?

  My additional question : I have not questioned if my project really needs rtp in the first place. Maybe my coworker didn’t know better and requested rtp when udp would be sufficient as well.

  The aim was to receive the RTP stream with a TV using DVB via IP. This was successful an a Panasonic TV.

  The SAT>IP Specification on page 10 requires rtp for Media Transport :

  The SAT>IP protocol makes use of :

  • UPnP for Addressing, Discovery and Description,
  • RTSP or HTTP for Control,
  • RTP or HTTP for Media Transport.

  Is udp out of the equation ?

  ---

  ffmpeg : (all options are in the output with -f mpegts)

  (HEX to decimal : 0x005A = 90, 0x005B = 91 0x005C = 92, 0x005D = 93, 0x005E= 94)

  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 \
  
  -flush_packets 0 \
  
  -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='WI' \ 
  
  -metadata service_name='W' \
  
  -mpegts_flags system_b -flush_packets 0 \
  
  -f mpegts "udp://239.1.1.10:1234?pkt_size=1316"

  StreamXpert Output :

  -mpegts_transport_stream_id = Transport Stream ID (yellow text highlight)

  -mpegts_original_network_id = Original Network ID, onw (green text highlight)

  -mpegts_service_id = Program, service (pink text highlight)

  -mpegts_pmt_start_pid = PMT PID, Table PID (turquoise text highlight)

  -mpegts_start_pid = PID, PCR PID (red text highlight)

  -mpegts_service_type = service type (blue text)

  service_name = Service name (orange text)

  service_provider = Service provider (pink text)