I've been hacking .lscps in a text editor, and something occurred to me
that would speed up the process considerably, imho.

We have a list of midi and audio ports for devices at the top of the doc.
We can name these, and they provide a good indication of what goes where.

Midi maps are also detailed in name, and again we can figure out what goes
where, in what order.


The Channel entries have none of the above, and we're purely reliant on
scrolling up and down to check device and map numbers associated with a
channel. When we load an instrument into a channel, or set one in the
.lscp for default, we can see the midi map, or loaded name for the
instrument, including the patch.


Would you consider doing the same with more verbose device assignments for
a channel?

Instead of:

ADD CHANNEL
SET CHANNEL MIDI_INPUT_DEVICE 42 0
SET CHANNEL MIDI_INPUT_PORT 42 17
SET CHANNEL MIDI_INPUT_CHANNEL 42 1
LOAD ENGINE SFZ 42
SET CHANNEL VOLUME 42 1.0
SET CHANNEL MIDI_INSTRUMENT_MAP 42 30
SET CHANNEL AUDIO_OUTPUT_DEVICE 42 0
SET CHANNEL AUDIO_OUTPUT_CHANNEL 42 0 19
SET CHANNEL AUDIO_OUTPUT_CHANNEL 42 1 20
LOAD INSTRUMENT NON_MODAL
'/usr/share/sounds/sonatina/Sonatina\x20Symphonic\x20Orchestra/Strings\x20-\x20Cello\x201st-violins.sfz'
0 42


something like this, where aliases created by the user for devices and
ports are reflected in the .lscp:

ADD CHANNEL
SET CHANNEL MIDI_INPUT_DEVICE 42 0 'alex-box-1-midi-1'
SET CHANNEL MIDI_INPUT_PORT 42 17 '1st-violins-midi'
SET CHANNEL MIDI_INPUT_CHANNEL 42 1
LOAD ENGINE SFZ 42
SET CHANNEL VOLUME 42 1.0
SET CHANNEL MIDI_INSTRUMENT_MAP 42 30 '1st-violins'
SET CHANNEL AUDIO_OUTPUT_DEVICE 42 0  'alex-audio-device-1'
SET CHANNEL AUDIO_OUTPUT_CHANNEL 42 0 19 '1st-violins-out-left'
SET CHANNEL AUDIO_OUTPUT_CHANNEL 42 1 20 '1st-violins-out-right'
LOAD INSTRUMENT NON_MODAL
'/usr/share/sounds/sonatina/Sonatina\x20Symphonic\x20Orchestra/Strings\x20-\x20Cello\x201st-violins.sfz'
0 42


This would help debug mischievous .lscps, and make the process of building
one from scratch a lot easier. I appreciate not all users are running
large sample libs in LS, and their .lscp files will probably be a lot
smaller than ours, however a more "user readable' administrative workflow
would be useful.



The same is true in Fantasia, for audio outputs. Where we can set an alias
for the output in the audio device dialog itself, we only see port numbers
in the channel set audio port dialog. Can this also reflect the alias
names we've set in the device, to make assigning audio ports more user
friendly?


Alex.



------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerry® mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry® DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1 
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel

Reply via email to