- I'm attaching the minimal test patch with which I was able to reproduce the bug. - I'm using Pd Vanilla, no externals installed nor required. - I'm running Pd on:
Macbook Pro 13" late 2011 (8,1) 2,4GHz Intel Core i5 16GB RAM, Intel HD Graphics 3000 512 MB
Running: OS X El Capitan (10.11.6)
PureData 0.47.1
On 11 Apr 2017, at 08:11, IOhannes m zmoelnig zmoelnig@iem.at wrote:
On 2017-04-11 00:56, Niccolò Granieri 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.
i don't think that this is a common (or even known) issue. since i'm pretty sure that a number of people are using OSC with DSP turned on, the problem ist most likely somewhere else.
please provide:
- a minimal test patch that shows the problem (since you are using
localhost, a single test patch should suffice)
- detailed information about which external libraries (and which
versions) you are using, esp. regarding OSC parsing and networking (you *can* do all those things with: vanilla objects, but traditionally externals were needed; it is not clear from your problem description which route you are taking)
- detailed information about your system (including your OS).
fgd IOhannes
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev