voxsunsky.blogg.se - Hope for mac degen 2017

Hope for mac degen 2017 Pc#

Last three videos were visually very similiar! *2560x1440 72 fps by OBS studio latency +quality 709 limited priority (RTX 2080 ti with high performance MSI afterburner profile) for short-term decoding for evaluation to get smooth video experience The difference between " 709 limited" and " 601 limited" not further investigated!Ģ560x1440 72 fps by OBS studio latency 709 limited priority (RTX 2080 ti with high performance MSI afterburner profile) for short-term decoding for short-term decoding for evaluation to get smooth video experienceĢ560x1440 72 fps by OBS studio 709 limited priority (RTX 2080 ti with high performance MSI afterburner profile) for short-short decoding for short-term decoding for evaluation to get smooth video experience looks like 20 fpsĢ560x1440 72 fps by OBS studio latency+performance 601 limited priority (RTX 2080 ti with high performance MSI afterburner profile) for long-term decoding for evaluation of performance drops in decoding (test canceled by my self)Ģ560x1440 72 fps by OBS studio latency+performance 709 limited priority (RTX 2080 ti with high performance MSI afterburner profile) for short-term decoding for evaluation to get smooth video experience > some theories on working process on the HW decoder (snapdragon 835 specifications) and made some decisions for the resolution and framerate setup.Ģ560x1440 120 fps by OBS studio latency+performance 601 limited priority (RTX 2080 ti with high performance MSI afterburner profile) for long-term decoding for evaluation of performance drops in decoding (test canceled by my self) > Recorded now to more performant storage in writing (HDD 7200 rpm SSD), use performance profile and tested: Big Freezes are gone with HDD 7200 rpm and performance profile for gfx. Maybe the freezes where a result of writing performance to HDD (5400rpm) or the encoder does not like the MSI afterburner profile. Summary of Quest behaviour: no frequent "network paket loss"-style failures identified within 40 minutes of streaming, but frame rate seems to decrease over time.

Hope for mac degen 2017 Pc#

Resolution: scaled output = basic resolution see following explanationsĢ888x1600 fps by OBS studio latency+quality priority (RTX 2080 ti was in a kind of energy profile in MSI afterburner)īig freezes about half a second (many/all of them are also visible on PC video playback, ingame they were not recognized by me), framerate is lowering over time,Īt the beginning of the video is smooth framerate (on pc it looks not that smooth on 60 Hz display but constantly), audio was perfect all the time. Recorded scene: auto-gameplay in assetto corsa

Playback on Oculus with oculus gallery, video streamed by Win 10 DLNA

Paket loss could be a seperate problem but could also depend on the performance issue! To drive native resolution to/with oculus quest without issues, it is much more complicated to achieve, regarding my theory (how the decoder works). Some more optimization to the settings color format, color rangeĪnd scale filter could lead to better image quality. Please try the mentioned encoder settings in ALVR. My conclusion is that following encode setup of alvr should be fine as a input for the oculus video decoder: The problem is the encoding was performed by "OBS Studio", so maybe some of the settings need some translation to ALVR-Server settings.

Freezing was probably fixed by changing the encoder profile to low latencyĭid some testing and analysing (focused on the decoding performance of the quest, independant from ALVR streaming but results could also be valid for ALVR), and I think I found settings which should work without "performance drops after a time".

Its not a buildup in one of the queues (NAL or encoder frames), flushing them does not help.

Using h264 seems to prolong the time until the error occurs.

changing power management on the quest did not help.

Changing the video encoder settings on the server did not help (intra refresh, number of reference frames and encoder low latency profile).

Sound is not the issue, even with sound enabled, the issue appears, but later.

The encoded video on the server side looks fine

Issue is most likely on the client (Quest) side.

There have been several issue reports ( #64, #54, #51, #6) and I'm trying to bundle all information and work done ( #66) to find this bug so far. Stopping the client on the HMD and restarting it helps for a shorter period of time (5-10min) and then the error reappears. After the streaming is running for some time time (10-45min and longer) an issue occurs that results in: