Bugs item #2957058, was opened at 2010-02-23 01:11
Message generated for change (Settings changed) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2957058&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: None
>Status: Open
Resolution: None
Priority: 7
Private: No
Submitted By: Jonathan Wilkes (jancsika1)
Assigned to: Nobody/Anonymous (nobody)
Summary: pointer to [route symbol]-[print] crashes pd
Initial Comment:
[namecanvas foo]
[traverse foo, bang(
|
[pointer]
|
[route symbol]
|
[print]
1) a pointer message is erroneously routed as a symbol
2) this crashes Pd
3) [route pointer] doesn't route a pointer
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 23:31
Message:
There are a number of "types" in pd:
[symbol] [float] [list] [bang] [pointer]
[trigger symbol float list bang pointer]
[route] does [route symbol float list bang] so it is inconsistent that
[route pointer] would not route the "pointer" atom type, and instead route
based on the "pointer" as a symbolic selector. That right there is a bug
IMHO.
As for the crash, I could also reproduce it using Pd version
0.42.5-extended-20100410 or pd-gui-rewrite 0.43 on Mac OS X 10.5.8/Intel.
The crash is actually in the [print], not the [route]. When I remove the
[print], it doesn't crash.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-03-01 16:58
Message:
Oops, I didn't realize that when lists get distributed the atoms are
interpreted, just like the [list] object classes. E.g., I though the
following would output an error but it works fine:
[list one two(
|
[select symbol]
You know, since [route list] has different behaviors depending on whether
the first element is a float or symbol, the same could be done for [route
pointer]-- strip the selector off of anythings, pass gpointer messages
through unchanged. That way there is at least some consistency, in the
sense that the selector is always being matched.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2010-03-01 13:41
Message:
Hi Jonathan,
that's not really what I meant. You can use pointers in a list-message of
course ("list <pt1> <pt2> <pt3>") or [pack/unpack] many of them and so on.
Even [pipe] works with pointers and lists of pointers now.
But when you strip a lone pointer from it's selector then the pointer
itself could become the selector like: "list set 2"->[route list] becomes
"set 2" and this will call the "set"-method of the next object. If this is
a message box it will be set to "2".
But with a pointer you'd get "pointer <pt>" -> [route pointer] -> "<pt>",
so now it would try to use some "<pt>" method, which is probably
undefined. BTW: I guess that's what leads to the crash here. I think
selectors must be symbols.
So to make use of the pointless pointer (pun intended :) one probably has
to attach a selector again with [list] or [pointer] or something.
Anyway I guess we're now talking about the usefulness of route's
implementation, which is debatable and led to the development of several
nicer variants in GridFlow.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-03-01 12:48
Message:
Hi Frank,
Is it really useless? If you send a gpointer through the following,
it works:
[rewind $1(
|
[pointer]
That's a meta message consisting of a symbol-atom and a pointer-atom. And
the pointer atom gets sent successfully to the right inlet. However, I
can't currently find a way to test sending a single pointer-atom to the
left inlet. (If you try to strip it with list trim you always end up with
the "list" selector.)
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-03-01 07:16
Message:
I meant to write:
useless just like a "gem_state" stripped of its *selector*.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-03-01 07:15
Message:
First I have to correct myself: The selector of a pointer-message is indeed
"pointer", as can be seen with zexy's new rawprint object or by exploiting
the error message of an object like [select] when sent a pointer which is
"no method for 'pointer'".
So "route pointer" could or maybe should indeed route a "pointer"
meta-message just like it can route a "gem_state" message However as
[route] also strips off the selector you would be left with just the
pointer that is more or less useless just like a "gem_state" stripped of
its pointer cannot be used in the gem chain anymore.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-02-28 22:11
Message:
(pointer) with the g missing is what is specified in m_atom.c for
displaying a pointer atom. So I assume there's a difference between a
pointer message and a pointer atom.
There are two reasons to [route] pointer messages.
1) Didactic-- [route] is a common object people use to learn about the
behavior of messages in Pd. It would be nice to show all the predefined
message types going to different outlets, which can't currently happen
because [route] doesn't differentiate between pointers and anythings.
2) Because anythings and pointers aren't differentiated, this diminishes
the flexibility of an abstraction inlet. So a data-structure related
abstraction that wants to take "set," "flush", "clear", and pointer
messages to the left inlet and do something else with the right inlet has
to add an additional inlet. The [pointer] object can differentiate between
a pointer and "rewind," for example. An abstraction should be able to have
the same flexibility.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-02-25 11:37
Message:
Yep, a gpointer is not simply a message composed of "pointer" and some
actual pointer blob. I don't know the exact details myself and don't really
understand the source code, but they seem to be something very "special"
just like signals are. As you know, [print] shows them as a not very
helpful "(gpointer)", but if you pass a pointer to [list prepend set]-[list
trim] and into a message box: There pointers show up as "(pointer)" with
the "g" missing. Anyway don't bother trying [route (pointer)], it doesn't
work either. :)
In the end we probably have to accept that gpointers don't have a
"printable" selector, just like audio signals don't have one. Introducing a
print- and routable selector as "pointer" may be useful, or maybe it's not,
as some people may already use "pointer" as a meta-message in their
patches, for example to handle mouse-"pointer" events or so.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-02-25 00:54
Message:
Hm, I'm just not understanding something about gpointers-- I'd just assumed
when you send a pointer message it consists of the selector "pointer"
followed by the gpointer itself (gridflow's [display] seems to confirm
this). But clearly something else is going on because [route pointer]
doesn't currently work for gpointers, nor will [pointer] accept a gpointer
that has passed through [pointer $1( (though [route] will, without
crashing, and output a usable gpointer that has the selector "list").
It also seems like "pointer 1 2 3" is an unchecked case of "bad arguments
to message 'pointer'". So I guess I'm saying I agree that [route pointer]
should route according to the selector "pointer", I just don't understand
why a gpointer wouldn't match under those conditions.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-02-23 03:40
Message:
Hi Jonathan,
I raised the priority as crashes are really serious. I disagree with your
item 3), though. [route pointer] should not route GPointers, but
meta-messages starting with the symbol "pointer" e.g.
[pointer 1 2 3(
|
[route pointer]
|
It does that just fine.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2957058&group_…
Bugs item #2957058, was opened at 2010-02-23 01:11
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2957058&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: None
>Status: Pending
Resolution: None
Priority: 7
Private: No
Submitted By: Jonathan Wilkes (jancsika1)
Assigned to: Nobody/Anonymous (nobody)
Summary: pointer to [route symbol]-[print] crashes pd
Initial Comment:
[namecanvas foo]
[traverse foo, bang(
|
[pointer]
|
[route symbol]
|
[print]
1) a pointer message is erroneously routed as a symbol
2) this crashes Pd
3) [route pointer] doesn't route a pointer
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 23:31
Message:
There are a number of "types" in pd:
[symbol] [float] [list] [bang] [pointer]
[trigger symbol float list bang pointer]
[route] does [route symbol float list bang] so it is inconsistent that
[route pointer] would not route the "pointer" atom type, and instead route
based on the "pointer" as a symbolic selector. That right there is a bug
IMHO.
As for the crash, I could also reproduce it using Pd version
0.42.5-extended-20100410 or pd-gui-rewrite 0.43 on Mac OS X 10.5.8/Intel.
The crash is actually in the [print], not the [route]. When I remove the
[print], it doesn't crash.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-03-01 16:58
Message:
Oops, I didn't realize that when lists get distributed the atoms are
interpreted, just like the [list] object classes. E.g., I though the
following would output an error but it works fine:
[list one two(
|
[select symbol]
You know, since [route list] has different behaviors depending on whether
the first element is a float or symbol, the same could be done for [route
pointer]-- strip the selector off of anythings, pass gpointer messages
through unchanged. That way there is at least some consistency, in the
sense that the selector is always being matched.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2010-03-01 13:41
Message:
Hi Jonathan,
that's not really what I meant. You can use pointers in a list-message of
course ("list <pt1> <pt2> <pt3>") or [pack/unpack] many of them and so on.
Even [pipe] works with pointers and lists of pointers now.
But when you strip a lone pointer from it's selector then the pointer
itself could become the selector like: "list set 2"->[route list] becomes
"set 2" and this will call the "set"-method of the next object. If this is
a message box it will be set to "2".
But with a pointer you'd get "pointer <pt>" -> [route pointer] -> "<pt>",
so now it would try to use some "<pt>" method, which is probably
undefined. BTW: I guess that's what leads to the crash here. I think
selectors must be symbols.
So to make use of the pointless pointer (pun intended :) one probably has
to attach a selector again with [list] or [pointer] or something.
Anyway I guess we're now talking about the usefulness of route's
implementation, which is debatable and led to the development of several
nicer variants in GridFlow.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-03-01 12:48
Message:
Hi Frank,
Is it really useless? If you send a gpointer through the following,
it works:
[rewind $1(
|
[pointer]
That's a meta message consisting of a symbol-atom and a pointer-atom. And
the pointer atom gets sent successfully to the right inlet. However, I
can't currently find a way to test sending a single pointer-atom to the
left inlet. (If you try to strip it with list trim you always end up with
the "list" selector.)
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-03-01 07:16
Message:
I meant to write:
useless just like a "gem_state" stripped of its *selector*.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-03-01 07:15
Message:
First I have to correct myself: The selector of a pointer-message is indeed
"pointer", as can be seen with zexy's new rawprint object or by exploiting
the error message of an object like [select] when sent a pointer which is
"no method for 'pointer'".
So "route pointer" could or maybe should indeed route a "pointer"
meta-message just like it can route a "gem_state" message However as
[route] also strips off the selector you would be left with just the
pointer that is more or less useless just like a "gem_state" stripped of
its pointer cannot be used in the gem chain anymore.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-02-28 22:11
Message:
(pointer) with the g missing is what is specified in m_atom.c for
displaying a pointer atom. So I assume there's a difference between a
pointer message and a pointer atom.
There are two reasons to [route] pointer messages.
1) Didactic-- [route] is a common object people use to learn about the
behavior of messages in Pd. It would be nice to show all the predefined
message types going to different outlets, which can't currently happen
because [route] doesn't differentiate between pointers and anythings.
2) Because anythings and pointers aren't differentiated, this diminishes
the flexibility of an abstraction inlet. So a data-structure related
abstraction that wants to take "set," "flush", "clear", and pointer
messages to the left inlet and do something else with the right inlet has
to add an additional inlet. The [pointer] object can differentiate between
a pointer and "rewind," for example. An abstraction should be able to have
the same flexibility.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-02-25 11:37
Message:
Yep, a gpointer is not simply a message composed of "pointer" and some
actual pointer blob. I don't know the exact details myself and don't really
understand the source code, but they seem to be something very "special"
just like signals are. As you know, [print] shows them as a not very
helpful "(gpointer)", but if you pass a pointer to [list prepend set]-[list
trim] and into a message box: There pointers show up as "(pointer)" with
the "g" missing. Anyway don't bother trying [route (pointer)], it doesn't
work either. :)
In the end we probably have to accept that gpointers don't have a
"printable" selector, just like audio signals don't have one. Introducing a
print- and routable selector as "pointer" may be useful, or maybe it's not,
as some people may already use "pointer" as a meta-message in their
patches, for example to handle mouse-"pointer" events or so.
----------------------------------------------------------------------
Comment By: Jonathan Wilkes (jancsika1)
Date: 2010-02-25 00:54
Message:
Hm, I'm just not understanding something about gpointers-- I'd just assumed
when you send a pointer message it consists of the selector "pointer"
followed by the gpointer itself (gridflow's [display] seems to confirm
this). But clearly something else is going on because [route pointer]
doesn't currently work for gpointers, nor will [pointer] accept a gpointer
that has passed through [pointer $1( (though [route] will, without
crashing, and output a usable gpointer that has the selector "list").
It also seems like "pointer 1 2 3" is an unchecked case of "bad arguments
to message 'pointer'". So I guess I'm saying I agree that [route pointer]
should route according to the selector "pointer", I just don't understand
why a gpointer wouldn't match under those conditions.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2010-02-23 03:40
Message:
Hi Jonathan,
I raised the priority as crashes are really serious. I disagree with your
item 3), though. [route pointer] should not route GPointers, but
meta-messages starting with the symbol "pointer" e.g.
[pointer 1 2 3(
|
[route pointer]
|
It does that just fine.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2957058&group_…
Bugs item #2957057, was opened at 2010-02-23 01:06
Message generated for change (Settings changed) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2957057&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: externals
>Group: v0.42
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: Jonathan Wilkes (jancsika1)
>Assigned to: Hans-Christoph Steiner (eighthave)
Summary: pddplink and pddp/dsp don't play well together
Initial Comment:
If you use pddplink and pddp/dsp in the same patch, pddplink gives the following error:
pddplink: internal error (open [path to the file shown in the link] )
This is caused by [r pd] in pddp/dsp. (Matju wrote something on the list about why this happens, but I can't seem to find it at the moment)
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 23:21
Message:
I couldn't reproduce this with Pd version 0.42.5-extended-20100405 on Mac
OS X 10.5.8/Intel but I suspect it was also fixed by recent pddplink
changes for bugs 2960967 and 2959373
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2957057&group_…
Bugs item #2959373, was opened at 2010-02-25 22:26
Message generated for change (Settings changed) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2959373&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: externals
>Group: v0.42
>Status: Pending
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Jonathan Wilkes (jancsika1)
>Assigned to: Hans-Christoph Steiner (eighthave)
Summary: pddplink doesn't handle relative paths correctly
Initial Comment:
The attached example shows the problem clearly. If you use the link in main.pd it will open ./myPatch.pd, but myPatch.pd will erroneously inherit the path of the canvas that contains the link. Thus helperAbstraction won't create because ./folder is not searched.
You can see this clearly in the window heading of myPatch.pd after you follow the link: it lists the object as "./folder/myPatch.pd" and the path as that of main.pd. But if you make an object [./folder/myPatch.pd] in main.pd and open it, you can see it correctly lists the object as "myPatch.pd" and makes ./folder part of the path. This is what pddplink should do, too.
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 23:10
Message:
Fixed with this commit:
http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=rev&revision=134…
And also fixed it within the menu_doc_open command in pd-extended and
pd-gui-rewrite:
http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=rev&revision=134…
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2959373&group_…
Bugs item #2975654, was opened at 2010-03-23 22:54
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2975654&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: None
Status: Closed
Resolution: Duplicate
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Feedback glitch
Initial Comment:
Can't run any PD patches without a persistent beeping glitching sound. Internal and external sound card.
Any help is appreciated.
Thanks!
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 22:16
Message:
This artifact has been marked as a duplicate of artifact 1561839 with
reason:
No explanation provided.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 17:34
Message:
This sounds like the classic "rhythmic glitching on PowerBook G4" bug:
https://sourceforge.net/tracker/index.php?func=detail&aid=1561839&group_id=…
Try a 0.42.5 nightly build:
http://autobuild.puredata.info/auto-build/latest/Pd-0.42.5-extended-macosx1…
----------------------------------------------------------------------
Comment By: SourceForge Robot (sf-robot)
Date: 2010-04-07 22: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: IOhannes m zmlnig (zmoelnig)
Date: 2010-03-24 04:39
Message:
did you try pd-vanilla? how does it work there?
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2010-03-24 04:39
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=2975654&group_…
Bugs item #2049943, was opened at 2008-08-13 13:19
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2049943&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.40.2
Status: Deleted
Resolution: Duplicate
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: puredata sound glitch
Initial Comment:
I've recently downloaded Pure Data extended (0.40.3) on a PowerBook G4 with OS X (10.4.11) [thanks, it looks like a platform I can work] and intend to input/output on an M-audio fast track pro. However, when I play an audio patch or the test audio patch, I get this glitch that pulses at about 100 bpm. When I press DIO I get:
audio I/O error history:
seconds ago error type
3.14 unknown
3.14 unknown
3.14 unknown
If I press it again the numbers increase.
I don't how to fix. Please help.
-Joe
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 22:15
Message:
This artifact has been marked as a duplicate of artifact 1561839 with
reason:
No explanation provided.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2008-08-14 19:52
Message:
Logged In: YES
user_id=27104
Originator: NO
duplicate of [ 1561839 ] rhythmic glitching on PowerBook G4
----------------------------------------------------------------------
Comment By: ClaudiusMaximus (claudiusmaximus)
Date: 2008-08-13 13:24
Message:
Logged In: YES
user_id=769033
Originator: NO
looks like a duplicate of this:
https://sourceforge.net/tracker/index.php?func=detail&aid=1561839&group_id=…
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2049943&group_…
Bugs item #2960764, was opened at 2010-02-28 12:48
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2960764&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: Nobody/Anonymous (nobody)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: System Crash with PD
Initial Comment:
Hello,
I have a windows xp intel atom processor with 2 gb of ram (it's a fairly nice netbook). I'm running Pd version 0.42-5 compiled for Microsoft Windows.
After I close pd, i check my system programs and pd.exe stays running taking up like 70% of my cpu processing. If I choose to end task it the I get a blue screen system failure and the computer restarts. So two issues: one pd.exe won't close, and two when i try to close it, it crashes my computer. Also, I noticed each time I started pd an added icon of the AISO sound driver pops up and i'm not sure why thats happening but it could be connect to a driver issue I guess.
Here's some event logs.
Application log
Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: 2/28/2010
Time: 1:39:50 AM
User: N/A
Computer: YOUR-W5VBZ7LYQ8
Description:
Hanging application wish84.exe, version 8.4.2.18, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 48 61 6e 67 ion Hang
0010: 20 20 77 69 73 68 38 34 wish84
0018: 2e 65 78 65 20 38 2e 34 .exe 8.4
0020: 2e 32 2e 31 38 20 69 6e .2.18 in
0028: 20 68 75 6e 67 61 70 70 hungapp
0030: 20 30 2e 30 2e 30 2e 30 0.0.0.0
0038: 20 61 74 20 6f 66 66 73 at offs
0040: 65 74 20 30 30 30 30 30 et 00000
0048: 30 30 30 000
System log:
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 2/28/2010
Time: 1:35:20 AM
User: N/A
Computer: YOUR-W5VBZ7LYQ8
Description:
Error code 100000d1, parameter1 00000000, parameter2 00000002, parameter3 00000000, parameter4 a91ecab0.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 64 100000d
0020: 31 20 20 50 61 72 61 6d 1 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 30 2c 20 000000,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 61 39 31 65 00, a91e
0050: 63 61 62 30 cab0
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 22:12
Message:
Pd can't directly cause a blue screen crash, but it can trigger a bug which
does. My guess is that your sound card driver has the bug, especially
since the ASIO stuff is popping up.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2960764&group_…
Bugs item #2969731, was opened at 2010-03-12 20:51
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2969731&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: Works For Me
Priority: 5
Private: No
Submitted By: Jonathan Wilkes (jancsika1)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: Can't open multiple files at once
Initial Comment:
In Pd version 0.42.5-extended-20100309 on hardy, if I go to File->Open and select multiple files like abs-help.pd and acoustics-ehlp.pd, I get the following error:
File "/path to my reference files/abs-help.pd acoustics-help.pd" does not exist. This works on xp, however, and I can open the files separately in hardy.
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-04-12 17:54
Message:
I can't reproduce this on Pd version 0.42.5-extended-20100409 on
Ubuntu/Karmic Netbook Remix. I selected three files and all three opened.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2969731&group_…