Recherche avancée

Sur d’autres sites (12226)

• 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.

  


• Dreamcast Development Desktop

  28 mars 2011, par Multimedia Mike — Sega Dreamcast

  Some people are curious about what kind of equipment is required to program a Sega Dreamcast. This is my setup :

  
  
  

  It’s a bit overcomplicated. The only piece in that picture which doesn’t play a role in the Dreamcast development process is the scanner. The Eee PC does the heavy lifting of development (i.e., text editing and cross compilation) and uploads to the Dreamcast via a special serial cable. Those are the most essential parts and are really the only pieces necessary for a lot of algorithmic stuff (things that can be validated via a serial console). But then I have to go up a level where I output video. That’s where things get messy.

  
  
  

  The Mac Mini and giant monitor really just act as a glorified TV in this case. Ideally, it will be more than that. The DC outputs audio and video via composite cables to a Canopus DV capture bridge. That’s connected via FireWire to the external hard drive underneath the Mac Mini, which is connected to the Mac. Adobe Premiere Pro handles the DV capture / display.

  One day I hope to have something worthwhile to capture.

• How to access builtin webcam from a docker container using ffmpeg ?

  1er novembre 2020, par philippos

  I have wrote my code that captures videos by my builtin webcam of my MAC using ffmpeg.

  On local machine, the code works fine. However, I built a docker container of my code, and tried to run it, but I got the following error :

  


  error: Command failed: ffmpeg -f avfoundation -framerate 30 -i "0" -target pal-vcd -vf scale=640x480 -flags +global_header -f segment -segment_time 10 -segment_list ../out.csv -segment_format_options movflags=+faststart -reset_timestamps 1 -strftime 1 %Y%m%d-%H%M%S.mp4
ffmpeg version git-2016-05-25-9591ca7 Copyright (c) 2000-2016 the FFmpeg developers
  built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  configuration: --extra-libs=-ldl --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-nonfree --enable-openssl
  libavutil      55. 24.100 / 55. 24.100
  libavcodec     57. 43.100 / 57. 43.100
  libavformat    57. 37.100 / 57. 37.100
  libavdevice    57.  0.101 / 57.  0.101
  libavfilter     6. 46.100 /  6. 46.100
  libswscale      4.  1.100 /  4.  1.100
  libswresample   2.  0.101 /  2.  0.101
  libpostproc    54.  0.100 / 54.  0.100
Unknown input format: 'avfoundation'


  


  

  1. as far as what I understood from this log, is that the docker
container doesn't have access to local devices.
     According to
this discussion Docker - a way to give access to a host USB or
serial device ? , I need to use the --device flag to pass my
device's location.
     However, according to this answer,
that is not possible ?

  


  2. In addition to what I've mentioned
above, I couldn't get my webcam's path at the first place. what is
a correct path for macbook webcam

  


  


  My question is : How to access my MAC's builtin camera to record from a docker container ?