Shing-Kwei

I use :"Kroonde" la kitchen to control my patch, but I got an error message:

Otudp: Out of packet buffers; have to drop packet(S)

From: maxmsp-bounces@cycling74.com [mailto:maxmsp-bounces@cycling74.com] On

Subject: Re: [maxmsp] Re: Talking 'bout tightness

How about seq~? While two dimensions wouldn't be enough to represent a

list, seq~ is a great help for looping control-rate events.

> IF you had a matrix whose width was the vector size, and height was 

> 1. then you could represent bangs and/or integers in audio rate.

> if you made it 2 dimensional, you could represent any max message at 

> if someone (**NOT ME**) wrote some objects on that principal, you 

> I know this is going to piss some people off, but Gregory Taylor once 

> told me that PD had an option to make any patcher run at any sampling 

> rate. More malulable sampling rates and datatypes really seems to be 

Hello! 
I use :"Kroonde" la kitchen to control my patch, but I got an error message:
Otudp: Out of packet buffers;  have to drop packet(S)
Thanks for any hints. 

-----Original Message-----
From: maxmsp-bounces@cycling74.com [mailto:maxmsp-bounces@cycling74.com] On
Behalf Of Peter McCulloch
Sent: Tuesday, March 13, 2007 1:53 PM
Subject: Re: [maxmsp] Re: Talking 'bout tightness

How about seq~?  While two dimensions wouldn't be enough to represent a
list, seq~ is a great help for looping control-rate events.

>
> ok... heres a FAR FAR out solution.
>
> IF you had a matrix whose width was the vector size, and height was  
> 1. then you could represent bangs and/or integers in audio rate.
>
> if you made it 2 dimensional, you could represent any max message at 
> audio rate.
>
> if someone (**NOT ME**) wrote some objects on that principal, you 
> could have audio rate max messages.
>
> whoa.
>
>
> I know this is going to piss some people off, but Gregory Taylor once 
> told me that PD had an option to make any patcher run at any sampling 
> rate.   More malulable sampling rates and datatypes really seems to be 
> a common solution.
>
>
www.petermcculloch.com

reotudp-problems

Did you try setting a larger number of buffers:

otudp read nbufs 128 (I'm not sure what the default value is)

> I use :"Kroonde" la kitchen to control my patch, but I got an error message:

> Otudp: Out of packet buffers; have to drop packet(S)

> From: maxmsp-bounces@cycling74.com [mailto:maxmsp-bounces@cycling74.com] On

> Subject: Re: [maxmsp] Re: Talking 'bout tightness

> How about seq~? While two dimensions wouldn't be enough to represent a

> list, seq~ is a great help for looping control-rate events.

> > IF you had a matrix whose width was the vector size, and height 

> > was 1. then you could represent bangs and/or integers in audio 

> > if you made it 2 dimensional, you could represent any max message 

> > if someone (**NOT ME**) wrote some objects on that principal, you 

> > I know this is going to piss some people off, but Gregory Taylor 

> > once told me that PD had an option to make any patcher run at any 

> > sampling rate. More malulable sampling rates and datatypes 

> > really seems to be a common solution.

otudp read  nbufs 128 (I'm not sure what the default value is)
otudp read  nbufs 256
otudp read  nbufs 512
otudp read  nbufs 1024

> ----- Original Message -----
> From: "Shing-kwei" 
> Subject: [maxmsp] RE:otudp problems
> Date: Tue, 13 Mar 2007 14:49:46 +0800
>
>
> Hello!
> I use :"Kroonde" la kitchen to control my patch, but I got an error message:
> Otudp: Out of packet buffers;  have to drop packet(S)
> Thanks for any hints.
>
> Shing-kwei
>
> -----Original Message-----
> From: maxmsp-bounces@cycling74.com [mailto:maxmsp-bounces@cycling74.com] On
> Behalf Of Peter McCulloch
> Sent: Tuesday, March 13, 2007 1:53 PM
> Subject: Re: [maxmsp] Re: Talking 'bout tightness
>
> How about seq~?  While two dimensions wouldn't be enough to represent a
> list, seq~ is a great help for looping control-rate events.
>
>
> >
> > ok... heres a FAR FAR out solution.
> >
> > IF you had a matrix whose width was the vector size, and height 
> > was  1. then you could represent bangs and/or integers in audio 
> > rate.
> >
> > if you made it 2 dimensional, you could represent any max message 
> > at audio rate.
> >
> > if someone (**NOT ME**) wrote some objects on that principal, you 
> > could have audio rate max messages.
> >
> > whoa.
> >
> >
> > I know this is going to piss some people off, but Gregory Taylor 
> > once told me that PD had an option to make any patcher run at any 
> > sampling rate.   More malulable sampling rates and datatypes 
> > really seems to be a common solution.
> >
> >
> www.petermcculloch.com
>
>

otudp has problems when you are in overdrive. That's the one time I

see this message, which tends to get worse over time, as you patch

runs. I imagine it has to do with the frequency of servicing otudp

when you are running MaxMSP processes in high and low priority

With overdrive off, really high data rates can cause this problem,

> > IF you had a matrix whose width was the vector size, and height was

> > 1. then you could represent bangs and/or integers in audio rate.

> > if you made it 2 dimensional, you could represent any max message at

> > if someone (**NOT ME**) wrote some objects on that principal, you

> > I know this is going to piss some people off, but Gregory Taylor once

> > told me that PD had an option to make any patcher run at any sampling

> > rate. More malulable sampling rates and datatypes really seems to be

----- |(*,+,#,=)(#,=,*,+)(=,#,+,*)(+,*,=,#)| -----

otudp has problems when you are in overdrive. That's the one time I
see this message, which tends to get worse over time, as you patch
runs. I imagine it has to do with the frequency of servicing otudp
when you are running MaxMSP processes in high and low priority
threads.

With overdrive off, really high data rates can cause this problem,
too, but it's much less of an issue.

On 3/13/07, Shing-kwei  wrote:
> Hello!
> I use :"Kroonde" la kitchen to control my patch, but I got an error message:
> Otudp: Out of packet buffers;  have to drop packet(S)
> Thanks for any hints.
>
> Shing-kwei
>
> -----Original Message-----
> From: maxmsp-bounces@cycling74.com [mailto:maxmsp-bounces@cycling74.com] On
> Behalf Of Peter McCulloch
> Sent: Tuesday, March 13, 2007 1:53 PM
> Subject: Re: [maxmsp] Re: Talking 'bout tightness
>
> How about seq~?  While two dimensions wouldn't be enough to represent a
> list, seq~ is a great help for looping control-rate events.
>
>
> >
> > ok... heres a FAR FAR out solution.
> >
> > IF you had a matrix whose width was the vector size, and height was
> > 1. then you could represent bangs and/or integers in audio rate.
> >
> > if you made it 2 dimensional, you could represent any max message at
> > audio rate.
> >
> > if someone (**NOT ME**) wrote some objects on that principal, you
> > could have audio rate max messages.
> >
> > whoa.
> >
> >
> > I know this is going to piss some people off, but Gregory Taylor once
> > told me that PD had an option to make any patcher run at any sampling
> > rate.   More malulable sampling rates and datatypes really seems to be
> > a common solution.
> >
> >
> www.petermcculloch.com
>
>
>

-- 
-----   |(*,+,#,=)(#,=,*,+)(=,#,+,*)(+,*,=,#)|   -----
