Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Add some way to select AVPro Low Latency mode at runtime #52

Open
lackofbindings opened this issue Dec 2, 2024 · 3 comments

Comments

@lackofbindings
Copy link

Some friends were looking for a world with AVPro low latency to host a VR portal, so I tried adding a second AVPro module to my world's VizVid player that has low latency turned on so that players could select it from the dropdown when entering a url. However having two AVPro modules they seem to fight over which has control over the audio sources.

Could we either get a way for VizVid to switch the audio sources between different instances of AVPro depending on which is active. Or could we get some in-game toggle in the options menu to use low latency mode?

Side note: Is it possible to toggle "Is Low Latency" on the VizVid AVPro core at runtime? Could I just make and Udon script that toggles that?

@JLChnToZ
Copy link
Owner

JLChnToZ commented Dec 2, 2024

As all the player backends are all modularized, you can simply duplicate a AVPro Module and enable Low latency mode there (remember to add the cloned one to core alongside with the original one).

For audio sources, yes, it is needed to duplicate a new set of audio source and assign them to your new AVPro module, as one audio source can only attached to one AVPro player.

@lackofbindings
Copy link
Author

How would I connect them both to audiolink then? Is there an event or variable or something I can listen for in Udon so that I could write a script to re-assign the references based on what core is active?

@JLChnToZ
Copy link
Owner

JLChnToZ commented Dec 2, 2024

No need to do that, this is where the purpose of "Main Audio Source" of each backend modules kick-in. What you need to do is use an existing audio source that assigned to the new module also configurated to output stereo audio, or duplicate one from AudioLink controller, assign it to plays audio from this video source, then assign it to "Main Audio Source" field. When user plays video/live stream with this module, the core will tell AudioLink to use that audio source automatically.

This is by designed, but sorry I didn't document it detailly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants