Recherche avancée

Sur d’autres sites (7285)

• avcodec/evc_parse : Check tid

  4 octobre 2023, par Michael Niedermayer

  avcodec/evc_parse : Check tid
  The check is based on not infinite looping. It is likely
  
  a more strict check can be done
  Fixes : Infinite loop
  
  Fixes : 62473/clusterfuzz-testcase-minimized-ffmpeg_BSF_EVC_FRAME_MERGE_fuzzer-5719883750703104
  
  Fixes : 62765/clusterfuzz-testcase-minimized-ffmpeg_dem_EVC_fuzzer-6448531252314112
  
  Fixes : 63378/clusterfuzz-testcase-minimized-ffmpeg_dem_MPEGPS_fuzzer-6504993844494336
  Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
  
  Reviewed-by : "Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics" <d.kozinski@samsung.com>
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavcodec/evc_parse.c

• ffmpeg's invalid input stream fps causes low latency [closed]

  9 mai 2024, par I have 10 fingers

  I have ffmpeg setup which produces rtmp stream from remote rtsp stream. The rtsp stream comes from ip camera which support multiple profiles. Each profile has 1080p 30 fps, 1080p 15 fps.

  


  The weird thing is that when ffmpeg analyze its input stream, one profile is recognized as 1 fps as below

  


  Input #0, rtsp, from 'rtsp://...':
  Metadata:
    title           : Media Presentation
    comment         : samsung
  Duration: N/A, start: 0.064144, bitrate: N/A
    Stream #0:0: Video: h264 (High), yuvj420p(pc, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], 1 fps, 1 tbr, 90k tbn, 2 tbc
    Stream #0:1: Data: none
Output #0, flv, to 'rtmp:...':
  Metadata:
    title           : Media Presentation
    comment         : samsung
    encoder         : Lavf58.29.100
    Stream #0:0: Video: h264 (High) ([7][0][0][0] / 0x0007), yuvj420p(pc, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 1 fps, 1 tbr, 1k tbn, 90k tbc
Stream mapping:
  Stream #0:0 -> #0:0 (copy)


  


  And when it is played the tbr is 30 i think it means the real fps from video stream is 30. No problem actually this gives me the lowest latency(2-3s).

  


  The other stream is normal 30 fps input 30 fps output and it gives me some delay(5-6s) so i want to know what cause this fps bug ? If i can use this bug i want to change all my streams to reduce the latency.

  


• Use HLS from Wifi device as input to stream over 4G

  26 février 2017, par pbdev

  I’m building an Android app that streams video from a Wifi device to a Wowza server. It should be quite simple but I can’t figure out how to use both Wifi and 4G at the same time. The device I’m using is a Samsung S5 with Android 6.0.1. To sum it up, this is the goal :

  1. Fetch the video stream from a GoPro device over Wifi.
  2. Send the video stream to a Wowza server over 4G.

  When connected to the GoPro’s Wifi network I can ping the GoPro and see the stream in a MediaPlayer. Since I’m connected to a Wifi device that doesn’t provide internet access, I can’t ping my Wowza server. Once I’ve disabled Wifi this is no problem, by using FFmpeg I can reach the Wowza server over 4G.

  This is the FFmpeg command I want to use to copy the stream to the Wowza server, where 10.5.5.9 is the IP-address of the GoPro :

  ffmpeg -i http://10.5.5.9:8080/live/amba.m3u8 -acodec aac -ar 44100 -ab 48k -vcodec copy -f flv rtmp://username:password@my-wowza-server.com:1935/my-app/my-stream

  If I enable Wifi and connect to the GoPro, 10.5.5.9 is reachable but my-wowza-server.com isn’t. The Samsung S5 provides a Smart network switch which makes the Wowza server reachable but the connection to the GoPro gets lost.

  Is there any way to bind 10.5.5.9 to the Wifi interface of the phone and bind my-wowza-server.com to the cellular interface ?