Hey all, I’ve read the faq and seen the threads about loading midi control configs onto the NK2 and I promise it’s not quite the same issue, though I have similar symptoms. Let me explain:
Few weeks ago I got into WPDSK just for fun and wanted to go deeper, so I picked up a used NK2 but ran into the common problem of the knobs working but none of the buttons or sliders. I found this forum, got the config file, loaded it up, but still have the same problem.
I thought it might have been a Windows 11 issue, but I tried on a Windows 10 pc and still have the same issue. I tried numerous different versions of WPDSK but no luck. I thought the midi controller might have been defective but Windows midi reporting shows that all the inputs are working correctly and being received by the OS. Just recently I went as far as grabbing a RPI 3B and loading an image of VSERPI Waaave Pool, and the NK2 works perfectly on that system, so it’s not the midi controller, and it’s not the config file.
Anyone have any other ideas? I’d really love to be able to use the NK2 on Windows, so far I’ve most enjoyed messing with existing video clips and was a little disappointed the VSERPI WP doesn’t seem to have a media player function.
2 Likes
howdy
most likely things happening
- your nk2 is not configured properly, or is otherwise broken. I have several poorly functioning nk2 that i’ve bought used, these are not the most robust units around.
- select midi inputs section and/or midi/gui stuff on WPDSK is not configured correctly
- midi latch on WPDSK isn’t catching up and you are psyching yourself out to think that somethings broken. this kind of seems like the most likely overall given the info provided.
if you are using WPDSK Pro, this is a non issue, public versions have no midi support as of rn
vserpi 2.0 will have built in media players. access to DIY build info, dev kit sales will be limited to 6mo+ patreon supporters starting in winter 2026.
1 Like
hey thanks for the tips, really appreciate the response. and great news about vserpi 2.0, been meaning to throw you some cash anyway since i think your projects are really cool.
anyway, re:
-
i thought that too but my nk2 worked perfectly on a rpi, plus windows midi monitoring shows all inputs are firing correctly.
-
is there anything more to do than selecting the correct midi controller, and checking the midi box? i don’t have any other midi devices connected to this pc, and i would think if those settings were wrong, the controller wouldn’t work at all rather than partially. otoh i admittedly don’t have a huge amount of experience with midi stuff so i’m happy to be told i’m wrong.
-
does midi latching have anything to do with the button functionality? i misspoke in my initial post, my sliders are are actually working, it just seems like it’s the buttons that won’t do anything, despite lighting up on the controller as expected and showing up correctly in monitoring.
it also occurs to me that this could just be yet another weird win11 issue, so i plan to try some more on other systems, and maybe i’ll give WPDSK Pro a try.
[edited] to include a couple screenshots of the midi monitoring and korg kontrol editor config in case i’m missing something
as per the midi documentation in WPDSK, the buttons aren’t mapped to anything. so if all the sliders and knobs work then everything is working fine!
if folks want like full midi mapping built in for buttons and stuff, significantly more support on patreon and/or the current WPDSKPRO kickstarter would result in lots more freeware in general as well as more work done on improving midi and other interface fuctionality in the freeware. as things stand rn, the original WPDSK will not get any further updates, in favor of WPDSK Pro free editions it will be fully open sourced after the WPDSK pro kickstarter finishes up tho so someone may eventually create a distro with exact midi specs
Oh I see. I guess the mappings for A-N in the manual are just for the rpi version?
the documentation for wpdsk midi (and everything else) is all in contained the app itself!
