continuous osc usage make VPT slowing down, freeze and sometimes crash

[musinou]

Hi,

I have 5 solid coloured layers, and I continually change fade, size and position via OSC. 

It works fine for some time, when I set it up, in a new project. And, at one point, some of the OSC messages does not seam to go through. I get less and less frames by second. And, at some point I get nothing anymore and have no other choice than force quitting. 

If I start VPT again, and call back the preset, it does not work, does the same freezing pattern. But, if I rebuilt the VPT settings from scratch, it works for some time, and, I get the same crashing pattern again, later.

I had the same problem with other type of VPT settings. It seams to happen when I use continuous OSC.

Is anyone here using VPT with continuous OSC? And getting  similar issues? Do you have any idea of what could cause this?

Many thanks!

[hc]

I have not had these issues, so it would be interesting to try to
figure out what is going on and if others have had similar issues.

How are you sending the osc data? Maybe there is a "traffic jam"
somewhere if too much data is sent too fast?
Could you please tell us which version of VPT you are using, which
platform, computer etc. Also, any error messages reported in the max
window (ctrl/apple m)?

[musinou]

Hi,

Thank you for your reply.

I have the same issue with v10 and v9. I have OS 10,6

I use Max 5 to send OSC messages.

I use [line 0. 60] - so, that should be ok for a 16 frames per second.

I get a port 6666 packet drop messages (hundreds) in the VPT's Max window after a long long freezing time.

For some reason, the x and y + scale x and scale y, completely stop working, while fade still works. Might be due to the  fact that I don't send as much fade as the other osc messages.

What is weird is that I can't make VPT work again even after restarting the computer. It seams that something get corrupt. But sometimes it works. I don't know yet what procedure I did to make it work again.

I actually even turn video processing off, and I just look at the settings window, see if the number are moving about, or actually, not moving while they are moving in Max/MSP. So, I do think it is UDP traffic jam.

Any idea of how to make it work? 

Thank you!

[musinou]

Sorry, I meant OSC traffic jam. As the fade still work, so, it seams that UDP is getting through.

[hc]

the dropped packet messages definitely indicates that there is more
incoming packets to the 6666 port than the computer can handle.
Maybe you could share the max patch so I could give it a go on my
computer?

[musinou]

Hi,

I realised that I missed patch something, and that  I was actually really doing continuous data  (something around every 1ms). So, by having something less frequent, let say no more than the frame rate, I get it to work. 

Do you have any filter, in VPT, that discard the OSC messages if you have them more often than the frame rate? I sent the same data to another UDP port, throughout Max, and did not get any drop packet messages, so, it looks like UDP could handle it, unless it is different when UDP messages are going through Max or through Max to VPT.

I want to thank you for this piece of software, it is great, thank you for sharing it with us and replying to questions, really nice of you!

[hc]

one thing is sending osc data to another udp port, another thing is to
send it to VPT which also has to parse and execute each osc message. I
don´t know what kind of internal limits there are in the udp objects
in max, but I guess the main problem here is the extremely high
frequency of messages sent.

Anyway, glad to hear that you figured it out.