Forums > MaxMSP

OSC Buffer size, Packets Per Second

December 1, 2007 | 2:07 pm

I am sending a constant stream of OSC messages via UDP inside a DIY Pluggo Plugin.

I am sending them back to myself, 127.0.0.1, localhost.

I am sending 45 packets per second and it works fine.

When I have more than one instance of the plug in though, I am getting network congestion.

So I was wondering if anyone could tell me:

a)How many packets I could realistically hope to send per second.

b)How to set up the udp buffer to maximize the above figure.

If anyone knows the answer, thanks alot

Gavin


December 2, 2007 | 12:28 pm

Are you sure the vst’s are not sending to eachother creating a network loop? 45 per second is not really much.

_
johan


December 2, 2007 | 1:53 pm

Not sure no but I’m only sending from my patch, not receiving!

As i said 45 per second works fine but when I have say 4 instances of the plug in things get a bit vlogged.

Seems to max out at about 100 per second

Gav


December 3, 2007 | 8:20 am

It overdrive is on, does turning it of do anything good?

_
johan


December 3, 2007 | 9:28 am

Quote: gavspav wrote on Sun, 02 December 2007 14:53
—————————————————-
> Not sure no but I’m only sending from my patch, not receiving!
>
> As i said 45 per second works fine but when I have say 4 instances of the plug in things get a bit vlogged.
>
> Seems to max out at about 100 per second
>
> Gav
—————————————————-

I am sure you tested this (not inside a pluggo, just in max):

#P window setfont "Sans Serif" 9.;
#P number 60 205 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P number 101 79 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P flonum 133 267 56 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P window linecount 1;
#P newex 133 247 49 196617 !/ 1000.;
#P newex 133 206 20 196617 t b;
#P newex 59 118 70 196617 random 1000;
#P toggle 59 79 15 0;
#P newex 59 98 52 196617 metro 10;
#P newex 133 227 35 196617 timer;
#P newex 60 185 86 196617 udpreceive 3000;
#P newex 59 138 120 196617 udpsend 127.0.0.1 3000;
#P comment 192 267 40 196617 msg/s;
#P connect 7 0 3 0;
#P connect 7 0 3 1;
#P connect 2 0 11 0;
#P connect 2 0 7 0;
#P connect 10 0 4 1;
#P connect 3 0 8 0;
#P connect 8 0 9 0;
#P connect 6 0 1 0;
#P connect 4 0 6 0;
#P connect 5 0 4 0;
#P window clipboard copycount 12;

With this patch I get at least up to 1000 msg/sec.

So I guess your question is what the difference is between sending udp messages to a pluggo compared to plain max. Is that correct?

Mattijs


December 3, 2007 | 11:25 am

No I haven’t tried it.

Converting this patch to send it to my osc receiver app I am getting 100 messages a second.

But if I send 4 messages I get 400 messages/sec no probelm.

So yes it is Pluggo that is slowing the rate.

I now understand this is because of the (in)frequency which my host (Live) sends parameter values to my plug in

Which judging my other forum threads is impossible to change?

By the way Mattijs I PM’d you.

thanks,

gavin


December 3, 2007 | 12:16 pm

Quote: gavspav wrote on Mon, 03 December 2007 12:25
—————————————————-

> By the way Mattijs I PM’d you.
>

That’s right, I haven’t had the time to reply yet. But I’m quite sure that the sync options of pluggo will not help in the communication to the outside world. They’re meant to sync playback inside pluggo to the host sequencer, mostly in the audio domain.

As long as the internal events thread doesn’t update often enough there is no way to get data from inside a pluggo to the outside world accurately timed.

What I do now is send the notes (that require most accurate timing) to max via midi and the automation changes via udp. Parameter changes that have to be rythmically (i.e. require accurate timing) are sent via cc’s.

But afaik any sending via midi should be unnecessary. Udp communication, especially within one computer, is more than fast enough to do this correctly.

In short, I guess, Cycling ’74, we’d greatly appreciate a way to communicate from pluggo to max, accurately timed.

Mattijs


Viewing 7 posts - 1 through 7 (of 7 total)