Question Ondemand Comparison : XUI ONE VS Xtream Ui

[Xpert007]

Hello everyone , i just installed xui one and ive noticed that channels on demand takes too much time to show in compare to xtream ui

Ive tried probsize in 256000 and also 512000 but its the same problem sometimes it takes to 40 secondes till the channel show up

Anyone can share a tweak to reduce the time so that channel on demand can show up fastly

Thank u

 

[Moutamared]

it may depends on Buffer Size value you did put on the settings, maybe use lower value like 10sec and check it again.

 

[Xpert007]

it may depends on Buffer Size value you did put on the settings, maybe use lower value like 10sec and check it again.

Thank you for your feedbacj when u say 5 seconds it means that i put 512000 in probsize right ?

 

[Youmeirean]

Hello everyone , i just installed xui one and ive noticed that channels on demand takes too much time to show in compare to xtream ui

Ive tried probsize in 256000 and also 512000 but its the same problem sometimes it takes to 40 secondes till the channel show up

Anyone can share a tweak to reduce the time so that channel on demand can show up fastly

Thank u

set llod v3 and probe and anylise to 500000 also look at server ping if its higher than 5-10 load times are slower the bigger the numbers

 

[julian]

set llod v3 and probe and anylise to 500000 also look at server ping if its higher than 5-10 load times are slower the bigger the numbers

I find that the most important factor for fast Ondemand operation is as @Youmeirean said, ping. I am referring to ping between main and Lb servers. If you set probe size too low (256000 or less) , streams will have audio problems, and might not start, best set to 512000. I find other settings dont make much difference. In other words, servers used for ondemand need to be close to each other, in the same datacenter ideally.

 

[nullArray]

Hello everyone , i just installed xui one and ive noticed that channels on demand takes too much time to show in compare to xtream ui

Ive tried probsize in 256000 and also 512000 but its the same problem sometimes it takes to 40 secondes till the channel show up

Anyone can share a tweak to reduce the time so that channel on demand can show up fastly

Thank u

Try with this value: 3000000 and this headers: -rtbufsize 15M -re -i {INPUT} -c:v copy -c:a copy -tune zerolatency -preset ultrafast -analyzeduration 3000000 -probesize 3000000

 

[julian]

Try with this value: 3000000 and this headers: -rtbufsize 15M -re -i {INPUT} -c:v copy -c:a copy -tune zerolatency -preset ultrafast -analyzeduration 3000000 -probesize 3000000

I don’t find above settings make a noticeable difference if ping is high, unfortunately, however the op needs to check if streams are failing to start at first attempt and if so, he needs to increase Ondemand probe to something higher then 512000, like 1024000. My guess is that he is getting failed attempts and he is going into wait time. Thats why the 40 seconds. I think that’s what he should check first. Basically observe streams while opening, look for failed starts and look through stream/error logs. Retry attempts and wait time can also be adjusted in general settings, streams would take a bit longer to start anyway if there are failed attempts, so increase on demand probe and/or solve the stream open failure before anything else. Poor streams could also cause it, apart other things. Thats how I seem to get best results with xui one, based on how it turned out in my case. Others could have solved it differently, so I would like to hear other opinions. Also, why -zerolatency and preset ultrafast? We are not transcoding here, just copying. I also recall reading that headers on xui one is different then an ffmpeg manual command in xtream ui, although they look similar in the gui. Thanks
On second thoughts it’s also important Xpert007 makes sure that his upstream provider is not using ondemand as well, that would cause a double slow down. At a pinch he can test the stream(s) individually from content > manage streams > edit stream > sources > scan sources. If the stream takes long to open or fails (even occasionally) during the test, it’s indicative of a bad source. The op needs to enable ‘ffmpeg show warning’ from general settings > streaming, that way ffmpeg warnings will be shown in stream error logs giving an indication of what’s going on. Logs will be in management > logs > stream errors.