Re: [Linuxsampler-devel] LinuxSampler GUI spec.

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

Hi Rui,
   Great 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.

   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.

   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.

   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.

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

Thanks,
Mark


On Thu, 2004-04-29 at 03:59, Rui Nuno Capela wrote:
> Hi all,
> 
> Here goes, at least under my point of view 8)
> 
> 
> Preliminar specification for the LinuxSampler GUI application
> -------------------------------------------------------------
> 
> According to current LSCP document draft (v.04), and the corresponding
> iblscp implementation, the following notes apply as proposed requirements
> for the primordial LinuxSampler GUI application.
> 
> 
> a)  Each sampler channel maps to one strip on the main GUI control panel,
>     whithin the main application window.
> 
> b)  Sampler channel strips may be stacked on either a vertical (like a
>     mixing desk) or horizontal layout (like a studio rack).
> 
> c)  Channel strips are added or removed at will.
> 
> d)  Each sampler channel strip shall have the following GUI controls:
> 
>  1. Engine        : string  <engine-name>   : option list.
> 
>  2. Instrument    : string  <filename>      : button; fileopen dialog.
> 
>  3. MIDI Type     : "alsa"                  : option list.
> 
>  4. MIDI Port     : string  <midi-port>     : edit box.
> 
>  5. MIDI Channel  : int     <midi-channel>  : option list.
> 
>  6. Audio Type    : "alsa" | "jack"         : option list.
> 
>  7. Audio Channel : int     <audio-channel> : edit spinbox.
> 
>  8. Volume        : float   <volume>        : knob/slider; edit spinbox.
> 
>  9. Voice Count   : int                     : display.
> 
> 10. Stream Usage  : int[]                   : display; chart.
> 
> 11. Reset         :                         : button.
> 
> 
> e)  The complete session state might be saved and loaded from the local
>     file system, as plain LSCP script documents.
> 
> f)  The application setup options dialog include the linuxsampler server
>     hostname and port specification with option to auto-start the server
> locally (localhost), where the corresponding startup command-line may be
> user editable.
> 
> g)  The main application window may follow the SDI model, with regular
>     menu, tool and status bars. The proposed initial menu hierarchy:
> 
>     File
> 
>         New             Start a new session state from scratch.
>         Open...         Load a session from an existing LSCP file.
>         Save            Save current state to a LSCP file.
>         Save As...      Save current state with an alternate name.
>         -               -
>         Quit            Quit application.
> 
>     Edit
> 
>         Add Channel     Add a new channel strip to current session.
>         Remove Channel  Remove selected channel strip from session.
>         -               -
>         Reset Channel   Reset currently selected sampler channel.
> 
>     View
> 
>         Show Menubar    Show/Hide the main window menubar.
>         Show Toolbar    Show/Hide the main window button toolbar.
>         Show Statusbar  Show/Hide the main window statusbar.
>         -               -
>         Show Messages   Show/Hide the messages log window (debug).
>         -               -
>         Options...      General options setup dialog.
> 
>     Help
> 
>         About...        Self-credits show off.
> 
> 
> Think this is enough, for the time being.
> 
> Yet again, another important question remains, which deals with the
> "official" application name. My proposals goes to, in strict biased
> descending order of preference:
> 
>     qsampler
>     qls
>     qlinuxsampler
>     lsgui
>     linuxsamplergui
> 
> Of course, those "q" prefixes comes from my reliance to Qt :)
> 
> So, make up your minds, ppl.
> 
> Cheers.