Patches item #1739650, was opened at 2007-06-19 06:58
Message generated for change (Comment added) made by mrpeach
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1739650&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: feature
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Martin Peach (mrpeach)
Summary: add default OSC-path to packOSC
Initial Comment:
this patch adds a message "prefix <symbol>" to the [packOSC] object, which adds a default OSC-prefix to all OSC-paths.
e.g. [prefix /bla, send /forth 1 2 3( will output the binary representation of the OSC-message "/bla/forth 1 2 3"
this is only for convenience, but when you are transmitting large numbers of osc-messages, prefixing each and everyone via pd's internal string-manipulation mechanisms can be rather slow. this should be faster...
----------------------------------------------------------------------
>Comment By: Martin Peach (mrpeach)
Date: 2007-06-20 16:42
Message:
Logged In: YES
user_id=919007
Originator: NO
OK, done.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1739650&group_…
Patches item #1739651, was opened at 2007-06-19 07:02
Message generated for change (Comment added) made by mrpeach
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1739651&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: feature
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Martin Peach (mrpeach)
Summary: convert non-"send" messages to OSC-messages via [packOSC]
Initial Comment:
this patch adds the ability to [packOSC] to send messages even when they are not prefixed with the "send" selector.
messages to be converted into osc-packets must have a selector starting with "/", which will become the OSC-path.
example:
"/bi/ba/bo 1 2 3" is the same as "send /bi/ba/bo 1 2 3"
reasoning:
- when dealing with large numbers of osc-messages, prepending "send" to each of them can become rather tireseome and cpu-consuming
- the "send" label is a suboptimal choice anyhow ([packOSC] does not know anything about "send"ing)
----------------------------------------------------------------------
>Comment By: Martin Peach (mrpeach)
Date: 2007-06-20 16:39
Message:
Logged In: YES
user_id=919007
Originator: NO
Done, also 'send' is still there for backwards compatibility.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1739651&group_…
Patches item #1739655, was opened at 2007-06-19 07:09
Message generated for change (Comment added) made by mrpeach
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1739655&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: feature
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Martin Peach (mrpeach)
Summary: automatically "send" lists with [udpsend]
Initial Comment:
with this patch one can use [udpsend] to send data without having to prepend the "send" selector to each message.
everything that is a "list" will automatically be "send".
e.g.
"1 2 3 59" is the same as "send 1 2 3 59"
"list /tmp/test.txt" is the same as "send /tmp/test.txt"
reasoning:
- when dealing with a lot of messages to be sent, it quickly becomes tiresome and cpu-consuming to have to prepend "send" to every message.
- lists are the native type of "data" in pd (as opposed to "commands"); [udpsend]s native way to deal with "data" is to send it (special behaviour like (dis)connecting is done via special messages)
might be that my reasoning is not completely in-line with pd-vanilla (compare the "send" message to [netsend])
if this gets accepted, [tcpsend] should also be modified accordingly
----------------------------------------------------------------------
>Comment By: Martin Peach (mrpeach)
Date: 2007-06-20 16:38
Message:
Logged In: YES
user_id=919007
Originator: NO
OK,good idea. I changed udpsend, also made the same change to tcpsend,
tcpclient and tcpserver.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1739655&group_…
Patches item #1561099, was opened at 2006-09-19 01:55
Message generated for change (Settings changed) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1561099&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: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Miller Puckette (millerpuckette)
Summary: Unused vars
Initial Comment:
Here is a patch with unused variables throughout PD.
It'll help readability.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1561099&group_…
Patches item #1739651, was opened at 2007-06-19 13:02
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1739651&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: feature
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Martin Peach (mrpeach)
Summary: convert non-"send" messages to OSC-messages via [packOSC]
Initial Comment:
this patch adds the ability to [packOSC] to send messages even when they are not prefixed with the "send" selector.
messages to be converted into osc-packets must have a selector starting with "/", which will become the OSC-path.
example:
"/bi/ba/bo 1 2 3" is the same as "send /bi/ba/bo 1 2 3"
reasoning:
- when dealing with large numbers of osc-messages, prepending "send" to each of them can become rather tireseome and cpu-consuming
- the "send" label is a suboptimal choice anyhow ([packOSC] does not know anything about "send"ing)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1739651&group_…
Patches item #1739650, was opened at 2007-06-19 12:58
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1739650&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: feature
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Martin Peach (mrpeach)
Summary: add default OSC-path to packOSC
Initial Comment:
this patch adds a message "prefix <symbol>" to the [packOSC] object, which adds a default OSC-prefix to all OSC-paths.
e.g. [prefix /bla, send /forth 1 2 3( will output the binary representation of the OSC-message "/bla/forth 1 2 3"
this is only for convenience, but when you are transmitting large numbers of osc-messages, prefixing each and everyone via pd's internal string-manipulation mechanisms can be rather slow. this should be faster...
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1739650&group_…
Bugs item #1738708, was opened at 2007-06-17 12:53
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1738708&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: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Miller Puckette (millerpuckette)
Summary: won't open files with $0 in file name
Initial Comment:
In Pd-0.40-2, it won't open a file that has a $0 in the filename. This works fine on Pd-0.39.2-extended-rc4 and Pd-0.39-2.
This is on Mac OS X/Intel 10.4.9
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-06-18 18:05
Message:
Logged In: YES
user_id=27104
Originator: YES
The original example file should be called "array with $0.pd".
As for how to handle these, I don't think we should do anything special
for abstractions, they can be left as is, otherwise it'll induce confusion,
IMHO. I am just thinking that people's patches might have something like
"this patch earned me $2.pd" and they would like to be able to open it.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2007-06-18 05:03
Message:
Logged In: YES
user_id=569446
Originator: NO
If you move the $0 in the filename to the front of the filename like
$0-file.pd, then no version of Pd I know of can open them from the menu,
including pd-extended. All Pd-versions open the file using the command line
quite okay, but even then saving the file still doesn't work.
Ths isn't restricted to $0, the same also happens for other
dollar-variables like $1-file.pd.
Maybe the more interesting question is: How should Pd deal with these
filenames? $1 for example is treated as a variable in object names, that is
replaced by the abstraction argument. If I use an abstraction [$1-file]
then in fact I'm trying to load a file depending on the value of $1 in
Pd-space, for example "0-file.pd". To be able to actually use the dollar in
the object name, we'd need a more general escaping mechanism which would
allow using an abstraction with an escaped dollar sign, for example
[\$1-file]. This however is a much bigger problem to solve in a smart (or
in a stupid) way.
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2007-06-18 03:45
Message:
Logged In: YES
user_id=564396
Originator: NO
so this time to concentrate on objects with "$0" in them, e.g. [parent$0]
or [array-with-$0]
these do not load anymore on recent versions of pd, since the $0 is
expanded at runtime, therefore pd is in fact looking for an object e.g.
[parent1004] (which it cannot find).
i do not see any solution for this, unless you do not want in-symbol
expansion of $args (which i think we all agreed is a good thing to have).
obviously one could make a special rule for $0 in object names (this is:
the 0th argument of an object box; all other arguments should be treated
"normally"); but i do think that this is counterproductive ($args are
complicated to understand anyhow; adding exception rules will make things
only worse)
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2007-06-18 03:40
Message:
Logged In: YES
user_id=564396
Originator: NO
could you add an example? i am not sure how you try to open the file:
- via the file->open menu?
- via a message?
- as abstraction?
- ...?
what is the expected behaviour in the light of the extended
$arg-expansion?
(e.g is it related to the [parent$0] problem? there won't be a solution
for this until we there is an escaping mechanism)
i am not sure i can reproduce any problem with the attached file on
0.40-1: it downloads as "array" (without extension), so i had to rename it
to array.pd; but i guess this has exactly undone the problem you described.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1738708&group_…
Bugs item #1727221, was opened at 2007-05-29 05:45
Message generated for change (Comment added) made by stffn
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1727221&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.39.2
Status: Open
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: pdp_ieee1394 doesn't load on Mac OS X
Initial Comment:
It looks like pdp_ieee1394 builds properly, but it does not load at all on Mac OS X. It acts as if the object does not exist. This is on Pd-0.39.2-extended-rc2.
----------------------------------------------------------------------
Comment By: stffn (stffn)
Date: 2007-06-18 11:45
Message:
Logged In: YES
user_id=1658640
Originator: NO
doh. thats how much i know about pdp.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-06-18 02:23
Message:
Logged In: YES
user_id=27104
Originator: YES
This now works find for me.
As for your error message, stffn, it looks like you don't have X11
installed. It's an extra install from the Mac OS X install DVD.
----------------------------------------------------------------------
Comment By: stffn (stffn)
Date: 2007-06-16 11:30
Message:
Logged In: YES
user_id=1658640
Originator: NO
On RC3 it doesn't create here (os x.4.9, macbook core duo). Instead, at
startup, this msg. is printed to the console:
/Applications/Pd-extended.app/Contents/Resources/Scripts/../extra/pdp.pd_darwin:
dlopen(/Applications/Pd-extended.app/Contents/Resources/Scripts/../extra/pdp.pd_darwin,
10): Library not loaded: /usr/X11R6/lib/libX11.6.dylib
Referenced from:
/Applications/Pd-extended.app/Contents/Resources/Scripts/../extra/pdp.pd_darwin
Reason: image not found
pdp: can't load library
/Applications/Pd-extended.app/Contents/Resources/Scripts/../extra/pidip.pd_darwin:
dlopen(/Applications/Pd-extended.app/Contents/Resources/Scripts/../extra/pidip.pd_darwin,
10): Library not loaded: /usr/X11R6/lib/libX11.6.dylib
Referenced from:
/Applications/Pd-extended.app/Contents/Resources/Scripts/../extra/pidip.pd_darwin
Reason: image not found
pidip: can't load library
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-06-12 05:58
Message:
Logged In: YES
user_id=27104
Originator: YES
it's working on my Intel Mac, can anyone else confirm it works for them?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1727221&group_…
Bugs item #1738289, was opened at 2007-06-16 12:06
Message generated for change (Comment added) made by fbar
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1738289&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: None
Priority: 3
Private: No
Submitted By: Frank Barknecht (fbar)
Assigned to: Miller Puckette (millerpuckette)
Summary: "View list" listview broken for arrays with $0 in name
Initial Comment:
The "View list" function in the Properties context menu of arrays is broken, if the name of the array contains a $0. This only affects visible arrays in graphs, arrays in [table] objects work correctly with $0-names.
See attached test patch for a demonstration.
The error message given by Tk is:
can't read "0": no such variable
can't read "0": no such variable
while executing
"array_viewlist .gfxstub82e3a78 $0-array 0"
invoked from within
".gfxstub82e3a78.listview invoke"
("uplevel" body line 1)
invoked from within
"uplevel #0 [list $w invoke]"
(procedure "tk::ButtonUp" line 22)
invoked from within
"tk::ButtonUp .gfxstub82e3a78.listview"
(command bound to event)
----------------------------------------------------------------------
>Comment By: Frank Barknecht (fbar)
Date: 2007-06-18 11:09
Message:
Logged In: YES
user_id=569446
Originator: YES
Please don't use spaces in filenames here, their names get mangled by
Sourceforge. I deleted the new example patch to not confuse readers. I
think the first example I posted already was illustrating the bug
sufficiently.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-06-17 18:49
Message:
Logged In: YES
user_id=27104
Originator: NO
Yup, same for me on Mac OS X 10.4.9 using Pd-0.39.2-extended-rc4 and Pd
0.40-2.
File Added: array with dollar zero.pd
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2007-06-17 11:14
Message:
Logged In: YES
user_id=569446
Originator: YES
It seems any version is affected.
I tested with CVS HEAD (0.4x) and pd-ext 0.39 rc-2.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-06-17 03:31
Message:
Logged In: YES
user_id=27104
Originator: NO
Which version of Pd? I hope it's not my bug ;) The version can be set in
the "Group" pulldown menu in the bug report form.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1738289&group_…
Bugs item #1738708, was opened at 2007-06-17 18:53
Message generated for change (Comment added) made by fbar
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1738708&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: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Miller Puckette (millerpuckette)
Summary: won't open files with $0 in file name
Initial Comment:
In Pd-0.40-2, it won't open a file that has a $0 in the filename. This works fine on Pd-0.39.2-extended-rc4 and Pd-0.39-2.
This is on Mac OS X/Intel 10.4.9
----------------------------------------------------------------------
>Comment By: Frank Barknecht (fbar)
Date: 2007-06-18 11:03
Message:
Logged In: YES
user_id=569446
Originator: NO
If you move the $0 in the filename to the front of the filename like
$0-file.pd, then no version of Pd I know of can open them from the menu,
including pd-extended. All Pd-versions open the file using the command line
quite okay, but even then saving the file still doesn't work.
Ths isn't restricted to $0, the same also happens for other
dollar-variables like $1-file.pd.
Maybe the more interesting question is: How should Pd deal with these
filenames? $1 for example is treated as a variable in object names, that is
replaced by the abstraction argument. If I use an abstraction [$1-file]
then in fact I'm trying to load a file depending on the value of $1 in
Pd-space, for example "0-file.pd". To be able to actually use the dollar in
the object name, we'd need a more general escaping mechanism which would
allow using an abstraction with an escaped dollar sign, for example
[\$1-file]. This however is a much bigger problem to solve in a smart (or
in a stupid) way.
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2007-06-18 09:45
Message:
Logged In: YES
user_id=564396
Originator: NO
so this time to concentrate on objects with "$0" in them, e.g. [parent$0]
or [array-with-$0]
these do not load anymore on recent versions of pd, since the $0 is
expanded at runtime, therefore pd is in fact looking for an object e.g.
[parent1004] (which it cannot find).
i do not see any solution for this, unless you do not want in-symbol
expansion of $args (which i think we all agreed is a good thing to have).
obviously one could make a special rule for $0 in object names (this is:
the 0th argument of an object box; all other arguments should be treated
"normally"); but i do think that this is counterproductive ($args are
complicated to understand anyhow; adding exception rules will make things
only worse)
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2007-06-18 09:40
Message:
Logged In: YES
user_id=564396
Originator: NO
could you add an example? i am not sure how you try to open the file:
- via the file->open menu?
- via a message?
- as abstraction?
- ...?
what is the expected behaviour in the light of the extended
$arg-expansion?
(e.g is it related to the [parent$0] problem? there won't be a solution
for this until we there is an escaping mechanism)
i am not sure i can reproduce any problem with the attached file on
0.40-1: it downloads as "array" (without extension), so i had to rename it
to array.pd; but i guess this has exactly undone the problem you described.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1738708&group_…