Recherche avancée

Sur d’autres sites (12864)

• Using Cut with Fast Seek -ss -to and HH:MM:SS:MS

  1er avril 2019, par Matt McManis

  I’m trying to cut a video using -ss and -to using HH:MM:SS:MS time.

  I’m using -to instead of -t because I want the cut to be "between" a time range and not "up to" time.
  I also have to use -to because it’s needed for another program’s time input textbox I’m using. I won’t be able to use -t for this case.

  Example :

  https://superuser.com/a/670590

  -ss 00:01:00:00 -to 00:02:00:00 cut starts at minute 1, ends at minute 2.
  -ss 00:01:00:00 -t 00:02:00:00 cut starts at minute 1, ends at minute 3.

  https://trac.ffmpeg.org/wiki/Seeking#Cuttingsmallsections

  ---

  Problem

  I’m not able to use Fast Seek, -ss before the -i, -to after.

  I’m only able to use Slow Seek, -ss and -to after the -i.

  ---

  1. Fast

  Doesn’t Work

  This cuts a minute ahead of what’s in the time.

  Cuts from 00:01:00 to 00:03:00, using the faster seek.

  ffmpeg -ss 00:01:00 -i video.mp4 -to 00:02:00 -c copy cut.mp4

  ---

  2. Slow

  Works

  I’m trying to do this but with fast seek.

  Cuts from 00:01:00 to 00:02:00, using the slower seek.

  ffmpeg -i video.mp4 -ss 00:01:00 -to 00:02:00 -c copy cut.mp4

  ---

  3. Fast

  Works (with problems)

  -copyts ruins video time bar in player.

  Cuts from 00:01:00 to 00:02:00, using the faster seek.

  ffmpeg -ss 00:01:00 -i video.mp4 -to 00:02:00 -c copy -copyts cut.mp4

• Revision 66261 : Une branche experimentale pour integrer BootStrap. Dev ONLY. DO NOT USE IN ...

  26 septembre 2012, par cedric@… — Log

  Une branche experimentale pour integrer BootStrap ?. Dev ONLY. DO NOT USE IN PRODUCTION

• Streaming live video from Windows to Android with FFmpeg

  29 avril 2018, par Alan Daniels

  I am capturing live video on a Windows PC and encoding it with FFmpeg. I can stream the content live to another PC using rtsp://[dest_ip:port]/live.sdp as FFmpeg’s output on the sender and using ffplay -rtsp_flags listen rtsp://[dest_ip:port]/live.sdp on the receiver. However, I have to run FFplay before starting the sender. Also, VLC cannot play the rtsp path :

  main debug: net: connecting to 127.0.0.1 port 5555
  
  main error: connection failed: Connection refused by peer
  
  access_realrtsp error: cannot connect to 127.0.0.1:5555
  
  access_realrtsp debug: could not connect to: 127.0.0.1:5555/live.sdp

  However, FFplay and VLC can play something like ffplay rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mov.

  On the Android side, I am using the Media API which can play content from a URI. It works with HTTP and RTSP (as far as I know).

  I’ve looked at FFmpeg’s streaming guide : https://trac.ffmpeg.org/wiki/StreamingGuide, but I am still confused about the difference between my path rtsp://[dest_ip:port]/live.sdp and rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mov.

  Do I need a streaming server in order to have my content accessible by URI ? Any recommendations since FFserver is depreciated ?