#AV1 issues?
1 messages · Page 1 of 1 (latest)
Hello @hazy moon!
If you're using Linux, please refer to this thread if you have any issues running ALVR: https://discord.com/channels/720612397580025886/1373139630605729802
i normally use linux, but this issue is with windows, thanks tho carl.
afaik the 'Client' refers to the headset, not the Server on the PC - it's also only a 'Warning' not an Error, so my guess is the headset is using software/CPU decoding, or it's a false positive which can just be ignored. if the headset is working fine with AV1 and you're not seeing poor performance/bad latency with it then i'm not really sure what you need help with here. Warnings are just that, Warnings. they're not the end of the world and usually just there for information if you encounter issues but in most cases can usually be ignored.
oh i see, well it gets that warning, and then disconnects errors out and reconnects, gpu ofc supports AV1. performance is more than good at 300mbps with AV1.
when its working that is
it may be a warning, but is clear that is the one resulting in the disconnects.
it also just randomly disconnects,
hmm it seems that headset doesnt support AV1, so unsure why its actually working??? it supports H.265 but i believe that also causes this.
it's all about silicon. Older headsets won't have hardware deocoders for AV1, H264/5 have been around a long time and it's supported in a lot of devices.
also morer isn't always betterer. 300mbps for an AV1 stream is quote excessive. you really only need 100 at most. AV1 is pretty sharp even at 50mbps.
quest 2 supports h.264/265 but not AV1
its adaptive, only hits 300 when i'm moving a lot
just keep in mind that there's a law of deminishing return with these headsets. Throwing more bits at the problem only solves it to a point, then you start over-saturating the network hardware and the dedcoder which begins to degrade the performance. the sweetspot is usually between 50-250mbps.