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

[Vladimir S. <ha...@so...>]

Rui,

Nice!!! I was able to get it up and running in no time.
I've noticed one little issue . . . when i load the instrument for the 
first time it thinks there is a timeout and will not show the instrument 
name on that channel.
If i then create another channel with the same instrument (ls loads it 
instantly since it is already loaded) then the GUI works correctly.
I think timeout may be a bit too low. It takes a while to load some 
instruments on my old pc :)

Regards,
Vladimir.

Rui Nuno Capela wrote:

>Hi,
>
>Qsampler is a work in progress for a Qt GUI interface for LinuxSampler.
>It's been under development, and still is, as there's still plenty to do.
>
>However I would like to announce a very primordial alpha release:
>
>Qsampler 0.0.1 is now made available. You can check it out from the
>following places:
>
>    http://qsampler.sourceforge.net
>    http://www.rncbc.org/ls
>
>From the later site you can even choose to download and install from RPM,
>which are available for some major distros (Mandrake 10.0, SUSE 9.1 and
>Fedora core 1). Remember to install the liblscp package as it's required
>for qsampler.
>
>Of course you need linuxsampler installed in the first place, but that's
>quite obvious ;)
>
>Please note that qsampler is barely functional, and in it's current state
>only relies on the current linuxsampler server LSCP implementation and
>features.
>
>In fact, it's missing some important LSCP commands (e.g. GET CHANNEL INFO)
>for the frontend being in pretty sync status with the server backend. So
>don't be alarmed it you don't get it straight first time you try. Please,
>do explore and expose just every simple feature or bug it has to give or
>take.
>
>For example, even though the volume slider works as expected, while
>sending the proper SET CHANNEL VOLUME commands to the backend, you will
>not hear any evidence of it. After all, is all still alpha software.
>
>This release is mainly for all those who couldn't cope with Sourceforge's
>anonymous CVS access. So rejoice :)
>
>Now, what can you do with qsampler? You can already start the server
>automatically, if there's one of course, then create one or more sampler
>channels, load the only available sampler engine ;) and any other gig
>instrument file, with corresponding MIDI/audio drivers (ALSA or JACK). You
>can follow the stream buffer fill and voice usage on screen while you play
> or feed the MIDI input driver. You may also save sampler sessions as LSCP
>script files and reload them back later. All initially proposed features
>are in place.
>
>Last but not least, you still have to connect the proper ALSA and/or JACK
>device ports by yourself, e.g. using qjackctl ;) if you ever want to play
>and listen anything at all.
>
>Hope you enjoy as much as I,
>
>Cheers.
>  
>