Ultra Low Latency Streaming

[antonymarion]

Hi AirenSoft team,

Did you heard about the project (Kyber) from the former VLC creator here: https://www.youtube.com/watch?v=0Vtg245ZDbU
In english here: https://www.youtube.com/watch?v=0RvosCplkCc

It is an ultra low latency streaming system based on the QUIC (Improved UDP) protocol (maybe MOQ I do not really know https://www.ietf.org/archive/id/draft-ietf-moq-transport-01.html#name-motivation)

Is there any plan in AirenSoft to compete with this kind of product (in terms of low latency) once it will be released?

Cheers,
Antony

[getroot]

The reason why OvenMediaEngine supports WebRTC and LL-HLS is because it can be played in most environments such as Web/Mobile/SmartTV. If a new protocol is released and it is popular and has the same coverage, we will try to introduce it to OME rather than competing with it.

[NXFinity]

UDP = Bandwidth = Poor Quality for low based 'Public Retail ISP'

Anything that is not 'Locked Down Client Based' on UDP transport, will never work properly IRL. It's why Microsoft Shelved FTL after purchasing Beam, it's why Caffine only worked through it's own OBS client. As a protocol, it's flawed to the worlds very poor network infrastructure.

[antonymarion]

UDP = Bandwidth = Poor Quality for low based 'Public Retail ISP'

Anything that is not 'Locked Down Client Based' on UDP transport, will never work properly IRL. It's why Microsoft Shelved FTL after purchasing Beam, it's why Caffine only worked through it's own OBS client. As a protocol, it's flawed to the worlds very poor network infrastructure.

let's keep an eye on Kyber ;) then

[NXFinity]

Don't need to really keep an eye on anything, whilst the worlds 'network' is out dated in terms of 'stabilizing' throughput and using outdated technology solutions for a fast paced world.

The issue with UDP are many, but the few I've worked with and resolved, are enough to show that we can't stably rely on UDP in a 'Public Setting'. A single MS change, is enough to send a UDP connection mental, top that with the most likely of users being 'Creators' and so used in a 'Public Format', there are many factors that can not be controlled.

PING & HOPS are two of the biggest factors in why UDP has not been widely adopted, and why in most cases such as with FTL, it was shelved.

UDP has and always will require a 'Stable Network' and the only way it has ever been achieved, is through Client to Client connection.

[antonymarion]

Don't need to really keep an eye on anything, whilst the worlds 'network' is out dated in terms of 'stabilizing' throughput and using outdated technology solutions for a fast paced world.

The issue with UDP are many, but the few I've worked with and resolved, are enough to show that we can't stably rely on UDP in a 'Public Setting'. A single MS change, is enough to send a UDP connection mental, top that with the most likely of users being 'Creators' and so used in a 'Public Format', there are many factors that can not be controlled.

PING & HOPS are two of the biggest factors in why UDP has not been widely adopted, and why in most cases such as with FTL, it was shelved.

UDP has and always will require a 'Stable Network' and the only way it has ever been achieved, is through Client to Client connection.

Maybe you should cast a glance over MP-QUIC for bad network conditions.

In any case, thank you for your explanations ..

[mpisat]

Media over QUIC is interesting. I'm sure OME will implement it when it becomes mainstream. Right now, it isn't.