Recherche avancée

Sur d’autres sites (6854)

• Possible to Combine Live m3u8 stream with PIP overlay from WebRTC source ?

  25 octobre 2015, par user1258530

  Can someone tell me what server-side technology (perhaps ffmpeg), one could use in order to :

  1) display this full-screen live-streaming video :

  http://aolhdshls-lh.akamaihd.net/i/gould_1@134793/master.m3u8

  2) and overlay it in the lower-right corner with a live video coming from a webRTC video-chat stream ?

  3) and send that combined stream into a new m3u8 live-stream

  4) Note that it needs to be a server-side solution - - - cannot launch multiple video players in this case (needs to pass the resulting stream to SmartTV’s which only have one video-decoder at a time)

  The closest example I’ve found so far is this article :

  https://trac.ffmpeg.org/wiki/Create%20a%20mosaic%20out%20of%20several%20input%20videos

  Which isn’t really live, nor is it really doing overlays.

  any advice is greatly appreciated.

• ffmpeg split video H264 stutters on Windows Media Player

  9 mars 2019, par Juan Foegen

  I am converting and splitting wmv and mp4 into new mp4 files. I am using ffmpeg to do the conversion with simply :
  ffmpeg -i inputfile.wmv -vcodec libx264 -ss 00:00:10 -t 00:00:15 outputfile.mp4

  So when I create my split video it plays fine on other video players, like VLC, but stutters when initially playing on Windows Media Player and even shows a blank screen for a moment and then after about 5 seconds, the video will play normally. If I then select play again without reloading, Windows Media Player will play the video fine, with no stuttering.

  If I REMOVE the start parameter when doing the conversion, then the resulting video will play without issues on all my players, INCLUDING Windows Media Player.

  I have tried changing the frame rate, the bit rate and altered different optimization options mentioned here - https://trac.ffmpeg.org/wiki/Encode/H.264

  I need the split video to play on Windows machines on Windows Media Player and on the web streamed using the video element. This is why I chose H264 codec and MP4.

  Has anyone had issues playing ffmpeg split videos using H264 codec with Windows Media Player ? I am using the latest version of ffmpeg. Anyone have any other suggestions on any different settings I could try to adjust ?

  Thanks

• ffmpeg segment naming - Moving to superuser (with apologies)

  21 juillet 2022, par kenneth558

  Maybe I am misinterpreting the downvote, but I conclude this question should go on superuser instead. Moving now and will delete this copy soon....

  


  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)