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

IOhannes m zmoelnig zmoelnig at iem.at
Tue Apr 11 09:11:09 CEST 2017


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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20170411/c222d794/attachment.sig>


More information about the Pd-dev mailing list