passing fsigs to UDOs?

View: New views
6 Messages — Rating Filter:   Alert me  

passing fsigs to UDOs?

by Dave Seidel :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Is there any plan to add support for f-variables in UDOs?  It would be
very handy.

In the meantime, can anyone suggest a technique for using an fsig in a
UDO, where the fsig has been created in the instrument that calls the UDO?

In my scenario, I have (so far) two UDOs I want to call from my
instrument, each of which would do different processing on the fsig and
return an asig.  In my first cut, I just passed an asig into the UDO and
each one did their own pvsanal, etc., but this seems too
resource-intensive -- my goal is to factor out the pvsanal (and
pvspitch/pvscent) from the UDOs and do it only once.

- Dave

--
http://mysterybear.net
http://twitter.com/DaveSeidel
http://daveseidel.tumblr.com



Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

Re: passing fsigs to UDOs?

by joachim heintz :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Perhaps you can use pvsbuffer/pvsbufread? This is one application in  
an UDO:
http://www.csounds.com/udo/displayOpcode.php?opcode_id=90
ciao -

        joachim


Am 17.10.2009 um 20:33 schrieb Dave Seidel:

> Is there any plan to add support for f-variables in UDOs?  It would  
> be very handy.
>
> In the meantime, can anyone suggest a technique for using an fsig in  
> a UDO, where the fsig has been created in the instrument that calls  
> the UDO?
>
> In my scenario, I have (so far) two UDOs I want to call from my  
> instrument, each of which would do different processing on the fsig  
> and return an asig.  In my first cut, I just passed an asig into the  
> UDO and each one did their own pvsanal, etc., but this seems too  
> resource-intensive -- my goal is to factor out the pvsanal (and  
> pvspitch/pvscent) from the UDOs and do it only once.
>
> - Dave
>
> --
> http://mysterybear.net
> http://twitter.com/DaveSeidel
> http://daveseidel.tumblr.com
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body  
> "unsubscribe csound"
>



Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

Re: Re: passing fsigs to UDOs?

by Dave Seidel :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

That's an interesting idea, thanks!  I will play around with it.

(But I also think it would be great if UDOs would someday work with
fsigs for i/o.)

- Dave

joachim heintz wrote:

> Perhaps you can use pvsbuffer/pvsbufread? This is one application in an
> UDO:
> http://www.csounds.com/udo/displayOpcode.php?opcode_id=90
> ciao -
>
>     joachim
>
>
> Am 17.10.2009 um 20:33 schrieb Dave Seidel:
>
>> Is there any plan to add support for f-variables in UDOs?  It would be
>> very handy.
>>
>> In the meantime, can anyone suggest a technique for using an fsig in a
>> UDO, where the fsig has been created in the instrument that calls the
>> UDO?
>>
>> In my scenario, I have (so far) two UDOs I want to call from my
>> instrument, each of which would do different processing on the fsig
>> and return an asig.  In my first cut, I just passed an asig into the
>> UDO and each one did their own pvsanal, etc., but this seems too
>> resource-intensive -- my goal is to factor out the pvsanal (and
>> pvspitch/pvscent) from the UDOs and do it only once.
>>
>> - Dave




Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

Re: Re: Re: passing fsigs to UDOs?

by peiman :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Also take a look at Matt Ingalls UDO. Here http://www.csounds.com/udo/displayOpcode.php?opcode_id=10

Using pvsftw and pvsftr.

Best,

Peiman

2009/10/20 Dave Seidel <dave@...>
That's an interesting idea, thanks!  I will play around with it.

(But I also think it would be great if UDOs would someday work with fsigs for i/o.)

- Dave


joachim heintz wrote:
Perhaps you can use pvsbuffer/pvsbufread? This is one application in an UDO:
http://www.csounds.com/udo/displayOpcode.php?opcode_id=90
ciao -

   joachim


Am 17.10.2009 um 20:33 schrieb Dave Seidel:

Is there any plan to add support for f-variables in UDOs?  It would be very handy.

In the meantime, can anyone suggest a technique for using an fsig in a UDO, where the fsig has been created in the instrument that calls the UDO?

In my scenario, I have (so far) two UDOs I want to call from my instrument, each of which would do different processing on the fsig and return an asig.  In my first cut, I just passed an asig into the UDO and each one did their own pvsanal, etc., but this seems too resource-intensive -- my goal is to factor out the pvsanal (and pvspitch/pvscent) from the UDOs and do it only once.

- Dave




Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"


Re: Re: Re: Re: passing fsigs to UDOs?

by Dave Seidel :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thanks, Pieman, I will study that.

- Dave

peiman khosravi wrote:

> Also take a look at Matt Ingalls UDO. Here
> http://www.csounds.com/udo/displayOpcode.php?opcode_id=10
>
> Using pvsftw and pvsftr.
>
> Best,
>
> Peiman
>
> 2009/10/20 Dave Seidel <dave@...
> <mailto:dave@...>>
>
>     That's an interesting idea, thanks!  I will play around with it.
>
>     (But I also think it would be great if UDOs would someday work with
>     fsigs for i/o.)
>
>     - Dave
>
>
>     joachim heintz wrote:
>
>         Perhaps you can use pvsbuffer/pvsbufread? This is one
>         application in an UDO:
>         http://www.csounds.com/udo/displayOpcode.php?opcode_id=90
>         ciao -
>
>            joachim
>
>
>         Am 17.10.2009 um 20:33 schrieb Dave Seidel:
>
>             Is there any plan to add support for f-variables in UDOs?
>              It would be very handy.
>
>             In the meantime, can anyone suggest a technique for using an
>             fsig in a UDO, where the fsig has been created in the
>             instrument that calls the UDO?
>
>             In my scenario, I have (so far) two UDOs I want to call from
>             my instrument, each of which would do different processing
>             on the fsig and return an asig.  In my first cut, I just
>             passed an asig into the UDO and each one did their own
>             pvsanal, etc., but this seems too resource-intensive -- my
>             goal is to factor out the pvsanal (and pvspitch/pvscent)
>             from the UDOs and do it only once.
>
>             - Dave




Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

Re: Re: Re: passing fsigs to UDOs?

by joachim heintz :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

+1 for having fsigs in UDOs
        j


Am 20.10.2009 um 00:24 schrieb Dave Seidel:

> That's an interesting idea, thanks!  I will play around with it.
>
> (But I also think it would be great if UDOs would someday work with  
> fsigs for i/o.)
>
> - Dave
>
> joachim heintz wrote:
>> Perhaps you can use pvsbuffer/pvsbufread? This is one application  
>> in an UDO:
>> http://www.csounds.com/udo/displayOpcode.php?opcode_id=90
>> ciao -
>>    joachim
>> Am 17.10.2009 um 20:33 schrieb Dave Seidel:
>>> Is there any plan to add support for f-variables in UDOs?  It  
>>> would be very handy.
>>>
>>> In the meantime, can anyone suggest a technique for using an fsig  
>>> in a UDO, where the fsig has been created in the instrument that  
>>> calls the UDO?
>>>
>>> In my scenario, I have (so far) two UDOs I want to call from my  
>>> instrument, each of which would do different processing on the  
>>> fsig and return an asig.  In my first cut, I just passed an asig  
>>> into the UDO and each one did their own pvsanal, etc., but this  
>>> seems too resource-intensive -- my goal is to factor out the  
>>> pvsanal (and pvspitch/pvscent) from the UDOs and do it only once.
>>>
>>> - Dave
>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body  
> "unsubscribe csound"
>



Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"