Csound Csound-dev Csound-tekno Search About

[Cs-dev] Flooper2 - feature request.

Date2009-10-24 18:32
FromJean Piché
Subject[Cs-dev] Flooper2 - feature request.
AttachmentsNone  None  


Hi Victor,

As you know, flooper2 is at the core of  the sampler in Cecilia4.

When the  kloopstart & kloopend points are changed for LARGER values, the sound will continue being read at the ongoing rate until it gets to the new kloopend point and will start looping with the new values whereas when a SMALLER value is given for kloopstart, the pointer goes to the new startpoint immediately. In some ways, this is expected behaviour but it leaves interesting applications behind.

If one could make the pointer jump to the kloopstart point as soon as a new value is received, granulation/stretching become possible along with a host of other "mangling" techniques.

We have tried to reset the loop points by using a "re-init" pass without success.

Could this be easily implemented?

All the best!

j


--
_____________________________
http://jeanpiche.com

Date2009-10-24 18:35
FromPeiman Khosravi
SubjectRe: [Cs-dev] Flooper2 - feature request.
AttachmentsNone  None  
Cecilia 4? When was that released?!!!! I'm dying to know!!!

Thanks,

Peiman

On 24 Oct 2009, at 18:32, Jean Piché wrote:



Hi Victor,

As you know, flooper2 is at the core of  the sampler in Cecilia4.

When the  kloopstart & kloopend points are changed for LARGER values, the sound will continue being read at the ongoing rate until it gets to the new kloopend point and will start looping with the new values whereas when a SMALLER value is given for kloopstart, the pointer goes to the new startpoint immediately. In some ways, this is expected behaviour but it leaves interesting applications behind.

If one could make the pointer jump to the kloopstart point as soon as a new value is received, granulation/stretching become possible along with a host of other "mangling" techniques.

We have tried to reset the loop points by using a "re-init" pass without success.

Could this be easily implemented?

All the best!

j


--
_____________________________
http://jeanpiche.com
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


Date2009-10-24 18:58
FromJean Piché
SubjectRe: [Cs-dev] Flooper2 - feature request.
AttachmentsNone  None  

Patience.....


On Sat, Oct 24, 2009 at 1:35 PM, Peiman Khosravi <peimankhosravi@gmail.com> wrote:
Cecilia 4? When was that released?!!!! I'm dying to know!!!

Thanks,

Peiman

On 24 Oct 2009, at 18:32, Jean Piché wrote:



Hi Victor,

As you know, flooper2 is at the core of  the sampler in Cecilia4.

When the  kloopstart & kloopend points are changed for LARGER values, the sound will continue being read at the ongoing rate until it gets to the new kloopend point and will start looping with the new values whereas when a SMALLER value is given for kloopstart, the pointer goes to the new startpoint immediately. In some ways, this is expected behaviour but it leaves interesting applications behind.

If one could make the pointer jump to the kloopstart point as soon as a new value is received, granulation/stretching become possible along with a host of other "mangling" techniques.

We have tried to reset the loop points by using a "re-init" pass without success.

Could this be easily implemented?

All the best!

j


--
_____________________________
http://jeanpiche.com
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel




--
_____________________________
http://jeanpiche.com

Date2009-10-24 19:08
FromVictor Lazzarini
SubjectRe: [Cs-dev] Flooper2 - feature request.
AttachmentsNone  None  
 I should be able to take care of this.

So, in summary, whenever the length of the loop changes, the pointer should
jump to the new starting point? Surely that might cause a click?

Victor

Victor
On 24 Oct 2009, at 18:32, Jean Piché wrote:



Hi Victor,

As you know, flooper2 is at the core of  the sampler in Cecilia4.

When the  kloopstart & kloopend points are changed for LARGER values, the sound will continue being read at the ongoing rate until it gets to the new kloopend point and will start looping with the new values whereas when a SMALLER value is given for kloopstart, the pointer goes to the new startpoint immediately. In some ways, this is expected behaviour but it leaves interesting applications behind.

If one could make the pointer jump to the kloopstart point as soon as a new value is received, granulation/stretching become possible along with a host of other "mangling" techniques.

We have tried to reset the loop points by using a "re-init" pass without success.

Could this be easily implemented?

All the best!

j


--
_____________________________
http://jeanpiche.com
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


Date2009-10-24 19:18
FromJean Piché
SubjectRe: [Cs-dev] Flooper2 - feature request.
AttachmentsNone  None  

Yes. To deal with the click, when  kstartloop resets one could apply the kcrossfade value immedaitely following the jump??

j



On Sat, Oct 24, 2009 at 2:08 PM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
 I should be able to take care of this.

So, in summary, whenever the length of the loop changes, the pointer should
jump to the new starting point? Surely that might cause a click?

Victor

Victor
On 24 Oct 2009, at 18:32, Jean Piché wrote:



Hi Victor,

As you know, flooper2 is at the core of  the sampler in Cecilia4.

When the  kloopstart & kloopend points are changed for LARGER values, the sound will continue being read at the ongoing rate until it gets to the new kloopend point and will start looping with the new values whereas when a SMALLER value is given for kloopstart, the pointer goes to the new startpoint immediately. In some ways, this is expected behaviour but it leaves interesting applications behind.

If one could make the pointer jump to the kloopstart point as soon as a new value is received, granulation/stretching become possible along with a host of other "mangling" techniques.

We have tried to reset the loop points by using a "re-init" pass without success.

Could this be easily implemented?

All the best!

j


--
_____________________________
http://jeanpiche.com
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel




--
_____________________________
http://jeanpiche.com

Date2009-10-24 19:18
FromVictor Lazzarini
SubjectRe: [Cs-dev] Flooper2 - feature request.
AttachmentsNone  None  
To be backward compatible, this will probably be implemented with a new
optional parameter (0 or 1) disabling/enabling the new feature. I will wait 
some clarification on what it's supposed to be and then I can implement it.

I'm very happy that flooper2 is going to be used in Cecilia 4.

Victor


On 24 Oct 2009, at 19:08, Victor Lazzarini wrote:

 I should be able to take care of this.

So, in summary, whenever the length of the loop changes, the pointer should
jump to the new starting point? Surely that might cause a click?

Victor

Victor
On 24 Oct 2009, at 18:32, Jean Piché wrote:



Hi Victor,

As you know, flooper2 is at the core of  the sampler in Cecilia4.

When the  kloopstart & kloopend points are changed for LARGER values, the sound will continue being read at the ongoing rate until it gets to the new kloopend point and will start looping with the new values whereas when a SMALLER value is given for kloopstart, the pointer goes to the new startpoint immediately. In some ways, this is expected behaviour but it leaves interesting applications behind.

If one could make the pointer jump to the kloopstart point as soon as a new value is received, granulation/stretching become possible along with a host of other "mangling" techniques.

We have tried to reset the loop points by using a "re-init" pass without success.

Could this be easily implemented?

All the best!

j


--
_____________________________
http://jeanpiche.com
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


Date2009-10-24 19:22
FromVictor Lazzarini
SubjectRe: [Cs-dev] Flooper2 - feature request.
AttachmentsNone  None  
yes, the sound should be made to crossfade. One small complication is that
we would also like to fade out the portion immediately after the jump point. 

This can be done possibly by setting internally the kloopend point to the jump
point and then after the crossfade, revert it to what  it was.

I'll let you know when I have something working and post you the plugin for testing.

Victor

On 24 Oct 2009, at 19:18, Jean Piché wrote:


Yes. To deal with the click, when  kstartloop resets one could apply the kcrossfade value immedaitely following the jump??

j



On Sat, Oct 24, 2009 at 2:08 PM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
 I should be able to take care of this.

So, in summary, whenever the length of the loop changes, the pointer should
jump to the new starting point? Surely that might cause a click?

Victor

Victor
On 24 Oct 2009, at 18:32, Jean Piché wrote:



Hi Victor,

As you know, flooper2 is at the core of  the sampler in Cecilia4.

When the  kloopstart & kloopend points are changed for LARGER values, the sound will continue being read at the ongoing rate until it gets to the new kloopend point and will start looping with the new values whereas when a SMALLER value is given for kloopstart, the pointer goes to the new startpoint immediately. In some ways, this is expected behaviour but it leaves interesting applications behind.

If one could make the pointer jump to the kloopstart point as soon as a new value is received, granulation/stretching become possible along with a host of other "mangling" techniques.

We have tried to reset the loop points by using a "re-init" pass without success.

Could this be easily implemented?

All the best!

j


--
_____________________________
http://jeanpiche.com
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel




--
_____________________________
http://jeanpiche.com
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


Date2009-10-24 20:23
FromIain Duncan
SubjectRe: [Cs-dev] Flooper2 - feature request.
On Sat, 2009-10-24 at 19:08 +0100, Victor Lazzarini wrote:
>  I should be able to take care of this.
> 
> 
> So, in summary, whenever the length of the loop changes, the pointer
> should
> jump to the new starting point? Surely that might cause a click?

Wait, could you control that behaviour with a flag? I'm using it too
( great opcode! ) but can think of times when I would *not* want that
behaviour. 

Iain
> 
> 
> Victor
> 
> 
> Victor
> On 24 Oct 2009, at 18:32, Jean Piché wrote:
> 
> > 
> > 
> > Hi Victor,
> > 
> > As you know, flooper2 is at the core of  the sampler in Cecilia4. 
> > 
> > When the  kloopstart & kloopend points are changed for LARGER
> > values, the sound will continue being read at the ongoing rate until
> > it gets to the new kloopend point and will start looping with the
> > new values whereas when a SMALLER value is given for kloopstart, the
> > pointer goes to the new startpoint immediately. In some ways, this
> > is expected behaviour but it leaves interesting applications behind.
> > 
> > If one could make the pointer jump to the kloopstart point as soon
> > as a new value is received, granulation/stretching become possible
> > along with a host of other "mangling" techniques. 
> > 
> > We have tried to reset the loop points by using a "re-init" pass
> > without success.
> > 
> > Could this be easily implemented?
> > 
> > All the best!
> > 
> > j
> > 
> > 
> > -- 
> > _____________________________
> > http://jeanpiche.com
> > ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart
> > your
> > developing skills, take BlackBerry mobile applications to market and
> > stay 
> > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > now!
> > http://p.sf.net/sfu/devconference_______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https

Date2009-10-24 20:23
FromIain Duncan
SubjectRe: [Cs-dev] Flooper2 - feature request.
On Sat, 2009-10-24 at 19:18 +0100, Victor Lazzarini wrote:
> To be backward compatible, this will probably be implemented with a
> new
> optional parameter (0 or 1) disabling/enabling the new feature. I will
> wait 
> some clarification on what it's supposed to be and then I can
> implement it.

oops. should have read the rest of the thread, you're way ahead of me!

Iain
> 
> 
> I'm very happy that flooper2 is going to be used in Cecilia 4.
> 
> 
> Victor
> 
> 
> 
> On 24 Oct 2009, at 19:08, Victor Lazzarini wrote:
> 
> >  I should be able to take care of this.
> > 
> > 
> > So, in summary, whenever the length of the loop changes, the pointer
> > should
> > jump to the new starting point? Surely that might cause a click?
> > 
> > 
> > Victor
> > 
> > 
> > Victor
> > On 24 Oct 2009, at 18:32, Jean Piché wrote:
> > 
> > > 
> > > 
> > > Hi Victor,
> > > 
> > > As you know, flooper2 is at the core of  the sampler in Cecilia4. 
> > > 
> > > When the  kloopstart & kloopend points are changed for LARGER
> > > values, the sound will continue being read at the ongoing rate
> > > until it gets to the new kloopend point and will start looping
> > > with the new values whereas when a SMALLER value is given for
> > > kloopstart, the pointer goes to the new startpoint immediately. In
> > > some ways, this is expected behaviour but it leaves interesting
> > > applications behind.
> > > 
> > > If one could make the pointer jump to the kloopstart point as soon
> > > as a new value is received, granulation/stretching become possible
> > > along with a host of other "mangling" techniques. 
> > > 
> > > We have tried to reset the loop points by using a "re-init" pass
> > > without success.
> > > 
> > > Could this be easily implemented?
> > > 
> > > All the best!
> > > 
> > > j
> > > 
> > > 
> > > -- 
> > > _____________________________
> > > http://jeanpiche.com
> > > ------------------------------------------------------------------------------
> > > Come build with us! The BlackBerry(R) Developer Conference in SF,
> > > CA
> > > is the only developer event you need to attend this year.
> > > Jumpstart your
> > > developing skills, take BlackBerry mobile applications to market
> > > and stay 
> > > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > > now!
> > > http://p.sf.net/sfu/devconference_______________________________________________
> > > Csound-devel mailing list
> > > Csound-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
> > 
> > 
> > ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart
> > your
> > developing skills, take BlackBerry mobile applications to market and
> > stay 
> > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > now!
> > http://p.sf.net/sfu/devconference_______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/

Date2009-10-24 21:57
FromOlivier Bélanger
SubjectRe: [Cs-dev] Flooper2 - feature request.
AttachmentsNone  None  
Sorry Jean, but I think you didn't explained the problem correctly...

"
If one could make the pointer jump to the kloopstart point as soon as a new value is received
"

This is not what we expected, especially for granulation/stretching processes. The pointer start and end positions must change only after the current loop is completed but actually, under particular context, it seems to take the *new* kloopend as the end point of the current loop. Internally, the opcode must wait after the loop complete (reach the initial end point) before resetting his values.

I will try to isolate this "context" and post a simple .csd to illustrate it.

Olivier


2009/10/24 Iain Duncan <iainduncan@telus.net>
On Sat, 2009-10-24 at 19:18 +0100, Victor Lazzarini wrote:
> To be backward compatible, this will probably be implemented with a
> new
> optional parameter (0 or 1) disabling/enabling the new feature. I will
> wait
> some clarification on what it's supposed to be and then I can
> implement it.

oops. should have read the rest of the thread, you're way ahead of me!

Iain
>
>
> I'm very happy that flooper2 is going to be used in Cecilia 4.
>
>
> Victor
>
>
>
> On 24 Oct 2009, at 19:08, Victor Lazzarini wrote:
>
> >  I should be able to take care of this.
> >
> >
> > So, in summary, whenever the length of the loop changes, the pointer
> > should
> > jump to the new starting point? Surely that might cause a click?
> >
> >
> > Victor
> >
> >
> > Victor
> > On 24 Oct 2009, at 18:32, Jean Piché wrote:
> >
> > >
> > >
> > > Hi Victor,
> > >
> > > As you know, flooper2 is at the core of  the sampler in Cecilia4.
> > >
> > > When the  kloopstart & kloopend points are changed for LARGER
> > > values, the sound will continue being read at the ongoing rate
> > > until it gets to the new kloopend point and will start looping
> > > with the new values whereas when a SMALLER value is given for
> > > kloopstart, the pointer goes to the new startpoint immediately. In
> > > some ways, this is expected behaviour but it leaves interesting
> > > applications behind.
> > >
> > > If one could make the pointer jump to the kloopstart point as soon
> > > as a new value is received, granulation/stretching become possible
> > > along with a host of other "mangling" techniques.
> > >
> > > We have tried to reset the loop points by using a "re-init" pass
> > > without success.
> > >
> > > Could this be easily implemented?
> > >
> > > All the best!
> > >
> > > j
> > >
> > >
> > > --
> > > _____________________________
> > > http://jeanpiche.com
> > > ------------------------------------------------------------------------------
> > > Come build with us! The BlackBerry(R) Developer Conference in SF,
> > > CA
> > > is the only developer event you need to attend this year.
> > > Jumpstart your
> > > developing skills, take BlackBerry mobile applications to market
> > > and stay
> > > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > > now!
> > > http://p.sf.net/sfu/devconference_______________________________________________
> > > Csound-devel mailing list
> > > Csound-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
> >
> > ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart
> > your
> > developing skills, take BlackBerry mobile applications to market and
> > stay
> > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > now!
> > http://p.sf.net/sfu/devconference_______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


Date2009-10-24 23:04
FromOlivier Bélanger
SubjectRe: [Cs-dev] Flooper2 - feature request.
Attachmentsex_flooper2.csd  None  None  
Here is a csd file to illustrate the problem:

In the first case, istart and kstart (uncommented) are forward steps on seconds, 1 second on each step. Note that on loop changes, the duration of the loop is not .1 second.

In the second case, istart and kstart (commented) are backward steps on seconds, 1 second on each step. This one works, the loop duration is always .1 second.

Note that is for forward loop mode. If the loop mode is backward, first case works and second case doesn't. For back-and-forth, both doesn't work...

Olivier


<CsoundSynthesizer>
<CsOptions>
-odac     -d
</CsOptions>
<CsInstruments>

sr = 44100
kr = 4410
nchnls = 1

; load a mono sound (~ 6 seconds)
gi1 ftgen 1, 0, 0, -1, "/Users/olipet/Desktop/sons/baseballmajeur_m.aif", 0, 0, 0

    instr 1

; fixed loop duration (to generate rhythmic sequence)    
iloopdur init .1

; start at 0 for 1 second, then 1 for 1 second, then 3 ...
; doesn't work
istart init 0                                               ; <- comment
kstart linseg 0, 1, 0, 0, 1, 1, 1, 0, 2, 1, 2, 0, 3, 1, 3   ; <-

; inversed
; start at 5 for 1 second, then 4 for 1 second, then 3 ...
; works
;istart init 5                                              ; <- uncomment
;kstart linseg 5, 1, 5, 0, 4, 1, 4, 0, 3, 1, 3, 0, 2, 1, 2  ; <-

kend = kstart + iloopdur
   
asig flooper2 1, 1, kstart, kend, .005, 1, istart

    out asig
    endin

</CsInstruments>
<CsScore>
i1  0  5
e
</CsScore>
</CsoundSynthesizer>


Le 24 octobre 2009 16:57, Olivier Bélanger <olivier.belanger@umontreal.ca> a écrit :
Sorry Jean, but I think you didn't explained the problem correctly...


"
If one could make the pointer jump to the kloopstart point as soon as a new value is received
"

This is not what we expected, especially for granulation/stretching processes. The pointer start and end positions must change only after the current loop is completed but actually, under particular context, it seems to take the *new* kloopend as the end point of the current loop. Internally, the opcode must wait after the loop complete (reach the initial end point) before resetting his values.

I will try to isolate this "context" and post a simple .csd to illustrate it.

Olivier


2009/10/24 Iain Duncan <iainduncan@telus.net>

On Sat, 2009-10-24 at 19:18 +0100, Victor Lazzarini wrote:
> To be backward compatible, this will probably be implemented with a
> new
> optional parameter (0 or 1) disabling/enabling the new feature. I will
> wait
> some clarification on what it's supposed to be and then I can
> implement it.

oops. should have read the rest of the thread, you're way ahead of me!

Iain
>
>
> I'm very happy that flooper2 is going to be used in Cecilia 4.
>
>
> Victor
>
>
>
> On 24 Oct 2009, at 19:08, Victor Lazzarini wrote:
>
> >  I should be able to take care of this.
> >
> >
> > So, in summary, whenever the length of the loop changes, the pointer
> > should
> > jump to the new starting point? Surely that might cause a click?
> >
> >
> > Victor
> >
> >
> > Victor
> > On 24 Oct 2009, at 18:32, Jean Piché wrote:
> >
> > >
> > >
> > > Hi Victor,
> > >
> > > As you know, flooper2 is at the core of  the sampler in Cecilia4.
> > >
> > > When the  kloopstart & kloopend points are changed for LARGER
> > > values, the sound will continue being read at the ongoing rate
> > > until it gets to the new kloopend point and will start looping
> > > with the new values whereas when a SMALLER value is given for
> > > kloopstart, the pointer goes to the new startpoint immediately. In
> > > some ways, this is expected behaviour but it leaves interesting
> > > applications behind.
> > >
> > > If one could make the pointer jump to the kloopstart point as soon
> > > as a new value is received, granulation/stretching become possible
> > > along with a host of other "mangling" techniques.
> > >
> > > We have tried to reset the loop points by using a "re-init" pass
> > > without success.
> > >
> > > Could this be easily implemented?
> > >
> > > All the best!
> > >
> > > j
> > >
> > >
> > > --
> > > _____________________________
> > > http://jeanpiche.com
> > > ------------------------------------------------------------------------------
> > > Come build with us! The BlackBerry(R) Developer Conference in SF,
> > > CA
> > > is the only developer event you need to attend this year.
> > > Jumpstart your
> > > developing skills, take BlackBerry mobile applications to market
> > > and stay
> > > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > > now!
> > > http://p.sf.net/sfu/devconference_______________________________________________
> > > Csound-devel mailing list
> > > Csound-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
> >
> > ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart
> > your
> > developing skills, take BlackBerry mobile applications to market and
> > stay
> > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > now!
> > http://p.sf.net/sfu/devconference_______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel



Date2009-10-24 23:29
FromJean Piché
SubjectRe: [Cs-dev] Flooper2 - feature request.
AttachmentsNone  None  

Yes. In fact, we want the pointer to jump to the new kloopstart point once it reaches the "old" kloopend point. However, I can also think of situations (such as long loop times), when you would want it to jump to the new kloopstart point immediately upon receiving the new value.


j





2009/10/24 Olivier Bélanger <olivier.belanger@umontreal.ca>
Sorry Jean, but I think you didn't explained the problem correctly...


"
If one could make the pointer jump to the kloopstart point as soon as a new value is received
"

This is not what we expected, especially for granulation/stretching processes. The pointer start and end positions must change only after the current loop is completed but actually, under particular context, it seems to take the *new* kloopend as the end point of the current loop. Internally, the opcode must wait after the loop complete (reach the initial end point) before resetting his values.

I will try to isolate this "context" and post a simple .csd to illustrate it.

Olivier


2009/10/24 Iain Duncan <iainduncan@telus.net>

On Sat, 2009-10-24 at 19:18 +0100, Victor Lazzarini wrote:
> To be backward compatible, this will probably be implemented with a
> new
> optional parameter (0 or 1) disabling/enabling the new feature. I will
> wait
> some clarification on what it's supposed to be and then I can
> implement it.

oops. should have read the rest of the thread, you're way ahead of me!

Iain
>
>
> I'm very happy that flooper2 is going to be used in Cecilia 4.
>
>
> Victor
>
>
>
> On 24 Oct 2009, at 19:08, Victor Lazzarini wrote:
>
> >  I should be able to take care of this.
> >
> >
> > So, in summary, whenever the length of the loop changes, the pointer
> > should
> > jump to the new starting point? Surely that might cause a click?
> >
> >
> > Victor
> >
> >
> > Victor
> > On 24 Oct 2009, at 18:32, Jean Piché wrote:
> >
> > >
> > >
> > > Hi Victor,
> > >
> > > As you know, flooper2 is at the core of  the sampler in Cecilia4.
> > >
> > > When the  kloopstart & kloopend points are changed for LARGER
> > > values, the sound will continue being read at the ongoing rate
> > > until it gets to the new kloopend point and will start looping
> > > with the new values whereas when a SMALLER value is given for
> > > kloopstart, the pointer goes to the new startpoint immediately. In
> > > some ways, this is expected behaviour but it leaves interesting
> > > applications behind.
> > >
> > > If one could make the pointer jump to the kloopstart point as soon
> > > as a new value is received, granulation/stretching become possible
> > > along with a host of other "mangling" techniques.
> > >
> > > We have tried to reset the loop points by using a "re-init" pass
> > > without success.
> > >
> > > Could this be easily implemented?
> > >
> > > All the best!
> > >
> > > j
> > >
> > >
> > > --
> > > _____________________________
> > > http://jeanpiche.com
> > > ------------------------------------------------------------------------------
> > > Come build with us! The BlackBerry(R) Developer Conference in SF,
> > > CA
> > > is the only developer event you need to attend this year.
> > > Jumpstart your
> > > developing skills, take BlackBerry mobile applications to market
> > > and stay
> > > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > > now!
> > > http://p.sf.net/sfu/devconference_______________________________________________
> > > Csound-devel mailing list
> > > Csound-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
> >
> > ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart
> > your
> > developing skills, take BlackBerry mobile applications to market and
> > stay
> > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > now!
> > http://p.sf.net/sfu/devconference_______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel




--
_____________________________
http://jeanpiche.com

Date2009-10-25 01:45
From"Dr. Richard Boulanger"
SubjectRe: [Cs-dev] Flooper2 - feature request.
AttachmentsNone  None  
two modes/options perhaps?  both would be cool.

-dB

Dr. Richard Boulanger  -  rboulanger@berklee.edu



On Oct 24, 2009, at 6:29 PM, Jean Piché wrote:


Yes. In fact, we want the pointer to jump to the new kloopstart point once it reaches the "old" kloopend point. However, I can also think of situations (such as long loop times), when you would want it to jump to the new kloopstart point immediately upon receiving the new value.


j





2009/10/24 Olivier Bélanger <olivier.belanger@umontreal.ca>
Sorry Jean, but I think you didn't explained the problem correctly...


"
If one could make the pointer jump to the kloopstart point as soon as a new value is received
"

This is not what we expected, especially for granulation/stretching processes. The pointer start and end positions must change only after the current loop is completed but actually, under particular context, it seems to take the *new* kloopend as the end point of the current loop. Internally, the opcode must wait after the loop complete (reach the initial end point) before resetting his values.

I will try to isolate this "context" and post a simple .csd to illustrate it.

Olivier


2009/10/24 Iain Duncan <iainduncan@telus.net>

On Sat, 2009-10-24 at 19:18 +0100, Victor Lazzarini wrote:
> To be backward compatible, this will probably be implemented with a
> new
> optional parameter (0 or 1) disabling/enabling the new feature. I will
> wait
> some clarification on what it's supposed to be and then I can
> implement it.

oops. should have read the rest of the thread, you're way ahead of me!

Iain
>
>
> I'm very happy that flooper2 is going to be used in Cecilia 4.
>
>
> Victor
>
>
>
> On 24 Oct 2009, at 19:08, Victor Lazzarini wrote:
>
> >  I should be able to take care of this.
> >
> >
> > So, in summary, whenever the length of the loop changes, the pointer
> > should
> > jump to the new starting point? Surely that might cause a click?
> >
> >
> > Victor
> >
> >
> > Victor
> > On 24 Oct 2009, at 18:32, Jean Piché wrote:
> >
> > >
> > >
> > > Hi Victor,
> > >
> > > As you know, flooper2 is at the core of  the sampler in Cecilia4.
> > >
> > > When the  kloopstart & kloopend points are changed for LARGER
> > > values, the sound will continue being read at the ongoing rate
> > > until it gets to the new kloopend point and will start looping
> > > with the new values whereas when a SMALLER value is given for
> > > kloopstart, the pointer goes to the new startpoint immediately. In
> > > some ways, this is expected behaviour but it leaves interesting
> > > applications behind.
> > >
> > > If one could make the pointer jump to the kloopstart point as soon
> > > as a new value is received, granulation/stretching become possible
> > > along with a host of other "mangling" techniques.
> > >
> > > We have tried to reset the loop points by using a "re-init" pass
> > > without success.
> > >
> > > Could this be easily implemented?
> > >
> > > All the best!
> > >
> > > j
> > >
> > >
> > > --
> > > _____________________________
> > > http://jeanpiche.com
> > > ------------------------------------------------------------------------------
> > > Come build with us! The BlackBerry(R) Developer Conference in SF,
> > > CA
> > > is the only developer event you need to attend this year.
> > > Jumpstart your
> > > developing skills, take BlackBerry mobile applications to market
> > > and stay
> > > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > > now!
> > > http://p.sf.net/sfu/devconference_______________________________________________
> > > Csound-devel mailing list
> > > Csound-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
> >
> > ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart
> > your
> > developing skills, take BlackBerry mobile applications to market and
> > stay
> > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > now!
> > http://p.sf.net/sfu/devconference_______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel




--
_____________________________
http://jeanpiche.com
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


Date2009-10-25 06:46
FromVictor Lazzarini
SubjectRe: [Cs-dev] Flooper2 - feature request.
AttachmentsNone  None  
Ok, I am sending you privately a new plugin with these features for you to test.

Victor


On 24 Oct 2009, at 23:29, Jean Piché wrote:


Yes. In fact, we want the pointer to jump to the new kloopstart point once it reaches the "old" kloopend point. However, I can also think of situations (such as long loop times), when you would want it to jump to the new kloopstart point immediately upon receiving the new value.


j





2009/10/24 Olivier Bélanger <olivier.belanger@umontreal.ca>
Sorry Jean, but I think you didn't explained the problem correctly...


"
If one could make the pointer jump to the kloopstart point as soon as a new value is received
"

This is not what we expected, especially for granulation/stretching processes. The pointer start and end positions must change only after the current loop is completed but actually, under particular context, it seems to take the *new* kloopend as the end point of the current loop. Internally, the opcode must wait after the loop complete (reach the initial end point) before resetting his values.

I will try to isolate this "context" and post a simple .csd to illustrate it.

Olivier


2009/10/24 Iain Duncan <iainduncan@telus.net>

On Sat, 2009-10-24 at 19:18 +0100, Victor Lazzarini wrote:
> To be backward compatible, this will probably be implemented with a
> new
> optional parameter (0 or 1) disabling/enabling the new feature. I will
> wait
> some clarification on what it's supposed to be and then I can
> implement it.

oops. should have read the rest of the thread, you're way ahead of me!

Iain
>
>
> I'm very happy that flooper2 is going to be used in Cecilia 4.
>
>
> Victor
>
>
>
> On 24 Oct 2009, at 19:08, Victor Lazzarini wrote:
>
> >  I should be able to take care of this.
> >
> >
> > So, in summary, whenever the length of the loop changes, the pointer
> > should
> > jump to the new starting point? Surely that might cause a click?
> >
> >
> > Victor
> >
> >
> > Victor
> > On 24 Oct 2009, at 18:32, Jean Piché wrote:
> >
> > >
> > >
> > > Hi Victor,
> > >
> > > As you know, flooper2 is at the core of  the sampler in Cecilia4.
> > >
> > > When the  kloopstart & kloopend points are changed for LARGER
> > > values, the sound will continue being read at the ongoing rate
> > > until it gets to the new kloopend point and will start looping
> > > with the new values whereas when a SMALLER value is given for
> > > kloopstart, the pointer goes to the new startpoint immediately. In
> > > some ways, this is expected behaviour but it leaves interesting
> > > applications behind.
> > >
> > > If one could make the pointer jump to the kloopstart point as soon
> > > as a new value is received, granulation/stretching become possible
> > > along with a host of other "mangling" techniques.
> > >
> > > We have tried to reset the loop points by using a "re-init" pass
> > > without success.
> > >
> > > Could this be easily implemented?
> > >
> > > All the best!
> > >
> > > j
> > >
> > >
> > > --
> > > _____________________________
> > > http://jeanpiche.com
> > > ------------------------------------------------------------------------------
> > > Come build with us! The BlackBerry(R) Developer Conference in SF,
> > > CA
> > > is the only developer event you need to attend this year.
> > > Jumpstart your
> > > developing skills, take BlackBerry mobile applications to market
> > > and stay
> > > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > > now!
> > > http://p.sf.net/sfu/devconference_______________________________________________
> > > Csound-devel mailing list
> > > Csound-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
> >
> > ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart
> > your
> > developing skills, take BlackBerry mobile applications to market and
> > stay
> > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > now!
> > http://p.sf.net/sfu/devconference_______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel




--
_____________________________
http://jeanpiche.com
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel