Fleeting thoughts, 11/25/23;

I should default to always including a kick and a snare (uniform, very basic) across all
sampler banks, ideally panned L and R respectively - regardless of sampler unit, I always
seem to be lacking the ability to add the finishing touch of a danceability factor to
these sample collages of sorts. Starting small, I could just add these pieces to every
S2000 and existing ESI32 bank (of which there's one). The thing is, on the S2000, there's
always examples of both seeing as I use the unit exclusively for percussive applications,
but on the rare occasion I'm overlaying a PDJ atop an isolated sample, those elements are
innaccessible as I can't (easily) carve out an exemption to the isolated span.

- Three device scheme, based around the JLC Nexus MIDI Utility; I have a desire to
have one of these units with only hardware sequencing devices, preferably ones with
tactile start/stop controls - this would be useful for spontaneous jams whereas a
separate instance featuring feeds from a workstation (like a PC w/ MIDI interface)
would be superior for clinical predefined triggering. This almost inspires me to
accrue older, more constrained units for use with the 'spontaneous' class of pulse
generators and save the later, more spacious examples for the alternative, central
approach as they would be fed with the products of the constrained setup.

Sampler virtualization selection tool concept; A half-rack control interface which is a
simple MIDI switch toggling between the real hardware and the virtual copies accessible
through MIDI interfaces of various PCs.

An idea about floppy banks; While SCSI was the solution way back when to get around
manually loading banks physically, it has fallen off the edge of relevance in the current
day - while somebody like myself will still see advantages to it and appreciate the
history and novelty of it, there exist updated mediums beyond SCSI to more efficiently
load sample banks on these legacy machines. Goteks are the defacto standard these days,
and while I am somewhat intrigued I can't see myself embracing them with any sense of
urgency. No, I am currently more than content with a mountain of floppy disks - but there
is a problem that I do wish to get crafty to surpass - seeing as I don't want to purchase
more than one example of any given machine beyond one that would grant me advantages
unattainable via software emulation (like a hardware sequencer for example), samplers
are largely unique to eachother in file format, meaning banks are only compatible with
the machine they were sampled on. A solution to this challenge of being restricted to
choosing one bank of many at a given time, pidgeonholing yourself into reaching same-y
pairings often would be to, when you feel a bank is useful beyond one instance, sample
the inital sampler from another unit, thus imperfectly but effectively cloning those
sounds for use in conjunction with other banks of the initial sampler's curation.
I currently possess three sampler units with unique file formats attached to each, so if
I were to convert everything into forms acceptable by each unit, I would need to triple
my already ~60 disk cumulative library - so for now I will limit cloning to banks I have
faith will be utilized.
	Now another which has ties to the future VST-integrated workflow - I'm not a
huge proponent of interrupting active tasks to squint and cursor-pick directories and
open projects - oftentimes this excersize squanders something. Something a bit more
workflow-friendly would be having one disk per bank which is essentially a bank mirror
that the computer will follow to the location of the files represented by the disk
and stored legitimately on the disks the hardware demands. Imagine if you will that
you are jamming with a sampler bank and you realize that you'd like to have two instances
of it, or use two or more local banks that ordinarily wouldn't be simultaneously
activatable - you conveniently possess two PC units with floppy drives that have
emulators of the sampler you're using. You place the PC-labelled representation of the
actively loaded bank in the drives of the two clone machines, and you have a script
present which automatically launches a Reaper instance containing a ready-to-go,
identical doppellganger of the hardware. You can now send sequencing/performance MIDI
data to both and work with two plus instances of a sample library.