Re: [Linuxsampler-devel] [ANNOUNCE] QSampler 0.0.1 released!

[Mark K. <mk...@co...>]

Christian Schoenebeck wrote:
> Es geschah am Dienstag, 8. Juni 2004 10:07 als Rui Nuno Capela schrieb:
> 
>>>SET AUDIO_OUTPUT_CHANNEL_PARAMETER <device-id> <audio-chan>
>>>VOLUME=<volume>
>>
>>I think what Mark would really like is if this could be a realtime
>>parameter. Will it be? :)
> 
> 
> Wait a second; LSCP is NOT meant for realtime operation. It's main purpose is 
> to setup the sampler session, although it also provides settings like volume, 
> etc. But realtime control will be part of the DMIDI Midi Input Device 
> implementation.
> 
> CU
> Christian
> 
Which is how it's done on GSt, correct? All control - volume, panning, 
etc., is over MIDI in my environment.

I didnt catch that distinction earlier.

However, this does raise some strangeness about the use of QS long term. 
Should my MIDI be going to LS directly, or should it be going to QS 
which is the app I actually run? In the QS model I really don't (and 
shouldn't) know anything about LS really. However, today I talk to the 
underlying LS instance in QJackCtl.

Sort of a strange model.

How would this work if QS was a Windows VSTi? The user would want to 
send MIDI to QS on the Windows box, and then QS would have to get it 
sent to LS on the Linux box somehow?

Or would QS reference the LS instance so that MIDI went directly to it? 
That would be better for latency, etc.

Sort of confusing...

- Mark