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] Full Screen Control #179

Open
DanielGarciaOnAir opened this issue Jul 17, 2024 · 1 comment
Open

[Feature Request] Full Screen Control #179

DanielGarciaOnAir opened this issue Jul 17, 2024 · 1 comment

Comments

@DanielGarciaOnAir
Copy link

This is a very "niche" request, but I would like to think it is a small request that can be completed without too much difficulty. (But I could be completely wrong!)

I work for a radio station, and one of the pieces of technology we use daily is the Wheatstone Glass LXE, a fully digital audio console that runs on a touchscreen, and is routed to operate the same way a physical audio console functions, but just eliminating the hardware aspect. (See link for more details)

I would love the ability to do something like this at home with the GoXLR so that I can put the physical hardware in a different spot while still having access to control the faders, activate the sound pads, voice modulator, etc. My idea to execute this is to allow a full screen option in some part of the app, and once entering full screen, you would only see the GoXLR mixer, and be able to control all aspects of it using your mouse, or in my case, touch controls on a touch screen monitor.

If this is possible, I would love to see it implemented for my use case, but I also understand it is a very niche request that might not be necessary enough to be implemented.

Thanks for all you have done so far to keep the GoXLR alive!

@FrostyCoolSlug
Copy link
Member

Sorry for the late response..

This is something which could be done in theory at least, but it would end up being quite a major undertaking. The API does support what would be needed for this (possibly outside of sample playback), and we do have an SVG representation of the GoXLR (which would need adjusting for this specific use case), but as you say, it's an incredibly niche use-case, and time would unfortunately be better spent working on other parts of the Utility.

I'll leave this open for now, in case that changes, or someone else wants to give it a shot. It's all open source, so someone else might want to try and give this a try :)

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