alvr is nto respecting my macium bit rate which overwehlms the av1 decode on my quest 3 (wired usb) causing artifacting toa unplayable extent
#alvr not respecting my maxium bit rate
lean plank
somber lintel
Could you send a copy of your session file?
lean plank
Could you send a copy of your session file?
yeah where do i find that
somber lintel
Where ever you installed ALVR
lean plank
Where ever you installed ALVR
ah leme figure out where that is i jsut isntalled the aur package
yeah feel like i am being stupid
[C2@C2archbtwdesktop ~]$ cat /usr/share/applications/alvr.desktop
[Desktop Entry]
Version=1.0
Type=Application
Name=ALVR
GenericName=Game
Comment=ALVR is an open source remote VR display which allows playing SteamVR games on a standalone headset such as Gear VR or Oculus Go/Quest.
Exec=alvr_dashboard
Icon=alvr
Categories=Game;
StartupNotify=true
PrefersNonDefaultGPU=true
X-KDE-RunOnDiscreteGpu=true
StartupWMClass=ALVR
[C2@C2archbtwdesktop ~]$
and clicking the open logs button dose nothing
tropic brook
@lean plank in all released versions of ALVR we made a mistake. In the graph, the horizontal lines you see are bitrate limits, but the white line is the throughout, not bitrate. If you install the nightly you can see both throughput and bitrate lines
As we explained in the tooltip, throughput is the effective maximum bitrate that the network supports in that moment, but not the actual bitrate that was sent
So basically you know that you're using 100% of your network if throughput and bitrate are roughly the same (except that because of some errors in the calculations, the limits we impose to the bitrate also affect the throughput)
lean plank
@tropic brook that confuised me mroe htne it helped i think. basiclay what your syaing is that the numbers i am seeing is the maxium my usb cable can do and not the actuly bit rate thats going on
tropic brook
<@777160299080974376> that confuised me mroe htne it helped i think. basiclay wh...
yes
the throughput is calculated as packet size / network latency
lean plank
well then uhh hopw do i check what is causing my issue becuase i am 70% sure it has to due with quest decode
tropic brook
while the bitrate is calculated as packet size * fps
lean plank
liek the whole screne jsut becomes a rgb mess of static
goes between midly annoying (not the whole screena s rgb mess) to unplayable
also how do i set a maxium bit rate then
tropic brook
yes, I see yo have huge decoder latency. 400Mbps is too high i think
start low at 100Mbps
lean plank
yes, I see yo have huge decoder latency. 400Mbps is too high i think
yeah thats not from the decoder i think beign weird theres some sort of bug somewhere
the latency only goes that high when the bug is present
tropic brook
use constant bitrate mode then
lean plank
kk i will try it
wary bone
constant 400mbps does work here fwiw (amd gpu, linux). i do have issues with adaptive too but i never bothered to really investigate it
robust tusk
we doubt you can do 400 av1
saying 400 on its own means nothing really
the headset cant decode this much, we know that quest3 can only handle 200mbit of h265 - and probably similar amount of av1
different headset maybe able to decode different amount
also note that setting 400 doesnt mean you generate 400mbit of entropy either - so cant use beatsaber or other lightweight stuff as test
wary bone
i'd take any explanation, including amd gpus doing magic. the fact, however, is, i can assign 400mbps on ALVR, and it is better than 300mbps and works fine
interestingly, h265 (again, in my conditions) falls apart IIRC at 300mbps w/ the Q3
fwiw thats also the limit, 450, and even 420, starts falling apart. this numbers are cabled. wifi i cant get to 400mbps av1 iirc
robust tusk
you can assign this value but that means nothing
we know the thing bottlenecks at 200
the pc has no problem encoding this much - but the headset cant decode it
and why would your quest3 be better than everyone elses?
its very difficult to setup a proper test scenario for this - you are relying on waving head around and subjective experience
and many other factors interfere, like auto-resolution or other adaptive settings
how would you even generate 400 mbit of av1 entropy consistently? not with beat saber
lean plank
and why would your quest3 be better than everyone elses?
ah i just though it could do 400 mbs av1
wary bone
be better than
Oh I don't mean that. All, and all I mean, is that I put 400mbps 90hz and it works. Whether something is lying or magic is happening, I do not know
entropy
I'm not sure what is meant, but, Assetto Corsa Competizione 120hz racing 40 vehicles has a loot happening on the screen, and if my impressions are correct, is quite annoying for encoders becasue things are changing subtly but quite fast. As I've just found out, moving from 90hz to 120hz has made me happy with the timing but the quality seems to have worsened and now I can only reach 350mbps/370mbps before glitching kicks in.
Going offtopic but anyway, quality improve while stopped but racing down the line it seems worse now 😦
Still offtopic but it feels to me there's a chasm between most people on VRChat or Skyrim VR or something, and me complaining about things but doing simracing, with the asphalt there in the middle all grey and needing to see details 'far' away.
lean plank
so any one knwo hwo i can get the thing to actuly use the correct bit rat
robust tusk
you dont want to set the bitrate, you just want to cap it so it doesnt overload headset - i move my slider a little bit so the peaks stay below 200 for hevc
but i dont trust the slider or the statistics graph, and there were changes and fixes made to this in various versions so it depends what you use