Danjel van Tijn

I am using the line output of long envelopes (made with function object) to generate changing control parameters (e.g. sample duration, FM carrier frequency, sample pitch). The target values were not signals yet routing them using a router object caused problems: the envelope data was really delayed and stretched out (basically distorted). It seemed like this was generating too many max messages for the router to deliver them in realtime.

I fixed the problem by converting them to signals and using the matrix~ object instead.

porblems-routing-line-output-via-router

On 4 sept. 07, at 16:42, Danjel van Tijn wrote:

> I am using the line output of long envelopes (made with function 

> object) to generate changing control parameters (e.g. sample 

> duration, FM carrier frequency, sample pitch). The target values 

> were not signals yet routing them using a router object caused 

> problems: the envelope data was really delayed and stretched out 

> (basically distorted). It seemed like this was generating too many 

> max messages for the router to deliver them in realtime.

> I fixed the problem by converting them to signals and using the 

That sounds weird. Could you post an example?

> I am using the line output of long envelopes (made with function  
> object) to generate changing control parameters (e.g. sample  
> duration, FM carrier frequency, sample pitch). The target values  
> were not signals yet routing them using a router object caused  
> problems: the envelope data was really delayed and stretched out  
> (basically distorted). It seemed like this was generating too many  
> max messages for the router to deliver them in realtime.
>
> I fixed the problem by converting them to signals and using the  
> matrix~ object instead.

> It seemed like this was generating too many max messages for the

I bet you have some right to left ordering issues not sorted out. router

works fine for me (and certainly is waayyy more effective than a matrix~ 

Danjel van Tijn schrieb:
> It seemed like this was generating too many max messages for the
> router to deliver them in realtime.

I bet you have some right to left ordering issues not sorted out. router
works fine for me (and certainly is waayyy more effective than a matrix~ 
object... ;-)

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com

what takes time is when you are using many arguments to route.

if the input to route is a hughe amount of data (such as lists from line) you should try using the last i.e. the rightmost outlet from route for this type of input.

the issue is that all of the input data I am routing is from line 0bjects. 5 inputs to 16 outputs.

Right now the matrix~ object is working fine although I assume this is far mroe taxing on cpu.

I will make up a model patch to show you guys what I am doing.

porblems routing line output via router?