-
Notifications
You must be signed in to change notification settings - Fork 1
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
VST => Ableton: No DAW Pass through = ports already in use. #2
Comments
Thanks for you kind words, There's no particular reason why I don't use the MIDI routed from the DAW in the plugin version. It simply felt easier to me to directly connect to the device. In that way you open the plugin and configure MIDI channels independently of where the plugin is loaded. Much like the "external instrument" devices do, you put MIDI config in the plugin independently of track's MIDI config. So far this has been no problem, but I only used JF Sebastian with Ableton for quick tests, mostly used within Bitwig or as standalone. Is it possible that this is a Windows only issue? |
This is causing an issue for me in Ableton 11. I see Deckard's Dream in the MIDI output drop-down, but it will not allow me to select it. I can change the channel, but that doesn't help. I suspect to support Ableton 11 we'll need DAW pass-through as an option. Edit: It looks like I can't select when using Bitwig as the host either, so something else must be going on. I noticed if I disable Deckard's Dream in the DAW's MIDI setting I can then connect to it, but that defeats the purpose. Any ideas what I might be running into? |
Hi @Spectavi, are you on windows? |
Yes, Windows 11. |
Hi, then this is probably an issue with windows not letting having a MIDI port open multiple times. This could probably be fixed if JF did not directly connect to the device (as explained in the comment above). I'll consider that for future upgrades, but it would require significant work and I don't think I'll be able to work on this anytime soon. |
I'm not sure how Bitwig is mitigating this but likely due to its port exceptions error handling. Using the VST, it's is very curious not to have midi routed via daw => thru. You can not define a port already in use per current implementation. Can you please explain why the VST version has stand alone midi configurables', if I understand I might be able to take a crack at the code.
quick aside. awesome tool!! github starred, hope I can help with window's daws'.
The text was updated successfully, but these errors were encountered: