nycpntr@yahoo.com

is there any latency when using send and receive vs. "standard" patch cords?

This question has been bugging me for a few weeks now. should have posted earlier, would not be up at 3:41 lol

is there any latency when using send and receive vs. "standard" patch cords?
This question has been bugging me for a few weeks now. should have posted earlier, would not be up at 3:41 lol 

SPAM: http://maxabeles.com/sounds/Mantanae.mp3 

send-receive-vs-patch-cords

send/receive are more CPU consuming than a "standard" patch cord.

I'm trying to find some "rules" for my own use here:

http://www.julienbayle.net/software/maxmspjitter/

I'm trying to find some "rules" for my own use here:
http://www.julienbayle.net/software/maxmspjitter/

Note that MaxMSP alone and M4L behave differently in this regard.

In my experience, with MaxMSP alone there is no latency at all.

You can verify this with the [timer] object.

In my experience, with MaxMSP alone there is no latency at all.
You can verify this with the [timer] object.


- send/receive in the same patch in M4L seems to be ok

- send/receive from a M4L patch to another one consumes CPU (we found that with Ralf Suckow by making this workaround to use 16 midi channels in & out instead of the channel1 limitation : 

http://forum.ableton.com/viewtopic.php?f=35&t=128795

by the way, in the last case, there is no other way to do that... so

I had to precise something:
- send/receive in the same patch in M4L seems to be ok
- send/receive from a M4L patch to another one consumes CPU (we found that with Ralf Suckow by making this workaround to use 16 midi channels in & out instead of the channel1 limitation : http://forum.ableton.com/viewtopic.php?f=35&t=128795 

by the way, in the last case, there is no other way to do that... so


send & receive vs. patch cords