On 1/18/23 11:46, Abhishek Chakravarti wrote:
>
> Hello!
>
> Brian Durant <contact@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 thoughts about scripts for music. I will avoid flooding the list
with all of my ideas but will simply provide a couple of basic ones.
Note that I am new to OpenBSD and have little experience with scripting:
OpenBSD music scripts
Scan midi/ values (from dmesg or...) and route them to midithru/0
similar to manual commands below:
(Is there a use case scenario for rerouting midi/1 - ? by use of
midithru/1 -?)
$ midicat -d -q midi/0 -q midithru/0
$ midicat -d -q midi/1 -q midithru/0
Record audio from USB sound card:
$ aucat -o /home/user/Music/set/1 - ?.wav
Playback audio file:
$ aucat -i /home/user/Music/set/1 - ?.wav
To my knowledge, most USB sound cards have at least two inputs (for
microphone and guitar / bass as examples). Important that any script is
input sensitive and can automatically number files for each input in
order for possible playback with effects by using a simple alias created
automatically for the purpose, for the session (?) Also important that
monitoring is possible during file creation to avoid pauses while
performing a set.
No comments:
Post a Comment