patch parameterisation: was [PD] abstractions which have their own memory
cyrille henry
cyrille.henry at la-kitchen.fr
Wed Jul 5 17:44:08 CEST 2006
Max Neupert a écrit :
>
> Am 05.07.2006 um 13:09 schrieb cyrille henry:
>> i personnaly choose to avoid netsend / netreceive and compute
>> everything in the same cpu/gpu. this is more optimised thant having
>> lots of netsend/receive, so i've got better results when i have lot's
>> of data for audio / video synthesys...
>
> this is interesting. i have made opposite experiences. to avoid lockup
> of pd and audio-glitches i have to use more than one instance of pd.
> preferably one with audio computation on and the other one off. also
> midi interfaces become often completely useless when trying to control
> gem stuff. so i use another instance to translate the midi into netsend
> and receive the data to control the things in the other instance which
> does the rendering. it is an awkward work-around but according to my
> experience a necessary one.
> could this be a bit platform specific too? i have this trouble on os x
> and have seen the same behavior on m$ win too. is it possible that this
> problem doesn't occur on linux?
well, i use a big and fat linux distribution with no specific real time
kernel. so i don't think linux will be lot's better than osX or windows
in this case.
i think the differences commes from the patch
i have a very big audiobuf size (~ 100ms) to avoid clicks.
the sound and video processing share lot's of data, and would create
huge netsend / netreceive dataflow
cyrille
>
> m.
>
>
More information about the Pd-list
mailing list