O.k., thanks, jagabo.
+ Reply to Thread
Results 31 to 32 of 32
Life could be so easy, if there weren't those f*** Details.
A quick report after using this for a while.
I have ended up with a download system using a script to capture the video stream and convert the geometry to 360p from 720p and make the output compressed mp4. When the script runs the geometry and compression step seems to run faster than the stream transfer rate so when the time limit is reached the file is indeed a compressed mp4 in 640x360p geometry.
It runs OK also on my slowest Ubuntu machine, but I use an HP Workstation 8440w as stream download engine onto an NFS mount sourced from the slower server.
Here is the ffmpeg command used inside the script:
read VIDEOURL < $URLFILE #The URL of the stream is in a file so it can be modified easily CAPTURETIME="$1" #Time is in seconds OUTPUTFILE="$2" #The target mp4 file # Now run the ffmpeg command: eval "ffmpeg -hide_banner -user_agent \"Mozilla\" -i $VIDEOURL -vf scale=w=-4:h=360 -c:v libx264 -preset fast -crf 26 -c:a copy -t $CAPTURETIME $OUTPUTFILE"
It would be nice to have ffmpeg wait a while with no incoming data before giving up...