On 1/18/23 18:35, Luke A. Call wrote:
On 2023-01-18 16:51:28+0100, Brian Durant <cont...@anarchosaxophonist.org>
wrote:
On 1/18/23 11:46, Abhishek Chakravarti wrote:
Brian Durant <cont...@anarchosaxophonist.org> writes:
The only disadvantage that I can see at this point, is that what I am
describing would require a number of open terminals on the desktop,
which can be confusing to sort through, particularly during a live
performance.
Although not a direct answer to your question, perhaps tmux(1) might be
helpful here? You could have one tmux session window split into several
panes. Cycling through the panes is quite simple with PREFIX + o (the
default PREFIX being CTRL+b; in my case it's mapped to CTRL+o
Thanks for that. I haven't played around with tmux for ages, but you are
correct that could potentially help with terminal clutter. Below are a few
[....]
FWIW I have my tmux set up to use Alt+# (alt+1, alt+2...) key
combinations to switch among tmux panes more easily under X than using Ctrl+b
every time, which might be helpful if efficiency is important. It is
also easier for me to put in muscle memory. I can provide details off-list if
desired.
Thank you for that generous offer. However, before we go there, I think
that there is a need to be more specific (to the extent that I can) at
this point, regarding my use case scenario. This can be divided between
audio (baritone saxophone, bass and singing) and MIDI (a class compliant
launchpad type controller and a class compliant MIDI keyboard). midish
looks like a very strong contender, but there are two issues that I am
unclear about:
1) Can Fluidsynth instruments be changed on the fly when using midish?
2) Can MIDI events be used to trigger sndio and ffmpeg actions on the
system? Here I am thinking of the possibility of using my controller pad
as an alternative to a script launcher.
The audio side is in many ways more clear cut. I need to be able to
record saxophone, voice and bass (I am unfortunately limited to two of
these at a time with my current hardware.). The input through the sound
card would need to be monitored (when live) and be recorded to file for
use as loops with basic sound effects (ffmpeg?).
Sooo the big question with relevance to tmux, is how many terminal
instances do I need for this scenario? I know my instruments, but as
stated, I am a new user to OpenBSD, so I am trying to wrap my head
around this scenario. I am cautiously optimistic, as (to my
understanding) Ableton Live and Launchpads use scripts (hidden behind
proprietary mumbo jumbo and GUI) so it should be possible to do this in
OpenBSD as well.
Any input on how many terminal instances I will need, particularly with
reference to audio, but also the MIDI in my scenario will be very much
appreciated, as this will help me nail down my need for using tmux, a
script editor, or something completely different to test this scenario
in action on OpenBSD.
