-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-09-16 23:10, Matthias Kronlachner wrote:
It's a message without argument: /1 I think this should be valid
OSC? (Wasn't this the same problem reported with Totalmix?)
However, the messages /1 crashes routeOSC if chained like this:
[/1 (
I think it's all fixed now, in svn. Anything not an OSC message is now
routed to the rightmost outlet, without prefixing a slash.
Let me know if it works or not for you. Thanks for finding the bug!
Martin
On 2013-09-16 17:22, Matthias Kronlachner wrote:
ok its even more simple than that..
a
Now it works fine for me, thanks.
Matthias
On 9/18/13 1:34 AM, Martin Peach wrote:
I think it's all fixed now, in svn. Anything not an OSC message is now
routed to the rightmost outlet, without prefixing a slash.
Let me know if it works or not for you. Thanks for finding the bug!
Martin
On
I found this workaround... maybe it helps:
http://puredata.hurleur.com/sujet-9201-touchosc-mrpeach-crash
El 16/09/13 13:08, Mario Mey escribió:
Thanks, Martin. I compiled it and test it. Again, in UbuntuStudio
12.04.3, it makes PureData crash. There's no message, it just crashs.
Is
Thanks, Martin. I compiled it and test it. Again, in UbuntuStudio
12.04.3, it makes PureData crash. There's no message, it just crashs.
Is anything I could do to help to avoid that? How could I debug it?
In the other hand, I'm having troubles to launch Pd from console (to see
if any message
It sounds like you have two issues: one is that the new external crashes
Pd as soon as it is instantiated, the other is that some OSC messages do
the same thing when [routeOSC] is involved.
For the second thing, just use
[udpreceive]
|
[unpackOSC]
|
[print]
and switch pages to see what raw
Hi!
I experience this bug today as well.
Attached is a Pd-patch that simulates this crash caused by the message
TouchOSC is sending if page is turned (although this can be changed in
the TouchOSC editor!).
This is the gdb output:
Program received signal EXC_BAD_ACCESS, Could not access
It's a message without argument: /1
I think this should be valid OSC? (Wasn't this the same problem reported
with Totalmix?)
However, the messages /1 crashes routeOSC if chained like this:
[/1 (
|
[routeOSC /1]
|
[routeOSC /foo]
And even if not specified in OSC, it should at least not crash
ok its even more simple than that..
a |bang( crashes routeOSC :-)
and a bang is sent to the outlet of routeOSC if a message has no argument...
On 9/16/13 11:51 PM, Martin Peach wrote:
OK, thanks for this.
Any idea what the message is that is causing the crash?
Is it valid OSC?
Martin
Now, I'm on Ubuntu 12.04 and I realized that I have a very old version
of mrpeach folder (routeOSC-help says: 2008/09/17 Martin Peach) and Pd
was configured to use it. That's why Pd doesn't crash after sending that
message from TouchOSC. In console, it only shows:
* routeOSC: ignoring empty
OK, thanks for this.
Any idea what the message is that is causing the crash?
Is it valid OSC?
Martin
On 2013-09-16 16:12, Matthias Kronlachner wrote:
Hi!
I experience this bug today as well.
Attached is a Pd-patch that simulates this crash caused by the message
TouchOSC is sending if page is
On 2013-09-14 19:28, Mario Mey wrote:
Martin Peach, I read somewhere that changing pages in TouchOSC makes Pd
(or Pd-Ext) to crash. My Pd-Extended doesn't crash, but this error is
shown: * routeOSC: ignoring empty list….
That doesn't happen here. There is no such message in the source code.
Martin Peach, I read somewhere that changing pages in TouchOSC makes Pd
(or Pd-Ext) to crash. My Pd-Extended doesn't crash, but this error is
shown: * routeOSC: ignoring empty list
Today, I've installed Ubuntu Studio 12.04.3 (with lowlatency kernel). It
seemed that it was a good distro
13 matches
Mail list logo
