Re: [PD] [PD-announce] new editing features of Pd-extended 0.43, now in beta!
- Original Message - From: Hans-Christoph Steiner h...@at.or.at To: pd-announce pd-annou...@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 ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [PD-announce] new editing features of Pd-extended 0.43, now in beta!
-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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9DaSQACgkQkX2Xpv6ydvTuwACg42vUZdWShhdqGW40RJM7gBuf Ql0An1VLghK5HkXHgF8C3dBAD3eMsJdu =s3xR -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [PD-announce] new editing features of Pd-extended 0.43, now in beta!
On Sun, Feb 19, 2012 at 4:20 AM, Hans-Christoph Steiner h...@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 ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [PD-announce] new editing features of Pd-extended 0.43, now in beta!
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 h...@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 lorenzofsut...@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-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/ 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
Re: [PD] [PD-announce] new editing features of Pd-extended 0.43, now in beta!
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 h...@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 lorenzofsut...@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-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/ 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
Re: [PD] [PD-announce] new editing features of Pd-extended 0.43, now in beta!
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-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/ 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-annou...@iem.at http://lists.puredata.info/listinfo/pd-announce ___ Pd-list@iem.at mailing list UNSUBSCRIBE and
Re: [PD] [PD-announce] new editing features of Pd-extended 0.43, now in beta!
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 lorenzofsut...@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-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/ 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
Re: [PD] [PD-announce] new editing features of Pd-extended 0.43, now in beta!
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 h...@at.or.at wrote: 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/ 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
[PD] [PD-announce] new editing features 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/ 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-annou...@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
Re: [PD] [PD-announce] new editing features of Pd-extended 0.43, now in beta!
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/ 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-annou...@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
Re: [PD] [PD-announce] new editing features of Pd-extended 0.43, now in beta!
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 lorenzofsut...@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