-
Notifications
You must be signed in to change notification settings - Fork 27
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
Fixes #911 - Set VCCS PTT and audio device via LogonDetails.exe #912
base: main
Are you sure you want to change the base?
Conversation
As per advice from Patrick, there are some modules that aren't a standard part of Python. Shall fix :) |
# VCCS PTT Key | ||
|
||
print("Push a key you want to use for VCCS. (Note: Keyboard only)") | ||
PTT = str(int(hex(keyboard.read_event().scan_code), 16) << 16) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The keybind prompt character may be transferred to the next prompt as input.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea not too sure on how to fix, all the methods I've tried still result in the input being transferred to the next prompt.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I've resolved this somehow somewhere else. I'll get back to you on it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this be the result of holding the key down for too long? You should make sure to check for the key-up event when reading keyboard input
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I knew there was an easy solution - keyboard.read_event(suppress=True)
This will suppress the key that's pressed from the console.
VCCSInput = sd.query_devices(sd.default.device[0])['name'] | ||
VCCSOutput = sd.query_devices(sd.default.device[1])['name'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't provide any protection against 'abridged' names being the default device, e.g. in my case, my default device is Headset Microphone (2- Corsair
rather than the full Headset Earphone (2- Corsair HS70 Wireless Gaming Headset)
as saved in ES .prf files. Do we need a warning/prohibition of this? I wonder if it might make more sense to force people to choose their device from a valid list??
PrfVCCSNick=("TeamSpeakVccs Ts3NickName "+CID) | ||
PrfVCCSPTT=("TeamSpeakVccs Ts3G2GPtt "+PTT) | ||
PrfVCCSInput=("TeamSpeakVccs CaptureDevice "+VCCSInput) | ||
PrfVCCSOutput=("TeamSpeakVccs PlaybackDevice "+VCCSOutput) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we be considering setting the TeamSpeakVccs CaptureMode
as well for completeness or does it not matter/default to something sensible?
Probably also worth renaming the file to something like "Profile Configurator". |
Yeah. Also, given this .exe is going to be used by new people and observers, should we be explaining more explicitly what VCCS is? Something like: "VCCS is used for voice coordination within EuroScope."... We could maybe even allow users to skip the configuration of it if they wish, but I think 'making' everyone set it up is good personally. |
Sorry about the delays everyone! Been busy with work and trying to get FS 2024 working. |
Fixes #911
Summary of changes
Updated LogonDetails.exe to now set up VCCS PTT and audio devices.
Screenshots (if necessary)
N/A