date:20120218

[PD] hid object does not work for wacom tablet under Linux

2012-02-18 Thread Sylvain Hanneton


Hello,
I try to capture the data from my Bamboo touch wacom tablet with the HID 
object.

Everything is ok except the polling of the data.

The tablet works fine with X. I can see the data with the xidump command 
line tool.


I think that the input events are provided only to the X event queue and 
not to the hid system of pd.

I'm certainly not alone to be in that situation.

Thank you !

PS : My linux is Ubuntu Lucid 10.04


___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list

[PD] nested nqpoly4's

2012-02-18 Thread James Mckernon

Hi all,

I've noticed that nesting nqpoly4 doesn't seem to work. i.e., if a patch
contains an nqpoly4 of patchX, and patchX contains an nqpoly4 of patchY,
then the patchY's will not instantiate. Instead, a bunch of 'connection
failed' messages appear in pd's console.

Is this a known bug? Any workarounds? I did discover that opening and
saving patchY will cause its nqpoly4 to reload, and then instantiate
properly, but I don't feel this is a good solution for regular use.

Cheers!
J
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list

[PD] sigmund list sort

2012-02-18 Thread labyrinthuscochlearis

hi all,

what would be a good way to transform sigmund~'s peaks output so that I
get a list with peak amplitudes but in the ascending order of the
corresponding frequencies?

thanks,
christian


___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] minicomputers for pd + gem (linux)

2012-02-18 Thread Jordi Sala

Thanks a lot!!

On 17 February 2012 21:46, Andy Farnell padawa...@obiwannabe.co.uk wrote:

 On Fri, Feb 17, 2012 at 03:12:57PM -0500, Hans-Christoph Steiner wrote:
 
  On Feb 17, 2012, at 2:17 PM, Mathieu Bouchard wrote:
 
   Le 2012-02-17 à 18:53:00, Jordi Sala a écrit :
  
   Can anyone help me with minicomputers that run acceptably with Ubuntu
 + PD (GEM)? some experience?
  
   DEC's PDP-1134 would be your best bet.
  
  
 http://1.bp.blogspot.com/_ud6cVWt3cc4/TFSxKkaka_I/AJ8/cICybvX3IHE/s1600/pdp1134.jpg
  
   It can't run Ubuntu, but it can run a fairly recent version of UNIX,
 to which PureData could be ported if it gets shrunk to fit in 0.000122 meg
 of RAM.
  
   If the RAM is a bit too tight, don't worry, it comes with two
 tapedecks, as you can see in the 1st and 4th towers.
  
   It's such a wonder of technology. Much smaller than a real computer.
  
   It wouldn't take that many man-months of porting to get it going...
  
   http://en.wikipedia.org/wiki/Minicomputer
 
  We are not living in the 80s any more. ;)


 But some of us have to keep reliving it in therapy

 http://www.thefashionpolice.net/2007/09/fashion-crimes-of-the-80s.html




 
  .hc
 
 
 
 
 
  The arc of history bends towards justice. - Dr. Martin Luther King,
 Jr.
 
 
 
  ___
  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




-- 
Jordi Sala
http://musa.poperbu.net
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] nested nqpoly4's

2012-02-18 Thread Jonathan Wilkes

Pd somehow checks for abstractions nested inside themselves and refuses to 
create the inner one(s).
 
Obviously under normal circumstances such self-nested abstractions would expand 
to infinity.
 
Can Pd tell the difference between dynamically instantiated objects and 
normal instantiation?
 
If not, you'll be forced to solve the halting problem to be able to get what 
you want, or else put an arbitrary 
limit on abstraction nesting depth (like Pd's recursion).
 
-Jonathan


From: James Mckernon jmcker...@gmail.com
To: pd-list@iem.at 
Sent: Saturday, February 18, 2012 9:47 AM
Subject: [PD] nested nqpoly4's


Hi all,

I've noticed that nesting nqpoly4 doesn't seem to work. i.e., if a patch 
contains an nqpoly4 of patchX, and patchX contains an nqpoly4 of patchY, then 
the patchY's will not instantiate. Instead, a bunch of 'connection failed' 
messages appear in pd's console.

Is this a known bug? Any workarounds? I did discover that opening and saving 
patchY will cause its nqpoly4 to reload, and then instantiate properly, but I 
don't feel this is a good solution for regular use.

Cheers!
J

___
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] sigmund list sort

2012-02-18 Thread Mathieu Bouchard


Le 2012-02-18 à 16:19:00, labyrinthuscochlearis a écrit :

what would be a good way to transform sigmund~'s peaks output so that I 
get a list with peak amplitudes but in the ascending order of the 
corresponding frequencies?


GridFlow's [#grade] gives you a list of item numbers in the order that you 
need to pick them so that they be sorted. This can be used for sorting a 
table with multiple columns according to one column, whereas other sorting 
tools in Pd might only support sorting individual values.


  http://gridflow.ca/help/%23grade-help.html

You will need the appropriate conversion from list to grid (a kind of 
super-list type) and grid to list. Also, [#store] is a great shortcut for 
reordering elements using the output of [#grade].


This uses a plugin that you'd download from http://gridflow.ca/

 __
| 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

[PD] [PD-announce] old editing features of Pd-extended 0.43

2012-02-18 Thread Mathieu Bouchard


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-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] old editing features of Pd-extended 0.43

2012-02-18 Thread Tuti

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 ma...@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-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




-- 
-
José Fornari (Tuti)
http:/sites.google.com/site/tutifornari/
email: tutiforn...@gmail.com
skype: tutifornari
cel: (11) 8318-8778

___
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!

2012-02-18 Thread João Pais


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!

2012-02-18 Thread Hans-Christoph Steiner

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] distorted sine on OSX 2.6.8 with firewire interface

2012-02-18 Thread João Pais


 some of my students reported problems with pd using external firewire
interfaces on MacBooks with OSX 2.6.8. A sine wave from the test
audio and midi panel is very distorted.

We encountered this problem on a consumer ESI Interface and on the RME
Fireface. We tried different pd versions (0.43 and 0.42 branches,
vanilla and extended) using coreaudio and jack with the same
result. The internal sound card and standard usb interfaces sound fine
with pd.

The problem seems strange as the firewire interfaces work without any
problems with other audio applications like logic or live.

I tried to google this problem but couldn't find anything. Is this a
known issue and can someone comment on this or give any advice how to
proceed?


I have problems running my RME Multiface on XP with pd 0.42, have to  
downgrade to 0.41 when I need it. But that might be an asio problem (or  
not?).


João

___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] old editing features of Pd-extended 0.43

2012-02-18 Thread Hans-Christoph Steiner


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.




___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] old editing features of Pd-extended 0.43

2012-02-18 Thread Hans-Christoph Steiner


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 ma...@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



___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] new editing features of Pd-extended 0.43, now in beta!

2012-02-18 Thread Hans-Christoph Steiner

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-now-in-beta/

http://autobuild.puredata.info/auto-build/latest/

• 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.

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

Re: [PD] new editing features of Pd-extended 0.43, now in beta!

2012-02-18 Thread João Pais

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-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

Re: [PD] new editing features of Pd-extended 0.43, now in beta!

2012-02-18 Thread Hans-Christoph Steiner

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-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.

• 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.

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.

Re: [PD] sigmund list sort

2012-02-18 Thread Miller Puckette

I believe there's no good way to do this in pd vanilla.  THere should be
a 'list sort' but I haven't figured out what would be the best design.
(and there's probably already a list sort in Pd extended :)

cheers
Miller
On Sat, Feb 18, 2012 at 04:19:58PM +0100, labyrinthuscochlearis wrote:
 hi all,
 
 what would be a good way to transform sigmund~'s peaks output so that I
 get a list with peak amplitudes but in the ascending order of the
 corresponding frequencies?
 
 thanks,
 christian
 
 
 ___
 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] old editing features of Pd-extended 0.43

2012-02-18 Thread Mathieu Bouchard


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___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] roughness Pitch-Comonality objects (was Re: number to fractions external?)

2012-02-18 Thread Mathieu Bouchard


Le 2012-02-14 à 13:54:00, Alexandre Torres Porres a écrit :

the object code is fine, but I've changed it, just have a look to see if 
you find something funny.


Can you just make a list of all the components that I worked on, to see 
whether I have all of them. I remember that I didn't have a copy of 
everything, and some files were lost in a HD crash, but I don't remember 
whether everything was recovered in the end, and whether I have the latest 
versions.


You see, it was a long time ago already...

 __
| 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

[PD] osc logger

2012-02-18 Thread Jeppi Jeppi


Hi all,I build a [coll]-based OSC logger to save to a file all the OSC activity 
received from the network (coming from 9 to 12 nodes). Unfortunately it seems 
it severely interferes with realtime audio in that PD instance when too much 
OSC is received.I wonder if any of you tried a different approach.
Thanks in advance,Josep M ___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] sigmund list sort

2012-02-18 Thread Mathieu Bouchard


Le 2012-02-18 à 09:58:00, Miller Puckette a écrit :

I believe there's no good way to do this in pd vanilla.  THere should be 
a 'list sort' but I haven't figured out what would be the best design. 
(and there's probably already a list sort in Pd extended :)


the [list-sort] abstraction uses a high-constant O(n²) algorithm that 
breaks once you try to sort more than 125 values. For [sigmund~]'s output 
this is not very relevant, what's relevant is that it can't deal with more 
than one « column », that is, it can't sort pairs of numbers.


That's why I mention [#grade]. Not only it's using a lean O(n log n) 
algorithm that can work on millions of elements, it also gives you the 
ordering instead of applying the sorting. This means that you can fairly 
easily construct a sorter by any kind of key column, including cases 
computed on the fly (e.g. sort according to dbA computed using both 
amplitude and frequencies, where the dbA is not part of the table).


That kind of modular design is something I borrowed from the APL language.

 __
| 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

[PD] save search path 0.43 OSX

2012-02-18 Thread Joson Android

Dear List!

i love pd-extended-0.43 !! but i cannot add any search path in the 
prefferences. It will show my new settings right when i make changes but wont 
save anything. It prints ripts/../extra/mapping: no such object in the 
pd-window. It works in pd-extended-0.42.5 . Should there be a file where pd 
saves the path? Where is it?
Also, when i make changes in 0.42.5, 0.43 will know about them on next startup.

I use OSX10.6.7 and the latest autobuild of xi386 version of 0.43.1-extended.

Maybe it is the fault of chaotic me and chaotic computer, so i deleted all old 
versions of pd, but that didn't help...

Johnny
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] Pd-extended can't see $0-arrays ???

2012-02-18 Thread Mathieu Bouchard


Le 2012-02-13 à 20:07:00, Jonathan Wilkes a écrit :

Do gpointers only point to scalars?  Because if you _could_ get a 
pointer to an array-- perhaps using my canvas 'get' method patch-- you 
could just make all arrays canvas local and forget all this $0- 
business:


AFAIK :

Pointers point either to scalars or to array elements. You can't point to 
a whole array in a way distinct from pointing to an element of it. 
Therefore, a pointer to the first element (0) of an array is the best 
equivalent of what would be a pointer to an array (like it is in C 
language).


 __
| 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

Re: [PD] Fwd: [PD-dev] New snapshot of pd-l2ork available -- feedback appreciated

2012-02-18 Thread Mathieu Bouchard


Le 2012-02-13 à 20:27:00, Patrice Colet a écrit :

oupse I've confused both versions, sorry for that, a thousands excuses 
:)


Je pense pas que ça veuille dire ce que tu penses que ça veut dire.

  http://en.wiktionary.org/wiki/excuse#Noun

 __
| 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

Re: [PD] [PD-announce] new editing features of Pd-extended 0.43, now in beta!

2012-02-18 Thread Mike Moser-Booth

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/

http://autobuild.puredata.info/auto-build/latest/

• 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.

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.

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

Re: [PD] GUI and DSP

2012-02-18 Thread Mathieu Bouchard


Le 2012-02-12 à 18:10:00, Hans-Christoph Steiner a écrit :

1) pd completely removed redrawing logic from the c code and migrated 
it into tcl (which is what you may have done in great part already 
inside desire-data)


The big problems with (1) is that not only you need to copy all the 
visible settings of the c object into tcl so that the tcl side has direct 
access to the info it needs to have, you also to have to sync those 
things between the two copies. E.g. what happens when you move an object 
while the patch changes its displayed value, or its background colour ?


2) pd used a different toolkit that allowed for more intelligent 
addressing of individual gui components (again, JUCE IMO comes at the 
very top here)


Ok, this needs something like step (1) above, but also note that if 
you are going to use a GUI toolkit that can't be used from Tcl, you either 
have to port it to Tcl, or stop depending on Tcl, which itself means 
either use a Tcl parser written in a language supported by JUCE, or use a 
different syntax that doesn't refer to Tcl (such as a binary protocol).



I agree.  I think a lot of this can be done incrementally.


It's not just that it can : it ought to be incremental. An example of 
something not done incrementally is DesireData, and see where it did lead.


Basically, take a chunk of logic and refactor it so that Tcl/Tk handles 
the GUI stuff and pd sends pd messages rather than lines of Tcl.


Sending Pd messages fixes the Tcl dependency problem. You could even run 
Pd in the server.


But note that client and server could be merged, so that you don't have to 
serialise and deserialise every thing that the client might need. Then 
pd-gui would become an extra thread in the server.


More client-server separation is more work, and the amount of sync-work 
required is greater than what it is in Pd now. I don't know how that 
compares to the amount of sync-work that would be done by a threaded 
model.


But basically, there are problems that are fundamental problems, and if 
you avoid solving things with multithread because mutexes are troublesome, 
then you'll solve those problems using processes that have to tell each 
other « ok, done, I'm ready » all of the time and it can grow to similar 
levels of complexity. For each situation, one or the other might be 
easier, but it's not very obvious in advance. What's obvious is that 
people can get into ideologies, and DesireData's design partially had to 
do with a threads-are-evil ideology.


OTOH, just because the possibility of multi-client pd and remote-client pd 
are not exploited by many people, doesn't really mean that they're not 
things worth pursuing... Johannes' multi-client pd involved inserting an 
extra process between the client and the server so that there can be 
several clients. Any kind of insertion like that is much harder (or 
impossible) in a threaded design.


 __
| 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

Re: [PD] save search path 0.43 OSX

2012-02-18 Thread Scott R. Looney

well, just to add my experience i think i can set search paths correctly,
but i would like to add that it seems to be quite difficult to have more
than one instance of PD-extended 0.43 on the computer (trying mac OS 10.6.4
w/ 32bit and 64bit builds) making it a bit challenging to check one build's
operation/stability against another on the same computer.

for example, the help browser shows all instances of installed objects on
the computer, and then console complains about multiple versions of files
existing. i've tried deleting the extra paths that show up to limit things,
which works temporarily, but on the next startup it just reverts back to
grabbing everything it can find again. it works the same in every .43
pd-extended build i've tried so far (several version of both 32 and 64 bit
builds in Dec/Jan). putting things on other drives doesn't work either - it
will find those paths as well.

scott

On Sat, Feb 18, 2012 at 10:17 AM, Joson Android 
joson.andr...@googlemail.com wrote:

 Dear List!

 i love pd-extended-0.43 !! but i cannot add any search path in the
 prefferences. It will show my new settings right when i make changes but
 wont save anything. It prints ripts/../extra/mapping: no such object in
 the pd-window. It works in pd-extended-0.42.5 . Should there be a file
 where pd saves the path? Where is it?
 Also, when i make changes in 0.42.5, 0.43 will know about them on next
 startup.

 I use OSX10.6.7 and the latest autobuild of xi386 version of
 0.43.1-extended.

 Maybe it is the fault of chaotic me and chaotic computer, so i deleted all
 old versions of pd, but that didn't help...

 Johnny
 ___
 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] GUI and DSP

2012-02-18 Thread Mathieu Bouchard


Le 2012-02-11 à 13:58:00, Ivica Ico Bukvic a écrit :

JUCE is amazing in terms of gui speed-up. Just check out bundled demos 
that come with the sdk... Half of Gem could be easily reimplemented 
using JUCE sdk...


Looks nice, but the window border of JuceDemo is weird. JuceDemo disables 
the WM-made border, and puts its own border, which doesn't seem to 
interpret «Maximise» the same way that the WM does, and is perhaps even 
buggy.


And what would be the cause of JUCE being slow on some computers ? I don't 
think that it would be acceptable that JUCE be mysteriously slow on some 
computers that aren't even old (if that's really what's happening).


 __
| 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

Re: [PD] Pd-extended can't see $0-arrays ???

2012-02-18 Thread Jonathan Wilkes

- Original Message -
 From: Mathieu Bouchard ma...@artengine.ca
 To: Jonathan Wilkes jancs...@yahoo.com
 Cc: Фывапр Олджэвич tofuc...@inbox.ru; PD-list pd-list@iem.at
 Sent: Saturday, February 18, 2012 1:20 PM
 Subject: Re: [PD] Pd-extended can't see $0-arrays ???

 Le 2012-02-13 à 20:07:00, Jonathan Wilkes a écrit :

 Do gpointers only point to scalars?  Because if you _could_ get a pointer 
 to an array-- perhaps using my canvas 'get' method patch-- you could 
 just make all arrays canvas local and forget all this $0- business:

 AFAIK :

 Pointers point either to scalars or to array elements. You can't point to a 
 whole array in a way distinct from pointing to an element of it. Therefore, a 
 pointer to the first element (0) of an array is the best equivalent of what 
 would be a pointer to an array (like it is in C language).

Hm, maybe it's simpler than that:
1) make all arrays canvas local, e.g., array1 is local to the canvas that 
holds its [table] object or Put menu array graph
2) tabread, tabwrite~, etc. read from the array on the local canvas
3) add an optional (gpointer) argument to the set method so you can do set 
arrayname (gpointer) to tell it to look in 
a different canvas for arrayname. (Since (gpointer) can point to the head of 
a glist.)

This could potentially double as a way to use ds-arrays inside tabread, 
tabwrite~, etc., since with set array (gpointer) 
$1 could specify the name of the [struct] that is used as a template for the 
array and $2 could point to scalar that contains it.

It wouldn't be hard to abstraction-ize it so the user doesn't even have to 
think about pointers or scalars or $0.

-Jonathan

 __
 | 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

Re: [PD] GUI and DSP

2012-02-18 Thread Jonathan Wilkes

- Original Message -
 From: Mathieu Bouchard ma...@artengine.ca
 To: Ivica Ico Bukvic i...@vt.edu
 Cc: Jonathan Wilkes jancs...@yahoo.com; Hans-Christoph Steiner 
 h...@at.or.at; pd-list@iem.at List pd-list@iem.at
 Sent: Saturday, February 18, 2012 2:06 PM
 Subject: Re: [PD] GUI and DSP

 Le 2012-02-11 à 13:58:00, Ivica Ico Bukvic a écrit :

 JUCE is amazing in terms of gui speed-up. Just check out bundled demos that 
 come with the sdk... Half of Gem could be easily reimplemented using JUCE 
 sdk...

 Looks nice, but the window border of JuceDemo is weird. JuceDemo disables the 
 WM-made border, and puts its own border, which doesn't seem to interpret 
 «Maximise» the same way that the WM does, and is perhaps even buggy.

From what I remember JUCE would by default give you pixel-exact UI down to the 
window border on every platform, at the expense of 
native-widgets/dialog-boxes/etc. 
for that specific OS.  Well, maybe you can get native widgets if you want, but 
I don't 
think you can get native window borders/dialog boxes/etc.

-Jonathan

 And what would be the cause of JUCE being slow on some computers ? I don't 
 think that it would be acceptable that JUCE be mysteriously slow on some 
 computers that aren't even old (if that's really what's happening).

 __
 | 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

Re: [PD] GUI and DSP

2012-02-18 Thread Mathieu Bouchard


Le 2012-02-18 à 11:29:00, Jonathan Wilkes a écrit :

From what I remember JUCE would by default give you pixel-exact UI down 
to the window border on every platform, at the expense of 
native-widgets/dialog-boxes/etc. for that specific OS.  Well, maybe you 
can get native widgets if you want, but I don't think you can get native 
window borders/dialog boxes/etc.


Then I don't think that we should be using JUCE. :-/

 __
| 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

Re: [PD] hid object does not work for wacom tablet under Linux

2012-02-18 Thread Hans-Christoph Steiner


[hid] on Linux relies on a /dev/input/event* devices.  If that device does not 
provide a /dev/input/event* device, then [hid] can't read it.  One possibility 
is that you are using an X driver for that tablet, so not a /dev/input/event* 
device.

.hc

On Feb 18, 2012, at 8:34 AM, Sylvain Hanneton wrote:

 Hello,
 I try to capture the data from my Bamboo touch wacom tablet with the HID 
 object.
 Everything is ok except the polling of the data.
 
 The tablet works fine with X. I can see the data with the xidump command line 
 tool.
 
 I think that the input events are provided only to the X event queue and not 
 to the hid system of pd.
 I'm certainly not alone to be in that situation.
 
 Thank you !
 
 PS : My linux is Ubuntu Lucid 10.04
 
 
 ___
 Pd-list@iem.at mailing list
 UNSUBSCRIBE and account-management - 
 http://lists.puredata.info/listinfo/pd-list





If nature has made any one thing less susceptible than all others of exclusive 
property, it is the action of the thinking power called an idea, which an 
individual may exclusively possess as long as he keeps it to himself; but the 
moment it is divulged, it forces itself into the possession of everyone, and 
the receiver cannot dispossess himself of it.- Thomas Jefferson



___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] osc logger

2012-02-18 Thread Hans-Christoph Steiner


Try using [textfile] for writing to a soundfile.  I've had good luck with it.

.hc

On Feb 18, 2012, at 1:06 PM, Jeppi Jeppi wrote:

 Hi all,
 I build a [coll]-based OSC logger to save to a file all the OSC activity 
 received from the network (coming from 9 to 12 nodes). Unfortunately it seems 
 it severely interferes with realtime audio in that PD instance when too much 
 OSC is received.
 I wonder if any of you tried a different approach.
 
 Thanks in advance,
 Josep M
 ___
 Pd-list@iem.at mailing list
 UNSUBSCRIBE and account-management - 
 http://lists.puredata.info/listinfo/pd-list





Mistrust authority - promote decentralization.  - the hacker ethic


___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] new editing features of Pd-extended 0.43, now in beta!

2012-02-18 Thread Hans-Christoph Steiner

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:

.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/

http://autobuild.puredata.info/auto-build/latest/

• 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.

Re: [PD] new editing features of Pd-extended 0.43, now in beta!

2012-02-18 Thread Ángel Faraldo

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: