Hi -

is it possible to have in
ares pvsadsyn fsrc, inoscs, kfmod [, ibinoffset] [, ibinincr]
the i-params as k-params?
This would be great and give many good possibilities to play live with  
it.
Thanks -

	joachim

As the code stands, this might be difficult, but Richard Dobson,
who is the author of the opcode might have some other ideas.

Victor
----- Original Message ----- 
From: "joachim heintz" 
To: 
Sent: Monday, May 25, 2009 7:13 PM
Subject: [Csnd] k-params in pvsadsynth?


> Hi -
>
> is it possible to have in
> ares pvsadsyn fsrc, inoscs, kfmod [, ibinoffset] [, ibinincr]
> the i-params as k-params?
> This would be great and give many good possibilities to play live with 
> it.
> Thanks -
>
> joachim
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound" 

[been away, working thru 500+ emails...]



I suspect the problem to avoid will be the clicks as partials are 
included/excluded, if implemented "naively". Really, we will want to 
crossfade each partial (i.e. potentially quite a lot of them) with some 
simple (?) envelope. That crossfade would need to be independent of 
ksmps, and doubtless users will want other controls (shape, etc). In 
short, it takes us more into partial-tracking territory. Which in turn 
suggests making a new more sophisticated opcode than rejgging the 
current one, which is most definititely  unsophisticated in this and 
other ways.

Richard Dobson


victor wrote:
> As the code stands, this might be difficult, but Richard Dobson,
> who is the author of the opcode might have some other ideas.
> 
> Victor
> ----- Original Message ----- From: "joachim heintz" 
> To: 
> Sent: Monday, May 25, 2009 7:13 PM
> Subject: [Csnd] k-params in pvsadsynth?
> 
> 
>> Hi -
>>
>> is it possible to have in
>> ares pvsadsyn fsrc, inoscs, kfmod [, ibinoffset] [, ibinincr]
>> the i-params as k-params?
>> This would be great and give many good possibilities to play live with 
>> it.
>> Thanks -
>>
>> joachim
>>

Well, there is already tradsyn which does basically that. Other
pvs track opcodes can be used to dynamically limit what goes
on in a set of tracks too (eg. trsplit )

Victor
----- Original Message ----- 
From: "Richard Dobson" 
To: 
Sent: Sunday, May 31, 2009 8:53 AM
Subject: [Csnd] Re: Re: k-params in pvsadsynth?


> [been away, working thru 500+ emails...]
>
>
>
> I suspect the problem to avoid will be the clicks as partials are 
> included/excluded, if implemented "naively". Really, we will want to 
> crossfade each partial (i.e. potentially quite a lot of them) with some 
> simple (?) envelope. That crossfade would need to be independent of ksmps, 
> and doubtless users will want other controls (shape, etc). In short, it 
> takes us more into partial-tracking territory. Which in turn suggests 
> making a new more sophisticated opcode than rejgging the current one, 
> which is most definititely  unsophisticated in this and other ways.
>
> Richard Dobson
>
>
> victor wrote:
>> As the code stands, this might be difficult, but Richard Dobson,
>> who is the author of the opcode might have some other ideas.
>>
>> Victor
>> ----- Original Message ----- From: "joachim heintz" 
>> To: 
>> Sent: Monday, May 25, 2009 7:13 PM
>> Subject: [Csnd] k-params in pvsadsynth?
>>
>>
>>> Hi -
>>>
>>> is it possible to have in
>>> ares pvsadsyn fsrc, inoscs, kfmod [, ibinoffset] [, ibinincr]
>>> the i-params as k-params?
>>> This would be great and give many good possibilities to play live with 
>>> it.
>>> Thanks -
>>>
>>> joachim
>>>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound" 

Thanks for your replies, Victor and Richard. I'll have a look at  
tradsyn and related opcodes.
	joachim



Am 31.05.2009 um 10:04 schrieb victor:

> Well, there is already tradsyn which does basically that. Other
> pvs track opcodes can be used to dynamically limit what goes
> on in a set of tracks too (eg. trsplit )
>
> Victor
> ----- Original Message ----- From: "Richard Dobson"  >
> To: 
> Sent: Sunday, May 31, 2009 8:53 AM
> Subject: [Csnd] Re: Re: k-params in pvsadsynth?
>
>
>> [been away, working thru 500+ emails...]
>>
>>
>>
>> I suspect the problem to avoid will be the clicks as partials are  
>> included/excluded, if implemented "naively". Really, we will want  
>> to crossfade each partial (i.e. potentially quite a lot of them)  
>> with some simple (?) envelope. That crossfade would need to be  
>> independent of ksmps, and doubtless users will want other controls  
>> (shape, etc). In short, it takes us more into partial-tracking  
>> territory. Which in turn suggests making a new more sophisticated  
>> opcode than rejgging the current one, which is most definititely   
>> unsophisticated in this and other ways.
>>
>> Richard Dobson
>>
>>
>> victor wrote:
>>> As the code stands, this might be difficult, but Richard Dobson,
>>> who is the author of the opcode might have some other ideas.
>>>
>>> Victor
>>> ----- Original Message ----- From: "joachim heintz" >> >
>>> To: 
>>> Sent: Monday, May 25, 2009 7:13 PM
>>> Subject: [Csnd] k-params in pvsadsynth?
>>>
>>>
>>>> Hi -
>>>>
>>>> is it possible to have in
>>>> ares pvsadsyn fsrc, inoscs, kfmod [, ibinoffset] [, ibinincr]
>>>> the i-params as k-params?
>>>> This would be great and give many good possibilities to play live  
>>>> with it.
>>>> Thanks -
>>>>
>>>> joachim
>>>>
>>
>>
>>
>> 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"
>