Bugs item #3010591, was opened at 2010-06-02 17:14
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3010591&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: v0.43
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: PD-extended v0.43 nightly build, v0.42 - midiout sysex fail
Initial Comment:
WinXP Pro SP3
Pd-extended v0.43 nightly build, v0.42
thread: http://puredata.hurleur.com/sujet-4260-sysex-out-synth
hey everyone,
Patch:
240, 71, 0, 104, 49, 0, 11, 8, 0, 0, 72, 97, 108, 108, 111, 32, 32, 32, 247
|
midiout
And to check the results, i used: midiout -> Midiyoke -> MidiOX (all latest versions)
Problem:
Instead of DEC
240, 71, 0, 104, 49, 0, 11, 8, 0, 0, 72, 97, 108, 108, 111, 32, 32, 32, 247
MidiOX receives DEC:
240
71, 0, 0,
0, 0, 0,
104, 0, 0,
49, 0, 0,
0, 0, 0,
11, 0, 0,
8, 0, 0,
0, 0, 0,
0, 0, 0,
72, 0, 0,
97, 0, 0,
108, 0, 0,
108, 0, 0,
111, 0, 0,
32, 0, 0,
32, 0, 0,
32, 0, 0,
247
sent from MidiOX, my MPD 24 will happily accept the sysex and execute it so the probelm is definitely not MidiOx or Midiyoke.
Questions
1) can anyone confirm this?
2) is anyone currently maintaining midiout, so this could maybe get fixed?
it'd be great to see sysex working!
thanks
groovelastig
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3010591&group_…
Bugs item #3010589, was opened at 2010-06-02 17:02
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3010589&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: v0.42
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: PD vanilla 0.42-5 - midiout 'loses' (re-orders) bit
Initial Comment:
WinXP Pro SP3
Pd version 0.42-5
17-Jan-07 version of PortMidi
thread: http://puredata.hurleur.com/sujet-4275-vanilla-portmidi-midiout-loses-order…
(see thread for text colored in where neccessary)
hey everyone,
I've been working with PD vanilla 0.42-5 - PortMidi midiout last night, trying to figure out why it wouldn't work with my AKAI MPD 24 properly. Here's what I found:
Patch (as attached:)
240, 71, 0, 104, 49, 0, 11, 8, 0, 0, 72, 97, 108, 108, 111, 32, 32, 32, 247
|
midiout
And to check the results, i used: midiout -> Midiyoke -> MidiOX (all latest versions)
Problem
The message I sent (which was a valid MPD 24 SysEx message, double-checked several times from MidiOX directly) was DEC
240, 71, 0, 104, 49, 0, 11, 8, 0, 0, 72, 97, 108, 108, 111, 32, 32, 32, 247
and should convert have converted to HEX
F0 47 00 68 31 00 0B 08 00 00 48 61 6C 6C 6F 20 20 20 F7
instead, it comes out HEX
F0 47 00 68 31 00 02 08 00 00 52 61 6C 6C 1B 20 20 20 F7
- with 3 wrong HEX pairs.
What happens
I looked a bit at the first number, DEC 11 that should come out HEX 0B but comes out HEX 02
here's how it behaves in reverse engineering:
when i send DEC 0, 1, 2 or 3, it comes out HEX 0
when i send DEC 4, 5 6 or 7, it comes out HEX 1
see table:
DEC .. DEC -> HEX
00 .. 03 -> 00
04 .. 07 -> 01
08 .. 11 -> 02
12 .. 15 -> 03
16 .. 19 -> 04
20 .. 23 -> 05
24 .. 27 -> 06
28 .. 31 -> 07
32 .. 35 -> 08
36 .. 39 -> 09
40 .. 43 -> 0A
44 .. -> 0B
etc.
When you look at the BIN, it becomes obvious what's happening:
DEC (BIN) .. DEC (BIN) -> HEX (BIN)
00 ( 0) .. 03 ( 11) -> 00 ( 0)
04 ( 100) .. 07 ( 111) -> 01 ( 1)
08 ( 1000) .. 11 ( 1011) -> 02 ( 10)
12 ( 1100) .. 15 ( 1111) -> 03 ( 11)
16 (10000) .. 19 (10011) -> 04 ( 100)
20 (10100) .. 23 (10111) -> 05 ( 101)
.. two bits at the end are truncated.
It wouldn't surprise me if we found them somewhere in the other 'wrong numbers' ofthe original message.
When I manipulate the numbers to come out correctly in MidiOX, my MPD 24 will happily accept the sysex and execute it so the probelm is definitely not MidiOx or Midiyoke.
Questions
1) can anyone confirm this?
2) is anyone currently maintaining PortMidi, so this could maybe get fixed?
thanks
groovelastig
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3010589&group_…
Bugs item #2952825, was opened at 2010-02-16 16:10
Message generated for change (Comment added) made by sistisette
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2952825&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: v0.42
>Status: Open
Resolution: Works For Me
Priority: 5
Private: No
Submitted By: Matteo Sisti Sette (sistisette)
Assigned to: Nobody/Anonymous (nobody)
Summary: pd hangs in windows Vista and won't work until system reboot
Initial Comment:
Sometimes (unfortunately I haven't observed any apparent cause that triggers the problem), I open PD and it won't create a new patch (file/new) nor open any patch (file/open). It won't even quit untill I kill the process, and clicking on "DIO errors" doesn't produce any printout.
Furthermore, all menus of the menu bar are empty (only a "--" item) except the File menu.
Even if I kill and restart PD, it won't ever work, untill I reboot the operating system, then everything is fine.
This is PD Vanilla 0.42.5 on Windows Vista.
When it gets "frozen" like this, if I launch it with -lib Gem (I have Gem installed), it won't print the usual Gem output on the console (no output at all).
After reboot, everything usually works.
This happens every once in a while, and it is NOT necessary after some crash or anything.
----------------------------------------------------------------------
>Comment By: Matteo Sisti Sette (sistisette)
Date: 2010-06-02 10:09
Message:
Hi,
I didn't find any way to make it happen. It happens from time to time, not
very often, when I start Pd.
By windows install do you mean Windows itself, or pd-for-windows' install?
I have never seen anything similar with any other program.
When this happens, the interface doesn't _seem_ unresponsive at first
sight: I mean, you can click on a menu and the menu drops down: but if you
choose any item (for example File/New), nothing happens. Also if you click
on "DIO Errors" the button does do the button-like "movement", but nothing
is printed on the console.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-06-02 03:15
Message:
Sounds to me like a problem with your windows install. Can you provide
step-by-step instructions to make it happen everytime?
----------------------------------------------------------------------
Comment By: Matteo Sisti Sette (sistisette)
Date: 2010-06-02 01:45
Message:
It's not always acrotray.exe. It has happened to me that killing
acrotray.exe didn't fix it and killing some other apparently random process
did.
And no, killing pd.exe does not fix it. When this happens, I have to kill
random processes (well not actually random: I try to kill those that i know
or guess that are useless or safe to kill) until I find one that works,
I'm not sure whether killing other processes without _also_ restarting Pd
works, because usually it goes as follows:
- first I restart Pd, and it's frozen again
- I close it, kill some process and open Pd again
- and so on, until it works.
Well, for this same reason maybe I didn't actually try killing pd.exe with
the task manager, but I certainly did check the task manager to ensure
there was no extra pd.exe process.
Note that these freezings I'm talking about are ALWAYS at Pd startup: I
start Pd and it's already frozen. It has never happened to me that it hangs
like this (and won't recover afret restart).
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-06-01 23:40
Message:
- try killing pd.exe in the Windows Task Manager, that has always done it
for me
- I haven't been able to reproduce this using recent builds of Pd-extended
0.42.5 on Windows XP and Windows 7.
- otherwise, it sounds like some weirdness with acrotray is the issue
----------------------------------------------------------------------
Comment By: Matteo Sisti Sette (sistisette)
Date: 2010-02-16 16:16
Message:
I've just found out that killing the "acrotray.exe" process seems to fix
the problem: after doing that, PD works fine.
Acrotray is something related to Adobe Acrobat or Acrobat Reader. What
relation it can have with PD is beyond my understanding.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2952825&group_…
Bugs item #3003023, was opened at 2010-05-18 00:45
Message generated for change (Comment added) made by sf-robot
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3003023&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: pd-extended
Group: None
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: pd crash
Initial Comment:
I have had continuos crashing, pd doesn't respond and need to force quit very often. It is not possible to work.
----------------------------------------------------------------------
>Comment By: SourceForge Robot (sf-robot)
Date: 2010-06-02 02:20
Message:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-05-18 05:24
Message:
Could you try a nightly build and report back whether the problem still
exists?
http://autobuild.puredata.info/auto-build/latest/
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-05-18 05:24
Message:
Please provide as detailed information as possible including which
operating system (OS), CPU type, specific hardware, and the exact distro
and version of Pd itself, etc.
For example:
Pd version 0.41.4-extended
Mac OS X 10.5.7/Intel
built-in sound
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3003023&group_…
Bugs item #2822249, was opened at 2009-07-16 04:21
Message generated for change (Comment added) made by sf-robot
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2822249&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: pd-extended
Group: None
>Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Martin Peach (mrpeach)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: font sizes when $pd_nt==1
Initial Comment:
Pd version 0.42.5-extended-20090715 on WinXP the fonts are too small. pd.tk sets the fonts smaller for tcl8.5 but this is not needed on Windows.
The attached diff fixes most of them, but the Path, Startup Audio Settings dialogs fonts do not seem to be set in pd.tk.
----------------------------------------------------------------------
>Comment By: SourceForge Robot (sf-robot)
Date: 2010-06-02 02:20
Message:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2009-07-16 21:47
Message:
Nice, thanks for looking at that. Feel free to commit the changes
directly.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2822249&group_…
Bugs item #2952825, was opened at 2010-02-16 10:10
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2952825&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: v0.42
>Status: Pending
Resolution: Works For Me
Priority: 5
Private: No
Submitted By: Matteo Sisti Sette (sistisette)
Assigned to: Nobody/Anonymous (nobody)
Summary: pd hangs in windows Vista and won't work until system reboot
Initial Comment:
Sometimes (unfortunately I haven't observed any apparent cause that triggers the problem), I open PD and it won't create a new patch (file/new) nor open any patch (file/open). It won't even quit untill I kill the process, and clicking on "DIO errors" doesn't produce any printout.
Furthermore, all menus of the menu bar are empty (only a "--" item) except the File menu.
Even if I kill and restart PD, it won't ever work, untill I reboot the operating system, then everything is fine.
This is PD Vanilla 0.42.5 on Windows Vista.
When it gets "frozen" like this, if I launch it with -lib Gem (I have Gem installed), it won't print the usual Gem output on the console (no output at all).
After reboot, everything usually works.
This happens every once in a while, and it is NOT necessary after some crash or anything.
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-06-01 21:15
Message:
Sounds to me like a problem with your windows install. Can you provide
step-by-step instructions to make it happen everytime?
----------------------------------------------------------------------
Comment By: Matteo Sisti Sette (sistisette)
Date: 2010-06-01 19:45
Message:
It's not always acrotray.exe. It has happened to me that killing
acrotray.exe didn't fix it and killing some other apparently random process
did.
And no, killing pd.exe does not fix it. When this happens, I have to kill
random processes (well not actually random: I try to kill those that i know
or guess that are useless or safe to kill) until I find one that works,
I'm not sure whether killing other processes without _also_ restarting Pd
works, because usually it goes as follows:
- first I restart Pd, and it's frozen again
- I close it, kill some process and open Pd again
- and so on, until it works.
Well, for this same reason maybe I didn't actually try killing pd.exe with
the task manager, but I certainly did check the task manager to ensure
there was no extra pd.exe process.
Note that these freezings I'm talking about are ALWAYS at Pd startup: I
start Pd and it's already frozen. It has never happened to me that it hangs
like this (and won't recover afret restart).
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-06-01 17:40
Message:
- try killing pd.exe in the Windows Task Manager, that has always done it
for me
- I haven't been able to reproduce this using recent builds of Pd-extended
0.42.5 on Windows XP and Windows 7.
- otherwise, it sounds like some weirdness with acrotray is the issue
----------------------------------------------------------------------
Comment By: Matteo Sisti Sette (sistisette)
Date: 2010-02-16 10:16
Message:
I've just found out that killing the "acrotray.exe" process seems to fix
the problem: after doing that, PD works fine.
Acrotray is something related to Adobe Acrobat or Acrobat Reader. What
relation it can have with PD is beyond my understanding.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2952825&group_…
Bugs item #2952825, was opened at 2010-02-16 16:10
Message generated for change (Comment added) made by sistisette
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2952825&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: v0.42
>Status: Open
Resolution: Works For Me
Priority: 5
Private: No
Submitted By: Matteo Sisti Sette (sistisette)
Assigned to: Nobody/Anonymous (nobody)
Summary: pd hangs in windows Vista and won't work until system reboot
Initial Comment:
Sometimes (unfortunately I haven't observed any apparent cause that triggers the problem), I open PD and it won't create a new patch (file/new) nor open any patch (file/open). It won't even quit untill I kill the process, and clicking on "DIO errors" doesn't produce any printout.
Furthermore, all menus of the menu bar are empty (only a "--" item) except the File menu.
Even if I kill and restart PD, it won't ever work, untill I reboot the operating system, then everything is fine.
This is PD Vanilla 0.42.5 on Windows Vista.
When it gets "frozen" like this, if I launch it with -lib Gem (I have Gem installed), it won't print the usual Gem output on the console (no output at all).
After reboot, everything usually works.
This happens every once in a while, and it is NOT necessary after some crash or anything.
----------------------------------------------------------------------
>Comment By: Matteo Sisti Sette (sistisette)
Date: 2010-06-02 01:45
Message:
It's not always acrotray.exe. It has happened to me that killing
acrotray.exe didn't fix it and killing some other apparently random process
did.
And no, killing pd.exe does not fix it. When this happens, I have to kill
random processes (well not actually random: I try to kill those that i know
or guess that are useless or safe to kill) until I find one that works,
I'm not sure whether killing other processes without _also_ restarting Pd
works, because usually it goes as follows:
- first I restart Pd, and it's frozen again
- I close it, kill some process and open Pd again
- and so on, until it works.
Well, for this same reason maybe I didn't actually try killing pd.exe with
the task manager, but I certainly did check the task manager to ensure
there was no extra pd.exe process.
Note that these freezings I'm talking about are ALWAYS at Pd startup: I
start Pd and it's already frozen. It has never happened to me that it hangs
like this (and won't recover afret restart).
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-06-01 23:40
Message:
- try killing pd.exe in the Windows Task Manager, that has always done it
for me
- I haven't been able to reproduce this using recent builds of Pd-extended
0.42.5 on Windows XP and Windows 7.
- otherwise, it sounds like some weirdness with acrotray is the issue
----------------------------------------------------------------------
Comment By: Matteo Sisti Sette (sistisette)
Date: 2010-02-16 16:16
Message:
I've just found out that killing the "acrotray.exe" process seems to fix
the problem: after doing that, PD works fine.
Acrotray is something related to Adobe Acrobat or Acrobat Reader. What
relation it can have with PD is beyond my understanding.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2952825&group_…
Bugs item #2952825, was opened at 2010-02-16 10:10
Message generated for change (Settings changed) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2952825&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
>Group: v0.42
>Status: Pending
>Resolution: Works For Me
Priority: 5
Private: No
Submitted By: Matteo Sisti Sette (sistisette)
Assigned to: Nobody/Anonymous (nobody)
Summary: pd hangs in windows Vista and won't work until system reboot
Initial Comment:
Sometimes (unfortunately I haven't observed any apparent cause that triggers the problem), I open PD and it won't create a new patch (file/new) nor open any patch (file/open). It won't even quit untill I kill the process, and clicking on "DIO errors" doesn't produce any printout.
Furthermore, all menus of the menu bar are empty (only a "--" item) except the File menu.
Even if I kill and restart PD, it won't ever work, untill I reboot the operating system, then everything is fine.
This is PD Vanilla 0.42.5 on Windows Vista.
When it gets "frozen" like this, if I launch it with -lib Gem (I have Gem installed), it won't print the usual Gem output on the console (no output at all).
After reboot, everything usually works.
This happens every once in a while, and it is NOT necessary after some crash or anything.
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-06-01 17:40
Message:
- try killing pd.exe in the Windows Task Manager, that has always done it
for me
- I haven't been able to reproduce this using recent builds of Pd-extended
0.42.5 on Windows XP and Windows 7.
- otherwise, it sounds like some weirdness with acrotray is the issue
----------------------------------------------------------------------
Comment By: Matteo Sisti Sette (sistisette)
Date: 2010-02-16 10:16
Message:
I've just found out that killing the "acrotray.exe" process seems to fix
the problem: after doing that, PD works fine.
Acrotray is something related to Adobe Acrobat or Acrobat Reader. What
relation it can have with PD is beyond my understanding.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2952825&group_…
Bugs item #2890661, was opened at 2009-11-02 06:59
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2890661&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: pd-extended
>Group: v0.42
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: georg (fricklr)
Assigned to: Miller Puckette (millerpuckette)
Summary: dsp on/off shortcuts crash pd winxp and "use callbacks"
Initial Comment:
using the shortcuts ctrl+/ or ctrl+. crashes pd
tested on winxp ext 0.42.5 an 0.43
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-06-01 17:37
Message:
Yeah, I could reproduce something similar. On Windows 7 using Pd-extended
0.42.5-rc1, I switch the audio to ASIO using ASIO4ALL, then opening up Test
Audio and MIDI. While the sound was playing I switched the audio setting
to MMIO and Pd hung. I didn't mess with 'use callbacks'. But now I can't
reproduce it. So it seems like the workaround is to set the audio with the
DSP off.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-01-27 18:02
Message:
There might be an issue related to "use callbacks", since that is new and
relatively untested. Does the same crash happen for you when using
Pd-vanilla?
----------------------------------------------------------------------
Comment By: georg (fricklr)
Date: 2010-01-27 03:09
Message:
i found out it crashes only if "use callbacks" is on maybe really just an
issue with my driver
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-01-26 18:36
Message:
I can't reproduce this on WinXP fully updated using Pd-extended
0.42.5-20100120 or Pd-devel 0.43.0-20100120
I am guessing it might be an issue with your audio interface or driver.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2890661&group_…
Patches item #2893947, was opened at 2009-11-07 16:23
Message generated for change (Settings changed) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=2893947&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: puredata
>Group: None
Status: Open
Resolution: Fixed
Priority: 6
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Miller Puckette (millerpuckette)
Summary: audio doesn't reconnect after sleep on Mac OS X
Initial Comment:
If you have Pd open on Mac OS X, and the computer goes to sleep, Pd looses connection to the audio, and you either need to restart or select the audio API again in order to get sound. Mac OS X can send sleep/wake events, so Pd should register to get these, and use them to reconnect to the audio when the machine wakes up.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-05-17 18:46
Message:
Turns out it was easier and more effective to disable the 'audio stuck'
code, which was done in Pd-extended 0.42.5:
http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=rev&sortby=date&…
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=2893947&group_…