Failed to query midi devices.
Closed this issue · 14 comments
On startup of .exe file i'm getting:
On startup of a main .ahk script i'm getting(AHK itself is installed, and 2 other scripts launched with no issue):
As a midi i use USB MIDI interface, similiar to this:
https://www.ebay.com/itm/USB-MIDI-Interface-Cable-PC-to-Novation-25-SL-MK2-USB-MIDI-Controller-Keyboard-/161466292936
Midi is detectable and works in sound editing programs(Such as LMMS), and Internet Browsers.
Any tip?
Can confirm i get the exact same error on Windows 10. Tested with a USB MIDI device and with LoopBe1
same problem here :c
Someone mentioned the same issue on Reddit. I need to figure this one out
same issue
Alright, so, I'm working on a new version that doesn't use Autohotkey (Uses C#). It's almost ready, I just need to get warframe to react to the inputs
How are you sending the inputs? Are you sending it as a key like the AHK version?
you could try using user32.dll to send the keys
@lilggamegenius Yes. I'm currently using WPF, so I can't use SendKeys.SendWait
.
I'm going to try it out with user32's PostMessage
, however it also has to be able to send mouse inputs, as that's what changes frets
maybe you can try that and add this extern function from the same dll? https://stackoverflow.com/a/2416762
Could work. I've been doing some research and from what I gather I also have to get around DirectX, since it also proceses inputs in a different way.
It's a bit late now for me, but I'll look at this tomorrow
Can you push what you have to a test branch? i can try doing some testing on my own.
Yup, done. Inside ActionManager.cs
you'll find all of the user32.dll
functions I've already implemented, as well as some of my (not yet finished) code.
OnNoteEvent
is the method where note events will be processed, and the note ID should be passed to transform it to a key press
@lilggamegenius You can make push requests to the Testing
branch as you please, but I'll keep the development branch as clean as possible
Made a PR of my current changes but not ready to be merged yet. Managed to get warframe to react to input but still needs some work.
#4
Issue no longer relevant to this new version. Closing