[Linuxsampler-devel] RE: Hi - Very quiet list - my first post

[Josh G. <jg...@us...>]

On Mon, 2003-01-20 at 09:56, Mark Knecht wrote:
> Josh,
>    Hi. Removed iiwusynth-devel as I am not a member of that list.
> 
>    I like what I see in Swami so far. It reminds me of parts of the
> GigaStudio editing interface where you build your own .gig files. It
> doesn't have all of the velocity mapping stuff, but most of it seems to
> be there.
> 

What kind of velocity functionality are you looking for?

>    The thing I see in Swami right now, and forgive me if I'm wrong about
> this after just a short read through, is that it appears oriented to
> dealing with samples and libraries, as opposed to being a MIDI-based
> sample player. (I.e. - and instrument) It does look like it makes using
> fluid-synth potentially easier, so I should pay attention to it for that
> reason alone I suppose.
> 

Currently the GUI is somewhat out-dated compared to the underlying API
architecture. Its currently structured primarily as an editor. But I
have many things on my list to add to make it a better front-end for
FluidSynth (wavetable MIDI channel instrument selections, GUI MIDI
controllers, session modulators, etc). As things are now you can start
up FluidSynth within Swami using the alsa_seq MIDI driver and connect a
sequencer to it (you can do this with FluidSynth stand alone as well).
Also I'm going to be making the layout very dynamic and flexible. The
GUI is already separated into self contained objects. I just need to
create a GUI manager that allows creating new GUI objects, designating
their layout (docked with other elements or in its own dialog, etc) and
setting their view parameters. So you could for instance create multiple
patch tree objects, a couple envelope editors, and define their layout
and save and restore it. This will allow for different setups depending
on if someone is editing, using it as a wavetable bank manager,
sequencing with it, etc.

>    If you want to go look at Battery's interface, it's pretty clean and
> to the point. 
> 
> http://www.nativeinstruments.de/index.php?id=battery_us
> 
>    It's really oriented towards playing short samples, but it can be
> used for longer ones also. 
> 

Yeah, the interface looks nice. I already have a crude envelope editor
in place. I haven't worked on it in a while, but I have been thinking
about making it really flexible and allowing it to be overlayed on the
sample waveform, allowing multiple parameters from different instruments
to be edited simultainiously, etc.

>    BTW - I am NOT a Battery owner. I have used it very little. I was
> just pointing out that as a sample playing app, it is a model that
> people seem to get their hands around quickly. I also think it's ideal
> for a first test vehicle for this sampler engine.
> 

As far as Linuxsampler and Swami are concerned.. Linuxsampler may end up
being a wavetable engine within Swami, as well as my libInstPatch
library being used for accessing patch formats. This all remains to be
seen though.

>    Maybe I'm taking some of the posts here in the wrong light, but yours
> and Dave's both seem aimed at getting me to use something that currently
> exists, where my idea was to find good uses for this new Linux-Sampler
> engine. If I'm off base and people here don't think this is a good use,
> then that's OK too. I was just speaking up since this list has been
> 'very quiet', as the title in my thread indicates!
> 

Sure.. You got things going again :)

> Cheers,
> Mark
> 

Lates..
	Josh Green