[integra-dev] integralive case study: "lichtweiss"

[Jamie Bullock]

On 16 Jul 2010, at 08:28, Peter Plessas wrote:

> Thanks Jamie for addressing the issues I proposed for discussion,
> 
> Jamie Bullock wrote:
> [...]
>> Yes, there is a QuadPanner module. It just needs adding to the database. [Added to request tracker]
> How could I follow progress and successful completion of this task?

If you like, I can set you as the person that added the request, then you will get an email when the task is complete. Let me know.

>>> How can one load sound files into the soundfile player module?
> Still wondering about this one...
> [...]
>> We have a proposed module list in the project dropbox. Probably this should go on the Wiki, so people can contribute suggestions. [Added to request tracker]
> Just found the list in the shared folder. Good info. I'd suggest moving
> the compressor/limiter up to high priority: If we want people without
> much tech knowledge to use IL without overloading their DACs, that is a
> good thing to include (setting the default values of this module to act
> like a brickwall -1dBFS limiter).
> 

Hm... or if this functionality is so essential, perhaps we should build a simple limiter into the *AudioOut modules? If the user can't construct module graphs without overloading their DACs, perhaps they don't know what a Limiter is or how to use it?

> Very excited to hear what you and your three collegues come up with. Let
> me ask another general question here: In contrast to the fancy modules
> that are in IL already (granulators, pvoc, etc) I wonder how all the
> program control (read: control messages) and timing is supposed to work.
> See here for example the requirements for one of the cues triggered at
> the end of the first movement by the musician within lichtweiss:
> 
> Fade out recording2
> Fade out playback1
> 
> Start recording3
> Start playback1 (second instance)
> Start playback2
> Fade in these three signals
> 
> wait for (fadetime) to pass
> 
> Stop recording2
> Stop playback1 (first instance)
> 

All of this can be achieved by using the forthcoming SimpleSampler module in combination with 'scenes' (and maybe envelopes). You can create scenes by click-dragging in the timeline just below the numbers. Each scene is bound to a key, which can be used to jump to that scene when in live view. Keys can be reassigned by dragging the scene names on the keyboard in live view.

There will be a 'quick start guide' explaining this stuff released this week as well as the SimpleSampler module. 

Jamie