-
Notifications
You must be signed in to change notification settings - Fork 28
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
Midi controls issues #205
Comments
The best working version of the application now for MIDI control is the
relatively new Seq66 project at:
https://github.com/ahlstromcj/seq66
It's a much better version of the Qt Sequencer64. And, since I finally bought
a controller (the Launchpad Mini), I was able to debug a lot of code. Also,
you can find "*.ctrl" files for the Launchpad Mini in 4x8 and 8x8 mode in the
data/linux directory and he data/win directory. You need to modify qseq66.rc
or qpseq66.rc to use one of those files, and run Seq66 in the mode (4x8 or 8x8)
that matches the file. You can tweak the "ctrl" files to match your setup.
One day I hope to catch up with the documentation of Seq66, as it is
sufficiently different from Sequencer64 that it is starting to matter.
Good luck!
…-------- zigmhount 11:18 Thu 07 May --------
Hello (again :) ),
I've been trying to set up more MIDI controls for my control surface, and I can't find any configuration that works, similarly to what I had in the end of the thread on #188.
I've tried many configurations on 3 different controls, here goes:
### 1. Mod Queue
`# mod queue`
`70 [1 0 144 87 127 127] [0 0 0 0 0 0] [0 0 0 0 0 0]`
or
`70 [1 0 144 87 0 127] [0 0 0 0 0 0] [0 0 0 0 0 0]`
don't do anything, not even if I keep key 87 pressed when selecting a pattern.
`70 [0 0 0 0 0 0] [1 0 144 87 127 127] [0 0 0 0 0 0]` turns on the queue mode, including the Q button on the interface - isn't that supposed to be "keep queue" instead? (question 1.a)
However I can't turn the queue mode off, not even with `70 [0 0 0 0 0 0] [1 0 144 87 127 127] [1 0 144 87 0 0]`. Question 1.b: am I missing something or is that a bug?
### 2. Keep queue
Neither of the two following seem to have any effect:
`# Keep queue`
`96 [1 0 144 87 127 127] [0 0 0 0 0 0] [0 0 0 0 0 0]`
`96 [0 0 0 0 0 0] [1 0 144 87 127 127] [0 0 0 0 0 0]`
### 3. Other similar controls
I've had similar results with the toggle command (only 1st column, haven't tried all combinations) for `screen set up` and down (66 and 67), `mod snapshot` (69), `mod glearn` (72) and `solo` (76).
### 4. Midi Record
When I open the pattern editor (with the solution from #188 that works ;) ) I try to active MIDI RECORD without success with any of these 3 attempts:
`# MIDI RECORD (toggle, on, off):`
`81 [1 0 144 82 0 127] [0 0 0 0 0 0] [0 0 0 0 0 0]`
`81 [1 0 144 82 127 127] [0 0 0 0 0 0] [0 0 0 0 0 0]`
`81 [0 0 0 0 0 0] [1 0 144 82 127 127] [0 0 0 0 0 0]`
### Conclusion
That's what I tried for now. Since so many controls are having similar issue, it may be a general problem (but I'd be surprised that nobody raised it before) or I may be doing something wrong :)
I'm on 0.96.8 midi_control. Midi controls work to turn patterns on and off, play/pause, pattern edit, and midi_control_out works (LEDs light up when I select Queue or Learn in the GUI, as well as patterns buttons' lights). I've briefly tried MIDI RECORD, Learn and Queue on 0.96.1 and I can't get it to work either (Play/Pause works though).
Sorry for the super long post, I've tried to be exhaustive, let me know if there's anything else you'd like me to try out.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#205
--
Money may buy friendship but money cannot buy love.
|
Great, thanks for the news, I'll give it a try! And congrats on buying a Launchpad :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello (again :) ),
I've been trying to set up more MIDI controls for my control surface, and I can't find any configuration that works, similarly to what I had in the end of the thread on #188.
I've tried many configurations on 3 different controls, here goes:
1. Mod Queue
# mod queue
70 [1 0 144 87 127 127] [0 0 0 0 0 0] [0 0 0 0 0 0]
or
70 [1 0 144 87 0 127] [0 0 0 0 0 0] [0 0 0 0 0 0]
don't do anything, not even if I keep key 87 pressed when selecting a pattern.
70 [0 0 0 0 0 0] [1 0 144 87 127 127] [0 0 0 0 0 0]
turns on the queue mode, including the Q button on the interface - isn't that supposed to be "keep queue" instead? (question 1.a)However I can't turn the queue mode off, not even with
70 [0 0 0 0 0 0] [1 0 144 87 127 127] [1 0 144 87 0 0]
. Question 1.b: am I missing something or is that a bug?2. Keep queue
Neither of the two following seem to have any effect:
# Keep queue
96 [1 0 144 87 127 127] [0 0 0 0 0 0] [0 0 0 0 0 0]
96 [0 0 0 0 0 0] [1 0 144 87 127 127] [0 0 0 0 0 0]
3. Other similar controls
I've had similar results with the toggle command (only 1st column, haven't tried all combinations) for
screen set up
and down (66 and 67),mod snapshot
(69),mod glearn
(72) andsolo
(76).4. Midi Record
When I open the pattern editor (with the solution from #188 that works ;) ) I try to active MIDI RECORD without success with any of these 3 attempts:
# MIDI RECORD (toggle, on, off):
81 [1 0 144 82 0 127] [0 0 0 0 0 0] [0 0 0 0 0 0]
81 [1 0 144 82 127 127] [0 0 0 0 0 0] [0 0 0 0 0 0]
81 [0 0 0 0 0 0] [1 0 144 82 127 127] [0 0 0 0 0 0]
Conclusion
That's what I tried for now. Since so many controls are having similar issue, it may be a general problem (but I'd be surprised that nobody raised it before) or I may be doing something wrong :)
I'm on 0.96.8 midi_control. Midi controls work to turn patterns on and off, play/pause, pattern edit, and midi_control_out works (LEDs light up when I select Queue or Learn in the GUI, as well as patterns buttons' lights). I've briefly tried MIDI RECORD, Learn and Queue on 0.96.1 and I can't get it to work either (Play/Pause works though).
Sorry for the super long post, I've tried to be exhaustive, let me know if there's anything else you'd like me to try out.
The text was updated successfully, but these errors were encountered: