http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here:
http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5).
pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.
There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.
• Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.
The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose.
There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well.
The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.
One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.
You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Thank you! Great news installed it and playing with it. Very good.
Lorenzo.
On 17/02/2012 21:02, Hans-Christoph Steiner wrote:
http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so weÂ’re looking for testers. Download a nightly build to try here:
http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they donÂ’t step on each otherÂ’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5).
pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. ThatÂ’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.
There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.
• Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.
The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose.
There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, itÂ’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well.
The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.
One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.
You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Thanks Hans!
I just tried on OS X Lion and got the following errors upon startup:
/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin: dlopen(/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin, 10): Symbol not found: _TclFreeObj Referenced from: /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin Expected in: dynamic lookup
/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../startup/tclpd: can't load startup library'!
Pretty fast startup though. :)
Cheers, Rich
On Sat, Feb 18, 2012 at 9:32 AM, Lorenzo Sutton lorenzofsutton@gmail.comwrote:
Thank you! Great news installed it and playing with it. Very good.
Lorenzo.
On 17/02/2012 21:02, Hans-Christoph Steiner wrote:
http://at.or.at/hans/blog/**2012/02/17/new-editing-** feature-of-pd-extended-0-43-**now-in-beta/http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43-now-in-beta/
The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here:
http://autobuild.puredata.**info/auto-build/latest/http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5).
pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.
There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.
• Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.
The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose.
There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well.
The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.
One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.
You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write?
______________________________**_________________ Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/**listinfo/pd-announcehttp://lists.puredata.info/listinfo/pd-announce
______________________________**_________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/** listinfo/pd-list http://lists.puredata.info/listinfo/pd-list
______________________________**_________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/** listinfo/pd-list http://lists.puredata.info/listinfo/pd-list
You're using the 64-bit Mac OS X version. That won't be a full release in 0.43 since there are some issues porting things away from Carbon that won't be resolved in time. The 64-bit version means you can address huge amounts of memory, but with 0.43 it means you will not have:
- Gem
- pdp
- gem2pdp
- tclpd
- hid
Other than that, everything should work fine. If anyone is interested in getting any of the above working on Mac OS X 64-bit sooner rather than later, I can point them where to work. Here's the general idea, in rough order of how much work it'd take:
pdp_qt, pdp_ieee1394: use 64-bit API to replace Quicktime and Carbon calls tclpd: make Pd work with Tk/Cocoa hid: use 64-bit API to replace Carbon calls gemwin, pix_video, pix_film, pix_image: use 64-bit API to replace Quicktime and Carbon calls gem2pdp: get Gem and pdp built
.hc
On Feb 18, 2012, at 1:00 AM, Rich E wrote:
Thanks Hans!
I just tried on OS X Lion and got the following errors upon startup:
/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin: dlopen(/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin, 10): Symbol not found: _TclFreeObj Referenced from: /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin Expected in: dynamic lookup
/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../startup/tclpd: can't load startup library'!
Pretty fast startup though. :)
Cheers, Rich
On Sat, Feb 18, 2012 at 9:32 AM, Lorenzo Sutton lorenzofsutton@gmail.com wrote: Thank you! Great news installed it and playing with it. Very good.
Lorenzo.
On 17/02/2012 21:02, Hans-Christoph Steiner wrote:
http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here:
http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5).
pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.
There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.
• Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.
The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose.
There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well.
The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.
One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.
You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
I have the audacity to believe that peoples everywhere can have three meals a day for their bodies, education and culture for their minds, and dignity, equality and freedom for their spirits. - Martin Luther King, Jr.
On Sun, Feb 19, 2012 at 4:20 AM, Hans-Christoph Steiner hans@at.or.atwrote:
You're using the 64-bit Mac OS X version. That won't be a full release in 0.43 since there are some issues porting things away from Carbon that won't be resolved in time. The 64-bit version means you can address huge amounts of memory, but with 0.43 it means you will not have:
Ah, got it. The i386 version works for me (I think the naming is a bit weird though, since I'm in OS X 10.7, not 10.5. It'd make more sense by appending the architecture, not OS X version), including gem and all other externals I tried so far (cpuload was missing, but that was already reported). The magic glass is really nifty! Saves alot of otherwise pointless number boxes.
One thing of concern however is the cpu usage when DSP is on and there are no patches open - Pd-0.43.1-extended-20120220 reports ~ 17% while Pd-0.43.1-vanilla reports 7%. What could be the cause of that?
Cheers, Rich
just wondering. how far has this has gone so far? anywhere?
gemwin, pix_video, pix_film, pix_image: use 64-bit API to replace Quicktime
BTW is this all done with a Gem plugin now? is that the idea? just to write a plugin for qtkit?
m
On Sat, Feb 18, 2012 at 12:20 PM, Hans-Christoph Steiner hans@at.or.at wrote:
You're using the 64-bit Mac OS X version. That won't be a full release in 0.43 since there are some issues porting things away from Carbon that won't be resolved in time. The 64-bit version means you can address huge amounts of memory, but with 0.43 it means you will not have:
- Gem
- pdp
- gem2pdp
- tclpd
- hid
Other than that, everything should work fine. If anyone is interested in getting any of the above working on Mac OS X 64-bit sooner rather than later, I can point them where to work. Here's the general idea, in rough order of how much work it'd take:
pdp_qt, pdp_ieee1394: use 64-bit API to replace Quicktime and Carbon calls tclpd: make Pd work with Tk/Cocoa hid: use 64-bit API to replace Carbon calls gemwin, pix_video, pix_film, pix_image: use 64-bit API to replace Quicktime and Carbon calls gem2pdp: get Gem and pdp built
.hc
On Feb 18, 2012, at 1:00 AM, Rich E wrote:
Thanks Hans!
I just tried on OS X Lion and got the following errors upon startup:
/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin: dlopen(/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin, 10): Symbol not found: _TclFreeObj Referenced from: /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin Expected in: dynamic lookup
/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../startup/tclpd: can't load startup library'!
Pretty fast startup though. :)
Cheers, Rich
On Sat, Feb 18, 2012 at 9:32 AM, Lorenzo Sutton lorenzofsutton@gmail.com wrote:
Thank you! Great news installed it and playing with it. Very good.
Lorenzo.
On 17/02/2012 21:02, Hans-Christoph Steiner wrote:
http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here:
http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5).
pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.
There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.
• Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.
The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose.
There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well.
The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.
One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.
You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
I have the audacity to believe that peoples everywhere can have three meals a day for their bodies, education and culture for their minds, and dignity, equality and freedom for their spirits. - Martin Luther King, Jr.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Yeah, its all plugins. I think the only progress is that someone wrote GLUT support for [gemwin], and Mac OS X supports GLUT. The rest still need to be done, but maybe could be supported by gmerlin.
.hc
On Feb 20, 2012, at 6:47 PM, m.e.grimm wrote:
just wondering. how far has this has gone so far? anywhere?
gemwin, pix_video, pix_film, pix_image: use 64-bit API to replace Quicktime
BTW is this all done with a Gem plugin now? is that the idea? just to write a plugin for qtkit?
m
On Sat, Feb 18, 2012 at 12:20 PM, Hans-Christoph Steiner hans@at.or.at wrote:
You're using the 64-bit Mac OS X version. That won't be a full release in 0.43 since there are some issues porting things away from Carbon that won't be resolved in time. The 64-bit version means you can address huge amounts of memory, but with 0.43 it means you will not have:
- Gem
- pdp
- gem2pdp
- tclpd
- hid
Other than that, everything should work fine. If anyone is interested in getting any of the above working on Mac OS X 64-bit sooner rather than later, I can point them where to work. Here's the general idea, in rough order of how much work it'd take:
pdp_qt, pdp_ieee1394: use 64-bit API to replace Quicktime and Carbon calls tclpd: make Pd work with Tk/Cocoa hid: use 64-bit API to replace Carbon calls gemwin, pix_video, pix_film, pix_image: use 64-bit API to replace Quicktime and Carbon calls gem2pdp: get Gem and pdp built
.hc
On Feb 18, 2012, at 1:00 AM, Rich E wrote:
Thanks Hans!
I just tried on OS X Lion and got the following errors upon startup:
>
/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin: dlopen(/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin, 10): Symbol not found: _TclFreeObj Referenced from: /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin Expected in: dynamic lookup
/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../startup/tclpd: can't load startup library'!
>
Pretty fast startup though. :)
Cheers, Rich
On Sat, Feb 18, 2012 at 9:32 AM, Lorenzo Sutton lorenzofsutton@gmail.com wrote:
Thank you! Great news installed it and playing with it. Very good.
Lorenzo.
On 17/02/2012 21:02, Hans-Christoph Steiner wrote:
http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here:
http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5).
pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.
There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.
• Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.
The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose.
There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well.
The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.
One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.
You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
I have the audacity to believe that peoples everywhere can have three meals a day for their bodies, education and culture for their minds, and dignity, equality and freedom for their spirits. - Martin Luther King, Jr.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- ____________________ m.e.grimm | m.f.a | ed.m. megrimm@gmail.com _________________________________
You can't steal a gift. Bird gave the world his music, and if you can hear it, you can have it. - Dizzy Gillespie
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-02-21 02:29, Hans-Christoph Steiner wrote:
Yeah, its all plugins. I think the only progress is that someone wrote GLUT support for [gemwin], and Mac OS X supports GLUT. The rest still need to be done, but maybe could be supported by gmerlin.
"someone" being the tireless Gem-development team. btw, the same people also bought you a [gemcocoawindow] which tries using the native windowing system on OSX.
and yes, somebody still needs to implement QTKit plugins.
fgmasdr IOhannes
Le 2012-02-17 à 15:02:00, Hans-Christoph Steiner a écrit :
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes.
It was already like that since the first version of pd ever, over 15 years ago. It's misleading to write it in the same paragraph as « the pd-gui side of Pd has been re-written from scratch ». You also don't state which part of the pd-gui has been rewritten from scratch, which obscures the fact that a large fraction of it hasn't been rewritten.
It's a bad idea to take credit for things that Miller had already done or that his contributors had done.
If you want to say, for example, that pd-extended 43 fixes a certain cause of hiccups due to bad sync between the two parts of pd, then you can say it like that, more or less, but a goal to keeping explanations simple doesn't entitle you to say what you have said.
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
I just wish that PD keeps the same philosophy of robustness and simplicity as before. Tuti
On Sat, Feb 18, 2012 at 2:54 PM, Mathieu Bouchard matju@artengine.ca wrote:
Le 2012-02-17 à 15:02:00, Hans-Christoph Steiner a écrit :
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes.
It was already like that since the first version of pd ever, over 15 years ago. It's misleading to write it in the same paragraph as « the pd-gui side of Pd has been re-written from scratch ». You also don't state which part of the pd-gui has been rewritten from scratch, which obscures the fact that a large fraction of it hasn't been rewritten.
It's a bad idea to take credit for things that Miller had already done or that his contributors had done.
If you want to say, for example, that pd-extended 43 fixes a certain cause of hiccups due to bad sync between the two parts of pd, then you can say it like that, more or less, but a goal to keeping explanations simple doesn't entitle you to say what you have said.
______________________________________________________________________ | Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC _______________________________________________ Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
That is for sure a goal. For the bare minimum, there is always Pd-vanilla.
.hc
On Feb 18, 2012, at 12:07 PM, Tuti wrote:
I just wish that PD keeps the same philosophy of robustness and simplicity as before. Tuti
On Sat, Feb 18, 2012 at 2:54 PM, Mathieu Bouchard matju@artengine.ca wrote:
It was already like that since the first version of pd ever, over 15 years ago. It's misleading to write it in the same paragraph as « the pd-gui side of Pd has been re-written from scratch ». You also don't state which part of the pd-gui has been rewritten from scratch, which obscures the fact that a large fraction of it hasn't been rewritten.
It's a bad idea to take credit for things that Miller had already done or that his contributors had done.
If you want to say, for example, that pd-extended 43 fixes a certain cause of hiccups due to bad sync between the two parts of pd, then you can say it like that, more or less, but a goal to keeping explanations simple doesn't entitle you to say what you have said. Le 2012-02-17 à 15:02:00, Hans-Christoph Steiner a écrit :
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes.
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
On Feb 18, 2012, at 11:54 AM, Mathieu Bouchard wrote:
Le 2012-02-17 à 15:02:00, Hans-Christoph Steiner a écrit :
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes.
It was already like that since the first version of pd ever, over 15 years ago. It's misleading to write it in the same paragraph as « the pd-gui side of Pd has been re-written from scratch ». You also don't state which part of the pd-gui has been rewritten from scratch, which obscures the fact that a large fraction of it hasn't been rewritten.
You are correct, the two process architecture has been there since the beginning, I guess my write-up was a bit unclear there. I only claim that the code for the 'pd-gui' process was rewritten, which is was. Every aspect of Pd's GUI was not rewritten. As I mentioned in that email, that is a target for some of us for 0.44.
It's a bad idea to take credit for things that Miller had already done or that his contributors had done.
If you want to say, for example, that pd-extended 43 fixes a certain cause of hiccups due to bad sync between the two parts of pd, then you can say it like that, more or less, but a goal to keeping explanations simple doesn't entitle you to say what you have said.
Where did I take credit for that? Sorry if there was confusion there. Pd and Pd-extended are the work of many people, I am just one of them. The pd-gui rewrite was also the work of at least 5 people.
.hc
"[T]he greatest purveyor of violence in the world today [is] my own government." - Martin Luther King, Jr.
Le 2012-02-18 à 12:25:00, Hans-Christoph Steiner a écrit :
On Feb 18, 2012, at 11:54 AM, Mathieu Bouchard wrote:
Le 2012-02-17 à 15:02:00, Hans-Christoph Steiner a écrit :
First off, the pd-gui side of Pd has been re-written from scratch.
You don't state which part of the pd-gui has been rewritten from scratch, which obscures the fact that a large fraction of it hasn't been rewritten.
I only claim that the code for the 'pd-gui' process was rewritten, which is was.
That's exactly what I'm talking about. The most important/central parts might have been rewritten, but much of the code in the 'pd-gui' process hasn't been touched at all.
This kind of claim involves a distinction between « rewrite of the code » and « rewrite of all the code » that might be clear in your head but is misleading to nearly anyone who reads your announcements.
Every aspect of Pd's GUI was not rewritten. As I mentioned in that email, that is a target for some of us for 0.44.
I am *not* talking about this.
Where did I take credit for that? Sorry if there was confusion there. Pd and Pd-extended are the work of many people, I am just one of them. The pd-gui rewrite was also the work of at least 5 people.
Ok, let's put this way : the way you said it and the way you still say it, you give credit to the pd-extended team for things that the pd-vanilla team has done well before pd-extended started existing.
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
Hi Matju
On Sat, 2012-02-18 at 11:54 -0500, Mathieu Bouchard wrote:
Le 2012-02-17 à 15:02:00, Hans-Christoph Steiner a écrit :
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes.
It's a bad idea to take credit for things that Miller had already done or that his contributors had done.
I can only speak for myself, but I didn't read it as Hans would have taken credit for those efforts.
Why have you changed the 'new' from the subject to 'old'?
I have the feeling you show some kind of an 'anti' attitude. Is that true? Why?
Roman
Le 2012-02-18 à 20:57:00, Roman Haefeli a écrit :
I can only speak for myself, but I didn't read it as Hans would have taken credit for those efforts.
Maybe you didn't read it. :-/ If you're interpreting it too much according to what you think Hans want to say, then you might not be paying attention to what he's saying.
Why have you changed the 'new' from the subject to 'old'?
Because I was talking about the parts that were portrayed as new or rewritten, but were coded over ten years ago. That's all what I'm talking about in this thread, and usually, I get told that I forget to change the subject-line to reflect the content. You should be happy that I changed it now.
an 'anti' attitude
What's that ?
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
On Sat, 2012-02-18 at 15:13 -0500, Mathieu Bouchard wrote:
an 'anti' attitude
What's that ?
An attitude of trying to make things look bad for no obvious reason. I think that all recent efforts done in Pd and Pd-extended are great and I haven't had the impression that the wrong people took credit for it (that's an impression I get from reading this mailing list). If people feel pretermitted, I think it's up to them to speak up.
Roman
Le 2012-02-18 à 21:57:00, Roman Haefeli a écrit :
An attitude of trying to make things look bad for no obvious reason.
What Hans has written at the beginning of the announcement is bad and this is why I « make it look bad ».
I think that all recent efforts done in Pd and Pd-extended are great
The great efforts that Hans puts in the Pd-extended project should not give him the right to say whatever he wants.
I'm not even talking about that topic.
If people feel pretermitted, I think it's up to them to speak up.
You mean that it's alright to give the impression that a lot more has changed in Pd than what really has changed ? Do you think that it helps making Pd be taken seriously ?
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
On Sat, 2012-02-18 at 16:47 -0500, Mathieu Bouchard wrote:
Le 2012-02-18 à 21:57:00, Roman Haefeli a écrit :
An attitude of trying to make things look bad for no obvious reason.
What Hans has written at the beginning of the announcement is bad and this is why I « make it look bad ».
I think that all recent efforts done in Pd and Pd-extended are great
The great efforts that Hans puts in the Pd-extended project should not give him the right to say whatever he wants.
Of course, not. Still, I - according to my personal judgment (I cannot speak for you) - didn't read Hans as he would be claiming unjustified credit.
I'm not even talking about that topic.
If people feel pretermitted, I think it's up to them to speak up.
You mean that it's alright to give the impression that a lot more has changed in Pd than what really has changed ?
No, I agree that giving a misleading impression should be avoided, but the point (again) is that I still believe I didn't get any wrong impression (probably I'm wrong here?). I must also say I haven't looked at the code itself, but followed the commit history of Pd-0.43 and the talks in the mailing lists pd-list and pd-dev. And my impression was that some of what could be changed regarding pd<->pd-gui communication was achieved, but it's still an ongoing process.
Do you think that it helps making Pd be taken seriously ?
Interesting question. I haven't thought about what could help make Pd be taken less or more seriously. Thinking about it, I feel that people often tend to take something seriously for odd reasons, like if has a 'nice' interface, if it costs much, if prominent person XY has a positive opinion about it, etc.
Roman
----- Original Message -----
From: Roman Haefeli reduzent@gmail.com To: pd-list@iem.at Cc: Sent: Monday, February 20, 2012 8:28 AM Subject: Re: [PD] [PD-announce] old editing features of Pd-extended 0.43
On Sat, 2012-02-18 at 16:47 -0500, Mathieu Bouchard wrote:
[...]
Do you think that it helps making Pd be taken seriously ?
Interesting question. I haven't thought about what could help make Pd be taken less or more seriously. Thinking about it, I feel that people often tend to take something seriously for odd reasons, like if has a 'nice' interface, if it costs much, if prominent person XY has a positive opinion about it, etc.
Roman
"Nice interface" does not belong in this list of odd reasons to take a program seriously.
-Jonathan
Le 2012-02-20 à 10:36:00, Jonathan Wilkes a écrit :
From: Roman Haefeli reduzent@gmail.com Interesting question. I haven't thought about what could help make Pd be taken less or more seriously. Thinking about it, I feel that people often tend to take something seriously for odd reasons, like if has a 'nice' interface, if it costs much, if prominent person XY has a positive opinion about it, etc.
"Nice interface" does not belong in this list of odd reasons to take a program seriously.
Depends who of you two guys is taking it to mean « shiny buttons » while the other one thinks in terms of efficient communication between the user and the software.
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
On Mon, 2012-02-20 at 10:36 -0800, Jonathan Wilkes wrote:
----- Original Message -----
From: Roman Haefeli reduzent@gmail.com To: pd-list@iem.at Cc: Sent: Monday, February 20, 2012 8:28 AM Subject: Re: [PD] [PD-announce] old editing features of Pd-extended 0.43
On Sat, 2012-02-18 at 16:47 -0500, Mathieu Bouchard wrote:
[...]
Do you think that it helps making Pd be taken seriously ?
Interesting question. I haven't thought about what could help make Pd be taken less or more seriously. Thinking about it, I feel that people often tend to take something seriously for odd reasons, like if has a 'nice' interface, if it costs much, if prominent person XY has a positive opinion about it, etc.
Roman
"Nice interface" does not belong in this list of odd reasons to take a program seriously.
Yeah, you're right. I should have said something else ('rounded corners'?)
Roman
well, speaking as a new member of the list and a very budding PD user coming from last using Max 5.1 i am happy with any incremental steps making the interface more usable. i do realize that usability can be a subjective term, but even simply paving the way for more options is an excellent start.
i don't believe i saw HC attempting to claim sole credit for the work he does every day on creating a more balanced release of on top of others hard work. his whole focus to me seems to be how to improve things and move PD forward both in terms of stability and usability/flexibility.
personally i have some gripes - i'm not enthusiastic about the look of Tcl/Tk apps in general - they are too blocky with no apparent ability for alpha channeling in the gui. i think Juce comes closer for me. i would love the ability to zoom in on patches. i use this feature all the time when in Max 5.1. i think not being able to pass the { and } characters without a somewhat convoluted workaround REALLY holds PD back from interacting with Javascript or most scripting languages in a way friendly a newbie.
in spite of all that, i see real progress behind the scenes with PD-extended, and i have no doubt that it will continue to move in a direction that will offer more flexibility and usability down the road using the input from as many users as who wish to participate. i don't see HC as claiming to have reinvented the PD gui but it's lot of work corralling many different extended efforts, keeping track of changes, and answering the majority of tech questions that comes across the list, and i am grateful to him and everyone else who contributes time and effort to making PD better for newbies and more flexible for pros.
scott
On Mon, Feb 20, 2012 at 11:30 AM, Roman Haefeli reduzent@gmail.com wrote:
On Mon, 2012-02-20 at 10:36 -0800, Jonathan Wilkes wrote:
----- Original Message -----
From: Roman Haefeli reduzent@gmail.com To: pd-list@iem.at Cc: Sent: Monday, February 20, 2012 8:28 AM Subject: Re: [PD] [PD-announce] old editing features of Pd-extended
0.43
On Sat, 2012-02-18 at 16:47 -0500, Mathieu Bouchard wrote:
[...]
Do you think that it helps making Pd be taken seriously ?
Interesting question. I haven't thought about what could help make Pd
be
taken less or more seriously. Thinking about it, I feel that people often tend to take something seriously for odd reasons, like if has a 'nice' interface, if it costs much, if prominent person XY has a positive opinion about it, etc.
Roman
"Nice interface" does not belong in this list of odd reasons to take a program seriously.
Yeah, you're right. I should have said something else ('rounded corners'?)
Roman
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Le 2012-02-20 à 12:56:00, Scott R. Looney a écrit :
i don't believe i saw HC attempting to claim sole credit for the work he does every day
I was only talking about the exaggeration of the difference between pd43 and pd42, and bad wording (or structure of the announcement). I don't say he was actually trying to take credit on his team's behalf or personal behalf for things that were not done by them or him, just that this announcement (and several previous ones) is/are misleading and give the impression of those claims.
i see real progress behind the scenes with PD-extended,
There is.
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
Thanks for your email, I always find it interesting to hear people's perspectives. I'm happy to see more people getting involved in development, so that means we can have more things like zooming interfaces. :-) Tcl/Tk can do zooming just fine, by the way ;-)
.hc
On Feb 20, 2012, at 3:56 PM, Scott R. Looney wrote:
well, speaking as a new member of the list and a very budding PD user coming from last using Max 5.1 i am happy with any incremental steps making the interface more usable. i do realize that usability can be a subjective term, but even simply paving the way for more options is an excellent start.
i don't believe i saw HC attempting to claim sole credit for the work he does every day on creating a more balanced release of on top of others hard work. his whole focus to me seems to be how to improve things and move PD forward both in terms of stability and usability/flexibility.
personally i have some gripes - i'm not enthusiastic about the look of Tcl/Tk apps in general - they are too blocky with no apparent ability for alpha channeling in the gui. i think Juce comes closer for me. i would love the ability to zoom in on patches. i use this feature all the time when in Max 5.1. i think not being able to pass the { and } characters without a somewhat convoluted workaround REALLY holds PD back from interacting with Javascript or most scripting languages in a way friendly a newbie.
in spite of all that, i see real progress behind the scenes with PD-extended, and i have no doubt that it will continue to move in a direction that will offer more flexibility and usability down the road using the input from as many users as who wish to participate. i don't see HC as claiming to have reinvented the PD gui but it's lot of work corralling many different extended efforts, keeping track of changes, and answering the majority of tech questions that comes across the list, and i am grateful to him and everyone else who contributes time and effort to making PD better for newbies and more flexible for pros.
scott
On Mon, Feb 20, 2012 at 11:30 AM, Roman Haefeli reduzent@gmail.com wrote: On Mon, 2012-02-20 at 10:36 -0800, Jonathan Wilkes wrote:
----- Original Message -----
From: Roman Haefeli reduzent@gmail.com To: pd-list@iem.at Cc: Sent: Monday, February 20, 2012 8:28 AM Subject: Re: [PD] [PD-announce] old editing features of Pd-extended 0.43
On Sat, 2012-02-18 at 16:47 -0500, Mathieu Bouchard wrote:
[...]
Do you think that it helps making Pd be taken seriously ?
Interesting question. I haven't thought about what could help make Pd be taken less or more seriously. Thinking about it, I feel that people often tend to take something seriously for odd reasons, like if has a 'nice' interface, if it costs much, if prominent person XY has a positive opinion about it, etc.
Roman
"Nice interface" does not belong in this list of odd reasons to take a program seriously.
Yeah, you're right. I should have said something else ('rounded corners'?)
Roman
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
"Free software means you control what your computer does. Non-free software means someone else controls that, and to some extent controls you." - Richard M. Stallman
Le 2012-02-20 à 22:51:00, Hans-Christoph Steiner a écrit :
Thanks for your email, I always find it interesting to hear people's perspectives. I'm happy to see more people getting involved in development, so that means we can have more things like zooming interfaces. :-) Tcl/Tk can do zooming just fine, by the way ;-)
How do you do zooming with Tcl/Tk ?
I mean... I implemented zooming using a big workaround which wouldn't have worked with Pd externals... is there a trouble-free way to zoom ?
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
----- Original Message -----
From: Mathieu Bouchard matju@artengine.ca To: Hans-Christoph Steiner hans@at.or.at Cc: "pd-list@iem.at" pd-list@iem.at Sent: Wednesday, February 22, 2012 12:48 AM Subject: [PD] Tk Zoom
Le 2012-02-20 à 22:51:00, Hans-Christoph Steiner a écrit :
Thanks for your email, I always find it interesting to hear people's
perspectives. I'm happy to see more people getting involved in development, so that means we can have more things like zooming interfaces. :-) Tcl/Tk can do zooming just fine, by the way ;-)
How do you do zooming with Tcl/Tk ?
I mean... I implemented zooming using a big workaround which wouldn't have worked with Pd externals... is there a trouble-free way to zoom ?
Curious about that, too.
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Feb 22, 2012, at 12:48 AM, Mathieu Bouchard wrote:
Le 2012-02-20 à 22:51:00, Hans-Christoph Steiner a écrit :
Thanks for your email, I always find it interesting to hear people's perspectives. I'm happy to see more people getting involved in development, so that means we can have more things like zooming interfaces. :-) Tcl/Tk can do zooming just fine, by the way ;-)
How do you do zooming with Tcl/Tk ?
I mean... I implemented zooming using a big workaround which wouldn't have worked with Pd externals... is there a trouble-free way to zoom ?
Didn't you use Tk scaling? That's what I mean. Yes, this would not work with existing GUI objects.
.hc
I have the audacity to believe that peoples everywhere can have three meals a day for their bodies, education and culture for their minds, and dignity, equality and freedom for their spirits. - Martin Luther King, Jr.
Le 2012-02-22 à 09:31:00, Hans-Christoph Steiner a écrit :
On Feb 22, 2012, at 12:48 AM, Mathieu Bouchard wrote:
How do you do zooming with Tcl/Tk ? I mean... I implemented zooming using a big workaround which wouldn't have worked with Pd externals... is there a trouble-free way to zoom ?
Didn't you use Tk scaling? That's what I mean. Yes, this would not work with existing GUI objects.
« Tk Scaling » is the name of a font measurement ratio for pt/px conversions, right ?
TkCanvas' «scale» command is unrelated, and does not do zoom, because it changes the size of items. The difference between that and zoom is that Tk doesn't make you see the prescaled coordinates, it still interacts with you only in terms of actual pixels. This means that most of the time, you'd have to scale the values on your own using [expr {$x*$scale}] and stuff.
In DesireData, I avoid TkCanvas's «scale» command entirely, and I make every canvas item creation/modification through a function that scans the arguments of the item, scales all coords it sees, scales the thickness of lines, scales the font sizes, automatically decides tags to be used, and figures out what to do differently in create vs modify.
That way, the widget's behaviour does not have to implement zoom, it does not have to implement modification-functions (because the create-function is able to redraw an existing thing), it does not have to implement the delete-function (because the enforced common tag makes a single command delete), etc.
That's not compatible with t_widgetbehavior and couldn't possibly be made to be.
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
i may be totally out of my depth here as i'm not a programmer but i believe MaxMSP was able to do zooming through the use of Juce. it certainly wasn't available beforehand in any of the 4.X series. personally i find zooming to be one the most massively useful things when editing patches. being old-ish my eyes definitely have more issues than they used to...
scott
On Wed, Feb 22, 2012 at 10:32 AM, Mathieu Bouchard matju@artengine.cawrote:
Le 2012-02-22 à 09:31:00, Hans-Christoph Steiner a écrit :
On Feb 22, 2012, at 12:48 AM, Mathieu Bouchard wrote:
How do you do zooming with Tcl/Tk ? I mean... I implemented zooming using a big workaround which wouldn't have worked with Pd externals... is there a trouble-free way to zoom ?
Didn't you use Tk scaling? That's what I mean. Yes, this would not work with existing GUI objects.
« Tk Scaling » is the name of a font measurement ratio for pt/px conversions, right ?
TkCanvas' «scale» command is unrelated, and does not do zoom, because it changes the size of items. The difference between that and zoom is that Tk doesn't make you see the prescaled coordinates, it still interacts with you only in terms of actual pixels. This means that most of the time, you'd have to scale the values on your own using [expr {$x*$scale}] and stuff.
In DesireData, I avoid TkCanvas's «scale» command entirely, and I make every canvas item creation/modification through a function that scans the arguments of the item, scales all coords it sees, scales the thickness of lines, scales the font sizes, automatically decides tags to be used, and figures out what to do differently in create vs modify.
That way, the widget's behaviour does not have to implement zoom, it does not have to implement modification-functions (because the create-function is able to redraw an existing thing), it does not have to implement the delete-function (because the enforced common tag makes a single command delete), etc.
That's not compatible with t_widgetbehavior and couldn't possibly be made to be.
______________________________**______________________________** __________ | Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
Le 2012-02-20 à 14:28:00, Roman Haefeli a écrit :
No, I agree that giving a misleading impression should be avoided, but the point (again) is that I still believe I didn't get any wrong impression (probably I'm wrong here?). I must also say I haven't looked at the code itself, but followed the commit history of Pd-0.43 and the talks in the mailing lists pd-list and pd-dev. And my impression was that some of what could be changed regarding pd<->pd-gui communication was achieved, but it's still an ongoing process.
Oh, something was achieved, yes. Pd 43 incorporates several ideas from DesireData, rewritten such that they work in vanilla/extended. For example, replacing pd-gui by plain Wish, and adding some tables so that Tk-side code can be more aware of what's going on, such as « canvas finished loading » events (though this part of pd43 is completely different from DesireData's equivalent).
But 43's «rewrite» is still a small portion of even just rewriting the Tk side of the GUI.
Do you think that it helps making Pd be taken seriously ?
Interesting question. I haven't thought about what could help make Pd be taken less or more seriously. Thinking about it, I feel that people often tend to take something seriously for odd reasons,
Ok. Now think about developers. What happens when one gets enthusiastic about pd43 because the announcement sounds like there was a huge amount of change, and then looks at the code and see that in the end there isn't nearly that much difference ?
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
Le 2012-02-20 à 14:27:00, Mathieu Bouchard a écrit :
and adding some tables so that Tk-side code can be more aware of what's going on, such as « canvas finished loading » events (though this part of pd43 is completely different from DesireData's equivalent).
I don't know why I mentioned it... it's definitely not similar enough.
But the thing about Wish still holds (deleting the C code in the Tk side and some related things).
And I didn't really want to go into those details. My mistake. The point was really about the proportion of code that changed.
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
----- Original Message -----
From: Mathieu Bouchard matju@artengine.ca To: Roman Haefeli reduzent@gmail.com Cc: pd-list@iem.at Sent: Monday, February 20, 2012 4:23 PM Subject: Re: [PD] [PD-announce] old editing features of Pd-extended 0.43
Le 2012-02-20 à 14:27:00, Mathieu Bouchard a écrit :
and adding some tables so that Tk-side code can be more aware of what's
going on, such as « canvas finished loading » events (though this part of pd43 is completely different from DesireData's equivalent).
I don't know why I mentioned it... it's definitely not similar enough.
And it doesn't quite work. The <<Loaded>> virtual event will trigger before Tk is actually finished drawing the patch window. At least I think that's what's happening, because I tried to do [loadbang]--[tip 1 hello(--[s this_canvas] (which will create a window item on the canvas with a label in it with the text "hello"), but the label is given too narrow a width and I get: h e l l o
If I send the message to create the tip manually, after the patch has finished loading, it displays fine.
-Jonathan
But the thing about Wish still holds (deleting the C code in the Tk side and some related things).
And I didn't really want to go into those details. My mistake. The point was really about the proportion of code that changed.
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 02/20/2012 04:54 PM, Jonathan Wilkes wrote:
----- Original Message -----
From: Mathieu Bouchard matju@artengine.ca To: Roman Haefeli reduzent@gmail.com Cc: pd-list@iem.at Sent: Monday, February 20, 2012 4:23 PM Subject: Re: [PD] [PD-announce] old editing features of Pd-extended 0.43
Le 2012-02-20 à 14:27:00, Mathieu Bouchard a écrit :
and adding some tables so that Tk-side code can be more aware of what's
going on, such as « canvas finished loading » events (though this part of pd43 is completely different from DesireData's equivalent).
I don't know why I mentioned it... it's definitely not similar enough.
And it doesn't quite work. The <<Loaded>> virtual event will trigger before Tk is actually finished drawing the patch window. At least I think that's what's happening, because I tried to do [loadbang]--[tip 1 hello(--[s this_canvas] (which will create a window item on the canvas with a label in it with the text "hello"), but the label is given too narrow a width and I get: h e l l o
If I send the message to create the tip manually, after the patch has finished loading, it displays fine.
That's a bug, IMHO. I think <<Loaded>> should be sent right before the loadbangs are. Or maybe <<Loaded>> should be after [loadbang] finish, and there should also be a <<Loadbang>> event.
Could you find a bug report on that?
.hc
Le 2012-02-20 à 13:54:00, Jonathan Wilkes a écrit :
And it doesn't quite work. The <<Loaded>> virtual event will trigger before Tk is actually finished drawing the patch window.
Well, there are four possible distinct meanings of « finished loading » that could be helpful :
- the patch has finished loading in the «server»... the t_canvas objects
have been created, their subobjects have been loaded if they're stored in files, the .x76543210 receive symbols exist, so Tk can send to them. [initbang] has been run (some dynamic patching depends on it).
- [loadbang] has also finished running. This means that all the rest of
the load-time dynamic patching is done, and the patch's own init has all been run, so that you can start using the patch for real.
- all the sys_queuegui() calls related to this toplevel canvas have been
done, and all sys_gui() calls have already gone through the sendbuf, the TCP connection, and have been eval'd. This means that all the Tk Canvas Items have been created, so that you can send to them, make stats about them, query their info, etc.
- All the stuff drawn in step 3 has appeared in the framebuffer of the
videocard. This means that it's read to use a screenshot tool such as [#in x11] or gnome-screenshot.
I think that there are different uses for each of those levels. For my patch_dans_patch picture series, I would have liked some kind of object that would have told me that everything has been drawn on the screen, but this would require a (very small) change to Tk itself, AFAIK.
If I send the message to create the tip manually, after the patch has finished loading, it displays fine.
The fact that you wait for it to appear on the screen, makes it a level 4 notification.
What you need for the tooltip to work is probably a level 3 notification.
What is available now in pd43 is a level 2 notification, afaik.
I don't have examples of uses of level 1 notifications, but I feel like there are. But I don't think that it's strictly necessary to implement this level, because it's quite close to level 2. I think that levels 2,3,4 are much more useful.
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
----- Original Message -----
From: Mathieu Bouchard matju@artengine.ca To: Jonathan Wilkes jancsika@yahoo.com Cc: Roman Haefeli reduzent@gmail.com; "pd-list@iem.at" pd-list@iem.at Sent: Monday, February 20, 2012 6:34 PM Subject: <<Loaded>> virtual event
Le 2012-02-20 à 13:54:00, Jonathan Wilkes a écrit :
And it doesn't quite work. The <<Loaded>> virtual event
will trigger before Tk is actually finished drawing the patch window.
Well, there are four possible distinct meanings of « finished loading » that could be helpful :
- the patch has finished loading in the «server»... the t_canvas objects have
been created, their subobjects have been loaded if they're stored in files, the .x76543210 receive symbols exist, so Tk can send to them. [initbang] has been run (some dynamic patching depends on it).
- [loadbang] has also finished running. This means that all the rest of the
load-time dynamic patching is done, and the patch's own init has all been run, so that you can start using the patch for real.
- all the sys_queuegui() calls related to this toplevel canvas have been done,
and all sys_gui() calls have already gone through the sendbuf, the TCP connection, and have been eval'd. This means that all the Tk Canvas Items have been created, so that you can send to them, make stats about them, query their info, etc.
Hm... I could ameliorate the problem by setting a minimum value for the -wraplength of the tk label for the tooltip. If I set it to be at least 150 pixels then it would at least be guaranteed to be legible for loadbanged tooltips (if unnecessarily scrunched for longer tips). This means that part of the tip could potentially be hidden in patches narrower than 150 pixels, but if your patch is narrower than 150 pixels chances are other things are hidden, too. Not great but I can't think of another workaround.
-Jonathan
- All the stuff drawn in step 3 has appeared in the framebuffer of the
videocard. This means that it's read to use a screenshot tool such as [#in x11] or gnome-screenshot.
I think that there are different uses for each of those levels. For my patch_dans_patch picture series, I would have liked some kind of object that would have told me that everything has been drawn on the screen, but this would require a (very small) change to Tk itself, AFAIK.
If I send the message to create the tip manually, after the patch has
finished loading, it displays fine.
The fact that you wait for it to appear on the screen, makes it a level 4 notification.
What you need for the tooltip to work is probably a level 3 notification.
What is available now in pd43 is a level 2 notification, afaik.
I don't have examples of uses of level 1 notifications, but I feel like there are. But I don't think that it's strictly necessary to implement this level, because it's quite close to level 2. I think that levels 2,3,4 are much more useful.
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
Le 2012-02-20 à 16:10:00, Jonathan Wilkes a écrit :
I could ameliorate the problem by setting a minimum value for the -wraplength of the tk label for the tooltip.
You can't ameliorate a big rock by walking around it...
the <<Loaded>> virtual event system still won't work.
To have a «level 3» event, it needs to be triggered by a sys_queuegui() that happens after every sys_queuegui() that came from loading the patch. The last sys_queuegui() will call sys_vgui() with a Tk command for sending a synthetic event, and that command will only be eval'd after every other sys_vgui() command related to loading the patch.
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
----- Original Message -----
From: Mathieu Bouchard matju@artengine.ca To: Jonathan Wilkes jancsika@yahoo.com Cc: Roman Haefeli reduzent@gmail.com; "pd-list@iem.at" pd-list@iem.at Sent: Monday, February 20, 2012 7:56 PM Subject: Re: <<Loaded>> virtual event
Le 2012-02-20 à 16:10:00, Jonathan Wilkes a écrit :
I could ameliorate the problem by setting a minimum value for the
-wraplength of the tk label for the tooltip.
You can't ameliorate a big rock by walking around it...
No but I can make the effects of the problem less drastic by walking around the rock (instead of turning around and going home).
the <<Loaded>> virtual event system still won't work.
Right.
To have a «level 3» event, it needs to be triggered by a sys_queuegui() that happens after every sys_queuegui() that came from loading the patch. The last sys_queuegui() will call sys_vgui() with a Tk command for sending a synthetic event, and that command will only be eval'd after every other sys_vgui() command related to loading the patch.
That is getting deeper into the Pd guts than I've gone. Does this mean putting a sys_queuegui() after sys_vgui("pdtk_canvas_getscroll .x%lx.c\n", x) in canvas_map?
-Jonathan
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
On Feb 20, 2012, at 7:56 PM, Mathieu Bouchard wrote:
Le 2012-02-20 à 16:10:00, Jonathan Wilkes a écrit :
I could ameliorate the problem by setting a minimum value for the -wraplength of the tk label for the tooltip.
You can't ameliorate a big rock by walking around it...
the <<Loaded>> virtual event system still won't work.
To have a «level 3» event, it needs to be triggered by a sys_queuegui() that happens after every sys_queuegui() that came from loading the patch. The last sys_queuegui() will call sys_vgui() with a Tk command for sending a synthetic event, and that command will only be eval'd after every other sys_vgui() command related to loading the patch.
That sounds very useful, feel like coding it? I think the Tk events could be named after the Pd events: initbang and loadbang.
.hc
There is no way to peace, peace is the way. -A.J. Muste
On Feb 20, 2012, at 7:10 PM, Jonathan Wilkes wrote:
----- Original Message -----
From: Mathieu Bouchard matju@artengine.ca To: Jonathan Wilkes jancsika@yahoo.com Cc: Roman Haefeli reduzent@gmail.com; "pd-list@iem.at" pd-list@iem.at Sent: Monday, February 20, 2012 6:34 PM Subject: <<Loaded>> virtual event
Le 2012-02-20 à 13:54:00, Jonathan Wilkes a écrit :
And it doesn't quite work. The <<Loaded>> virtual event
will trigger before Tk is actually finished drawing the patch window.
Well, there are four possible distinct meanings of « finished loading » that could be helpful :
- the patch has finished loading in the «server»... the t_canvas objects have
been created, their subobjects have been loaded if they're stored in files, the .x76543210 receive symbols exist, so Tk can send to them. [initbang] has been run (some dynamic patching depends on it).
- [loadbang] has also finished running. This means that all the rest of the
load-time dynamic patching is done, and the patch's own init has all been run, so that you can start using the patch for real.
- all the sys_queuegui() calls related to this toplevel canvas have been done,
and all sys_gui() calls have already gone through the sendbuf, the TCP connection, and have been eval'd. This means that all the Tk Canvas Items have been created, so that you can send to them, make stats about them, query their info, etc.
Hm... I could ameliorate the problem by setting a minimum value for the -wraplength of the tk label for the tooltip. If I set it to be at least 150 pixels then it would at least be guaranteed to be legible for loadbanged tooltips (if unnecessarily scrunched for longer tips). This means that part of the tip could potentially be hidden in patches narrower than 150 pixels, but if your patch is narrower than 150 pixels chances are other things are hidden, too. Not great but I can't think of another workaround.
Setting a minimum width makes sense to me as a workaround. Its easy and there shouldn't be serious downsides.
.hc
"[T]he greatest purveyor of violence in the world today [is] my own government." - Martin Luther King, Jr.
Hi Hans,
great job. But, here in XP, I get audio problems: trying to run with asio
(as I always do with 0.42), the audio is very noisy.
Audio options are -asio -audioindev 2 -audiooutdev 2 -channels 2
-midiindev 1 -midioutdev 1 -audiobuf 40, and they always worked with
previous versions of pd-ext.
João
http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time, about
18 months now, mostly because there are lots of big improvements, and we
wanted to make sure we got it right, so your patches all work, but the
improvements all shine. Its now solidly beta, so we’re looking for
testers. Download a nightly build to try here:http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When
you run Pd, you are actually running two programs: pd is the core engine
and pd-gui is the GUI. Since basically all computers now come with
multiple CPU cores, this means that pd-gui will usually run on a
separate CPU core than pd, so they don’t step on each other’s toes. pd
can entirely take over its own core. If you want to make your patch use
more CPU cores, then check out the [pd~] object introduced in the last
release (0.42.5).pd still handles some of the GUI stuff, but we are working on splitting
that out for the 0.44 release. That is a big chunk of work but it will
also bring big gains. In particular, it means that it will be possible
for people to write their own GUIs for Pd, covering not just the display
of the patch, but also the editing, and everything else. You like
OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using
the toolkit of your choice. That’s the idea at least. That will take a
solid chunk of work, so we are looking for people to join that effort.There are so many ideas for making a better editing experience in Pd,
this release makes big strides to address the editing experience. There
are new features like Magic Glass, Autotips, Autopatch and Perf Mode,
all available on the Edit menu.• Magic Glass let’s you magically see the messages as they pass through
the cords. Just turn it on and hover above a cord, and you’ll see the
messages as they go by. You can even look at signal/audio cords.• Autotips gives you tips about what an object does, what its inlet
expects, and what comes out of the outlets.• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to
accidentally close windows that are part of your performance.The Pd Window is also majorly overhauled. First of all, its fast. Much
much faster than the old one. You can now print thousands of messages
per second to the Pd Window and still edit your patch. No more will an
accidental dump of info cause the GUI to freeze up (well, ok, maybe if
you send 10,000 messages/second but that is a way too many). There are
also now 5 levels of printing messages to the Pd Window: fatal, error,
normal, debug, all. If you are only interested in fatal errors, switch
the Pd Window to 0 – fatal, and you’ll only see the worst problems. You
want to see every single message to debug? Switch to 4 – all, and you’ll
get the whole firehose.There is also the new log library, which lets you easily send messages
for those different levels. And all messages logged with the objects
from the log library are clickable: when you Ctrl-Click or Cmd-click
(Mac OS X) on the line in the Pd Window, it’ll pop up the patch where
the message came from, and highlight the specific object that printed
it. That even works for many messages from other objects as well.The Pd Window also includes very basic level meters for monitoring the
input and output levels. And for those who want to play with the GUI in
realtime, you can type Tcl code in the Tcl entry field, and directly
modify and probe the running GUI.One thing that you can do now is customize the GUI using GUI plugins.
You can change all sorts of colors, some fonts, and many behaviors. Want
to create a new object when you triple-click? Try the tripleclick
example plugin Want to make the patch cords disappear when you leave
Edit Mode? Check out the “only show cords in edit mode” example. Those
are the simple ones. There is also Tab Completion, a search engine for
the docs, a category browser for the right-click menu, a buttonbar for
creating objects, and more.You can find many GUI plugins in the new section of the downloads page
as well as documentation for making your own. What kind of GUI plugin
will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
What do you mean by noisy? Can you give more information? I really don't know much about Windows, so I rely on others to tell me how things there should be handled. patco and pob have been doing a lot of valuable work there.
.hc
On Feb 18, 2012, at 12:13 PM, João Pais wrote:
Hi Hans,
great job. But, here in XP, I get audio problems: trying to run with asio (as I always do with 0.42), the audio is very noisy. Audio options are -asio -audioindev 2 -audiooutdev 2 -channels 2 -midiindev 1 -midioutdev 1 -audiobuf 40, and they always worked with previous versions of pd-ext.
João
http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here:
http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5).
pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.
There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.
• Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.
The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose.
There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well.
The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.
One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.
You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Friedenstr. 58 10249 Berlin (Deutschland) Tel +49 30 42020091 | Mob +49 162 6843570 Studio +49 30 69509190 jmmmpais@googlemail.com | skype: jmmmpjmmmp
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
It sounds as if the audio isn't synced to the system card, or something.
The sinus in the audio test patch has lots of irregular clicks, almost as
if they would be dropouts.
What do you mean by noisy? Can you give more information? I really
don't know much about Windows, so I rely on others to tell me how things
there should be handled. patco and pob have been doing a lot of
valuable work there..hc
On Feb 18, 2012, at 12:13 PM, João Pais wrote:
Hi Hans,
great job. But, here in XP, I get audio problems: trying to run with
asio (as I always do with 0.42), the audio is very noisy. Audio options are -asio -audioindev 2 -audiooutdev 2 -channels 2
-midiindev 1 -midioutdev 1 -audiobuf 40, and they always worked with
previous versions of pd-ext.João
http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time,
about 18 months now, mostly because there are lots of big
improvements, and we wanted to make sure we got it right, so your
patches all work, but the improvements all shine. Its now solidly
beta, so we’re looking for testers. Download a nightly build to try
here:http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch.
When you run Pd, you are actually running two programs: pd is the core
engine and pd-gui is the GUI. Since basically all computers now come
with multiple CPU cores, this means that pd-gui will usually run on a
separate CPU core than pd, so they don’t step on each other’s toes. pd
can entirely take over its own core. If you want to make your patch
use more CPU cores, then check out the [pd~] object introduced in the
last release (0.42.5).pd still handles some of the GUI stuff, but we are working on
splitting that out for the 0.44 release. That is a big chunk of work
but it will also bring big gains. In particular, it means that it will
be possible for people to write their own GUIs for Pd, covering not
just the display of the patch, but also the editing, and everything
else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your
own pd-gui using the toolkit of your choice. That’s the idea at least.
That will take a solid chunk of work, so we are looking for people to
join that effort.There are so many ideas for making a better editing experience in Pd,
this release makes big strides to address the editing experience.
There are new features like Magic Glass, Autotips, Autopatch and Perf
Mode, all available on the Edit menu.• Magic Glass let’s you magically see the messages as they pass
through the cords. Just turn it on and hover above a cord, and you’ll
see the messages as they go by. You can even look at signal/audio
cords.• Autotips gives you tips about what an object does, what its inlet
expects, and what comes out of the outlets.• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to
accidentally close windows that are part of your performance.The Pd Window is also majorly overhauled. First of all, its fast. Much
much faster than the old one. You can now print thousands of messages
per second to the Pd Window and still edit your patch. No more will an
accidental dump of info cause the GUI to freeze up (well, ok, maybe if
you send 10,000 messages/second but that is a way too many). There are
also now 5 levels of printing messages to the Pd Window: fatal, error,
normal, debug, all. If you are only interested in fatal errors, switch
the Pd Window to 0 – fatal, and you’ll only see the worst problems.
You want to see every single message to debug? Switch to 4 – all, and
you’ll get the whole firehose.There is also the new log library, which lets you easily send messages
for those different levels. And all messages logged with the objects
from the log library are clickable: when you Ctrl-Click or Cmd-click
(Mac OS X) on the line in the Pd Window, it’ll pop up the patch where
the message came from, and highlight the specific object that printed
it. That even works for many messages from other objects as well.The Pd Window also includes very basic level meters for monitoring the
input and output levels. And for those who want to play with the GUI
in realtime, you can type Tcl code in the Tcl entry field, and
directly modify and probe the running GUI.One thing that you can do now is customize the GUI using GUI plugins.
You can change all sorts of colors, some fonts, and many behaviors.
Want to create a new object when you triple-click? Try the tripleclick
example plugin Want to make the patch cords disappear when you leave
Edit Mode? Check out the “only show cords in edit mode” example. Those
are the simple ones. There is also Tab Completion, a search engine for
the docs, a category browser for the right-click menu, a buttonbar for
creating objects, and more.You can find many GUI plugins in the new section of the downloads page
as well as documentation for making your own. What kind of GUI plugin
will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list-- Friedenstr. 58 10249 Berlin (Deutschland) Tel +49 30 42020091 | Mob +49 162 6843570 Studio +49 30 69509190 jmmmpais@googlemail.com | skype: jmmmpjmmmp
I spent 33 years and four months in active military service and during
that period I spent most of my time as a high class muscle man for Big
Business, for Wall Street and the bankers. - General Smedley Butler
Please file a bug report with as much detail as possible.
.hc
On Feb 18, 2012, at 12:41 PM, João Pais wrote:
It sounds as if the audio isn't synced to the system card, or something. The sinus in the audio test patch has lots of irregular clicks, almost as if they would be dropouts.
What do you mean by noisy? Can you give more information? I really don't know much about Windows, so I rely on others to tell me how things there should be handled. patco and pob have been doing a lot of valuable work there.
.hc
On Feb 18, 2012, at 12:13 PM, João Pais wrote:
Hi Hans,
great job. But, here in XP, I get audio problems: trying to run with asio (as I always do with 0.42), the audio is very noisy. Audio options are -asio -audioindev 2 -audiooutdev 2 -channels 2 -midiindev 1 -midioutdev 1 -audiobuf 40, and they always worked with previous versions of pd-ext.
João
http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here:
http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5).
pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.
There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.
• Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.
The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose.
There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well.
The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.
One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.
You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Friedenstr. 58 10249 Berlin (Deutschland) Tel +49 30 42020091 | Mob +49 162 6843570 Studio +49 30 69509190 jmmmpais@googlemail.com | skype: jmmmpjmmmp
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
-- Friedenstr. 58 10249 Berlin (Deutschland) Tel +49 30 42020091 | Mob +49 162 6843570 Studio +49 30 69509190 jmmmpais@googlemail.com | skype: jmmmpjmmmp
'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
Hi there,
also frequent and irregular audio clicks on mac OSX 10.6.8, no matter how big the delay time is set to in the audio properties. (Tested with 'test audio/midi patch' @ SR 44100 and 48000 Hz with built-in audio, portaudio).
also, [cputime] appears not to work.
(pd-0.43.1-extended-20120218-macosx105-i386)
Ángel Faraldo _________________ www.angelfaraldo.info
On Feb 18, 2012, at 6:41 PM, João Pais wrote:
It sounds as if the audio isn't synced to the system card, or something. The sinus in the audio test patch has lots of irregular clicks, almost as if they would be dropouts.
What do you mean by noisy? Can you give more information? I really don't know much about Windows, so I rely on others to tell me how things there should be handled. patco and pob have been doing a lot of valuable work there.
.hc
On Feb 18, 2012, at 12:13 PM, João Pais wrote:
Hi Hans,
great job. But, here in XP, I get audio problems: trying to run with asio (as I always do with 0.42), the audio is very noisy. Audio options are -asio -audioindev 2 -audiooutdev 2 -channels 2 -midiindev 1 -midioutdev 1 -audiobuf 40, and they always worked with previous versions of pd-ext.
João
http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here:
http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5).
pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.
There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.
• Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.
The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose.
There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well.
The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.
One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.
You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Friedenstr. 58 10249 Berlin (Deutschland) Tel +49 30 42020091 | Mob +49 162 6843570 Studio +49 30 69509190 jmmmpais@googlemail.com | skype: jmmmpjmmmp
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
-- Friedenstr. 58 10249 Berlin (Deutschland) Tel +49 30 42020091 | Mob +49 162 6843570 Studio +49 30 69509190 jmmmpais@googlemail.com | skype: jmmmpjmmmp
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Ángel Faraldo _________________ www.angelfaraldo.info
What kind of computer and audio interface are you using?
Hmm yeah, [cputime] does seem broken. Could you post a bug report please?
.hc
On Feb 18, 2012, at 2:54 PM, Ángel Faraldo wrote:
Hi there,
also frequent and irregular audio clicks on mac OSX 10.6.8, no matter how big the delay time is set to in the audio properties. (Tested with 'test audio/midi patch' @ SR 44100 and 48000 Hz with built-in audio, portaudio).
also, [cputime] appears not to work.
(pd-0.43.1-extended-20120218-macosx105-i386)
Ángel Faraldo _________________ www.angelfaraldo.info
On Feb 18, 2012, at 6:41 PM, João Pais wrote:
It sounds as if the audio isn't synced to the system card, or something. The sinus in the audio test patch has lots of irregular clicks, almost as if they would be dropouts.
What do you mean by noisy? Can you give more information? I really don't know much about Windows, so I rely on others to tell me how things there should be handled. patco and pob have been doing a lot of valuable work there.
.hc
On Feb 18, 2012, at 12:13 PM, João Pais wrote:
Hi Hans,
great job. But, here in XP, I get audio problems: trying to run with asio (as I always do with 0.42), the audio is very noisy. Audio options are -asio -audioindev 2 -audiooutdev 2 -channels 2 -midiindev 1 -midioutdev 1 -audiobuf 40, and they always worked with previous versions of pd-ext.
João
http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here:
http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5).
pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.
There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.
• Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.
The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose.
There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well.
The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.
One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.
You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Friedenstr. 58 10249 Berlin (Deutschland) Tel +49 30 42020091 | Mob +49 162 6843570 Studio +49 30 69509190 jmmmpais@googlemail.com | skype: jmmmpjmmmp
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
-- Friedenstr. 58 10249 Berlin (Deutschland) Tel +49 30 42020091 | Mob +49 162 6843570 Studio +49 30 69509190 jmmmpais@googlemail.com | skype: jmmmpjmmmp
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Ángel Faraldo _________________ www.angelfaraldo.info
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
Begin forwarded message:
From: Hans-Christoph Steiner hans@at.or.at Date: February 18, 2012 9:02:07 PM GMT+01:00 To: Ángel Faraldo angelfaraldo@gmail.com Cc: João Pais jmmmpais@googlemail.com, "pd-list@iem.at List" pd-list@iem.at Subject: Re: [PD] new editing features of Pd-extended 0.43, now in beta!
also frequent and irregular audio clicks on mac OSX 10.6.8, no matter how big the delay time is set to in the audio properties. (Tested with 'test audio/midi patch' @ SR 44100 and 48000 Hz with built-in audio, portaudio).
What kind of computer and audio interface are you using?
macbook pro 2.66GHz Intel Core 2 Duo with OSX 10.6.8. I tested it with the built-in audio and a RME Fireface 800 with similar results.
Hmm yeah, [cputime] does seem broken. Could you post a bug report please?
done
ángel faraldo
.hc
On Feb 18, 2012, at 2:54 PM, Ángel Faraldo wrote:
Hi there,
also frequent and irregular audio clicks on mac OSX 10.6.8, no matter how big the delay time is set to in the audio properties. (Tested with 'test audio/midi patch' @ SR 44100 and 48000 Hz with built-in audio, portaudio).
also, [cputime] appears not to work.
(pd-0.43.1-extended-20120218-macosx105-i386)
Ángel Faraldo _________________ www.angelfaraldo.info
On Feb 18, 2012, at 6:41 PM, João Pais wrote:
It sounds as if the audio isn't synced to the system card, or something. The sinus in the audio test patch has lots of irregular clicks, almost as if they would be dropouts.
What do you mean by noisy? Can you give more information? I really don't know much about Windows, so I rely on others to tell me how things there should be handled. patco and pob have been doing a lot of valuable work there.
.hc
On Feb 18, 2012, at 12:13 PM, João Pais wrote:
Hi Hans,
great job. But, here in XP, I get audio problems: trying to run with asio (as I always do with 0.42), the audio is very noisy. Audio options are -asio -audioindev 2 -audiooutdev 2 -channels 2 -midiindev 1 -midioutdev 1 -audiobuf 40, and they always worked with previous versions of pd-ext.
João
http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here:
http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5).
pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.
There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.
• Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.
The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose.
There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well.
The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.
One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.
You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Friedenstr. 58 10249 Berlin (Deutschland) Tel +49 30 42020091 | Mob +49 162 6843570 Studio +49 30 69509190 jmmmpais@googlemail.com | skype: jmmmpjmmmp
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
-- Friedenstr. 58 10249 Berlin (Deutschland) Tel +49 30 42020091 | Mob +49 162 6843570 Studio +49 30 69509190 jmmmpais@googlemail.com | skype: jmmmpjmmmp
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Ángel Faraldo _________________ www.angelfaraldo.info
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
Ángel Faraldo _________________ www.angelfaraldo.info
On Sun, Feb 19, 2012, at 11:19, Ángel Faraldo wrote:
Begin forwarded message:
From: Hans-Christoph Steiner hans@at.or.at Date: February 18, 2012 9:02:07 PM GMT+01:00 To: Ángel Faraldo angelfaraldo@gmail.com Cc: João Pais jmmmpais@googlemail.com, "pd-list@iem.at List" pd-list@iem.at Subject: Re: [PD] new editing features of Pd-extended 0.43, now in beta!
also frequent and irregular audio clicks on mac OSX 10.6.8, no matter how big the delay time is set to in the audio properties. (Tested with 'test audio/midi patch' @ SR 44100 and 48000 Hz with built-in audio, portaudio).
What kind of computer and audio interface are you using?
macbook pro 2.66GHz Intel Core 2 Duo with OSX 10.6.8. I tested it with the built-in audio and a RME Fireface 800 with similar results.
I'm on a very similar machine', a MacBook pro 3 - 2.4ghz running 10.6.8. Ive never seen this before. I don't have any external interface, perhaps its related to the drivers from your interface? Just a guess. Do other audio apps work? Like Audacity? It also uses portaudio.
Please file a bug report on this one too.
.hc
Hmm yeah, [cputime] does seem broken. Could you post a bug report please?
done
ángel faraldo
.hc
On Feb 18, 2012, at 2:54 PM, Ángel Faraldo wrote:
Hi there,
also frequent and irregular audio clicks on mac OSX 10.6.8, no matter how big the delay time is set to in the audio properties. (Tested with 'test audio/midi patch' @ SR 44100 and 48000 Hz with built-in audio, portaudio).
also, [cputime] appears not to work.
(pd-0.43.1-extended-20120218-macosx105-i386)
Ángel Faraldo _________________ www.angelfaraldo.info
On Feb 18, 2012, at 6:41 PM, João Pais wrote:
It sounds as if the audio isn't synced to the system card, or something. The sinus in the audio test patch has lots of irregular clicks, almost as if they would be dropouts.
What do you mean by noisy? Can you give more information? I really don't know much about Windows, so I rely on others to tell me how things there should be handled. patco and pob have been doing a lot of valuable work there.
.hc
On Feb 18, 2012, at 12:13 PM, João Pais wrote:
Hi Hans,
great job. But, here in XP, I get audio problems: trying to run with asio (as I always do with 0.42), the audio is very noisy. Audio options are -asio -audioindev 2 -audiooutdev 2 -channels 2 -midiindev 1 -midioutdev 1 -audiobuf 40, and they always worked with previous versions of pd-ext.
João
> > http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43... > > The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here: > > http://autobuild.puredata.info/auto-build/latest/ > > First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5). > > pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort. > > There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu. > > • Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords. > > • Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets. > > • Autopatch mode automatically connects objects as you create them. > > • Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance. > > The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose. > > There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well. > > The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI. > > One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more. > > You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write? > > > > _______________________________________________ > Pd-announce mailing list > Pd-announce@iem.at > http://lists.puredata.info/listinfo/pd-announce > > _______________________________________________ > Pd-list@iem.at mailing list > UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Friedenstr. 58 10249 Berlin (Deutschland) Tel +49 30 42020091 | Mob +49 162 6843570 Studio +49 30 69509190 jmmmpais@googlemail.com | skype: jmmmpjmmmp
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
-- Friedenstr. 58 10249 Berlin (Deutschland) Tel +49 30 42020091 | Mob +49 162 6843570 Studio +49 30 69509190 jmmmpais@googlemail.com | skype: jmmmpjmmmp
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Ángel Faraldo _________________ www.angelfaraldo.info
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
Ángel Faraldo _________________ www.angelfaraldo.info
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Feb 19, 2012, at 7:08 PM, Hans-Christoph Steiner wrote:
On Sun, Feb 19, 2012, at 11:19, Ángel Faraldo wrote:
Begin forwarded message:
From: Hans-Christoph Steiner hans@at.or.at Date: February 18, 2012 9:02:07 PM GMT+01:00 To: Ángel Faraldo angelfaraldo@gmail.com Cc: João Pais jmmmpais@googlemail.com, "pd-list@iem.at List" pd-list@iem.at Subject: Re: [PD] new editing features of Pd-extended 0.43, now in beta!
also frequent and irregular audio clicks on mac OSX 10.6.8, no matter how big the delay time is set to in the audio properties. (Tested with 'test audio/midi patch' @ SR 44100 and 48000 Hz with built-in audio, portaudio).
What kind of computer and audio interface are you using?
macbook pro 2.66GHz Intel Core 2 Duo with OSX 10.6.8. I tested it with the built-in audio and a RME Fireface 800 with similar results.
I'm on a very similar machine', a MacBook pro 3 - 2.4ghz running 10.6.8. Ive never seen this before. I don't have any external interface, perhaps its related to the drivers from your interface? Just a guess. Do other audio apps work? Like Audacity? It also uses portaudio.
Actually I have tried it on an older macbook without problem, but on my computer keeps on clicking awfully if I use portaudio --I attach a mp3 file with the output--. If I select jack there are no clicks. Besides, the audio in Audacity works perfectly fine.
(These tests were done with the mac built-in audio and with a RME fireface 800 with similar results).
ángel
Please file a bug report on this one too.
.hc
Hmm yeah, [cputime] does seem broken. Could you post a bug report please?
done
ángel faraldo
.hc
On Feb 18, 2012, at 2:54 PM, Ángel Faraldo wrote:
Hi there,
also frequent and irregular audio clicks on mac OSX 10.6.8, no matter how big the delay time is set to in the audio properties. (Tested with 'test audio/midi patch' @ SR 44100 and 48000 Hz with built-in audio, portaudio).
also, [cputime] appears not to work.
(pd-0.43.1-extended-20120218-macosx105-i386)
Ángel Faraldo _________________ www.angelfaraldo.info
On Feb 18, 2012, at 6:41 PM, João Pais wrote:
It sounds as if the audio isn't synced to the system card, or something. The sinus in the audio test patch has lots of irregular clicks, almost as if they would be dropouts.
What do you mean by noisy? Can you give more information? I really don't know much about Windows, so I rely on others to tell me how things there should be handled. patco and pob have been doing a lot of valuable work there.
.hc
On Feb 18, 2012, at 12:13 PM, João Pais wrote:
> Hi Hans, > > great job. But, here in XP, I get audio problems: trying to run with asio (as I always do with 0.42), the audio is very noisy. > Audio options are -asio -audioindev 2 -audiooutdev 2 -channels 2 -midiindev 1 -midioutdev 1 -audiobuf 40, and they always worked with previous versions of pd-ext. > > João > >> >> http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43... >> >> The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here: >> >> http://autobuild.puredata.info/auto-build/latest/ >> >> First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5). >> >> pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort. >> >> There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu. >> >> • Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords. >> >> • Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets. >> >> • Autopatch mode automatically connects objects as you create them. >> >> • Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance. >> >> The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose. >> >> There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well. >> >> The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI. >> >> One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more. >> >> You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write? >> >> >> >> _______________________________________________ >> Pd-announce mailing list >> Pd-announce@iem.at >> http://lists.puredata.info/listinfo/pd-announce >> >> _______________________________________________ >> Pd-list@iem.at mailing list >> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list > > > -- > Friedenstr. 58 > 10249 Berlin (Deutschland) > Tel +49 30 42020091 | Mob +49 162 6843570 > Studio +49 30 69509190 > jmmmpais@googlemail.com | skype: jmmmpjmmmp
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
-- Friedenstr. 58 10249 Berlin (Deutschland) Tel +49 30 42020091 | Mob +49 162 6843570 Studio +49 30 69509190 jmmmpais@googlemail.com | skype: jmmmpjmmmp
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Ángel Faraldo _________________ www.angelfaraldo.info
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
Ángel Faraldo _________________ www.angelfaraldo.info
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Ángel Faraldo _________________ www.angelfaraldo.info
On Feb 20, 2012, at 5:53 AM, Ángel Faraldo wrote:
On Feb 19, 2012, at 7:08 PM, Hans-Christoph Steiner wrote:
On Sun, Feb 19, 2012, at 11:19, Ángel Faraldo wrote:
Begin forwarded message:
From: Hans-Christoph Steiner hans@at.or.at Date: February 18, 2012 9:02:07 PM GMT+01:00 To: Ángel Faraldo angelfaraldo@gmail.com Cc: João Pais jmmmpais@googlemail.com, "pd-list@iem.at List" pd-list@iem.at Subject: Re: [PD] new editing features of Pd-extended 0.43, now in beta!
also frequent and irregular audio clicks on mac OSX 10.6.8, no matter how big the delay time is set to in the audio properties. (Tested with 'test audio/midi patch' @ SR 44100 and 48000 Hz with built-in audio, portaudio).
What kind of computer and audio interface are you using?
macbook pro 2.66GHz Intel Core 2 Duo with OSX 10.6.8. I tested it with the built-in audio and a RME Fireface 800 with similar results.
I'm on a very similar machine', a MacBook pro 3 - 2.4ghz running 10.6.8. Ive never seen this before. I don't have any external interface, perhaps its related to the drivers from your interface? Just a guess. Do other audio apps work? Like Audacity? It also uses portaudio.
Actually I have tried it on an older macbook without problem, but on my computer keeps on clicking awfully if I use portaudio --I attach a mp3 file with the output--. If I select jack there are no clicks. Besides, the audio in Audacity works perfectly fine.
(These tests were done with the mac built-in audio and with a RME fireface 800 with similar results). <pd_testAudio_44100_20msec_portaudio.mp3>
What happens if you increase the Delay (msec) in the Audio Settings to something like 50?
.hc
ángel
Please file a bug report on this one too.
.hc
Hmm yeah, [cputime] does seem broken. Could you post a bug report please?
done
ángel faraldo
.hc
On Feb 18, 2012, at 2:54 PM, Ángel Faraldo wrote:
Hi there,
also frequent and irregular audio clicks on mac OSX 10.6.8, no matter how big the delay time is set to in the audio properties. (Tested with 'test audio/midi patch' @ SR 44100 and 48000 Hz with built-in audio, portaudio).
also, [cputime] appears not to work.
(pd-0.43.1-extended-20120218-macosx105-i386)
Ángel Faraldo _________________ www.angelfaraldo.info
On Feb 18, 2012, at 6:41 PM, João Pais wrote:
It sounds as if the audio isn't synced to the system card, or something. The sinus in the audio test patch has lots of irregular clicks, almost as if they would be dropouts.
> > What do you mean by noisy? Can you give more information? I really don't know much about Windows, so I rely on others to tell me how things there should be handled. patco and pob have been doing a lot of valuable work there. > > .hc > > On Feb 18, 2012, at 12:13 PM, João Pais wrote: > >> Hi Hans, >> >> great job. But, here in XP, I get audio problems: trying to run with asio (as I always do with 0.42), the audio is very noisy. >> Audio options are -asio -audioindev 2 -audiooutdev 2 -channels 2 -midiindev 1 -midioutdev 1 -audiobuf 40, and they always worked with previous versions of pd-ext. >> >> João >> >>> >>> http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43... >>> >>> The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here: >>> >>> http://autobuild.puredata.info/auto-build/latest/ >>> >>> First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5). >>> >>> pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort. >>> >>> There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu. >>> >>> • Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords. >>> >>> • Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets. >>> >>> • Autopatch mode automatically connects objects as you create them. >>> >>> • Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance. >>> >>> The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose. >>> >>> There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well. >>> >>> The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI. >>> >>> One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more. >>> >>> You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write? >>> >>> >>> >>> _______________________________________________ >>> Pd-announce mailing list >>> Pd-announce@iem.at >>> http://lists.puredata.info/listinfo/pd-announce >>> >>> _______________________________________________ >>> Pd-list@iem.at mailing list >>> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list >> >> >> -- >> Friedenstr. 58 >> 10249 Berlin (Deutschland) >> Tel +49 30 42020091 | Mob +49 162 6843570 >> Studio +49 30 69509190 >> jmmmpais@googlemail.com | skype: jmmmpjmmmp > > > > ---------------------------------------------------------------------------- > > I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler > >
-- Friedenstr. 58 10249 Berlin (Deutschland) Tel +49 30 42020091 | Mob +49 162 6843570 Studio +49 30 69509190 jmmmpais@googlemail.com | skype: jmmmpjmmmp
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Ángel Faraldo _________________ www.angelfaraldo.info
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
Ángel Faraldo _________________ www.angelfaraldo.info
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Ángel Faraldo _________________ www.angelfaraldo.info
Computer science is no more related to the computer than astronomy is related to the telescope. -Edsger Dykstra
Hey Hans,
I'm on OSX 10.5, and I'm getting this at startup:
/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin: dlopen(/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin, 10): Library not loaded: @executable_path/../Frameworks/Tcl.framework/Versions/8.5/Tcl Referenced from: /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin Reason: no suitable image found. Did find: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl: mach-o, but wrong architecture /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../startup/tclpd: can't load startup library'!
For shits and giggles, I tried replacing the bad 8.5 folder that it does find with the one included in the Pd-extended-20120217.app package, and the error goes away. So, I'm guessing the @executable_path isn't set correctly?
.mmb
On Fri, Feb 17, 2012 at 3:02 PM, Hans-Christoph Steiner hans@at.or.at wrote:
http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here:
http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5).
pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.
There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.
• Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.
The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose.
There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well.
The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.
One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.
You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Looks like you downloaded the 64-bit version. See my previous mail in this thread about the 64-bit version.
.hc
On Feb 18, 2012, at 1:44 PM, Mike Moser-Booth wrote:
Hey Hans,
I'm on OSX 10.5, and I'm getting this at startup:
/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin: dlopen(/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin, 10): Library not loaded: @executable_path/../Frameworks/Tcl.framework/Versions/8.5/Tcl Referenced from: /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin Reason: no suitable image found. Did find: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl: mach-o, but wrong architecture /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../startup/tclpd: can't load startup library'!
For shits and giggles, I tried replacing the bad 8.5 folder that it does find with the one included in the Pd-extended-20120217.app package, and the error goes away. So, I'm guessing the @executable_path isn't set correctly?
.mmb
On Fri, Feb 17, 2012 at 3:02 PM, Hans-Christoph Steiner hans@at.or.at wrote:
http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here:
http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5).
pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.
There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.
• Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.
The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose.
There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well.
The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.
One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.
You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Mike Moser-Booth - mmoserbooth@gmail.com Master's Student in Music Technology Schulich School of Music, McGill University Centre for Interdisciplinary Research in Music Media and Technology
"If you think education is expensive, try ignorance" -Derek Bok
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
I downloaded the one named Pd-0.43.1-extended-macosx105-i386.dmg. Is that not the right one?
.mmb
On Sat, Feb 18, 2012 at 2:45 PM, Hans-Christoph Steiner hans@at.or.at wrote:
Looks like you downloaded the 64-bit version. See my previous mail in this thread about the 64-bit version.
.hc
On Feb 18, 2012, at 1:44 PM, Mike Moser-Booth wrote:
Hey Hans,
I'm on OSX 10.5, and I'm getting this at startup:
/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin: dlopen(/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin, 10): Library not loaded: @executable_path/../Frameworks/Tcl.framework/Versions/8.5/Tcl Referenced from: /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin Reason: no suitable image found. Did find: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl: mach-o, but wrong architecture /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../startup/tclpd: can't load startup library'!
For shits and giggles, I tried replacing the bad 8.5 folder that it does find with the one included in the Pd-extended-20120217.app package, and the error goes away. So, I'm guessing the @executable_path isn't set correctly?
.mmb
On Fri, Feb 17, 2012 at 3:02 PM, Hans-Christoph Steiner hans@at.or.at wrote:
http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here:
http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5).
pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.
There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.
• Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.
The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose.
There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well.
The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.
One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.
You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Mike Moser-Booth - mmoserbooth@gmail.com Master's Student in Music Technology Schulich School of Music, McGill University Centre for Interdisciplinary Research in Music Media and Technology
"If you think education is expensive, try ignorance" -Derek Bok
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
That's the right one. Here's the problem:
Reason: no suitable image found. Did find: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl: mach-o, but wrong architecture
You have installed a Tcl framework in /Library/Frameworks that seems to be for the wrong architecture.
.hc
On Feb 18, 2012, at 3:53 PM, Mike Moser-Booth wrote:
I downloaded the one named Pd-0.43.1-extended-macosx105-i386.dmg. Is that not the right one?
.mmb
On Sat, Feb 18, 2012 at 2:45 PM, Hans-Christoph Steiner hans@at.or.at wrote:
Looks like you downloaded the 64-bit version. See my previous mail in this thread about the 64-bit version.
.hc
On Feb 18, 2012, at 1:44 PM, Mike Moser-Booth wrote:
Hey Hans,
I'm on OSX 10.5, and I'm getting this at startup:
/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin: dlopen(/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin, 10): Library not loaded: @executable_path/../Frameworks/Tcl.framework/Versions/8.5/Tcl Referenced from: /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin Reason: no suitable image found. Did find: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl: mach-o, but wrong architecture /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../startup/tclpd: can't load startup library'!
For shits and giggles, I tried replacing the bad 8.5 folder that it does find with the one included in the Pd-extended-20120217.app package, and the error goes away. So, I'm guessing the @executable_path isn't set correctly?
.mmb
On Fri, Feb 17, 2012 at 3:02 PM, Hans-Christoph Steiner hans@at.or.at wrote:
http://at.or.at/hans/blog/2012/02/17/new-editing-feature-of-pd-extended-0-43...
The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements, and we wanted to make sure we got it right, so your patches all work, but the improvements all shine. Its now solidly beta, so we’re looking for testers. Download a nightly build to try here:
http://autobuild.puredata.info/auto-build/latest/
First off, the pd-gui side of Pd has been re-written from scratch. When you run Pd, you are actually running two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release (0.42.5).
pd still handles some of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.
There are so many ideas for making a better editing experience in Pd, this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.
• Magic Glass let’s you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.
The Pd Window is also majorly overhauled. First of all, its fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, ok, maybe if you send 10,000 messages/second but that is a way too many). There are also now 5 levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll get the whole firehose.
There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects as well.
The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.
One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.
You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. What kind of GUI plugin will write?
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Mike Moser-Booth - mmoserbooth@gmail.com Master's Student in Music Technology Schulich School of Music, McGill University Centre for Interdisciplinary Research in Music Media and Technology
"If you think education is expensive, try ignorance" -Derek Bok
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
-- Mike Moser-Booth - mmoserbooth@gmail.com Master's Student in Music Technology Schulich School of Music, McGill University Centre for Interdisciplinary Research in Music Media and Technology
"If you think education is expensive, try ignorance" -Derek Bok
News is what people want to keep hidden and everything else is publicity. - Bill Moyers
Right. But why is it looking for that one if the correct one is included in the Pd-0.43.1-extended app? When I took out the one had installed, I still got the error. But it worked fine when I copied the one in the app and replaced the bad version. I guess I'm just wondering why the Tcl framework is in the app if it's not being used.
.mmb
On Sat, Feb 18, 2012 at 8:25 PM, Hans-Christoph Steiner hans@at.or.at wrote:
That's the right one. Here's the problem:
Reason: no suitable image found. Did find: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl: mach-o, but wrong architecture
You have installed a Tcl framework in /Library/Frameworks that seems to be for the wrong architecture.
.hc
On Feb 18, 2012, at 3:53 PM, Mike Moser-Booth wrote:
I downloaded the one named Pd-0.43.1-extended-macosx105-i386.dmg. Is that not the right one?
.mmb
On Sat, Feb 18, 2012 at 2:45 PM, Hans-Christoph Steiner hans@at.or.at wrote:
Looks like you downloaded the 64-bit version. See my previous mail in this thread about the 64-bit version.
.hc
On Feb 18, 2012, at 1:44 PM, Mike Moser-Booth wrote:
Hey Hans,
I'm on OSX 10.5, and I'm getting this at startup:
/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin: dlopen(/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin, 10): Library not loaded: @executable_path/../Frameworks/Tcl.framework/Versions/8.5/Tcl Referenced from: /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin Reason: no suitable image found. Did find: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl: mach-o, but wrong architecture /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../startup/tclpd: can't load startup library'!
For shits and giggles, I tried replacing the bad 8.5 folder that it does find with the one included in the Pd-extended-20120217.app package, and the error goes away. So, I'm guessing the @executable_path isn't set correctly?
.mmb
Good point, hopefully fixed with this commit:
http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=revision&revi...
.hc
On Feb 19, 2012, at 1:25 PM, Mike Moser-Booth wrote:
Right. But why is it looking for that one if the correct one is included in the Pd-0.43.1-extended app? When I took out the one had installed, I still got the error. But it worked fine when I copied the one in the app and replaced the bad version. I guess I'm just wondering why the Tcl framework is in the app if it's not being used.
.mmb
On Sat, Feb 18, 2012 at 8:25 PM, Hans-Christoph Steiner hans@at.or.at wrote:
That's the right one. Here's the problem:
Reason: no suitable image found. Did find: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl: mach-o, but wrong architecture
You have installed a Tcl framework in /Library/Frameworks that seems to be for the wrong architecture.
.hc
On Feb 18, 2012, at 3:53 PM, Mike Moser-Booth wrote:
I downloaded the one named Pd-0.43.1-extended-macosx105-i386.dmg. Is that not the right one?
.mmb
On Sat, Feb 18, 2012 at 2:45 PM, Hans-Christoph Steiner hans@at.or.at wrote:
Looks like you downloaded the 64-bit version. See my previous mail in this thread about the 64-bit version.
.hc
On Feb 18, 2012, at 1:44 PM, Mike Moser-Booth wrote:
Hey Hans,
I'm on OSX 10.5, and I'm getting this at startup:
/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin: dlopen(/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin, 10): Library not loaded: @executable_path/../Frameworks/Tcl.framework/Versions/8.5/Tcl Referenced from: /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin Reason: no suitable image found. Did find: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl: mach-o, but wrong architecture /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../startup/tclpd: can't load startup library'!
For shits and giggles, I tried replacing the bad 8.5 folder that it does find with the one included in the Pd-extended-20120217.app package, and the error goes away. So, I'm guessing the @executable_path isn't set correctly?
.mmb
-- Mike Moser-Booth - mmoserbooth@gmail.com Master's Student in Music Technology Schulich School of Music, McGill University Centre for Interdisciplinary Research in Music Media and Technology
"If you think education is expensive, try ignorance" -Derek Bok
Programs should be written for people to read, and only incidentally for machines to execute.
- from Structure and Interpretation of Computer Programs
Just gave the auto-build a go, and it appears that the error is fixed. Thanks!
.mmb
On Sun, Feb 19, 2012 at 5:16 PM, Hans-Christoph Steiner hans@at.or.at wrote:
Good point, hopefully fixed with this commit:
http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=revision&revi...
.hc
On Feb 19, 2012, at 1:25 PM, Mike Moser-Booth wrote:
Right. But why is it looking for that one if the correct one is included in the Pd-0.43.1-extended app? When I took out the one had installed, I still got the error. But it worked fine when I copied the one in the app and replaced the bad version. I guess I'm just wondering why the Tcl framework is in the app if it's not being used.
.mmb
On Sat, Feb 18, 2012 at 8:25 PM, Hans-Christoph Steiner hans@at.or.at wrote:
That's the right one. Here's the problem:
Reason: no suitable image found. Did find: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl: mach-o, but wrong architecture
You have installed a Tcl framework in /Library/Frameworks that seems to be for the wrong architecture.
.hc
On Feb 18, 2012, at 3:53 PM, Mike Moser-Booth wrote:
I downloaded the one named Pd-0.43.1-extended-macosx105-i386.dmg. Is that not the right one?
.mmb
On Sat, Feb 18, 2012 at 2:45 PM, Hans-Christoph Steiner hans@at.or.at wrote:
Looks like you downloaded the 64-bit version. See my previous mail in this thread about the 64-bit version.
.hc
On Feb 18, 2012, at 1:44 PM, Mike Moser-Booth wrote:
Hey Hans,
I'm on OSX 10.5, and I'm getting this at startup:
/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin: dlopen(/Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin, 10): Library not loaded: @executable_path/../Frameworks/Tcl.framework/Versions/8.5/Tcl Referenced from: /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../extra/tclpd/tclpd.pd_darwin Reason: no suitable image found. Did find: /Library/Frameworks/Tcl.framework/Versions/8.5/Tcl: mach-o, but wrong architecture /Applications/Pd-0.43.1-extended-20120217.app/Contents/Resources/Scripts/../startup/tclpd: can't load startup library'!
For shits and giggles, I tried replacing the bad 8.5 folder that it does find with the one included in the Pd-extended-20120217.app package, and the error goes away. So, I'm guessing the @executable_path isn't set correctly?
.mmb
-- Mike Moser-Booth - mmoserbooth@gmail.com Master's Student in Music Technology Schulich School of Music, McGill University Centre for Interdisciplinary Research in Music Media and Technology
"If you think education is expensive, try ignorance" -Derek Bok
Programs should be written for people to read, and only incidentally for machines to execute. - from Structure and Interpretation of Computer Programs
----- Original Message -----
From: Hans-Christoph Steiner hans@at.or.at To: pd-announce pd-announce@iem.at Cc: Sent: Friday, February 17, 2012 3:02 PM Subject: [PD] [PD-announce] new editing features of Pd-extended 0.43, now in beta!
[...]
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
You can also make manual tips that are basically like notifications to a canvas:
[tgl] | [tip $1 Hello World( | [send thisCanvas]
[namecanvas thisCanvas]
The tip will try to stay out of the way of the mouse. This is a nice tool to design tutorials that can dynamically give tips as the user clicks on stuff, for example. You can also generate the tips from a gui plugin-- might be interesting to make a "patching clock" that sends a timed message to the canvas that currently has focus: "Hey, you've been patching for 20 minutes straight... take a break!"
-Jonathan
-
Hans-Christoph Steiner -
IOhannes m zmoelnig -
Jonathan Wilkes -
João Pais -
Lorenzo Sutton -
m.e.grimm -
Mathieu Bouchard -
Mike Moser-Booth -
Rich E -
Roman Haefeli -
Scott R. Looney -
Tuti -
Ángel Faraldo