Re: [Linuxsampler-devel] LinuxSampler GUI spec.

[Rui N. C. <rn...@rn...>]

Hi Mark,

>
>    Great start.
>

Thanks, and it's just that, a start :)

>
>    From a user's perspective, let me suggest a 'Mute' button and a
> 'Solo' button on each sampler channel. Also, mostly for ease of setup,
> it would be very helpful to have an LED that shows MIDI activity on this
> specific sampler channel. Not sure if this is possibly your 'Stream
> usage' item. I think this activity light could share space with mute and
> just flash when there's activity, but be lit all the time when muted.
>

Please note that I've stuck with the available LSCP specification, and
there's no command (yet) to handle the mono/solo channel mode nor MIDI
activity.

However the mono/solo modes may be emulated on the client by juggling with
the volume setting. Is this workaround acceptable or consensual?

>
>    Gst 2.5 offers both tuning and panning sliders, and also a feature
> I've never used where you can change these sliders to have a connection
> to any MIDI controller value. (At this level my MIDI capabilities are
> pretty minimal.) This is true for the volume slider also.
>

Again, the client sits exclusively on top of the LSCP layer (liblscp). If
LSCP does not provide the intended functionality, the client is left in
the blind for that matter. Period. Remember that the linuxsampler server
and the GUI client may not reside on the same node/machine.

My assertion is that the client must behave and expose the very same
functionality whether it's on same local machine or on the other side of
the world, in regard to the LS server.

Therefore, any additional accessability feature (in client software terms,
not user ones :) must be defined and supported on a future LSCP
specification and implementation.

We'll get there, eventually, and we're just starting with the basics, and
there's plenty to do already.


>
>    I think that your Instrument will need to be more selective than just
> a file name since gig file contain many instruments, etc. We need to see
> the actual instrument chosen from within the gig file.
>

Of course. The idea is that once a file is selected for loading into a
channel, via a traditional file-open dialog, it's type and format are
checked and, in case of a gig file, an instrument-index selection dialog
is in order. I assume that libgig will come to the rescue.

>
>    One could argue the value, if they wanted to, for the ability to
> insert a plugin at this point. I'd probably reserve that for the mixer
> GUI.
>

Yep. That's yet another feature ..)

>
>    I'll wait for your suggestions on other GUI pages such as the mixer,
> loaded instruments as they will likely be quite good.
>

They'll come, as further development progresses... slowly. Please be
(very) patient :) Note that my GUI proposal is neither complete nor final,
whatsoever. And considering it, I know it doesn't make justice as the
professional-grade product comparable to linuxsampler's ambitions. Yet. As
said, it's just a start.

This is not an excuse for not willing to work on your suggestions. In
fact, it's just the opposite. It's just pragmatism running free ;)

Cheers.
-- 
rncbc aka Rui Nuno Capela
rn...@rn...