Dear Pure Dataheads,
following the PD FLOSS Booksprint in Croatia last month, the 0.1 version of the Pure Data FLOSS Manual is now online!
http://flossmanuals.net/puredata
The Pure Data FLOSS Manual is conceived as a beginner's approach to Pure Data which, unlike most of the existing documentation, doesn't assume that the user has a degree in mathematics or computer science before they get started! Currently, information on installing and configuring PD, the interface, dataflow tutorials and audio tutorials are included. The FLOSS Manuals philosophy is that chapters from the different available FLOSS Manuals can be "remixed" to create new manuals (for course readers & curriculums, classroom manuals, etc etc). Everything is published under the GNU General Public License.
Adam Hyde, Luka Prinčič and myself busted some serious ass to get this up, and now we're ready to take on our toughest customers: YOU.
We'd really appreciate it if members of this list could read through the chapters, keeping the following points in mind:
- Is the text clear and consistent?
- If technical jargon is used, is it defined inline or included in the
Glossary in the back? 3) Are the tutorials complete, or are some steps or information missing? 4) Grammar/spelling, of course 5) Could each chapter exist as a self-standing tutorial outside the context of the PD Manual (i.e. could it be "remixed" with chapters from other FLOSS Manuals without losing anything)?
Those not so familiar with Pure Data are encouraged to go through the different tutorials and give feedback as to whether they need more (or less!) information, and whether different parts are redundant or need to be split off from the chapters they are in. Experienced PD users are also welcome, of course!
Also, we are still seeking help getting graphics and screenshots for several sections. And there is a HUGE to-do list if you want to get more seriously involved in the project!
Thanks and best wishes! Derek
----TO DO BY CHAPTER LIST----
# Pure Data # Introduction
---cover image, important!
# WhatIsGraphicalProgramming
----icons/graphics to go with concepts in text ----icons of modular synth with patch cables or similar analog "patching" ----flowchart of inputs and outputs between PD and audio, MIDI, network, video, Arduino/motors, etc ----chart describing relationship of PD to Externals
# WhatIsDigitalAudio
----icons/graphics to go with concepts in text ----icon of speaker cone movement ----icon of microphone to voltage to soundcard ----icon of soundcard to voltage to speaker movement ----icon of clipping audio ----icon/graph illustrating Nyquist foldover
# Installing # Linux (source) # Windows # InstallingOSX
---Updated Extended installation instruction ---Screenshots of installation
# ConfiguringPD
---Screenshots of config menus from all three operating systems (slightly different locations on OSX, Windows, Linux) ---Better introduction to Path, Startup and how to configure Externals with Extended
# TroubleShooting
---"I don't hear any sound!" Screenshot "compute audio" button + audio settings in PD, Maybe also audio control panels from different OSes? ---"The test tone sounds distorted!" Add screencap of testtone.pd patch ---"I'm not seeing any audio input!"audio settings in PD, with inputs and outputs highlighted ---"I don't see any MIDI input!" Screencaps: audio/midi prefernces with midi highlighted, OSX: Audio MIDI Setup.app, Linux: QJackctl, Windows: MIDI Ox/MIDI Yoke Junction ---"I get the message "... couldn't create" when I open a patch and there's a dashed line around my object!" Screencap: patch with uncreated objects (missing path/external problem)
# Getting Started # StartingPD
---"Starting PD with the Clickable Icon": OSX, Linux screencaps
# TheInterface
---Screenshots of different menus from all three OSes
# AudioTutorials
---"Introduction": block diagram of synthesizer architecture, as desribed in text ---Formatting: messages like "bang" inside quotes (no Caps, as I have done with "Bang" in some places and need to change...)
# AudioStreaming # DataflowTutorials
---give titles to screenshots so that readers can tell which patches match which images (some do this, some don't...) ---"Math": examples/discussion of [expr]??? ---"Order of connecting and [trigger]": explain the patches in-line, rather than only in comments in screenshots (so that text is searchable, copy/pasteable..) ---Screencaps are very aliased, to the point where you can't read the ~ in the object names. Should they be redone at new resolution or with antialiasing?
# Appendices # PureGlossary
---format of object names = [italics in square brackets], must be formatted correctly ---format of glossary words in general text: we don't have one yet. Bold on first use in chapter maybe? Needs formatting all through text.
# ListofObjects
---incomplete, please add more libs ---maybe more discussion of externals needed as well ---formatting of object names?
# PureLinks
---always welcome
# Credits
----MORE CHAPTERS/SECTIONS TO DO-----
- Configuring "Path" and "Startup" + adding Externals VERY IMPORTANT!
- MIDI tutorial (keyboards, sliders, etc, input + output to/from devices
or other programs)
- HID sensor tutorial
- Patching strategies (advanced usage and examples of GoP, Abstractions
mostly)
- Audiofile manipulation (tables + Extended objects)
- Realtime effects tutorial (delays, filters, etc)
- GEM VJ tutorial (pix_film, pix_movie)
- Networked data (OSC, netsend/netreceive)
I've already pointed some people to the manual during the last weeks, everyone gave me a very good feedback. I think the site is great! marius.
Derek Holzer wrote:
Dear Pure Dataheads,
following the PD FLOSS Booksprint in Croatia last month, the 0.1 version of the Pure Data FLOSS Manual is now online!
http://flossmanuals.net/puredata
The Pure Data FLOSS Manual is conceived as a beginner's approach to Pure Data which, unlike most of the existing documentation, doesn't assume that the user has a degree in mathematics or computer science before they get started! Currently, information on installing and configuring PD, the interface, dataflow tutorials and audio tutorials are included. The FLOSS Manuals philosophy is that chapters from the different available FLOSS Manuals can be "remixed" to create new manuals (for course readers & curriculums, classroom manuals, etc etc). Everything is published under the GNU General Public License.
Adam Hyde, Luka Prinčič and myself busted some serious ass to get this up, and now we're ready to take on our toughest customers: YOU.
We'd really appreciate it if members of this list could read through the chapters, keeping the following points in mind:
- Is the text clear and consistent?
- If technical jargon is used, is it defined inline or included in the
Glossary in the back? 3) Are the tutorials complete, or are some steps or information missing? 4) Grammar/spelling, of course 5) Could each chapter exist as a self-standing tutorial outside the context of the PD Manual (i.e. could it be "remixed" with chapters from other FLOSS Manuals without losing anything)?
Those not so familiar with Pure Data are encouraged to go through the different tutorials and give feedback as to whether they need more (or less!) information, and whether different parts are redundant or need to be split off from the chapters they are in. Experienced PD users are also welcome, of course!
Also, we are still seeking help getting graphics and screenshots for several sections. And there is a HUGE to-do list if you want to get more seriously involved in the project!
Thanks and best wishes! Derek
----TO DO BY CHAPTER LIST----
# Pure Data # Introduction
---cover image, important!
# WhatIsGraphicalProgramming
----icons/graphics to go with concepts in text ----icons of modular synth with patch cables or similar analog "patching" ----flowchart of inputs and outputs between PD and audio, MIDI, network, video, Arduino/motors, etc ----chart describing relationship of PD to Externals
# WhatIsDigitalAudio
----icons/graphics to go with concepts in text ----icon of speaker cone movement ----icon of microphone to voltage to soundcard ----icon of soundcard to voltage to speaker movement ----icon of clipping audio ----icon/graph illustrating Nyquist foldover
# Installing # Linux (source) # Windows # InstallingOSX
---Updated Extended installation instruction ---Screenshots of installation
# ConfiguringPD
---Screenshots of config menus from all three operating systems (slightly different locations on OSX, Windows, Linux) ---Better introduction to Path, Startup and how to configure Externals with Extended
# TroubleShooting
---"I don't hear any sound!" Screenshot "compute audio" button + audio settings in PD, Maybe also audio control panels from different OSes? ---"The test tone sounds distorted!" Add screencap of testtone.pd patch ---"I'm not seeing any audio input!"audio settings in PD, with inputs and outputs highlighted ---"I don't see any MIDI input!" Screencaps: audio/midi prefernces with midi highlighted, OSX: Audio MIDI Setup.app, Linux: QJackctl, Windows: MIDI Ox/MIDI Yoke Junction ---"I get the message "... couldn't create" when I open a patch and there's a dashed line around my object!" Screencap: patch with uncreated objects (missing path/external problem)
# Getting Started # StartingPD
---"Starting PD with the Clickable Icon": OSX, Linux screencaps
# TheInterface
---Screenshots of different menus from all three OSes
# AudioTutorials
---"Introduction": block diagram of synthesizer architecture, as desribed in text ---Formatting: messages like "bang" inside quotes (no Caps, as I have done with "Bang" in some places and need to change...)
# AudioStreaming # DataflowTutorials
---give titles to screenshots so that readers can tell which patches match which images (some do this, some don't...) ---"Math": examples/discussion of [expr]??? ---"Order of connecting and [trigger]": explain the patches in-line, rather than only in comments in screenshots (so that text is searchable, copy/pasteable..) ---Screencaps are very aliased, to the point where you can't read the ~ in the object names. Should they be redone at new resolution or with antialiasing?
# Appendices # PureGlossary
---format of object names = [italics in square brackets], must be formatted correctly ---format of glossary words in general text: we don't have one yet. Bold on first use in chapter maybe? Needs formatting all through text.
# ListofObjects
---incomplete, please add more libs ---maybe more discussion of externals needed as well ---formatting of object names?
# PureLinks
---always welcome
# Credits
----MORE CHAPTERS/SECTIONS TO DO-----
- Configuring "Path" and "Startup" + adding Externals VERY IMPORTANT!
- MIDI tutorial (keyboards, sliders, etc, input + output to/from devices
or other programs)
- HID sensor tutorial
- Patching strategies (advanced usage and examples of GoP, Abstractions
mostly)
- Audiofile manipulation (tables + Extended objects)
- Realtime effects tutorial (delays, filters, etc)
- GEM VJ tutorial (pix_film, pix_movie)
- Networked data (OSC, netsend/netreceive)
Derek,
Thanks so much for putting this together!...I've definitely been using it and will try to post helpful feedback soon...glad to see this is on the list of todo's:
- Configuring "Path" and "Startup" + adding Externals VERY IMPORTANT!
I just made a switch to OSX from windows...not sure if it is related, but I finally feel like I am making sense of the objects. Maybe just more comfortable spending time on this new machine. I am finding that learning is coming from lots of different sources...I've also gained alot from the help files in the doc folder particularly the ones written by hcs...but your floss, really helped get things rolling!
Toby Sinkinson
On Tue, May 6, 2008 at 1:54 PM, Derek Holzer derek@umatic.nl wrote:
Dear Pure Dataheads,
following the PD FLOSS Booksprint in Croatia last month, the 0.1 version of the Pure Data FLOSS Manual is now online!
http://flossmanuals.net/puredata
The Pure Data FLOSS Manual is conceived as a beginner's approach to Pure Data which, unlike most of the existing documentation, doesn't assume that the user has a degree in mathematics or computer science before they get started! Currently, information on installing and configuring PD, the interface, dataflow tutorials and audio tutorials are included. The FLOSS Manuals philosophy is that chapters from the different available FLOSS Manuals can be "remixed" to create new manuals (for course readers & curriculums, classroom manuals, etc etc). Everything is published under the GNU General Public License.
Adam Hyde, Luka Prinčič and myself busted some serious ass to get this up, and now we're ready to take on our toughest customers: YOU.
We'd really appreciate it if members of this list could read through the chapters, keeping the following points in mind:
- Is the text clear and consistent?
- If technical jargon is used, is it defined inline or included in the
Glossary in the back? 3) Are the tutorials complete, or are some steps or information missing? 4) Grammar/spelling, of course 5) Could each chapter exist as a self-standing tutorial outside the context of the PD Manual (i.e. could it be "remixed" with chapters from other FLOSS Manuals without losing anything)?
Those not so familiar with Pure Data are encouraged to go through the different tutorials and give feedback as to whether they need more (or less!) information, and whether different parts are redundant or need to be split off from the chapters they are in. Experienced PD users are also welcome, of course!
Also, we are still seeking help getting graphics and screenshots for several sections. And there is a HUGE to-do list if you want to get more seriously involved in the project!
Thanks and best wishes! Derek
----TO DO BY CHAPTER LIST----
# Pure Data # Introduction
---cover image, important!
# WhatIsGraphicalProgramming
----icons/graphics to go with concepts in text ----icons of modular synth with patch cables or similar analog "patching" ----flowchart of inputs and outputs between PD and audio, MIDI, network, video, Arduino/motors, etc ----chart describing relationship of PD to Externals
# WhatIsDigitalAudio
----icons/graphics to go with concepts in text ----icon of speaker cone movement ----icon of microphone to voltage to soundcard ----icon of soundcard to voltage to speaker movement ----icon of clipping audio ----icon/graph illustrating Nyquist foldover
# Installing # Linux (source) # Windows # InstallingOSX
---Updated Extended installation instruction ---Screenshots of installation
# ConfiguringPD
---Screenshots of config menus from all three operating systems (slightly different locations on OSX, Windows, Linux) ---Better introduction to Path, Startup and how to configure Externals with Extended
# TroubleShooting
---"I don't hear any sound!" Screenshot "compute audio" button + audio settings in PD, Maybe also audio control panels from different OSes? ---"The test tone sounds distorted!" Add screencap of testtone.pd patch ---"I'm not seeing any audio input!"audio settings in PD, with inputs and outputs highlighted ---"I don't see any MIDI input!" Screencaps: audio/midi prefernces with midi highlighted, OSX: Audio MIDI Setup.app, Linux: QJackctl, Windows: MIDI Ox/MIDI Yoke Junction ---"I get the message "... couldn't create" when I open a patch and there's a dashed line around my object!" Screencap: patch with uncreated objects (missing path/external problem)
# Getting Started # StartingPD
---"Starting PD with the Clickable Icon": OSX, Linux screencaps
# TheInterface
---Screenshots of different menus from all three OSes
# AudioTutorials
---"Introduction": block diagram of synthesizer architecture, as desribed in text ---Formatting: messages like "bang" inside quotes (no Caps, as I have done with "Bang" in some places and need to change...)
# AudioStreaming # DataflowTutorials
---give titles to screenshots so that readers can tell which patches match which images (some do this, some don't...) ---"Math": examples/discussion of [expr]??? ---"Order of connecting and [trigger]": explain the patches in-line, rather than only in comments in screenshots (so that text is searchable, copy/pasteable..) ---Screencaps are very aliased, to the point where you can't read the ~ in the object names. Should they be redone at new resolution or with antialiasing?
# Appendices # PureGlossary
---format of object names = [italics in square brackets], must be formatted correctly ---format of glossary words in general text: we don't have one yet. Bold on first use in chapter maybe? Needs formatting all through text.
# ListofObjects
---incomplete, please add more libs ---maybe more discussion of externals needed as well ---formatting of object names?
# PureLinks
---always welcome
# Credits
----MORE CHAPTERS/SECTIONS TO DO-----
- Configuring "Path" and "Startup" + adding Externals VERY IMPORTANT!
- MIDI tutorial (keyboards, sliders, etc, input + output to/from devices
or other programs)
- HID sensor tutorial
- Patching strategies (advanced usage and examples of GoP, Abstractions
mostly)
- Audiofile manipulation (tables + Extended objects)
- Realtime effects tutorial (delays, filters, etc)
- GEM VJ tutorial (pix_film, pix_movie)
- Networked data (OSC, netsend/netreceive)
-- derek holzer ::: http://www.umatic.nl ::: http://blog.myspace.com/macumbista ---Oblique Strategy # 36: "Consult other sources -promising -unpromising"
PD-announce mailing list PD-announce@iem.at http://lists.puredata.info/listinfo/pd-announce _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
It's wonderful. The style is nice and the layout and ordering has really improved since you first started.
Do you think the URL is likely to remain stable enough to be a ref in a textbook?
Also,
Can you renew my twiki login please?
Wasn't I once in the credits but you factored out the synth tutorial? (fair enough because it wasn't beginner level)
What about incorporating a chapter on Pd idioms and Fx once it's converted from LaTeX to HTML?
Andy
n Tue, 06 May 2008 21:54:48 +0200 Derek Holzer derek@umatic.nl wrote:
Dear Pure Dataheads,
following the PD FLOSS Booksprint in Croatia last month, the 0.1 version of the Pure Data FLOSS Manual is now online!
http://flossmanuals.net/puredata
The Pure Data FLOSS Manual is conceived as a beginner's approach to Pure Data which, unlike most of the existing documentation, doesn't assume that the user has a degree in mathematics or computer science before they get started! Currently, information on installing and configuring PD, the interface, dataflow tutorials and audio tutorials are included. The FLOSS Manuals philosophy is that chapters from the different available FLOSS Manuals can be "remixed" to create new manuals (for course readers & curriculums, classroom manuals, etc etc). Everything is published under the GNU General Public License.
Adam Hyde, Luka Prin__i__ and myself busted some serious ass to get this up, and now we're ready to take on our toughest customers: YOU.
We'd really appreciate it if members of this list could read through the chapters, keeping the following points in mind:
- Is the text clear and consistent?
- If technical jargon is used, is it defined inline or included in the
Glossary in the back? 3) Are the tutorials complete, or are some steps or information missing? 4) Grammar/spelling, of course 5) Could each chapter exist as a self-standing tutorial outside the context of the PD Manual (i.e. could it be "remixed" with chapters from other FLOSS Manuals without losing anything)?
Those not so familiar with Pure Data are encouraged to go through the different tutorials and give feedback as to whether they need more (or less!) information, and whether different parts are redundant or need to be split off from the chapters they are in. Experienced PD users are also welcome, of course!
Also, we are still seeking help getting graphics and screenshots for several sections. And there is a HUGE to-do list if you want to get more seriously involved in the project!
Thanks and best wishes! Derek
----TO DO BY CHAPTER LIST----
# Pure Data # Introduction
---cover image, important!
# WhatIsGraphicalProgramming
----icons/graphics to go with concepts in text ----icons of modular synth with patch cables or similar analog "patching" ----flowchart of inputs and outputs between PD and audio, MIDI, network, video, Arduino/motors, etc ----chart describing relationship of PD to Externals
# WhatIsDigitalAudio
----icons/graphics to go with concepts in text ----icon of speaker cone movement ----icon of microphone to voltage to soundcard ----icon of soundcard to voltage to speaker movement ----icon of clipping audio ----icon/graph illustrating Nyquist foldover
# Installing # Linux (source) # Windows # InstallingOSX
---Updated Extended installation instruction ---Screenshots of installation
# ConfiguringPD
---Screenshots of config menus from all three operating systems (slightly different locations on OSX, Windows, Linux) ---Better introduction to Path, Startup and how to configure Externals with Extended
# TroubleShooting
---"I don't hear any sound!" Screenshot "compute audio" button + audio settings in PD, Maybe also audio control panels from different OSes? ---"The test tone sounds distorted!" Add screencap of testtone.pd patch ---"I'm not seeing any audio input!"audio settings in PD, with inputs and outputs highlighted ---"I don't see any MIDI input!" Screencaps: audio/midi prefernces with midi highlighted, OSX: Audio MIDI Setup.app, Linux: QJackctl, Windows: MIDI Ox/MIDI Yoke Junction ---"I get the message "... couldn't create" when I open a patch and there's a dashed line around my object!" Screencap: patch with uncreated objects (missing path/external problem)
# Getting Started # StartingPD
---"Starting PD with the Clickable Icon": OSX, Linux screencaps
# TheInterface
---Screenshots of different menus from all three OSes
# AudioTutorials
---"Introduction": block diagram of synthesizer architecture, as desribed in text ---Formatting: messages like "bang" inside quotes (no Caps, as I have done with "Bang" in some places and need to change...)
# AudioStreaming # DataflowTutorials
---give titles to screenshots so that readers can tell which patches match which images (some do this, some don't...) ---"Math": examples/discussion of [expr]??? ---"Order of connecting and [trigger]": explain the patches in-line, rather than only in comments in screenshots (so that text is searchable, copy/pasteable..) ---Screencaps are very aliased, to the point where you can't read the ~ in the object names. Should they be redone at new resolution or with antialiasing?
# Appendices # PureGlossary
---format of object names = [italics in square brackets], must be formatted correctly ---format of glossary words in general text: we don't have one yet. Bold on first use in chapter maybe? Needs formatting all through text.
# ListofObjects
---incomplete, please add more libs ---maybe more discussion of externals needed as well ---formatting of object names?
# PureLinks
---always welcome
# Credits
----MORE CHAPTERS/SECTIONS TO DO-----
- Configuring "Path" and "Startup" + adding Externals VERY IMPORTANT!
- MIDI tutorial (keyboards, sliders, etc, input + output to/from devices
or other programs)
- HID sensor tutorial
- Patching strategies (advanced usage and examples of GoP, Abstractions
mostly)
- Audiofile manipulation (tables + Extended objects)
- Realtime effects tutorial (delays, filters, etc)
- GEM VJ tutorial (pix_film, pix_movie)
- Networked data (OSC, netsend/netreceive)
-- derek holzer ::: http://www.umatic.nl ::: http://blog.myspace.com/macumbista ---Oblique Strategy # 36: "Consult other sources -promising -unpromising"
PD-announce mailing list PD-announce@iem.at http://lists.puredata.info/listinfo/pd-announce _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Perhaps the Dataflow tutorials needs to come before the synth tutorial as we don't know about subpatches &c at this point.
I need to read through the whole thing again but the points on my mind are to with structure and ordering of concepts if this is for beginners.
best
andy
Derek Holzer wrote:
Dear Pure Dataheads,
following the PD FLOSS Booksprint in Croatia last month, the 0.1 version of the Pure Data FLOSS Manual is now online!
http://flossmanuals.net/puredata
Adam Hyde, Luka Prinčič and myself busted some serious ass to get this up, and now we're ready to take on our toughest customers: YOU.
great that it is here now.
We'd really appreciate it if members of this list could read through the chapters, keeping the following points in mind:
- Is the text clear and consistent?
Installing:
i find it highly confusing that the "Installing Pure Data on Debian" (and ubuntu) does not mention in a single word that you could just run "aptitude install puredata"
also, the InstallingOSX is probably not completed yet, as this is the only installer-page that has no beautiful imagery (but then it mentions 'canonical' Pd)
and very minor: please rename "Windows" to "InstallingWindows"
StartingPD: i think "starting Pd from shell on w32" should use C:\Program Files\pd\bin\pd.com instead of C:\Program Files\pd\bin\pd.exe in order to have any benefit of using the cli. also it would probably be better to use %ProgramFiles%\pd\bin\ to make it work on any installation (but then again, i guess this is probably too complicated)
Troubleshooting in the "sack-overflow" faq, i find the the mentioning of "Dataflow Objects" rather confusing, as in the rest of the text, these are just "objects". are "DataFlow Objects" a different kind of objects? (digging deeper into the tutorial i notice that you seem to refer to message-objects as "Dataflow Objects", so it makes a bit more sense; however, for me, this terminology is new; i therefore wonder why you introduced it)
PureGlossary: VectorBasedGraphics are graphics "where every element on the screen is defined by a set of numbers describing their appearance". now i wonder what's the difference to an "image", where every element on the screen (pixel) is defined by a set of numbers (R, G, B) describing their appearance.
ListOfObjects: MarkEx is no longer part of Gem
PureLinks:
- in the Installing section you seem to refer to puredata.info, which is
not at all found on the PureLinks page (well it is, in the mailinglist section); i would suggest to either use puredata.org _or_ puredata.info (and would favour the latter :-))
- "Linux Distributions with Pd": both Debian and ubuntu (regular) are
simply missing; ubuntu studio has a " " leftover
- Grammar/spelling, of course
Miller refers to "Pd" rather than "PD", shouldn't this canonical form be used? (which reminds me, that even the header of this list says [PD] :-|)
Thanks and best wishes!
_very nice_
can i just incorporate some of the info into the puredata FAQ?
mfga.sdr IOhannes
On May 7, 2008, at 9:54 AM, IOhannes m zmoelnig wrote:
Derek Holzer wrote:
Dear Pure Dataheads,
following the PD FLOSS Booksprint in Croatia last month, the 0.1
version of the Pure Data FLOSS Manual is now online!http://flossmanuals.net/puredata
Adam Hyde, Luka Prinčič and myself busted some serious ass to get
this up, and now we're ready to take on our toughest customers: YOU.great that it is here now.
We'd really appreciate it if members of this list could read
through the chapters, keeping the following points in mind:
- Is the text clear and consistent?
Installing:
i find it highly confusing that the "Installing Pure Data on Debian" (and ubuntu) does not mention in a single word that you could just run "aptitude install puredata"
also, the InstallingOSX is probably not completed yet, as this is the only installer-page that has no beautiful imagery (but then it
mentions 'canonical' Pd)
InstallingOSX looks pretty complete to me, I guess screenshots would
be good, there is actually an extraneous line. This line last
applied for version 0.38.4, it would be much better if it was
entirely removed:
3. Copy the file named org.puredata.pd.plist to ~/Library/
Preferences. (The '~' character stands for your home folder).
[REMARK: Is this still required? I think it worked 'automagically'
when I installed it...]
Also, I think it should not be called "Hans-Christoph Steiner's
extended version", many other people have contributed, and I indeed
starting building on the work of others. I think it would be better
labeled "the Pd community's extended version" since it included the
externals, docs, patches, etc of many many people.
One possible addition to InstallingOSX would be referencing JackOSX
(http://jackosx.com/) for anyone who might want to use Jack. Or on
the InstallingWindows, it would be very good to point to ASIO4ALL
http://www.asio4all.com/, since it is free as in beer and usually
makes the audio work much better on Windows.
.hc
and very minor: please rename "Windows" to "InstallingWindows"
StartingPD: i think "starting Pd from shell on w32" should use C:\Program Files\pd\bin\pd.com instead of C:\Program Files\pd\bin\pd.exe in order to have any benefit of using the cli. also it would probably be better to use %ProgramFiles%\pd\bin\ to make it work on any installation (but then again, i guess this is probably too complicated)
Troubleshooting in the "sack-overflow" faq, i find the the mentioning of "Dataflow Objects" rather confusing, as in the rest of the text, these are just "objects". are "DataFlow Objects" a different kind of objects? (digging deeper into the tutorial i notice that you seem to refer to message-objects as "Dataflow Objects", so it makes a bit more sense; however, for me, this terminology is new; i therefore wonder why you introduced it)
PureGlossary: VectorBasedGraphics are graphics "where every element on the screen is defined by a set of numbers describing their appearance". now i wonder what's the difference to an "image", where every
element on the screen (pixel) is defined by a set of numbers (R, G, B) describing their appearance.ListOfObjects: MarkEx is no longer part of Gem
PureLinks:
- in the Installing section you seem to refer to puredata.info,
which is not at all found on the PureLinks page (well it is, in the mailinglist section); i would suggest to either use puredata.org _or_
puredata.info (and would favour the latter :-))
- "Linux Distributions with Pd": both Debian and ubuntu (regular) are
simply missing; ubuntu studio has a " " leftover
- Grammar/spelling, of course
Miller refers to "Pd" rather than "PD", shouldn't this canonical
form be used? (which reminds me, that even the header of this list says
[PD] :-|)Thanks and best wishes!
_very nice_
can i just incorporate some of the info into the puredata FAQ?
mfga.sdr IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
kill your television
On 07/05/2008, at 9.54, IOhannes m zmoelnig wrote:
Derek Holzer wrote:
- Grammar/spelling, of course
Miller refers to "Pd" rather than "PD", shouldn't this canonical
form be used? (which reminds me, that even the header of this list says
[PD] :-|)
Oh dear. Any chance of changing that (for all the iem-lists)? Please.
Steffen Juul wrote:
On 07/05/2008, at 9.54, IOhannes m zmoelnig wrote:
Derek Holzer wrote:
- Grammar/spelling, of course
Miller refers to "Pd" rather than "PD", shouldn't this canonical form be used? (which reminds me, that even the header of this list says [PD] :-|)
Oh dear. Any chance of changing that (for all the iem-lists)? Please.
i could easily. but then i guess 500 people will start shouting at me, because their mail-filters won't work anymore :-)
if nobody objects within the next week, i will change the subject-prefix from [PD] to [Pd] (and accordingly) on all Pd-related mailinglists.
fgmadr IOhannes
changing the mail filters shouldn't be too hard ;-)
i'd say, if you announce it again just before you do it, everyone should be fine.
roman
On Fri, 2008-05-09 at 08:55 +0200, IOhannes m zmölnig wrote:
Steffen Juul wrote:
On 07/05/2008, at 9.54, IOhannes m zmoelnig wrote:
Derek Holzer wrote:
- Grammar/spelling, of course
Miller refers to "Pd" rather than "PD", shouldn't this canonical form be used? (which reminds me, that even the header of this list says [PD] :-|)
Oh dear. Any chance of changing that (for all the iem-lists)? Please.
i could easily. but then i guess 500 people will start shouting at me, because their mail-filters won't work anymore :-)
if nobody objects within the next week, i will change the subject-prefix from [PD] to [Pd] (and accordingly) on all Pd-related mailinglists.
fgmadr IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Steffen Juul wrote:
On 09/05/2008, at 11.27, Roman Haefeli wrote:
changing the mail filters shouldn't be too hard ;-)
And why filter list-mail by subject? I might miss an obvious reason,
thats why i ask.
i assumed that many people have never ever looked at the mail-headers of an email - apart from the obvious fields that are shown by default on most mtas (subject:, from:, date:, ...) - and don't even know that they could filter based on rfc2919
i might be wrong of course.
mgf,adsr IOhannes
PS: probably most people don't do any filtering anyhow...
IOhannes m zmölnig wrote:
Steffen Juul wrote:
On 07/05/2008, at 9.54, IOhannes m zmoelnig wrote:
Derek Holzer wrote:
- Grammar/spelling, of course
Miller refers to "Pd" rather than "PD", shouldn't this canonical form be used? (which reminds me, that even the header of this list says [PD] :-|)
Oh dear. Any chance of changing that (for all the iem-lists)? Please.
i could easily. but then i guess 500 people will start shouting at me, because their mail-filters won't work anymore :-)
if nobody objects within the next week, i will change the subject-prefix from [PD] to [Pd] (and accordingly) on all Pd-related mailinglists.
I think mail filters are not case sensitive, at least thunderbird is not. I am more worried about spam filters of they are case sensitive, I had to train my mail programs (gmail [please don't shout at me...] and thunderbird), because some of the pd mails went to spam. maybe you can send out a testmail with the new header and see if it comes through. marius.
Hallo, marius schebella hat gesagt: // marius schebella wrote:
I am more worried about spam filters of they are case sensitive, I had to train my mail programs (gmail [please don't shout at me...] and thunderbird), because some of the pd mails went to spam. maybe you can send out a testmail with the new header and see if it comes through.
I hope, you don't have "Pd" and "pd" as well as "PD" and maybe "pD" in your blacklist. ;)
Ciao
Frank
Hallo, IOhannes m zmölnig hat gesagt: // IOhannes m zmölnig wrote:
if nobody objects within the next week, i will change the subject-prefix from [PD] to [Pd] (and accordingly) on all Pd-related mailinglists.
Personally I filter by "List-Id:" but currently this is referring to "PureData" which also is incorrect (at least according to the FAQ-item I just added: http://puredata.info/docs/faq/pdspelling)
Maybe you want to change that as well while you're at it - with an advance warning so I can adapt my filter in time.
Ciao
Frank Barknecht _ ______footils.org__
On 12/05/2008, at 23.40, Frank Barknecht wrote:
Maybe you want to change that as well while you're at it
Good idea.
- with an advance warning so I can adapt my filter in time.
Alternatively you could make your filter look for list-id in '"List- ID:" [phrase] "<" list-id ">"' instead of (part of) phrase.
Best
Hi IOhannes,
just getting back around to these edits..
IOhannes m zmoelnig wrote:
Installing:
i find it highly confusing that the "Installing Pure Data on Debian" (and ubuntu) does not mention in a single word that you could just run "aptitude install puredata"
Does this install PD Extended? The manual is aimed at Extended rather than Vanilla. If it does install extended, have the package requirements which forced us to make some strange workarounds for Ubuntu been resolved? Or do the repositories still need to be edited. See the InstallingUbuntu page for details...
http://flossmanuals.net/PureData/InstallingUbuntu
best! D.
Derek Holzer wrote:
Hi IOhannes,
just getting back around to these edits..
IOhannes m zmoelnig wrote:
Installing:
i find it highly confusing that the "Installing Pure Data on Debian" (and ubuntu) does not mention in a single word that you could just run "aptitude install puredata"
Does this install PD Extended?
no it installs vanilla Pd.
The manual is aimed at Extended rather
this is news to me, as i nowhere found a reference to that.
the "InstallingOSX" sections explicitely tells you how to install pd-vanilla, and only later goes for Pd-extended. it doesn't tell the user anywhere that they are expected to use Pd-extended if they want to follow the tutorials.
all other installation-instructions seem to imply Pd-extended, but nowhere say so. instead they refer to millers homepage (where you would get pd-vanilla), and refer to version-used-for-this-installation "0.39-3" which might have substantial differences between Pd and PdX.
at the very least i would suggest:
- use "0.39-3-extended" as the version string
- clarify for OSX users that they should actually install Pd-extended.
(on my wishlist would be to make the os-x install instructions to be of the same quality as for the other OSs)
oh...i just saw that someone already (derek?) already submitted an "standardized" version of InstallingOSX, but it is not visible yet to the public. probably it is still "pending"?
fmgas IOhannes
Hey IOhannes,
last night I already changed the InstallingOSX page to be like the others, however I'm having trouble getting it "published". In the next day or so it should get sorted out, and then it will be very clear that the focus is Pd-Extended for all platforms.
best! D.
IOhannes m zmoelnig wrote:
Derek Holzer wrote:
Hi IOhannes,
just getting back around to these edits..
IOhannes m zmoelnig wrote:
Installing:
i find it highly confusing that the "Installing Pure Data on Debian" (and ubuntu) does not mention in a single word that you could just run "aptitude install puredata"
Does this install PD Extended?
no it installs vanilla Pd.
The manual is aimed at Extended rather
this is news to me, as i nowhere found a reference to that.
the "InstallingOSX" sections explicitely tells you how to install pd-vanilla, and only later goes for Pd-extended. it doesn't tell the user anywhere that they are expected to use Pd-extended if they want to follow the tutorials.
all other installation-instructions seem to imply Pd-extended, but nowhere say so. instead they refer to millers homepage (where you would get pd-vanilla), and refer to version-used-for-this-installation "0.39-3" which might have substantial differences between Pd and PdX.
at the very least i would suggest:
- use "0.39-3-extended" as the version string
- clarify for OSX users that they should actually install Pd-extended.
(on my wishlist would be to make the os-x install instructions to be of the same quality as for the other OSs)
oh...i just saw that someone already (derek?) already submitted an "standardized" version of InstallingOSX, but it is not visible yet to the public. probably it is still "pending"?
fmgas IOhannes
-
Andy Farnell -
Derek Holzer -
Frank Barknecht -
Hans-Christoph Steiner -
IOhannes m zmoelnig -
IOhannes m zmölnig
-
marius schebella -
Roman Haefeli -
Steffen Juul -
Toby Sinkinson