glad to report that it correctly works with my guitar, with the rocksmith USB cord, and was able to beat a boss in Pato Box with it :D -
Abject Audio Inputs
A downloadable weird tool for Windows
This is a small project which allows you to bind inputs from your keyboard to frequencies recorded from your audio devices.
I was able to play Dark Souls and Doom Eternal with it, using a bass and a flute. Singing works as well as long as you are able to keep a certain consistency in your tone.
I still don't know actually...
Didn't try much so far... I used a Focusrite Scarlet Solo for the bass, and my headset mic and webcam mic for the flute. It even works with the Stereo-Mix from Windows!
Click download now to get access to the following files:
Log in with itch.io to leave a comment.
Hi, I noticed that this doesn't work with USB microphones (they don't show up on the device list), is this planned in the future or is this an issue with my computer?
EDIT: It recognises my webcam microphone but not my other mic, assumedly because it's labelled "generic USB audio" as opposed to "microphone" or something similar.
Amazing project! Is there currently a feature or hack for importing/exporting multiple keybinding sets for different games?
Not for now, but this is something I have in mind for later
1.2.0 is the version you are looking for ;^)
I'm trying to figure out a way to bind camera controls with this (to play subnautica) - I get why assigning mouse movements would be difficult, but maybe as a workaround it could output using a game controller? I don't seem to be able to assign any pitches to game controller outputs (while selecting the input, pressing buttons on my controller does nothing), but if that was added as a feature, it'd basically eliminate the need to control the mouse for any game that can use a game controller. Is this a potential option?
I can only assign keyboard inputs for now. The thing to understand is that my tool "send" inputs to a window, using the Win32 library. Whereas when a game records a controller, it is directly linked to this said controller. Thus, I can look into it a bit, but it might be hard
Ok I've been fiddling and found a workaround - with AutoHotKey I can pipe the key output from AAI to do whatever script I want. So I've got it set to move the mouse by outputting a "j" and then AHK moves the mouse when the j key is pressed. Bam. Camera control achieved.
I'm having a little difficulty with making nice, fluid motion, though - I was hoping I could turn right as long as I was playing a certain note, for example. And I've got a script that, so long as I hold "j", the mouse continues to slide right at a constant rate. But when I try to use AAI to send a "j" to move the mouse, it seems to only send and release one "j" instead of holding it down, even though I'm using the "holded" type, and the mouse stops moving. Is there a way to "hold" a button down for as long as the corresponding note is being played? Thanks!
EDIT: I think I fixed it - I think it was a problem with my script and not the app. Camera control is starting to feel pretty smooth! This is really cool!
I'm having this issue where my inputs are registered by windows explorer and chrome, but when it comes to games they aren't. Any idea of why that's happening?
Anyway, congrats on putting out such a cool tool!
Hmm... Are your games in foreground ? Have you tried windowed and full-screen ? Is the "On-Off" button turned On ? (Sorry if my questions seem dumb, I have to ask them if I want to distance-debug ^^)
No problem! I understand these questions are essential.
So I got it working by changing user permissions for both dark souls and the tool. I also had to change all inputs to "holding" as single inputs weren't being read by DS (may have something to do with my PC not being powerful enough?)
Thank you for the reply. I hope that this comment can eventually help someone with the same issue.
Oh ! Do you have a monitor which has a refresh rate of more than 60 FPS ? I think it is what causes the single-tap to not work. luckily, I'm updating the tool in 1.0.7 in the next hour and it should fix your issue (I guess... I hope...)