-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
v5.6.0 Win x64 : cannot select MIDI-Ports #152
Comments
I see the same problem (Windows 10). All my devices appear in the menu list, but any attempt to connect produces the error shown by @Possemo Otherwise, JUCE 6 looks very nice, and I'm looking forward to testing more! |
I too think that it is the right way to progress and use the newest JUCE libs. This bug seems to come form the upgrade to JUCE 6, there are probably some changes needed in order to get it working again. Interestingly the "Microsoft GS Wavetable Synth" does work so it shouldn't be too hard to fix. I looked into it but my knowledge about C++ is too little. I saw that the demo from JUCE about MIDI-ports does it quite differently: |
The pull request from dehnhardt "make it compile and work under Linux #151" fixes it! Great, thanks dehnhardt |
Is it really fixed @Possemo? I built ctrlr standalone with #151 and tested with the Reface CS panel. I could send data to my Reface, but I didn't get anything back. There was no error opening the input device, but nothing showed on the midi monitor when I moved a slider on the hardware instrument. |
I used vs2019 on Windows. My build seems to work ok. I have to say that I took the newest master branch and I added the changes from dehnhardt related to mididevices myself. This way I hoped to learn something... oh well. I tested it with my Matrix-1000 panel and it looks all ok - bidirectional MIDI communication, Lua scripts etc. Tested with the Matrix-1000 hardware synth. Also the vst plugins seem to work. There are some small bugs on vst3 but it's basically working ok as well. |
Thanks! I also used VS2019 on Windows, so it should work for me. I'll keep trying. |
I separated the patch for upgrading MIDI to the current JUCE implementation. See: dehnhardt#1 |
After some testing, I see that midi is received, and I can fetch the value in lua and update the modulatorValue myself and see it reflected on the panel. The problem seems to be that ctrlr does not do it by itself. Has anyone else seen the same thing for modulators not using lua? |
You mean that the sliders do not react to incoming midi? This has nothing to do with Lua (afaik). That never really worked for me, even with v5.3.201. My conclusion: you have to do that yourself with Lua scripts. |
Thanks again @Possemo ! For me with v5.3.201, the sliders usually do react to incoming midi, both for CC and SysEx. The exception is a certain kind of Roland SysEx (#140), where the only solution was to write a lua script. Actually, the reason I started building ctrlr from source was so that I could fix that issue, but now there seems to be a deeper problem. It may not be worth trying to track it down if Roman is planning to redo that part of the code anyway. |
Only device I can select is the standard "Microsoft GS Wavetable Synth". This one seems to work, other ones throw the above error.
I tested Standalone and VST3, it's the same on both.
Btw. on the VST3 "input from pluginhost" does not seem to work, "output to pluginhost" does not pass sysex. Output does work for notes and program changes tough. But this is another issue I'd say is on much lower priority than the non-working MIDI-ports
The text was updated successfully, but these errors were encountered: