or better flooper2...
----- Original Message ----- 
From: "Oeyvind Brandtsegg" 
To: 
Sent: Friday, January 11, 2008 8:44 PM
Subject: [Csnd] Re: 'boulder' synthesis


> Maybe flooper would be a good opcode "base" for this kind of thing ?
> Oeyvind
>
> 2008/1/11, aaron@akjmusic.com :
>> Hi all,
>>
>> My friend and composer Christopher Bailey has used a technique he and a
>> friend call 'boulder' synthesis: instead of looping a sampleduring a
>> sustain portion of an envelope, where one can here the artificiality of
>> looping points, etc. implement an 'engine' which does everything else a
>> sample engine does, except that instead of looping to sustain a note, one
>> uses randomized, cross-faded segments of the original sample. This adds a
>> more life-like organic realism to a sustained tone when using samples. 
>> The
>> 'boulder' idea is that this is sort of a larger scale analog to granular
>> synthesis. i have been most impressed with the results he has illustrated
>> to me. (In fact, I'm amazed that this idea isn't already more widespread,
>> even in commercial hardware)
>>
>> My question--I have an broadly-outlined idea of how to implement this in
>> CSound (Chris does it in CMIX) with the diskin opcode, some F-tables to
>> match MIDI notes with samples, etc., but might it not be more beneficial
>> in the long run to implement this as an opcode, especially if it could be
>> built on modifying some existing codebase? Perhaps one could import
>> soundfonts, and do everything that the fluidsynth code does, except 
>> change
>> the looping procedure for sustain parts of the envelope to the above
>> described procedure instead.
>>
>> How easy would this be? I can imagine it would really be a neat addition
>> to the CSound arsenal, especially for sample-loving folk. The opcode 
>> might
>> be called 'fluidboulder', and maybe for non-soundfont based sample work,
>> instead of 'loscil' we could have 'boulderoscil' :)
>>
>> Best,
>> AKJ.
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
>> csound"
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound" 

Yes i raised this about 3 days after joining the list in Dec 2006

http://www.nabble.com/Sample-Start--Skiptime--Offset---Sample-based-synthesis-wavetables-to7711453.html#a7729811

My example appears to have been truncated by the nabble archive however, & i
can't find it on my harddrive ; ( .... it may well not have worked very well
- i'd been using it less than a week after all!

I'm pretty sure i just defined (generated) random start, p3, & end points in
the sample "target" zone as score, & then executed playback, with a suitable
"overlap" of notes & X fade envelope shape (that way if you want to do
something more "expressive" with a deferred loop end point you can (like if
your sample has a steady state decay. it was making "natural" sounding
continuums out of steady state decay sounds that lead me to explore this in
the first place....))



Victor.Lazzarini wrote:
> 
> or better flooper2...
> ----- Original Message ----- 
> From: "Oeyvind Brandtsegg" 
> To: 
> Sent: Friday, January 11, 2008 8:44 PM
> Subject: [Csnd] Re: 'boulder' synthesis
> 
> 
>> Maybe flooper would be a good opcode "base" for this kind of thing ?
>> Oeyvind
>>
>> 2008/1/11, aaron@akjmusic.com :
>>> Hi all,
>>>
>>> My friend and composer Christopher Bailey has used a technique he and a
>>> friend call 'boulder' synthesis: instead of looping a sampleduring a
>>> sustain portion of an envelope, where one can here the artificiality of
>>> looping points, etc. implement an 'engine' which does everything else a
>>> sample engine does, except that instead of looping to sustain a note,
>>> one
>>> uses randomized, cross-faded segments of the original sample. This adds
>>> a
>>> more life-like organic realism to a sustained tone when using samples. 
>>> The
>>> 'boulder' idea is that this is sort of a larger scale analog to granular
>>> synthesis. i have been most impressed with the results he has
>>> illustrated
>>> to me. (In fact, I'm amazed that this idea isn't already more
>>> widespread,
>>> even in commercial hardware)
>>>
>>> My question--I have an broadly-outlined idea of how to implement this in
>>> CSound (Chris does it in CMIX) with the diskin opcode, some F-tables to
>>> match MIDI notes with samples, etc., but might it not be more beneficial
>>> in the long run to implement this as an opcode, especially if it could
>>> be
>>> built on modifying some existing codebase? Perhaps one could import
>>> soundfonts, and do everything that the fluidsynth code does, except 
>>> change
>>> the looping procedure for sustain parts of the envelope to the above
>>> described procedure instead.
>>>
>>> How easy would this be? I can imagine it would really be a neat addition
>>> to the CSound arsenal, especially for sample-loving folk. The opcode 
>>> might
>>> be called 'fluidboulder', and maybe for non-soundfont based sample work,
>>> instead of 'loscil' we could have 'boulderoscil' :)
>>>
>>> Best,
>>> AKJ.
>>>
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
>>> csound"
>>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
>> csound" 
> 
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
> 
> 

-- 
View this message in context: http://www.nabble.com/%27boulder%27-synthesis-tp14764322p14767445.html
Sent from the Csound - General mailing list archive at Nabble.com.

I think it was soon after i discovered the phase vocoder, & the idea became a
lesser priority ....



Tim Mortimer wrote:
> 
> Yes i raised this about 3 days after joining the list in Dec 2006
> 
> http://www.nabble.com/Sample-Start--Skiptime--Offset---Sample-based-synthesis-wavetables-to7711453.html#a7729811
> 
> My example appears to have been truncated by the nabble archive however, &
> i can't find it on my harddrive ; ( .... it may well not have worked very
> well - i'd been using it less than a week after all!
> 
> I'm pretty sure i just defined (generated) random start, p3, & end points
> in the sample "target" zone as score, & then executed playback, with a
> suitable "overlap" of notes & X fade envelope shape (that way if you want
> to do something more "expressive" with a deferred loop end point you can
> (like if your sample has a steady state decay. it was making "natural"
> sounding continuums out of steady state decay sounds that lead me to
> explore this in the first place....))
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/%27boulder%27-synthesis-tp14764322p14767603.html
Sent from the Csound - General mailing list archive at Nabble.com.