• Support
  • Bug with Alpha videos and DLNA

It looks like the player is ignoring the alpha property of videos when played over DLNA. They show the alpha passthrough option when played on-device, but not when played via DLNA (tested with the same file).

Hey, we are aware of this, thanks for reporting, no estimate on fix yet.

Edit: Actually we will make a workaround, showing the Alpha button for DLNA streamed videos. You will be able to turn it on yourself.

Filename automation is not possible trough DLNA since some servers rename the video. Solution will probably be moving it to metadata.

Thanks, I appreciate the update! An override/manual button in the passthrough panel would be great!

    samsalot 13.12 version will get 2 smaller updates, we will include this fix into 13.12.2

    I'm not sure that the problem is with the filename, since the player shows the correct filename with my DLNA server (Kobi) but in any case always showing the toggle is a very welcome addition.

    a month later

    Hello, just wanted to check in on this. With the quest3 and it's improved passthrough due to be arriving in the next week, is the 13.12.2 update scheduled to be released any time soon? This would be an extremely useful feature to have working with it.

    You won't have to worry about the Quest 3 and alpha not working since DEO is unable to see any DLNA server or any local files on the Quest 3 yet. Clicking into the local file option at the bottom menu is broken.

      wgknestrick FIX: Can't see local files in DeoVR on the Quest 3? Here's how to solve it
      Tip for Quest 3 users who can't see their local files: you need to set manually permissions so that the DeoVR app has access to your Quest 3's internal storage.

      For some reason, Meta doesn't mention this when doing the auto-install of your existing apps onto your new device. It doesn't set (or even ask to set) the permission for any of your legacy apps. Set the permissions properly and DeoVR will work perfectly.

      To set permissions:

      Press / on your controller to pull up your universal menu.

      Select Settings in the top right-hand corner.

      Select Apps to open the Apps permissions menu.

      Select DeoVR app and give permission.

      Thanks to user wgknestrick on the DeoVR forum for pointing this out! https://forum.deovr.com/d/2060-quest-3-unable-to-see-local-files

      7 days later

      hey gang, any ETA on the workaround patch for the forced alpha button?

      Thanks

      I have same problem with Quest 3 and shared PT vids via DLNA - there is no "Alpha" button !
      Please make a fix for this ASAP !

      There is a newer version released today 13.12.1.3 but the problem is not fixed and I don't find the changelog.
      Note he argument that DeoVR cannot correctly read file names when the video is open via DLNA is not correct because it recognizes keywords like 'FISHEYE190', mkx200, etc. But not 'ALPHA'...

      Chiming in here because I also would like to use the alpha channel via DLNA, because having to actually transfer the huge mp4 files onto the device is a huge pain. Especially a 128gb device. And the user @boudaba is correct. It isn't an issue with filenames because DeoVR still recognizes keywords like 'FISHEYE190', mkx200, etc. But not 'ALPHA'...

      We can still modify the chroma key colors ourselves, but no matter how much tweaking it is never as good as the alpha channel filter which works pretty much perfectly with the click of a button.

      Please figure it out and fix this. Thanks...

      Even better will be if you can adopt the PC version of DeoVR for proper playback of PT vids via VirtualDesktop . It works now but for some reason the hairs of the models are half transparent regardless of the hair color ... ?!

      Why is the alpha (or any video settings) flag set via filename and not inside metadata (where it seems like it should reside)? Filename is not the place to store pertinent metadata for files to playback properly. If only there was a place for that.....

        19 days later

        wgknestrick While not documented (yet?) it is possible to specify the alpha in the JSON metadata:

        {"encodings" : [...],
         "chromaKey" = { "enabled" : False, "hasAlpha" : True,
                          "h" : 0, "s" : 0, "v" : 0, "opacity" : 1, "threshold" : 0},
         "title" = "...",
        ...
        }

        I hope this helps.

        Update, the latest update has fixed the issue with the Alpha filter not working correctly when streamed via DNLA. Thanks for fixing the issue because it frees up a lot of space on my device.

          a month later

          KatDEO
          Hi KarDEO,
          It appears this issue still happens with http. I made my own local server and that serves a webpage I made which works, except the _ALPHA is still ignored. I have DeoVR 13.13. Any ETA on a fix?

            2 months later

            justsomeguy

            I'm also not able to get Alpha passthrough working on an http / https site. It would awesome if this could be looked into.

            For now I setup a DLNA container just for this purpose. I felt the need to lock it down with firewall rules since it bugs me that DLNA is just open/advertised to anyone on the subnet.