Re: [PD] Teaching Pd to Children

2008-06-20 Thread Hans-Christoph Steiner


This sounds like a very cool project, please do keep us posted on  
it.  I'd love to hear more about it.


.hc

On Jun 15, 2008, at 11:29 PM, Kyle Klipowicz wrote:

Thanks so much for your comments everybody! I am still mulling over  
it, but I like the idea of using something like Squeak as well. I  
remember using a DSP software last year that was very children- 
oriented, but cannot for the life of me remember the name of the  
software or where to get it!


As for Pd, I will be scouring for more resources. I'm thinking that  
"fun" is more important than math. After all, this IS summer school.


As for what K-8 summer school is: K-8 is an age range from 5 years  
old (K, Kindergarden) to 13 years old (8, 8th grade). Summer school  
is an extra time for kids to catch up on learning when everyone  
else is on break in the US.


Also, thanks Andy for providing such a wonderful resource! It's  
grown quite a bit since I first laid eyes on it.


~Kyle

On Sat, Jun 14, 2008 at 4:27 PM, Peter Plessas <[EMAIL PROTECTED]> wrote:
Kyle Klipowicz wrote:
Hello Listers~

I'm teaching a 1 month Summer school session for K-8 grade students  
and
would like to include Pd for a mathematics learning tool. I am  
wondering if
anyone else has done something similar, or has any links to DSP/ 
math related
materials that would be suitable for this age group. Also, if  
anyone is
sharing their lesson plans for Pd beginners, I would love to see  
something

that I might be able to adapt for my students.

Any ideas would be greatly appreciated, as kids often hate Summer  
school and

I want to make this a fun activity for them.

Make sure to tackle number ranges (mapping), like: Moving one  
slider up will make another one go down, but only half as far, etc...



~Kyle




-- 
--


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




--
-

 -
  - --
http://perhapsidid.wordpress.com
http://myspace.com/kyleklipowicz
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/ 
listinfo/pd-list




 



News is what people want to keep hidden and everything else is  
publicity.  - Bill Moyers



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


Re: [PD] bug in gop data-structs?

2008-06-20 Thread Miller Puckette
yep, I'm getting this too.  I'll try to figure that one out.

cheers
Miller

On Thu, Jun 19, 2008 at 08:16:40AM +0200, Frank Barknecht wrote:
> Hallo,
> Rich E hat gesagt: // Rich E wrote:
> 
> > I'm just checking to see if this is in fact a bug, or I am doing something
> > wrong with GOP data structs.  The attached patch draws bars that symbolize 2
> > measures, with 4 sub divisions each.  The problem is, when I minimize the
> > patch and bring it back up, they disappear... seems like a bug to me, and
> > I'll file a report if it is.
> 
> With your new patch I can confirm the bug for pd 0.41 under blackbox
> on Linux: They disappear.
> 
> Ciao
> -- 
>  Frank Barknecht _ __footils.org__
> 
> ___
> 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.tk: how to get rid of scrollbars and menus?

2008-06-20 Thread Mathieu Bouchard

On Thu, 12 Jun 2008, patrick wrote:

in pdmtl abstractions the 1.browser.pd doesn't have any menu or scrollbar. 
this hack is done without editing pd.tk - also disabling ctrl+e.
tof did it, so i don't know the detail about this little hack. but i think he 
used toxy to do it.


Most likely using a tk command like [pack forget .x%x.whatever] or 
[destroy .x%x.whatever]. Most likely [pack forget], because then the 
scrollbar still exists, so that things that are interacting with the 
scrollbar don't get an error trying to interact with a dead object.


The menu bar is a special thing. ten years ago, people were using normal 
tk widgets and layouts to make a menu bar. However, to integrate better 
with the Mac, the [pack forget .x%x.whatever] command can't be used, as 
the layout is handled by the window itself; therefore it has to be done 
using [.x%x configure -menubar something].


 _ _ __ ___ _  _ _ ...
| Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Spotlight Importer for OS X

2008-06-20 Thread Hans-Christoph Steiner

On Jun 20, 2008, at 2:34 PM, Luke Iannini wrote:

> On Fri, Jun 20, 2008 at 5:15 AM, Hans-Christoph Steiner  
> <[EMAIL PROTECTED]> wrote:
>>
>> On Jun 20, 2008, at 1:55 PM, Luke Iannini wrote:
>>
>>> On Fri, Jun 20, 2008 at 4:02 AM, Hans-Christoph Steiner
>>> <[EMAIL PROTECTED]> wrote:

 Does this work at all on 10.4/Tiger?

>>> Yes, it's configured by default to work with both 10.4 and 10.5.
>>
>> Any idea whether it would cause problems on 10.3?  That's not a make-
>> or-break thing, but it would be nice if it could still work on 10.3.
>> As for including the Info.plist changes in v0-40, it would need to be
>> throughly tested before including it.  Currently, there are only a
>> couple outstanding bugs that need to be fixed for this release
>> (AFAIK), so I am really hesitant to include something totally new.
>>
> According to this http://developer.apple.com/qa/qa2005/qa1406.html the
> public.plain-text UTI we're using existed in 10.3.  Also, this seems
> to be a transitional document for 10.3>10.4, and doesn't include any
> callouts except:  "Note: UTIs are available in Mac OS X v10.3 Panther
> and later. Mac OS X v10.4 Tiger added many new types and integrated
> support throughout the operating system."
>
> So I think it won't be a problem for the keys in the plist, and in the
> future, 10.3 should just ignore the
> Library/Spotlight/PureData.mdimporter file just as it would ignore any
> other file it didn't recognize in the bundle.


Ok, sounds like it is worth trying to add the Info.plist UTI stuff to  
this release.  Feel free to add it now to branches/pd-extended/v0-40,  
but please test it.

.hc



 As for building it, how do you build it yourself?  That's usually a
 good starting point for adding it to the auto-build.  If it is an
 xcode project, you can use the command line tool xcodebuild.

>>> Yo,
>>> I just built in with the build button : ).  I like buttons...
>>> So yea, I have the project.  Looks like it builds aok with  
>>> xcodebuild,
>>> thanks for the tip.  Where should I put the project folder?
>>
>> Good question. The first place I thought of is packages/darwin_app
>> since it is only for things related to the Pd.app for Mac OS X.   
>> Maybe:
>>
>> packages/darwin_app/spotlight_importer
>>
>> Then it probalby makes sense to make a separate 'spotlight_importer:'
>> target in packages/darwin_app/Makefile to build and install it.
>>
>> .hc
>
> Will do.
> Cheers
> Luke



 


All information should be free.  - the hacker ethic





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


Re: [PD] better tabread4~

2008-06-20 Thread Mathieu Bouchard

On Wed, 11 Jun 2008, cyrille henry wrote:


ok, if you don't wish to compile in order to test, here are 2 samples :
http://www.chdh.free.fr/tab/tabosc4.wav
http://www.chdh.free.fr/tab/tabosc4c.wav
note that this is the worst case for tabread4~ : a very small table play at low 
frequency.


I believe that the difference will be more perceivable in non-sound 
contexts or at least non-waveform contexts, e.g. video/OpenGL, or 
sequencing.



for bigger table, the difference can be very small.


For a normal 4-point interpolator, the size of the table does not matter, 
because you always only use the previous two points and the next two 
points. It's just the scale at which you are looking at the thing, that 
gives the impression of large details.


I tried [tabread4] between two arrays of different sizes, to visualise 
interpolation, and just clicking around in one array for a few minutes got 
me to produce quite wild discontinuities of first derivative. This has 
little to do with the twice-continuously-differentiable (C2) nice things 
that I learned in school and such.


In very large tables, the interpolation will get lousy because the 
resolution of floats gets too close to the resolution of the table indices 
themselves (that is, there are not enough fractions between two 
consecutive integers). But this does not happen at the beginning of the 
table. On average, though, or on worst-case (which often matters), bigger 
tables make things worse in pd.


 _ _ __ ___ _  _ _ ...
| Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] DMX oriented library for PD?

2008-06-20 Thread Vincent Rioux

>
>>
>> I get this error message when i try to load it but i guess this is 
>> because i don't have any dmx-usb device (yet) ;-)
>> dmxin.pd_linux: undefined symbol: DMXINdev dmxin
>
> aye, this was due to some library havoc i head on my machine (having 
> installed both the dmx4linux debian package and dmx4linux from source; 
> and actually linking against the library provided by the debian package)
>
> should be fixed now in svn.

yes, thanks IOhannes.



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


Re: [PD] [PD-dev] What goes on during dsp ticks?

2008-06-20 Thread Mathieu Bouchard

On Sun, 15 Jun 2008, PSPunch wrote:


I hear that malloc is a "relatively" expensive task.


It's mostly just OSX's malloc that is obscenely expensive beyond a certain 
size. But that threshold is more like 16k or so. On Linux, it's 128k 
instead, but if both thresholds were the same, you'd see that Linux 
takes this change well, whereas OSX does not.


The threshold corresponds to when malloc switches from doing its own 
memory management, to just delegating its job to the kernel.


 _ _ __ ___ _  _ _ ...
| Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] pyext thread question

2008-06-20 Thread altern
hi thomas

thanks!! this solved my problem.

enrike

Thomas Grill(e)k dio:
> Hi all,
> there are (at least) two ways to enable detaching. Please find the 
> attached pd patch and pyext script to see how it works.
> 
> 
> 
> 
> 
> 
> 
> 
>>
>>
>> I am still using pyext regularly and could compile it without problems 
>> with python2.4 and pd 39.
>> I just tried now from fresh svn, pd41 and python2.5 but i get this 
>> compilation error:
>> /usr/local/include/flext/flcontainers.h:380: erreur: invalid 
>> static_cast from type «Lifo::Cell*» to type «FifoEl*»
>>>
> 
> 
>>> and actually this pb was already reported
>>> http://lists.puredata.info/pipermail/pd-list/2008-04/060994.html
>>>
> 
> 
> The problem is that the change from CVS to SVN broke the scripts which did 
> the syncing from my local SVN to the PD repository. I think i already fixed 
> this problem, but it might only have been in the CVS.
> 
> Currently I have no time/interest to fix the sync scripts, but i made parts 
> of my SVN available... this should probably be mirrored (using svn:externals 
> properties) to the PD SVN.
> 
> 
> 
> Please try if those versions work better... they are always cutting edge 
> experimental stuff.
> 
> 
> 
> https://svn.g.org/ext/trunk/flext/
> 
> https://svn.g.org/ext/trunk/py/
> 
> my other externals/projects have respective addresses
> 
> 
> 
> 
> 
>> Thomas, is it something that requires a lot of work to mend?
>> Could we find an arrangement so that you could work on it?
>>
> 
> 
> I think the above should solve your problems.
> 
> In general i have great difficulties finding time to work on things that i 
> don't need for my own projects.
> 
> If someone needs something very urgently for artistic work i often can 
> motivate myself to help out, on the other hand, as long as even members of 
> organizations with enormous facilities using my stuff don't feel the 
> obligation to donate a few bucks to my paypal account i'd rather save my time.
> 
> Many thanks to the individuals who have donated their own private money so 
> far.
> 
> 
> 
> gr~~~
> 
> 
> 



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


Re: [PD] Spotlight Importer for OS X

2008-06-20 Thread Luke Iannini
On Fri, Jun 20, 2008 at 5:15 AM, Hans-Christoph Steiner <[EMAIL PROTECTED]> 
wrote:
>
> On Jun 20, 2008, at 1:55 PM, Luke Iannini wrote:
>
>> On Fri, Jun 20, 2008 at 4:02 AM, Hans-Christoph Steiner
>> <[EMAIL PROTECTED]> wrote:
>>>
>>> Does this work at all on 10.4/Tiger?
>>>
>> Yes, it's configured by default to work with both 10.4 and 10.5.
>
> Any idea whether it would cause problems on 10.3?  That's not a make-
> or-break thing, but it would be nice if it could still work on 10.3.
> As for including the Info.plist changes in v0-40, it would need to be
> throughly tested before including it.  Currently, there are only a
> couple outstanding bugs that need to be fixed for this release
> (AFAIK), so I am really hesitant to include something totally new.
>
According to this http://developer.apple.com/qa/qa2005/qa1406.html the
public.plain-text UTI we're using existed in 10.3.  Also, this seems
to be a transitional document for 10.3>10.4, and doesn't include any
callouts except:  "Note: UTIs are available in Mac OS X v10.3 Panther
and later. Mac OS X v10.4 Tiger added many new types and integrated
support throughout the operating system."

So I think it won't be a problem for the keys in the plist, and in the
future, 10.3 should just ignore the
Library/Spotlight/PureData.mdimporter file just as it would ignore any
other file it didn't recognize in the bundle.

>
>>> As for building it, how do you build it yourself?  That's usually a
>>> good starting point for adding it to the auto-build.  If it is an
>>> xcode project, you can use the command line tool xcodebuild.
>>>
>> Yo,
>> I just built in with the build button : ).  I like buttons...
>> So yea, I have the project.  Looks like it builds aok with xcodebuild,
>> thanks for the tip.  Where should I put the project folder?
>
> Good question. The first place I thought of is packages/darwin_app
> since it is only for things related to the Pd.app for Mac OS X.  Maybe:
>
> packages/darwin_app/spotlight_importer
>
> Then it probalby makes sense to make a separate 'spotlight_importer:'
> target in packages/darwin_app/Makefile to build and install it.
>
> .hc

Will do.
Cheers
Luke

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


Re: [PD] Spotlight Importer for OS X

2008-06-20 Thread Hans-Christoph Steiner

On Jun 20, 2008, at 1:55 PM, Luke Iannini wrote:

> On Fri, Jun 20, 2008 at 4:02 AM, Hans-Christoph Steiner  
> <[EMAIL PROTECTED]> wrote:
>>
>> Does this work at all on 10.4/Tiger?
>>
> Yes, it's configured by default to work with both 10.4 and 10.5.

Any idea whether it would cause problems on 10.3?  That's not a make- 
or-break thing, but it would be nice if it could still work on 10.3.   
As for including the Info.plist changes in v0-40, it would need to be  
throughly tested before including it.  Currently, there are only a  
couple outstanding bugs that need to be fixed for this release  
(AFAIK), so I am really hesitant to include something totally new.


>> As for building it, how do you build it yourself?  That's usually a
>> good starting point for adding it to the auto-build.  If it is an
>> xcode project, you can use the command line tool xcodebuild.
>>
> Yo,
> I just built in with the build button : ).  I like buttons...
> So yea, I have the project.  Looks like it builds aok with xcodebuild,
> thanks for the tip.  Where should I put the project folder?

Good question. The first place I thought of is packages/darwin_app  
since it is only for things related to the Pd.app for Mac OS X.  Maybe:

packages/darwin_app/spotlight_importer

Then it probalby makes sense to make a separate 'spotlight_importer:'  
target in packages/darwin_app/Makefile to build and install it.

.hc


>> Also, it seems that .pat should have a separate entry, something like
>> this:
>>
>>
>>UTTypeConformsTo
>>public.plain-text
>>UTTypeIdentifier
>>org.puredata.max-patch
>>UTTypeTagSpecification
>>
>>public.filename-extension
>>
>>pat
>>
>>
>>
>>
> Sure, makes sense.  I'll do that
>
>> .hc
>>
>> On Jun 19, 2008, at 2:10 PM, Luke Iannini wrote:
>>
>>> Hi all,
>>> Here's a Spotlight importer for Pd (and AFAIK .pat) files.
>>>
>>> Starting with tonight or tomorrow's autobuild, installing it (just
>>> double-click it) will let Spotlight look inside your Pd patches.
>>> Also, a beneficial side-effect of a necessary change to Pd- 
>>> extended's
>>> bundle means that Pd-patches are now Quick Look-enabled (don't get
>>> /too/ excited, it is only the plaintext representation, but still
>>> extremely handy).  And after the importer itself gets enveloped by
>>> Pd-extended's bundle, it will just work (no installation needed).
>>>
>>> This version just indexes the entire text.  In the future I could  
>>> add
>>> specific metadata keys to correspond to "Pure Data Objects", "Pure
>>> Data Messages", "Pure Data Comments", and "Pure Data [declares]",
>>> which could then be used to construct complex Spotlight queries  
>>> (but I
>>> just learned enough Obj-C to get this far tonight so give me a  
>>> while :
>>> ) ).
>>>
>>> Hans, apparently placing it in
>>> Pd-extended.app/Contents/Library/Spotlight will make it magically
>>> start working the first time Pd is dragged out of its .dmg.  I don't
>>> have a clue about building this dynamically in the autobuilds, but
>>> since it is a Universal Binary and OS X only is it cool to add
>>> statically?
>>>
>>> enjoy
>>> Luke
>>>
>>> (by the way, you'll know you have the right Pd-extended when running
>>> "mdls -name kMDItemContentType a-patch.pd" gives
>>> "org.puredata.pd-patch" rather than "dyn.ah62d4rv4ge81a3a" or
>>> similar)
>>> ___ 
>>> __
>>> __
>>> Pd-list@iem.at mailing list
>>> UNSUBSCRIBE and account-management -> http://lists.puredata.info/
>>> listinfo/pd-list
>>
>>
>>
>>
>> - 
>> ---
>> 
>>
>> All mankind is of one author, and is one volume; when one man dies,
>> one chapter is not torn out of the book, but translated into a better
>> language; and every chapter must be so translated -John Donne
>>
>>
>>
>> ___
>> Pd-list@iem.at mailing list
>> UNSUBSCRIBE and account-management -> http://lists.puredata.info/ 
>> listinfo/pd-list
>>



 


There is no way to peace, peace is the way.   -A.J. Muste



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


Re: [PD] pyext compilation

2008-06-20 Thread Vincent Rioux
hi Thomas,
> The problem is that the change from CVS to SVN broke the scripts which did 
> the syncing from my local SVN to the PD repository. I think i already fixed 
> this problem, but it might only have been in the CVS.
>   
that was it.
> Currently I have no time/interest to fix the sync scripts, but i made parts 
> of my SVN available... this should probably be mirrored (using svn:externals 
> properties) to the PD SVN.
>
>   
well, i am not sure about that - i tried to compile flext and py from

svn co  https://pure-data.svn.sourceforge.net/svnroot/pure-data/trunk/externals

without chance.
>
> Please try if those versions work better... they are always cutting edge 
> experimental stuff.
>
>   
yes, this seems to work! it compiles and load at least.
Thanks a lot!

(i just noticed that you can't compile pyext without py_num or py_array 
support, but this really is a minor issue).

> https://svn.g.org/ext/trunk/flext/
>
> https://svn.g.org/ext/trunk/py/
>
> my other externals/projects have respective addresses
>
>
>> Thomas, is it something that requires a lot of work to mend? Could we 
>> find an arrangement so that you could work on it? 
>
> I think the above should solve your problems.
>
> In general i have great difficulties finding time to work on things that i 
> don't need for my own projects.
>
> If someone needs something very urgently for artistic work i often can 
> motivate myself to help out, on the other hand, as long as even members of 
> organizations with enormous facilities using my stuff don't feel the 
> obligation to donate a few bucks to my paypal account i'd rather save my time.
>   
Sounds really fair.
best regards,
Vincent

> Many thanks to the individuals who have donated their own private money so 
> far.
>
>
>
> gr~~~
>
>
>
>   


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


Re: [PD] Spotlight Importer for OS X

2008-06-20 Thread Luke Iannini
(sorry, I mean it's not necessary if we're not including the importer
in the bundle of course)

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


Re: [PD] Spotlight Importer for OS X

2008-06-20 Thread Hans-Christoph Steiner

One more thing I forgot to mention,  it's too late to include the  
spotlight importer into this release, but I did make the Makefile  
create the Library/Spotlight directory, to make it a bit easier to  
manually install it.  Once we set up the 0.41-extended builds, it can  
be included there.

.hc

On Jun 19, 2008, at 2:10 PM, Luke Iannini wrote:

> Hi all,
> Here's a Spotlight importer for Pd (and AFAIK .pat) files.
>
> Starting with tonight or tomorrow's autobuild, installing it (just
> double-click it) will let Spotlight look inside your Pd patches.
> Also, a beneficial side-effect of a necessary change to Pd-extended's
> bundle means that Pd-patches are now Quick Look-enabled (don't get
> /too/ excited, it is only the plaintext representation, but still
> extremely handy).  And after the importer itself gets enveloped by
> Pd-extended's bundle, it will just work (no installation needed).
>
> This version just indexes the entire text.  In the future I could add
> specific metadata keys to correspond to "Pure Data Objects", "Pure
> Data Messages", "Pure Data Comments", and "Pure Data [declares]",
> which could then be used to construct complex Spotlight queries (but I
> just learned enough Obj-C to get this far tonight so give me a while :
> ) ).
>
> Hans, apparently placing it in
> Pd-extended.app/Contents/Library/Spotlight will make it magically
> start working the first time Pd is dragged out of its .dmg.  I don't
> have a clue about building this dynamically in the autobuilds, but
> since it is a Universal Binary and OS X only is it cool to add
> statically?
>
> enjoy
> Luke
>
> (by the way, you'll know you have the right Pd-extended when running
> "mdls -name kMDItemContentType a-patch.pd" gives
> "org.puredata.pd-patch" rather than "dyn.ah62d4rv4ge81a3a" or  
> similar) 
> _ 
> __
> Pd-list@iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/ 
> listinfo/pd-list





 


"Free software means you control what your computer does. Non-free  
software means someone else controls that, and to some extent  
controls you." - Richard M. Stallman



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


Re: [PD] Spotlight Importer for OS X

2008-06-20 Thread Hans-Christoph Steiner

Does this work at all on 10.4/Tiger?

As for building it, how do you build it yourself?  That's usually a  
good starting point for adding it to the auto-build.  If it is an  
xcode project, you can use the command line tool xcodebuild.

Also, it seems that .pat should have a separate entry, something like  
this:


UTTypeConformsTo
public.plain-text
UTTypeIdentifier
org.puredata.max-patch
UTTypeTagSpecification

public.filename-extension

pat




.hc

On Jun 19, 2008, at 2:10 PM, Luke Iannini wrote:

> Hi all,
> Here's a Spotlight importer for Pd (and AFAIK .pat) files.
>
> Starting with tonight or tomorrow's autobuild, installing it (just
> double-click it) will let Spotlight look inside your Pd patches.
> Also, a beneficial side-effect of a necessary change to Pd-extended's
> bundle means that Pd-patches are now Quick Look-enabled (don't get
> /too/ excited, it is only the plaintext representation, but still
> extremely handy).  And after the importer itself gets enveloped by
> Pd-extended's bundle, it will just work (no installation needed).
>
> This version just indexes the entire text.  In the future I could add
> specific metadata keys to correspond to "Pure Data Objects", "Pure
> Data Messages", "Pure Data Comments", and "Pure Data [declares]",
> which could then be used to construct complex Spotlight queries (but I
> just learned enough Obj-C to get this far tonight so give me a while :
> ) ).
>
> Hans, apparently placing it in
> Pd-extended.app/Contents/Library/Spotlight will make it magically
> start working the first time Pd is dragged out of its .dmg.  I don't
> have a clue about building this dynamically in the autobuilds, but
> since it is a Universal Binary and OS X only is it cool to add
> statically?
>
> enjoy
> Luke
>
> (by the way, you'll know you have the right Pd-extended when running
> "mdls -name kMDItemContentType a-patch.pd" gives
> "org.puredata.pd-patch" rather than "dyn.ah62d4rv4ge81a3a" or  
> similar) 
> _ 
> __
> Pd-list@iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/ 
> listinfo/pd-list




 


All mankind is of one author, and is one volume; when one man dies,  
one chapter is not torn out of the book, but translated into a better  
language; and every chapter must be so translated -John Donne



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


Re: [PD] pyext thread question

2008-06-20 Thread Thomas Grill

Hi all,
there are (at least) two ways to enable detaching. Please find the  
attached pd patch and pyext script to see how it works.


detach.pd
Description: Binary data
import pyext,time

class detach(pyext._class):
def __init__(self,d = False):
if d: 
print "Detaching script"
self._detach(True)

def bang_1(self):
print "START"
time.sleep(5)
print "STOP"







I am still using pyext regularly and could compile it without  
problems with python2.4 and pd 39.
I just tried now from fresh svn, pd41 and python2.5 but i get this  
compilation error:
/usr/local/include/flext/flcontainers.h:380: erreur: invalid  
static_cast from type «Lifo::Cell*» to type «FifoEl*»





and actually this pb was already reported
http://lists.puredata.info/pipermail/pd-list/2008-04/060994.html



The problem is that the change from CVS to SVN broke the scripts which  
did the syncing from my local SVN to the PD repository. I think i  
already fixed this problem, but it might only have been in the CVS.
Currently I have no time/interest to fix the sync scripts, but i made  
parts of my SVN available... this should probably be mirrored (using  
svn:externals properties) to the PD SVN.


Please try if those versions work better... they are always cutting  
edge experimental stuff.


https://svn.g.org/ext/trunk/flext/
https://svn.g.org/ext/trunk/py/
my other externals/projects have respective addresses



Thomas, is it something that requires a lot of work to mend?
Could we find an arrangement so that you could work on it?



I think the above should solve your problems.
In general i have great difficulties finding time to work on things  
that i don't need for my own projects.
If someone needs something very urgently for artistic work i often can  
motivate myself to help out, on the other hand, as long as even  
members of organizations with enormous facilities using my stuff don't  
feel the obligation to donate a few bucks to my paypal account i'd  
rather save my time.
Many thanks to the individuals who have donated their own private  
money so far.


gr~~~



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] issues with [readsf~]/[writesf~]

2008-06-20 Thread Hans-Christoph Steiner

Please add these to the bug tracker.

.hc

On Jun 20, 2008, at 5:26 AM, [EMAIL PROTECTED] wrote:

>
> hello.
>
> i just want to report a few bugs that i can spot with
> the [readsf~]/[writesf~] couple ..
>
> a)
>   i have already wrote about this, and i'll write again, cause i'm
>   very sure on this one.
>   when i write a file with this command:
>   [open -byte 4 -nextstep -little -rate 96000 /tmp/recording-ex01(
>   it produces a file which is recognised by unix command file(1)
>   as just a 'data' file, and then opening it in Snd editor it come
>   up as a raw pcm and i set the header values and write the header
>   to it, ..then file actualy gives this output:
>   '/home/110101/mtk/rec/recording-ex01.snd: Sun/NeXT audio data:  
> stereo, 96000 Hz'
>   instead of '/tmp/recording-ex01.snd: data'
>   so trying to load the modified header file into [readsf~]
>   doesn't parse the header, but trying to load the unmodified one
>   is okay.
>   probably it's about endianes of the magic byte ..
>   well.. it could be actually not a pd bug but Snd and file(1) bug
>   .. but they are two, i'll try to check with other programms but
>   it's a majority to me already.
>
> b)
>   [readsf~] heppends to segfault Pd when i load my 4channel 10min
>   lond file which was recorded with [writesf~] with above [open 
> ( command.
>   i run Pd (version 0.41-4) on amd64 linux machine which has 1g of
>   ram ..
>   it segfaults in a big patch, which i'll hopefully manage to
>   package soon ..it has really a lot of abstraction that i made
>   and quite many subpatches.
>   i did manage to get it working with some subpatches [switched~]
>   off. so i think it's definetly some memory allocation problem in
>   there, could be in soundfiler code, or may be in some other
>   objects that i have there ..(there are many VUs which are now in
>   [switch~]ed subpatches and when i'm kindda carefull it doesn't
>   crash ;)
>
> well, anyhow i reckon that readsf~ needs some replacment for my  
> purpose ..
> cause the file is that big .. (du -hs reports 1022M)
> perhaps, i could experiment on system with ONLY puredata running,
> but there a lot of important processes which i cannot kill at the  
> moment..
>
>
> cheers,
> -- 
> ilya .d
>
> ___
> Pd-list@iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/ 
> listinfo/pd-list



 


If you are not part of the solution, you are part of the problem.



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


Re: [PD] tape-like transport emulation (search for external)

2008-06-20 Thread errordeveloper
On Fri, Jun 20, 2008 at 09:11:14AM +0200, [EMAIL PROTECTED] wrote:
> Did you ever look at record~?

the one in svn/externals/miXed ?

i'm trying to compile it now ..

> 
> Best recards
> 
> 
> >
> 

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