[linux-audio-user] Anyone interested in helping with melotron

[John Check]

On Friday 11 March 2005 08:45 am, james at dis-dot-dat.net wrote:
> On Fri, 11 Mar, 2005 at 12:44PM +0000, tim hall spake thus:
> > Last Thursday 10 March 2005 21:08, John Check was like:
> > > As far as moving patches from one font to another, hilite the source
> > > patch and right click over the destination for a context menu with
> > > "paste". FWIW, Multiple selections work. What other questions have ye?
> >
> > Thanks John, I'll try it again then.
> >
> > How do I get smurf to make any sound? I have ALSA/MIDI working perfectly
> > and yet I don't seem to be able to hook my external keyboard up so it can
> > trigger the soundfont I want to edit. Smurf is pre-JACK isn't it?
> >
> > > > doesn't help much and I never got round to compiling Swami, it's not
> > > > included in AGNULA/DeMuDi, so I'm wondering if it's less-than-free or
> > > > what the deal is with it. It strikes me as being dumb to use the .sf2
> > > > format if we don't have an accessible editor. Either we help Josh
> > > > Green make Swami accessible and distributable or we should seriously
> > > > consider some other options.
> > >
> > > Well.. the format exists already and is widespread, so while designing
> > > a replacement or reimplementation  has it's merits, it'd be throwing
> > > out the baby with the bath water.
> >
> > I wasn't really suggesting throwing out the baby. If it's an open format,
> > no problem. If there are no license problems, I would have thought that
> > building a command-line interface for SWAMI would really be the way to
> > go.
>
> That does solve some "problems" - it becomes commandline and
> more accessible.  It doesn't really solve all of them, though: you'd
> have to have a program that did everything in a session.
>

Too, there are a carload of parameters per sample * instruments * presets.


> Ideally, we want a way to be able to create soundfonts as they are
> needed with commandline tools.  You get the accessibility, plus you
> can write the patch descriptions in any editor, or from a script,
> whatever.  You then just compile the description and waves into a
> soundfont.  This way is much more flexible.
>

First thing that comes to mind from an efficiency POV is setting loop points 
in the individual samples (snippet)  that make up the instruments. I don't 
know what kind of algorithm it would take.. finding zero crossings is easy 
enough, but getting a smooth loop can be a challenge WRT timbre. 


> > cheers,
> >
> > tim hall
> > http://glastonburymusic.org.uk