You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all, and thanks Simon for making this application. It's the thing I need right now and is very cool!
I am using the Wooting keyboard with this program under Windows and planning to use it with various DAWs and other MIDI programs.
currently, the application works happily when its window is in focus. Unfortunately, if I change focus to another program (Reaper, in my case), the Wooting is now recognised by the OS as a standard input keyboard, and my virtuosic keyboard noodling translates as wild spamming of the DAW's keyboard shortcuts.
As a programmer, I'd rank myself as elderly script kiddie at best, and I do realise that this request is the entrance of a rabbit hole on many levels.
For starters, the program could no longer be so neatly cross-platform since I imagine that the means for getting lower down in the OS will differ greatly for each platform and will need completely different code for each.
As far as I can search up, achieving this in Windows would need Raw Input From reading this though, I am not clear on whether there is a way to make sure all other apps ignore the Wooting's existence as a HID keyboard when the other apps are in focus.
Sooo, what do people think? Is this just trying to put legs on a snake? Have people already found a neat way to deal with this?
My goal in using this program with the Wooting is to create a basic and affordable isomorphic keyboard for people wanting to study, compose and/or perform microtonal music (using scales and tunings other than the standard western 12-note scale and tuning).
My first attempt can be seen/heard here on a mechanical keyboard with no velocity of course: Youtube Link.
Image: Detail of Wooting with resin-printed translucent keycaps.
The text was updated successfully, but these errors were encountered:
Hi all, and thanks Simon for making this application. It's the thing I need right now and is very cool!
I am using the Wooting keyboard with this program under Windows and planning to use it with various DAWs and other MIDI programs.
currently, the application works happily when its window is in focus. Unfortunately, if I change focus to another program (Reaper, in my case), the Wooting is now recognised by the OS as a standard input keyboard, and my virtuosic keyboard noodling translates as wild spamming of the DAW's keyboard shortcuts.
As a programmer, I'd rank myself as elderly script kiddie at best, and I do realise that this request is the entrance of a rabbit hole on many levels.
For starters, the program could no longer be so neatly cross-platform since I imagine that the means for getting lower down in the OS will differ greatly for each platform and will need completely different code for each.
As far as I can search up, achieving this in Windows would need Raw Input From reading this though, I am not clear on whether there is a way to make sure all other apps ignore the Wooting's existence as a HID keyboard when the other apps are in focus.
The only Rust example I could find was this one: https://github.com/Jonesey13/multiinput-rust that seems geared toward allowing multiple mice and joysticks on the one machine.
Sooo, what do people think? Is this just trying to put legs on a snake? Have people already found a neat way to deal with this?
My goal in using this program with the Wooting is to create a basic and affordable isomorphic keyboard for people wanting to study, compose and/or perform microtonal music (using scales and tunings other than the standard western 12-note scale and tuning).
My first attempt can be seen/heard here on a mechanical keyboard with no velocity of course:
Youtube Link.
Image: Detail of Wooting with resin-printed translucent keycaps.
The text was updated successfully, but these errors were encountered: