-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Playtime doesn't work with MIDI input devices > ID 63 #1165
Comments
Works here. What if you close and reopen the Playtime window (or press the refresh button in the window title bar)? Maybe it just didn't get the information about the newly added loopback MIDI port. |
Which version of Helgobox? |
It says 2.16.1 in the top right of Playtime.. |
Not sure if it would make a difference, but the current version is 2.16.3 (update via ReaPack). Can you try that? If that doesn't work, what's the ID of the loopback input device in the MIDI preferences? |
Just updated it and nope no change! How odd. It's device number 64 (I've got a lot of MIDI flying about, plus a lot of redundant devices to be fair). Not enabled for Control messages but that shouldn't be an issue as neither are several other inputs which do work with Playtime.. |
If you assign it an ID that's lower, it should work. Could be a bug indeed. |
Yes, it's a bug. Will be fixed in 2.16.4. Until then, you can use the mentioned workaround. |
…ting only 63 MIDI devices helgoboss/helgobox#1165
Describe the bug
To better control what and who is sending MIDI to Playtime for various loops, I would like to use a virtual MIDI port (Reaper Loopback 1 via MIDI Device List). It sets ok in the main arrange window but Playtime shows 'No input' and refuses to play ball
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should work as expected above
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
MacOS 12.6.1, Reaper v7.20
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: