Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

HereSphere VR Video Player (Meta Quest)

VR video player with immersion-enhancing algorithms, streaming, and media library features · By HereSphere

Remote API altering the original media path

A topic by Khrull created Jun 12, 2022 Views: 542 Replies: 7
Viewing posts 1 to 6

Hey I'm the developer of XTP a funscript player for tcode sync. Im am looking at the remote API in HereSphere. I notice the path to the media playing has bee changed to "/storage/emulated/0/Interactive/<media>" for SMB and "download" links. My player needs to know where the media is located so I can pickup the script remotely. But it cant do this if the path to the original media has been modified. 

Is this intentional? It would seem to me any remote software would require the path to the original file. Even if that IS on the local filesystem.

Thanks

Developer

This is intended behavior. SMB files and files streamed over download links don't have a full path. SMB files only have the share folder name as the root directory, so it's incomplete. The sent path is the fallback directory for scripts. Users can define it in the user settings, even inputting the path to their script folder on their PC. You could also implement additional fallback directories like ScriptPlayer, which allows users to add folders to look for scripts.

Well that blows. Ya I have a media library set up that works but it would be nice to not have to be tied to that. Download streaming links have the same issue? I have a built in web server that uses this.

Also just FYI, basic html select elements do not work for some reason in the browser. I converted mine into radio inputs for the time being.

Developer

The html select elements probably has to generate a new window, which isn't implemented yet.

I could add some logic to check to see if the fallback script directory is blank, and then just send the incomplete SMB path or the video url if that's the case.

I don't know what this incomplete SMB path looks like but I'm not sure an internal URI would be useful for any external remote controls.
The file name is an absolute necessary for me in any case.

Do you have any documentation for the remote control API yet? I have not found any but thought Id ask just in case I missed it.

Developer

The remote control API follows the same structure as DeoVR: https://deovr.com/app/doc#remote-control

The SMB path starts with the shared folder. Anything above that shared folder is unknown, so you won't be able to get the full path with the drive letter. Is it absolutely necessary that you have the complete path? Can't you scan designated folders to see if the filename matches and just use that instead?

Yes, I have it search the user selected media library for the file if it cant find it in the same path passed back by the remote control.
I use the same code I use for Deo that I use for HereSphere. Not sure that was a good thing though cause Deo's implementation is kind of jank. Seriously, who uses 0 for true?! Still, dev wise, It was nice to not have to do much to the existing code. The only differences being DeoVR would pass back the web link URL directly if the streaming link was a url launched in the browser. I also didn't need to add the download attribute to the clicked link for it to play in the Deo native player.

Not a huge deal.

TBH you can leave it the way it is as I've already compensated for it and it works pretty well for me now. 

I was just asking cause something seemed off about a remote control machine receiving a inaccessible path internally on the quest. 

I'm glad to see a good VR player on quest finally has this feature.

Thanks!