Re: [PD] [PD-announce] Pd FLOSS Manual Update pt 1

[adam hyde]

hey


the br_pt manual is here:

http://translate.flossmanuals.net/bin/view/PureData_br_pt

info on how to use the translation system is here:
http://en.flossmanuals.net/FLOSSManuals/TranslatingAManual


so...which tutorials from estudio livre do u wish to transfer? :)

adam



On Sat, 2009-04-11 at 17:52 -0300, glerm soares wrote:
> 
> 
> 2009/4/11 adam hyde 
> I will set up a translation
> 
> i'll send the link soon!
> 
> adam
> 
> 
> Hey Adam, that´s great.
> 
> We can put http://estudiolivre.org tutorials there also. There´s lot
> and lots of FLOSS tutorials there im pt_br, mainly about multimedia
> tools...
> 
> I will sign the FLOSS manuals mailing list and we continue this issue
> there.
> 
> thanx
> 
> té+
> glerm
>  
> 
> 
-- 
Adam Hyde
Founder FLOSS Manuals
German mobile : + 49 15 2230 54563
Email : a...@flossmanuals.net
irc: irc.freenode.net #flossmanuals

"Free manuals for free software"
http://www.flossmanuals.net/about



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

Re: [PD] Pd FLOSS Manual Update pt 1

[Frank Barknecht]

Hallo,
Jonathan Wilkes hat gesagt: // Jonathan Wilkes wrote:

> I agree that meta-messages should be called meta-messages, if 
> they're called anything.  But I don't see how to make the 
> distinction clear without having a comprehensive table of relevant 
> pd-vanilla objects and their behavior regarding meta-messages.
> Why do the first inlets of pack and symbol accept [pitch( ?
> Why wouldn't the secondary inlets of pack and symbol accept 
> [pitch( ?

Or their behaviour regarding data messages: Why doesn't the first inlet of
float accept symbol-messages? *Of course* you have to learn each object's
behaviour to be able to use it. But if nobody tells you that there's a
difference between "pitch" and "symbol pitch" many of the object's behaviour
will seem arcane to you. 

In fact I believe, that beginners have difficulites to understand messages
because their tutors ignore these issues. Maybe they ignore them because they
themselves feel uncomfortable with messages, meta-messages, symbols and other
magic things - and a tutor needs to understand a topic in a much deeper way
than his student.

But people are way too scared of meta-messages. They are nothing special. If
you understand the difference between "symbol"- and "float"- messages, there
is no problem understanding the difference between a "float"- and a
"set"-message or between a "symbol" and a "read"-messages. And you surely are
using these messages all the time. 

> Why does the second inlet of [list] accept [pitch( but the first 
> inlet of [makefilename %s] doesn't?

[list] objects accept everything and convert all incoming messages to data
messages, i.e. to list-messages. [list trim] converts back to meta messages. 

> How do message-box dollar signs handle meta-messages?

They take the first element as selector, and then start counting from there. 

> How does [list length] handle them?

See above: Like all [list]-objects it first converts to a list.

> Do you need [list trim] to route a float list by the first value?

No but it doesn't hurt.

Ciao
-- 
Frank

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

Re: [PD] Ded simple bass drum synth?

[J. Simon van der Walt]

Thanks for the bass drum patches...

JS




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

Re: [PD] how to capture movement

[Jose Luis Santorcuato]

Jajajaja, Jaime i write the post in  linux but i use pure data in osx... src
is a folder in linux...so ... cant install the object in osx???... snif...
so sad...
Thanks Jaime

José

2009/4/11 Jaime Oliver 

> Hi here is a compiled intel version, put it in /src/Pixes of your gem
> distribution and it should work...
>
> J
>
> On Fri, Apr 10, 2009 at 5:38 PM, Jose Luis Santorcuato
>  wrote:
> > Hi everybody, i download the objects .ccp .h for the objetc
> > pix_motion_sector but i cant run with this object in GEM. how to
> compile?.
> > I use a blckbook intel core 2 duo an PD 0.40.3.
> > I agrre the folder with the objets for others users.
> > Thanks
> > José
> >
> > 2009/4/8 Jose Luis Santorcuato 
> >>
> >> Oh yes i can view the pic... really thanks... really...
> >>
> >> José
> >>
> >> 2009/4/8 Jaime Oliver 
> >>>
> >>> checkout william brents pix_scan_sector or something like that...
> >>>
> >>> http://williambrent.conflations.com/pages/research.html
> >>>
> >>> J
> >>>
> >>> On Wed, Apr 8, 2009 at 3:44 PM, Jose Luis Santorcuato
> >>>  wrote:
> >>> > Dear friends, i have a question,¿ how i can capture movement or apply
> a
> >>> > matrix for segments detect?... i test the gem help with the x_blob
> but
> >>> > is
> >>> > not enough, very inestable...
> >>> > Cheers from Chile
> >>> >
> >>> > José Luis
> >>> >
> >>> > --
> >>> > http://arselectronicachile.blogspot.com/
> >>> > www.myspace.com/santorcuato
> >>> >
> >>> > ___
> >>> > Pd-list@iem.at mailing list
> >>> > UNSUBSCRIBE and account-management ->
> >>> > http://lists.puredata.info/listinfo/pd-list
> >>> >
> >>> >
> >>>
> >>>
> >>>
> >>> --
> >>> Jaime E Oliver LR
> >>>
> >>> joliv...@ucsd.edu
> >>> www.realidadvisual.org/jaimeoliver
> >>> www-crca.ucsd.edu/
> >>> www.realidadvisual.org
> >>>
> >>> 858 202 1522
> >>> 9168 Regents Rd. Apt. G
> >>> La Jolla, CA 92037
> >>> USA
> >>
> >>
> >>
> >> --
> >> http://arselectronicachile.blogspot.com/
> >> www.myspace.com/santorcuato
> >
> >
> >
> > --
> > http://arselectronicachile.blogspot.com/
> > www.myspace.com/santorcuato
> >
>
>
>
> --
> Jaime E Oliver LR
>
> joliv...@ucsd.edu
> www.realidadvisual.org/jaimeoliver
> www-crca.ucsd.edu/
> www.realidadvisual.org
>
> 858 202 1522
> 9168 Regents Rd. Apt. G
> La Jolla, CA 92037
> USA
>



-- 
http://arselectronicachile.blogspot.com/
www.myspace.com/santorcuato
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] pyext on pd-extended 0.40.3-extended

[Martin Dupras]

I've tried the examples. The examples which use the py object work; the ones
that use the pyext object do not (the pyext object does not instantiate.) I
don't understand why one works and the other doesn't.

Any idea why one works and the other doesn't?

- martin

2009/4/11 patrick 

> hi martin,
>
> did you try to open the help patch? creating only the object without
> argument will not work.
> [pyext yourpythonfile yourclass]
>
> pat
>
>
>
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Re: [PD] Pd FLOSS Manual Update pt 1

[Jonathan Wilkes]

--- On Sat, 4/11/09, Frank Barknecht  wrote:

> From: Frank Barknecht 
> Subject: Re: [PD] Pd FLOSS Manual Update pt 1
> To: pd-list@iem.at
> Date: Saturday, April 11, 2009, 8:49 PM
> Hallo,
> Derek Holzer hat gesagt: // Derek Holzer wrote:
> 
> > as I've mentioned before, this obscure and arcane
> business of many types  
> > of messages is probably the most incomprehensible bit
> for new users  
> > coming to Pd. What I'd like to see in this chapter
> is not just another  
> > taxonomy of the different kind of messages Pd has.
> Rather, I'd like to  
> > see clear tutorials with real world examples of why
> you would use  
> > different messages for different purposes instead of
> presenting a bunch  
> > of abstract information right away.
> >
> > I think the priority for the FLOSS Manual should be to
> show *why* things  
> > are used, rather than to be exhaustive about all the
> different things  
> > that *could* be used. 
> 
> Meta-messages (I'll use this term now) have a very
> important "why": In Pd they
> are generally used to set the status of objects or make
> them do specific
> actions. Sending a "stop"-meta-message to [poly]
> will make it stop playing,
> sending a "set"-meta-message to a [makefilename]
> will change the format string,
> a "set" to a tabread sets the table to read from
> and so on.
> 
> The other messages - float, symbol or list - generally are
> data carrying
> messages. Floats to tabread will give the value of that
> index in the table,
> symbol to makefilename will apply the format string, lists
> to [poly] will be
> tagged with a number and output it. All of these change
> data and pass it along.
> 
> There's lots of potential for explaining the difference
> with examples taken
> from daily use.
> 
> The distinction between meta-messages and data messages
> becomes very 
> important in message boxes, which are only doing the
> expected dollar expansion
> properly when the incoming message is a data message, and
> they react to meta
> messages like "set" in completely different ways.
> 
>   "Messages in Pd are simewhat artificially divided
> into two
>   classes. First are data-holding messages (bang, float,
>   symbol, list) which are the primary way of communicating
>   between objects. Second is "everything else"
> (you could
>   call them out-of-band messages or metamessages) that
>   describe changes in configuration, read and write files,
>   quit Pd, etc. These are provided so that complex objects
>   don't need to have 100 separate inlets for every
> possible
>   functionality. It's not clear whether this was a good
>   design choice, but it's entrenched."
>   
> That's a quote from list-help.pd
> 
> > So if obscure details are skipped in the beginning  
> > in favor of clarity, I would prefer that. Other, later
> examples can show  
> > the more exotic types and uses of "meta
> messages" "custom messages" etc,  
> > or the distinctions between them when it becomes
> important.
> 
> The distincion is important all the time. Even if it's
> explained in detail
> later, the terminology should not be different. That's
> why I recommended to not
> use "undefined strings" which is not a common
> term for the messages it refers
> to, especially as most of
> http://en.flossmanuals.net/bin/view/PureData/Messages
> deals with meta-messages and [route]. [route] almost always
> is used with either
> number lists or meta-messages, and only very rarely with
> data messages not
> starting with a float. (That's why my [route]s often
> come in tandem with [list
> trim].)

I agree that meta-messages should be called meta-messages, if 
they're called anything.  But I don't see how to make the 
distinction clear without having a comprehensive table of relevant 
pd-vanilla objects and their behavior regarding meta-messages.

Why do the first inlets of pack and symbol accept [pitch( ?
Why wouldn't the secondary inlets of pack and symbol accept 
[pitch( ?
Why does the second inlet of [list] accept [pitch( but the first 
inlet of [makefilename %s] doesn't?
How do message-box dollar signs handle meta-messages?
How does [list length] handle them?
Do you need [list trim] to route a float list by the first value?

-Jonathan

> 
> Ciao
> -- 
> Frank
> 
> ___
> 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] Pd FLOSS Manual Update pt 1

[Georg Werner]

Hi Derek,

thanks for your work of getting this all together and reviewing it etc.
i liked the sprint and especially liked getting a face connected to some
of the names i knew from the list.
some questions:


* http://en.flossmanuals.net/bin/view/PureData/Tables
--where does this go? Dataflow or Audio? (Audio I think)

yes i thought audio
--Would be good to integrate with 
http://en.flossmanuals.net/bin/view/PureData/ArraysGraphsTables

a lot of the things i did are covered there but more in the style of a
reference then a story - i tried to have one but i'm confused about

--Could this also be structured like tutorial rather than taxonomy?

what do you mean by taxonomy?

--I'd like to crop screenshots to get rid of menu bar

no problem

--Incomplete, needs expansion and also "loop it" and "play sections" parts

will do that if i have the feeling that its work that is done in a way
it is helpful.
(the idea was to loop it with line~ and then bring the first part
(melodie step sequencer)
together with the second by playing samples at different speeds
controlled by the sequencer).
but just now i dont really understand what i did wrong in order to make
it a tutorial.
g.




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

Re: [PD] Pd FLOSS Manual Update pt 1

[João Pais]

or you can also make the changes you see fit directly (for now I am too  
busy even to finish the math chapter)



Hallo,
Derek Holzer hat gesagt: // Derek Holzer wrote:


as I've mentioned before, this obscure and arcane business of many types
of messages is probably the most incomprehensible bit for new users
coming to Pd. What I'd like to see in this chapter is not just another
taxonomy of the different kind of messages Pd has. Rather, I'd like to
see clear tutorials with real world examples of why you would use
different messages for different purposes instead of presenting a bunch
of abstract information right away.

I think the priority for the FLOSS Manual should be to show *why* things
are used, rather than to be exhaustive about all the different things
that *could* be used.


Meta-messages (I'll use this term now) have a very important "why": In  
Pd they

are generally used to set the status of objects or make them do specific
actions. Sending a "stop"-meta-message to [poly] will make it stop  
playing,
sending a "set"-meta-message to a [makefilename] will change the format  
string,

a "set" to a tabread sets the table to read from and so on.

The other messages - float, symbol or list - generally are data carrying
messages. Floats to tabread will give the value of that index in the  
table,
symbol to makefilename will apply the format string, lists to [poly]  
will be
tagged with a number and output it. All of these change data and pass it  
along.


There's lots of potential for explaining the difference with examples  
taken

from daily use.

The distinction between meta-messages and data messages becomes very
important in message boxes, which are only doing the expected dollar  
expansion
properly when the incoming message is a data message, and they react to  
meta

messages like "set" in completely different ways.

  "Messages in Pd are simewhat artificially divided into two
  classes. First are data-holding messages (bang, float,
  symbol, list) which are the primary way of communicating
  between objects. Second is "everything else" (you could
  call them out-of-band messages or metamessages) that
  describe changes in configuration, read and write files,
  quit Pd, etc. These are provided so that complex objects
  don't need to have 100 separate inlets for every possible
  functionality. It's not clear whether this was a good
  design choice, but it's entrenched."
That's a quote from list-help.pd


So if obscure details are skipped in the beginning
in favor of clarity, I would prefer that. Other, later examples can show
the more exotic types and uses of "meta messages" "custom messages" etc,
or the distinctions between them when it becomes important.


The distincion is important all the time. Even if it's explained in  
detail
later, the terminology should not be different. That's why I recommended  
to not
use "undefined strings" which is not a common term for the messages it  
refers
to, especially as most of  
http://en.flossmanuals.net/bin/view/PureData/Messages
deals with meta-messages and [route]. [route] almost always is used with  
either
number lists or meta-messages, and only very rarely with data messages  
not
starting with a float. (That's why my [route]s often come in tandem with  
[list

trim].)

Ciao




--
Friedenstr. 58
10249 Berlin (Deutschland)
Tel +49 30 42020091 | Mob +49 162 6843570
jmmmp...@googlemail.com | skype: jmmmpjmmmp

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

Re: [PD] [PD-announce] Pd FLOSS Manual Update pt 1

[glerm soares]

2009/4/11 adam hyde 

> I will set up a translation
>
> i'll send the link soon!
>
> adam
>


Hey Adam, that´s great.

We can put http://estudiolivre.org tutorials there also. There´s lot and
lots of FLOSS tutorials there im pt_br, mainly about multimedia tools...

I will sign the FLOSS manuals mailing list and we continue this issue there.

thanx

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

Re: [PD] pd and recent jackd

[joel silvestre]

> Strange but I have no dropouts when running those patchs on my laptop
> with both alsa and firewire jack backends.
> So I give a try on 2 others hardware and no matter what I do dropouts
> are always here ...
> 
> I think your case was different since I have no crash like " zombified -
> calling shutdown handler " but "only" watchdog: signaling pd... and
> dropouts.
> And troubles arises only when the -rt patch is started with -nogui.
> 
> Very simple patch like just [osc~] and [dac~] doesnt' trigger the
> watchdog.
> 
> Joël
> 


I digg a litlle further and found out it's probably a scheduling issue.
When the gui send the "I am happy" signal to the watchdog process all is
fine but when there is no gui this task is devoted to the main process
and sometimes fails to do it in time.
As a very ugly workaround I comment out  the   kill(getppid(), SIGHUP);
line in s_watchdog.c 
Watchdog is still signaling as before but dropouts are gone! To be sure
the pd patch outputs a 1Khz sinewave monitored with jaaa in peak hold
mode.

That's all my little knowlegde can do...

All the best
Joël






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

Re: [PD] Pd FLOSS Manual Update pt 1

[Frank Barknecht]

Hallo,
Derek Holzer hat gesagt: // Derek Holzer wrote:

> as I've mentioned before, this obscure and arcane business of many types  
> of messages is probably the most incomprehensible bit for new users  
> coming to Pd. What I'd like to see in this chapter is not just another  
> taxonomy of the different kind of messages Pd has. Rather, I'd like to  
> see clear tutorials with real world examples of why you would use  
> different messages for different purposes instead of presenting a bunch  
> of abstract information right away.
>
> I think the priority for the FLOSS Manual should be to show *why* things  
> are used, rather than to be exhaustive about all the different things  
> that *could* be used. 

Meta-messages (I'll use this term now) have a very important "why": In Pd they
are generally used to set the status of objects or make them do specific
actions. Sending a "stop"-meta-message to [poly] will make it stop playing,
sending a "set"-meta-message to a [makefilename] will change the format string,
a "set" to a tabread sets the table to read from and so on.

The other messages - float, symbol or list - generally are data carrying
messages. Floats to tabread will give the value of that index in the table,
symbol to makefilename will apply the format string, lists to [poly] will be
tagged with a number and output it. All of these change data and pass it along.

There's lots of potential for explaining the difference with examples taken
from daily use.

The distinction between meta-messages and data messages becomes very 
important in message boxes, which are only doing the expected dollar expansion
properly when the incoming message is a data message, and they react to meta
messages like "set" in completely different ways.

  "Messages in Pd are simewhat artificially divided into two
  classes. First are data-holding messages (bang, float,
  symbol, list) which are the primary way of communicating
  between objects. Second is "everything else" (you could
  call them out-of-band messages or metamessages) that
  describe changes in configuration, read and write files,
  quit Pd, etc. These are provided so that complex objects
  don't need to have 100 separate inlets for every possible
  functionality. It's not clear whether this was a good
  design choice, but it's entrenched."
  
That's a quote from list-help.pd

> So if obscure details are skipped in the beginning  
> in favor of clarity, I would prefer that. Other, later examples can show  
> the more exotic types and uses of "meta messages" "custom messages" etc,  
> or the distinctions between them when it becomes important.

The distincion is important all the time. Even if it's explained in detail
later, the terminology should not be different. That's why I recommended to not
use "undefined strings" which is not a common term for the messages it refers
to, especially as most of http://en.flossmanuals.net/bin/view/PureData/Messages
deals with meta-messages and [route]. [route] almost always is used with either
number lists or meta-messages, and only very rarely with data messages not
starting with a float. (That's why my [route]s often come in tandem with [list
trim].)

Ciao
-- 
Frank

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

Re: [PD] pyext on pd-extended 0.40.3-extended

[patrick]

hi martin,

did you try to open the help patch? creating only the object without 
argument will not work.

[pyext yourpythonfile yourclass]

pat



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

Re: [PD] pd and recent jackd

[joel silvestre]

> currently I'm using jackd version 0.116.1, before that I was using 
> 0.109.2-3ubuntu1 (current intrepid version?), which already had this 
> "issue".
> 
> I also noticed that different timeout settings made noticeable changes 
> to this issue but it didn't solve the problem entirely,  (btw. I already 
> was using 9000ms, and this watchdog is not jack-related but built into 
> pd / gui as far as i know.)
> 
> when trying different things concerning realtime permissions I also 
> noticed that priorities for "audio" group in /etc/security/limits to 
> something below 10 (don't know exactly anymore) also had an influence 
> (because pd had no more rt permissions then).
> 
> now everything's fine when jack is started with sufficient priority, no 
> matter which other settings I use with jack (except dropouts with too 
> low latency or doing graphics stuff with gem in the same instance of pd).
> 
> Martin
> 


Strange but I have no dropouts when running those patchs on my laptop
with both alsa and firewire jack backends.
So I give a try on 2 others hardware and no matter what I do dropouts
are always here ...

I think your case was different since I have no crash like " zombified -
calling shutdown handler " but "only" watchdog: signaling pd... and
dropouts.
And troubles arises only when the -rt patch is started with -nogui.

Very simple patch like just [osc~] and [dac~] doesnt' trigger the
watchdog.

Joël







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

[PD] pyext on pd-extended 0.40.3-extended

[Martin Dupras]

I would like to know if anyone is having success in using pyext with
0.40.3-extended.

I'm on OS X 10.5.

I get the following errors in the console:

---
py/pyext 0.2.1pre - python script objects
(C)2002-2008 Thomas Grill - http://g.org/ext

using Python 2.5.1 (r251:54863, Feb  4 2008, 21:48:13)
[GCC 4.0.1 (Apple Inc. build 5465)]

Python array support enabled


pyext: can't load library
-

Any help much appreciated.


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

Re: [PD] capturing pd outwindow in win

[chris clepper]

pix_snap + pix_record is what you want.  Make sure it is the last thing in
the render order ( [gemhead 99] ).

On Sat, Apr 11, 2009 at 7:16 AM,  wrote:

> hi all
>
> does anybody know how to capture a gemwindow. i tried snap2tex but failed.
> snap2tex does not force pix_record to write. it does not show any frame
> numberchanges and if you stop it, no file is created. since i have a lot
> of gem chains in that patch and also snap2tex feedback, i need to have a
> own renderchain for the capturing. I also tried the pix_depot and friends
> but same behavior like pix_record. both are working well with pix-film or
> pix_video
>
> thank you in advance
> der.brandt
>
>
> ___
> 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] Pd FLOSS Manual Update pt 1

[adam hyde]

I will set up a translation

i'll send the link soon!

adam


On Fri, 2009-04-10 at 01:57 +0200, Derek Holzer wrote:
> Hey Glerm,
> 
> no problem to borrow, as it's GPL, etc etc. However, if you wanted to 
> engage in actual proper translation then then organization and 
> infrastructure of FLOSS Manuals would be at your disposal. Best to wait 
> until there are some 1.0 and later 2.0 (with sensors, networking, GEM, 
> MIDI, etc) versions to translate of course. But I think Brazilian 
> translation would be a very cool first translation of the releases. 
> Maybe Adam Hyde from FLOSS Manuals could offer some suggestions on how 
> to do it as well. They are actually busy writing a manual on how to 
> translate manuals I believe...
> 
> best!
> D.
> 
> glerm soares wrote:
> > 
> > 
> > 2009/4/9 glerm soares mailto:organi...@gmail.com>>
> > 
> > Since it's GPL,
> > I will translate some of them to brazilian portuguese and put into
> > http://artesanato.devolts.org website, ok? This is a new brazilian
> > hacklab weblog we just started...
> > 
> > 
> > In fact, I don't think I will "translate" litteraly, but use as some 
> > kind of guide for topics, and maybe use some pictures and examples... 
> > Any problem?
> 
> 
-- 
Adam Hyde
Founder FLOSS Manuals
German mobile : + 49 15 2230 54563
Email : a...@flossmanuals.net
irc: irc.freenode.net #flossmanuals

"Free manuals for free software"
http://www.flossmanuals.net/about



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

Re: [PD] Pd FLOSS Manual Update pt 1

[Derek Holzer]

Hi Frank,

as I've mentioned before, this obscure and arcane business of many types 
of messages is probably the most incomprehensible bit for new users 
coming to Pd. What I'd like to see in this chapter is not just another 
taxonomy of the different kind of messages Pd has. Rather, I'd like to 
see clear tutorials with real world examples of why you would use 
different messages for different purposes instead of presenting a bunch 
of abstract information right away.


I think the priority for the FLOSS Manual should be to show *why* things 
are used, rather than to be exhaustive about all the different things 
that *could* be used. So if obscure details are skipped in the beginning 
in favor of clarity, I would prefer that. Other, later examples can show 
the more exotic types and uses of "meta messages" "custom messages" etc, 
or the distinctions between them when it becomes important.


It's a different approach than most people currently in Pd seem to be 
used to writing. Probably this has to do with how they learned it...by 
being given lists of things to memorize! ;-)


best!
D.

Frank Barknecht wrote:

Hallo,
Jo?o Pais hat gesagt: // Jo?o Pais wrote:


* http://en.flossmanuals.net/bin/view/PureData/Messages
--Looks very good!

thanks,


One remark though: In messages08.pd messages without a symbol/list/float
selector ("meta-messages") are called "undefined strings" which I think is
misleading and even wrong: Pd vanilla doesn't have proper strings, and these
messages are defined like anything else, they even are very common everywhere 
in Pd
("reset", "set", "read", "open" etc. come to mind).

In messages09.pd ff. a lot of these meta-messages are used, so it's even more
misleading to call them undefined strings before.

In the context of this explanation I would just call them "other messages" or
meta-messages, which is the term used by Miller, or "custom messages".

Ciao


--
::: derek holzer ::: http://blog.myspace.com/macumbista ::: 
http://www.vimeo.com/macumbista :::

---Oblique Strategy # 146:
"Spectrum analysis"

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

[PD] capturing pd outwindow in win

[brandt]

hi all

does anybody know how to capture a gemwindow. i tried snap2tex but failed.
snap2tex does not force pix_record to write. it does not show any frame
numberchanges and if you stop it, no file is created. since i have a lot
of gem chains in that patch and also snap2tex feedback, i need to have a
own renderchain for the capturing. I also tried the pix_depot and friends
but same behavior like pix_record. both are working well with pix-film or
pix_video

thank you in advance
der.brandt


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

Re: [PD] Pd FLOSS Manual Update pt 1

[Frank Barknecht]

Hallo,
Jo?o Pais hat gesagt: // Jo?o Pais wrote:

>> * http://en.flossmanuals.net/bin/view/PureData/Messages
>> --Looks very good!
>
> thanks,

One remark though: In messages08.pd messages without a symbol/list/float
selector ("meta-messages") are called "undefined strings" which I think is
misleading and even wrong: Pd vanilla doesn't have proper strings, and these
messages are defined like anything else, they even are very common everywhere 
in Pd
("reset", "set", "read", "open" etc. come to mind).

In messages09.pd ff. a lot of these meta-messages are used, so it's even more
misleading to call them undefined strings before.

In the context of this explanation I would just call them "other messages" or
meta-messages, which is the term used by Miller, or "custom messages".

Ciao
-- 
Frank

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

Re: [PD] Creation Argument Weirdness

[Frank Barknecht]

Hallo,
Matt Barber hat gesagt: // Matt Barber wrote:

> I haven't tried this (and can't on this computer), but it occurred to
> me you may want to see what happens if you put the [pipe 0] directly
> after the [loadbang] (before the trigger).  [pipe] and [delay] should
> always make a break in logic flow, right?

They change the depth-first message passing to a breadth-first, i.e. if you
have e.g. a [t b b b] on top and have a [delay/pipe] connected to the rightmost
outlet, then processing is suspended when the delay is reached to let the other
two bangs to their thing first, then processing is resumed after the
delay/pipe.

Ciao
-- 
Frank

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