Recherche avancée

Sur d’autres sites (11050)

• Merge commit ’2830bce47e2eb29c76202f19017031ddc1f95dd3’

  10 octobre 2015, par Hendrik Leppkes

  Merge commit ’2830bce47e2eb29c76202f19017031ddc1f95dd3’
  * commit ’2830bce47e2eb29c76202f19017031ddc1f95dd3’ :
  
    w32pthreads : Load dynamically loaded functions on demand
  Merged-by : Hendrik Leppkes <h.leppkes@gmail.com>
  

  • [DH] compat/w32pthreads.h

• ffmpeg segment naming of rtsp surveillance stream HikVisions

  20 juillet 2022, par kenneth558

  I need to ensure unique segment names : Apparent POE cable defects, etc. around campus cause HikVision camera streams to require their ffmpeg daemons re-started once or twice or more times/day. (I am miles away from this campus for the most part, so I prefer a command line fix until the hardware fixes get applied.) When ffmpeg has to be restarted for a camera (by background bash script), I need the names of the new .mp4 segments positively not to be the same as any previous names.

  


  Background bash process currently does fine to specify an acceptable ddHHMM style new starting name for the first segment after ffmpeg restart BUT after the first or sometime second or third segment is made, ffmpeg insists on future naming to default to an unacceptable YYYmmdd style and thus start to overwrite previous segments. I use "$(date +%d%H%M)" to obtain my acceptable date style.

  


  I've tried a lot of different combinations of date codes and date embedding and both ssegment and segment muxers ; also I know very little of the very complex realm that ffmpeg is normally used in outside of simple rtsp stream copy to .mp4 files.

  


  ffmpeg command that is launched from inside bash script :
bash -c 'nohup ffmpeg -nostdin -stimeout 10000000 -rtsp_transport udp -i "rtsp://192.168.0.11:6554/Streaming/channels/101" -reconnect 1 -reconnect_at_eof 1 -reconnect_streamed 1 -c:v libx264 -f ssegment -strftime 0 -segment_time 180 -segment_format_options movflags=+faststart -reset_timestamps 0 -increment_tc 1 -avoid_negative_ts 1 -c copy -flags +global_header /var/www/camera_streams/camera_east_driveway/"$(date +%d%H%M)"_%3d.mp4 > /dev/null 2>/dev/null & '

  


  Can the segment naming pattern be carried forward indefinitely like I want ? Honestly, I wonder if ffmpeg does not allow for my specific use case naming need ?

  


  (Yes, I know changing from udp to tcp can help, but I don't consider it to be the specific solid naming fix I'm hoping for right now. And I mention HikVision in case there is known frame encoding differences for them than other cameras)

  


• How to build ffmpeg as a single application on Mac

  14 septembre 2023, par Devin Dixon

  I am trying to compile ffmpeg on mac as a single executable static executable so it can be distributed. Here is my ./configure.

  


  ./configure \
    --pkg_config='pkg-config --static' \
    --enable-libopenh264 \
    --enable-version3 \
    --enable-libopus \
    --enable-libvpx \
    --enable-libvorbis \
    --enable-libaom \
    --enable-libdav1d \
    --enable-videotoolbox \
    --enable-hwaccel=h264_videotoolbox \
    --disable-gpl \
    --disable-w32threads \
    --enable-pthreads \
    --disable-shared \
    --enable-static \
  --extra-ldflags="-L/usr/local/lib" \
--prefix=~/FFmpeg/dist


  


  Except it compiles it and still requires linked libraries. If I open it on another mac I get errors likeL

  


  Library not loaded: /opt/homebrew/opt/libxcb/lib/libxcb.1.dylib


  


  And thoughts on what flags I am missing ?