[PD-dev] Conflict: incoming OSC data and DSP on

Niccolò Granieri granieriniccolo at gmail.com
Wed Apr 12 14:02:39 CEST 2017


> I cannot with the same Pd version on Linux. I wonder whether it is
> related to the high refresh rate of the number boxes.
> 
> Does the GUI freeze still occur if the the update rate of the number
> boxes (not that of actual data going through the wire!) is throttled? 

Hi Roman, I'm not quite sure how I would throttle the number boxes, can you be more specific?

> Is wish more likely the bottleneck on some platforms, but not on
> others? Is wish using 100% of a CPU core when the freeze happens?

Actually Pd drops in CPU usage after the freeze happens. From 40% to 0,8%. But the GUI is completetly frozen and the audio has up to a 5second delay!

_______________________________________________
Pd-dev mailing list
Pd-dev at lists.iem.at <mailto:Pd-dev at lists.iem.at>
https://lists.puredata.info/listinfo/pd-dev <https://lists.puredata.info/listinfo/pd-dev>


> On 12 Apr 2017, at 12:55, Roman Haefeli <reduzent at gmail.com> wrote:
> 
> 
> 
> On Die, 2017-04-11 at 18:33 +0200, Damian Stewart wrote:
>> Fwiw I can reproduce exactly the behaviour that Niccolò is seeing
>> here. OSX 10.12.3, pd vanilla 0.47.1 64 bit.
> 
> I cannot with the same Pd version on Linux. I wonder whether it is
> related to the high refresh rate of the number boxes.
> 
> Does the GUI freeze still occur if the the update rate of the number
> boxes (not that of actual data going through the wire!) is throttled? 
> 
> Is wish more likely the bottleneck on some platforms, but not on
> others? Is wish using 100% of a CPU core when the freeze happens?
> 
> (Sorry if I'm repeating what IOhannes already said)
> 
> Roman
> 
> 
> p.s.: Why is this on pd-dev?
> 
> 
>>> On 11 Apr 2017, at 00:56, Niccolò Granieri
>>> <granieriniccolo at gmail.com> wrote:
>>> 
>>> Hello Pd-dev mailing list,
>>> 
>>> I am writing, for the first time, to point out an issue I'm having
>>> with incoming OSC data in Pd and DSP being turned on.
>>> 
>>> The problem occurs when, while receiving OSC data from inside my
>>> machine (thus using a localhost), I turn on DSP. The OSC data stops
>>> flowing until I don't turn the DSP off.
>>> 
>>> The only workaround I found to solve this issue is to run two
>>> separate instances of Pd: the first one that will act as an OSC
>>> parser, not having the need to turn on DSP. Once the data is
>>> parsed, the data is sent to a second instance of Pd via FUDI
>>> protocol (netsend) where it can coexist with DSP on without causing
>>> any issues.
>>> 
>>> This unfortunately brings up the amount of computing power needed.
>>> 
>>> I was wondering if anyone encountered the same problem before, and
>>> if there was any better solution.
>>> 
>>> Thanks in advance, glad to be in this mailing list,
>>> 
>>> Niccolò
>>> 
>>> Pure Data 0.47.1 - 64 bit
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Pd-dev mailing list
>>> Pd-dev at lists.iem.at
>>> https://lists.puredata.info/listinfo/pd-dev
>> 
>> _______________________________________________
>> Pd-dev mailing list
>> Pd-dev at lists.iem.at
>> https://lists.puredata.info/listinfo/pd-dev
> _______________________________________________
> Pd-dev mailing list
> Pd-dev at lists.iem.at <mailto:Pd-dev at lists.iem.at>
> https://lists.puredata.info/listinfo/pd-dev <https://lists.puredata.info/listinfo/pd-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20170412/da589d44/attachment-0001.html>


More information about the Pd-dev mailing list