[Consortium] Re: [Swami-devel] Re: [Linuxsampler-devel] Re: linuxsampler and oneshotsampler

Josh Green jgreen at users.sourceforge.net
Fri Mar 18 18:07:06 EST 2005

On Fri, 2005-03-18 at 21:05 +0100, Bluefuture wrote:
> Il giorno ven, 18-03-2005 alle 09:35 -0800, Mark Knecht ha scritto:
> > There is no reason that these two orgranizations/projects couldn't
> > leverage off of each others work. Gig files are indeed forst and
> > foremost a collection of wave files, but gig files support many things
> > beyond just the wave files so making a good gig file is more than just
> > collecting the wave files together into a single gig file.
> > 
> > Note that to date there is no work going on to make a Gig file editor
> > under Linux that I know of. I still use the ones that come with the
> > different versions of GigaStudio.
> I think that swami already support editing of gig file. Yes swami could
> be improved but is a good starting point in sampling editing [1][2].
> It could be posted a tutorial on oneshotsampler about creating good
> Gigafile instead of simple wave file. 
> If linuxaudio consortuim could give the hardware infrastructure for
> hosting Gigafiles in oneshotsampler we could have an usable sampling
> free software/free sampler banks infrastructure in linux (like
> gigastudio and sampletank in windows), hoping that Swami will improve as
> SoundFont 2.0, DLS and GigaSampler frontend editor/manager. 
> What do u think about this solution?
> Cheers,
> Stefano
> [1]http://swami.sourceforge.net/
> [2]http://sourceforge.net/mailarchive/forum.php?thread_id=6272148&forum_id=8242

the current development cycle for the Swami 1.x branch has been almost 3
years in the making without a fully functional release.  I'm confident
in the architecture in regards to creating a multi instrument patch
format editing platform, but there is still a bit of work to do.  There
is very minimal support for GigaSampler files at this point.  I've
decided to make DLS the "native" format of Swami.  Rather than having to
create converters from every instrument type to every other supported
type, DLS would be used as the master format that is converted to/from.
When not converting formats though, files would still be edited natively
(at least this is the plan).

Current features of libInstPatch:
- object oriented instrument editing library (uses GObject)
- support for multiple formats (SF2, DLS and partial GigaSampler
- Python binding for scripting editing tasks
- CRAM (Compress hybRid Audio Media) - a format created to compress
binary/audio hybrid files such as patch files (DLS, SF2 and Gig
- audio format conversion
- extendable sample data storage methods

Areas that need attention in libInstPatch:
- Finalize units handling and conversion system
- Implement more object converters between instrument object types
- Finish object paste system
- Cleanup the Python binding
- Finish voice caching mechanism for soft synths.  Instrument objects
are rendered into voices compatible with a particular soft synth
(rendering occurs during program change for example), which can then be
accessed very quickly when note on received.

Current features of Swami:
- Object oriented user interface (drag and drop controls, split views,
- Model/view/controller parameter network for parameter controls and
MIDI event routing (change a parameter, changes all views)
- some nice GnomeCanvas based controls for sample loop editing (sample
loop crossing view), editing splits, and scalable virtual piano.
- Python shell (needs some work)

Areas needing attention:
- Interface manager needs to be even more object oriented (some cleanup)
- Preferences and XML config save/restore
- Undo state manager
- Finish FFT auto sample tuning plugin
- More object oriented device creation and config (MIDI drivers, soft
synths, etc)
- Paste GUI
- Some general love to pull the whole beast together

My development laptop recently broke, but once I get it back in order I
will return to these projects.  I would really like to have more
developers involved, since this project is turning out to be quite a bit
bigger than I anticipated, so please contact me or the swami-devel list
if you are interested.  There is a lot of potential for collaboration
between projects too and I think it would be good to discuss how this
can happen.  There is still quite a huge TODO list for
libInstPatch/Swami though, but its getting there :)  Cheers.
	Josh Green

More information about the Consortium mailing list