no real clue, but http and https inputs seem to have zero f'ing useful
countdown/timeout handling... nor "-t" counting.
I was trying something similar, like so:
$ while :; do ffmpeg -xerror -re -i
https://stream.nightride.fm/datawave.mp3 -filter_complex
"[0:a]avectorscope=s=640x518:r=24000/1001:m
It begins with:
ffmpeg -i https://listen.wruu.org/stream -t 3720 -reconnect true
-reconnect_streamed true -reconnect_on_network_error true -timelimit 3720
-loglevel warning wruu_JoeFrank-20250130-2100.mp3
ffmpeg version 7.1 Copyright (c) 2000-2024 the FFmpeg developers
built with gcc 14.2.0
Add verbosity and see if you can pickup on that error?
`-v 48` should do it.
On Fri, Jan 17, 2025 at 8:00 AM arthurpeabody
wrote:
> I started identical captures on my home computer and at a remote server.
> The capture at home stopped capturing at 42 minutes; the capture at the
> remote computer
I started identical captures on my home computer and at a remote server. The
capture at home stopped capturing at 42 minutes; the capture at the remote
computer finished. The process at home is still running; the process at the
remote computer ended. No error was reported.
https://pastebin.c
Whoops! Ignore that example. The stream went down. I'll have an example in
which it didn't eventually.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmp
ffmpeg quit 14 minutes into this capture, didn't reconnect:
https://pastebin.com/uGHPqiBy
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@
On 1/12/2025 6:28 PM, arthurpeabody wrote:
There is no banner and stream.
Hmm, the originally-posted command
ffmpeg -i
https://playerservices.streamtheworld.com/api/livestream-redirect/KUNMFM_32.mp3
-t 180 -reconnect true -reconnect_streamed true
-reconnect_on_network_error true -timelimit
Quoth Carl Zwanzig:
'That's missing the entire banner and stream info - "Always show your
actual, unscripted ffmpeg command and the complete, uncut console output
from your command." (the first point in faq section 6.1)'
I showed the entire console output. Here's the command in my script:
ffmpe
On 1/12/2025 11:27 AM, arthurpeabody wrote:
There was nothing until I terminated the processes with kill:
That's missing the entire banner and stream info - "Always show your
actual, unscripted ffmpeg command and the complete, uncut console output
from your command." (the first point in faq s
Quoth Carl Zwanzig:
' Please always include not only the complete command but the command
output, it often contains quite useful info for debugging (see section 6
of https://www.ffmpeg.org/mailing-list-faq.html).'
There was nothing until I terminated the processes with kill:
[out#0/mp3 @ 0x2c31d
On 1/12/2025 7:28 AM, arthurpeabody wrote:
I capture live streams.
Please always include not only the complete command but the command
output, it often contains quite useful info for debugging (see section 6
of https://www.ffmpeg.org/mailing-list-faq.html).
z!
I capture live streams. When a stream drops ffmpeg stops capturing, doesn't
reconnect, and keeps running after the time limit. For example:
ffmpeg -i
https://playerservices.streamtheworld.com/api/livestream-redirect/KUNMFM_32.mp3
-t 180 -reconnect true -reconnect_streamed true -reconnect_on_n
12 matches
Mail list logo