• Release

  • DeoVR app version 14.5 (Comment, Forgot password, AB loop fix)

New version of DeoVR app 14.5 is available on Quest, Pico and Steam.

New

  • Added comments section to video player left panel
  • Added “Forgot password” option to sign in window

Improvement

  • Search input is saved between searches

Bug fixes

  • Fixed showing video in playlist even though it was removed
  • Fixed “Reset to default” binding not applying previous settings
  • Fixed video restarting to beginning while seeking
  • Fixed subtitles being shown behind video
  • Fixed tags layout on videos with a lot of tags
  • AB loop not being set properly fixed
    .- Fix for previous/next button inconsistencies in player

    Kieshi
    Same thing as in 14.4, there is an issue with remote control api.

    The remote api server uses VideoPlayer.CurrentTimeAsync to send current video time which has flawed logic. While video is paused the value will fluctuate because CurrentTimeAsync adds CurrentAppTime - lastCurrentTimeUpdate to the actual current video time. lastCurrentTimeUpdate is updated on each frame in Update() but if the remote api server reads CurrentTimeAsync between frames the value will not be stable.

    Sample currentTime values sent from remote api server with video paused:

    754.977
754.977356
754.981445
754.981934
754.9834
754.9844
754.9772

    This also has another issue on some headsets. If the device stops rendering, Update() will not be called and VideoPlayer.CurrentTimeAsync will grow infinitely even when the video is paused.

        @Kieshi I recently updated my DeoVR app for Pico 4 and now I can't see any of my media using DLNA streaming. I can connect to my PC and see folders but then no videos or pictures show in the list. DeoVR team please fix this issue ASAP!

          I'm using the single video deeplink formatting from the specification and now every video is throwing the error:
          "invalid video_url in video data". video_url is not part of the single video deeplink spec so something is broken in the new version.

            • Kieshi

            • Post #5
            • Edited

            Yoooi We will have a look. Can you please let us know which headset you use?

                denos can you please let me know which headset this is happening on?

                    Kieshi Yes I have updated the app through Pico's interface directly. I can try again but definitely seems like something was broken about this.

                      Kieshi
                      The core issue of remote control server not sending stable currentTime is present on all heatsets/pc.
                      The issue of currentTime growing infinitely was reported by a MFP user using Quest 3 when he put down the headset and it went to some sleep/standby mode.

                          9 days later

                          denos can you please check if the issue is fixed now?

                            Yoooi I will check with the team, thanks