jeanette_c wrote: ↑Sun Sep 10, 2023 11:01 amHi @Linuxmusician01 , I don't know of much in the way of tutorials. If you are interested, you migith be interested in my extra commands:
http://juliencoder.de/test/sound/jbs_mi ... .8.tar.bz2
At the end of your ~/.midishrc add:
exec "/path/to/your/user_dir/.midish_extra";
At the top of that file you need to make your device setup, which is outlined in the manual. My setup has lines like these, using ALSA sequencer:
dnew 0 "20:0" rw # use sequencer port 20:0 in read/write or i/o mode
dnew 1 "Prophet 12 Keyboard" rw # use the ALSA sequencer port of that name for read/write input/output
To add more USB MIDI gear that you sometimes want and sometimes not, you could have a procedure like that in your .midishrc:
proc add_burte {
dnew 4 "Arturia MiniBrute 2S" rw;
inew brute {4 0}; # named input channel
onew brute {4 0}; # named output channel
dclktx [dlist]; # make sure clock is sent to all devices
}
These inew and onew commands are good ones to put in your .midishrc, so you can create named channels. That way you can address your synths' MIDI channels by name and not by numbers like {4 0} or {0 12}. Much more usable.
If you have further questions, please feel free to ask, either right here or via PM.
Best wishes, Jeanette
Thank you for the info and the tips. I'm gonna have to try and find me some time to read the manual.
Curious to see if quickly creating a Midi file for synth or drumcomputer is doable. And curious to see if Midish is usable for looping. The current solutions I have for this via the command line and they pause for a short time after playing, which timing-wise is a deal breaker for drum computer sequences of course.
