hello
i have some streams that are not starting or not even scan probe size, but the source is good, i saw this command on the process when i start the channel.
/usr/bin/timeout 12s /home/xui/bin/ffprobe -user_agent Mozilla -probesize 5000000 -analyzeduration 5000000 -i http://ip_address/example/file.m3u8........etc...
if i run that command manually, my stream take around 20 to 25 seconds to respond, could that be the issue? and in that case, that 12s timeout is a value possible to increase?
just as comment, old xtream ui is able to start the same source
Thanks in Advance,
i have some streams that are not starting or not even scan probe size, but the source is good, i saw this command on the process when i start the channel.
/usr/bin/timeout 12s /home/xui/bin/ffprobe -user_agent Mozilla -probesize 5000000 -analyzeduration 5000000 -i http://ip_address/example/file.m3u8........etc...
if i run that command manually, my stream take around 20 to 25 seconds to respond, could that be the issue? and in that case, that 12s timeout is a value possible to increase?
just as comment, old xtream ui is able to start the same source
Thanks in Advance,
