[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] hauptwerk

From: Josh Green
Subject: Re: [fluid-dev] hauptwerk
Date: Mon, 30 Jul 2007 12:07:26 -0700

On Mon, 2007-07-30 at 13:42 -0500, Bert Douglas wrote:
> Thanks for answer.
> Hauptwerk is samples only.  No effects.  It is intended for church organ
> replacement.  The focus is on long high quality samples and ability to
> mix many samples together without distortion (high order polyphony).
> Hauptwerk stores all samples in ram.
> Each sample is separate wav file, named according to notes.
> There is one repeat/loop mark in wav file.
> Do you think this would be a good fit for FluidSynth ?
> Or should I look for another platform ?
> Hauptwerk is going more and more closed and commercial.  And it is
> windows only.   I am looking for a free substitute for Hauptwerk.
> Thanks,
> Bert Douglas

So there is no meta data which describes where the samples are placed,
what organ stops they are related to, etc?  libInstPatch has Python
support, so a proof of concept converter script could likely be easily
written to convert Hauptwerk instruments to SoundFont files.  If the
samples of Hauptwerk are already all loaded into RAM, then that would be
the same when using FluidSynth.  You'll still have that 4GB limit
though, and you better hope you have that much RAM too! (or whatever
size your instruments are).  It seems like FluidSynth could probably
work OK in this situation.  If you have any more info on Hauptwerk
instruments (or perhaps a small example), I might just code up a
converter script for you.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]