Update of /cvsroot/pure-data/pd/doc/1.manual In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv20598/pd/doc/1.manual
Modified Files: Tag: stable_0_38 fig1.1.png fig11.1.png fig11.2.png index.htm x2.htm x3.htm Log Message: 0.38-0 release.
Index: fig1.1.png =================================================================== RCS file: /cvsroot/pure-data/pd/doc/1.manual/fig1.1.png,v retrieving revision 1.1 retrieving revision 1.1.8.1 diff -C2 -d -r1.1 -r1.1.8.1 Binary files /tmp/cvsq5wVjh and /tmp/cvs0FTQ3B differ
Index: x3.htm =================================================================== RCS file: /cvsroot/pure-data/pd/doc/1.manual/x3.htm,v retrieving revision 1.4 retrieving revision 1.4.6.1 diff -C2 -d -r1.4 -r1.4.6.1 *** x3.htm 6 Sep 2004 20:20:25 -0000 1.4 --- x3.htm 3 Jan 2005 04:13:35 -0000 1.4.6.1 *************** *** 34,37 **** --- 34,39 ---- The rest of this section describes how to get audio and MIDI to work.
+ <H3> <A name=s1.0> 3.1. Audio and MIDI </A> </H3> + <P> To test audio and MIDI, start Pd and select "test Audio and MIDI" from the *************** *** 133,165 **** specify more if your hardware supports it.
! <H3> <A name=s1.1> 3.1. Installing Pd in Microsoft Windows </A> </H3>
! <P> Pd is compiled under NT, but should work under any version of Windows since ! 95. Pd will appear as a self-extracting archive (a ".exe" file). Run this and ! select a destination directory when prompted, such as "\pd" or "Program ! Files\pd".
! <P> ! If for example you put Pd in "C:Program Files\pd", the executable program will be ! "C:Program Files\pd\bin\pd". You can simply adjust your path to include ! C:\pd\bin and then ! invoke "pd" in a command prompt window. You can also make a shortcut to the ! executable program (left-click on it and drag to the desktop, for example.)
! <P> Pd requires "TCP/IP networking" to be turned on. This doesn't mean you ! have to be on a real network, but simply that Pd actually consists of two ! programs that make a "network link" (locally) to intercommunicate.
- <H4> The vanishing window </H4>
! <P> Pd is a "command line" program. Most error and diagnostic ! messages from Pd appear on the command prompt window Pd runs from.
! <P> If you start Pd from the "run" menu or as a shortcut, and if there's ! a problem with run-time flags (see the Pd command line below), Pd will ! print an error and exit. You won't see this error unless you arrange for the ! "command prompt" or "msdos" window to stay open after Pd exits. One way ! to do this is to make a "batch" file ("run.bat", say) containing the Pd ! command line.
<H4> Audio in Microsoft Windows </H4> --- 135,168 ---- specify more if your hardware supports it.
! Other parameters may be tweaked using the command line; see under ! <A href=#s4> preferences and startup options </A>.
! <H6> MIDI </H6>
! <A> The "channel message" midi objects in Pd ! such as notein or pgmout will take channels 1-16 to mean the first open MIDI ! port, 17-32 the second one, and so on. The midiin, sysexin, midiout objects ! give you a separate inlet to specify which of the open MIDI port numbers ! you want.
! <P> System exclusive MIDI message input and output is theoretically supported ! in version 0.37 but does not work correctly on windows, even in 0.38.
! <H3> <A name=s1.1> 3.2. Installing Pd in Microsoft Windows </A> </H3>
! <P> Pd should work under any version of Windows since 95. You can download as ! a self-extracting archive (a ".exe" file). Run this and select a destination ! directory when prompted, such as "\pd" or "Program Files\pd". ! ! <P> If for example you put Pd in "C:Program Files\pd", the executable program ! will be "C:Program Files\pd\bin\pd". You can simply adjust your path to ! include C:\pd\bin and then invoke "pd" in a command prompt window. You can also ! make a shortcut to the executable program (left-click on it and drag to the ! desktop, for example.) ! ! <P> Pd requires "TCP/IP networking" to be turned on. This doesn't mean you ! have to be on a real network, but simply that Pd actually consists of two ! programs that make a "network link" (locally) to intercommunicate.
<H4> Audio in Microsoft Windows </H4> *************** *** 170,174 **** Type "pd -help" (or make any mistake) to get the syntax for specifying which device to use. You can modify the Pd shortcut (or batch file) to ! set these.
<P> --- 173,178 ---- Type "pd -help" (or make any mistake) to get the syntax for specifying which device to use. You can modify the Pd shortcut (or batch file) to ! set these, or else use the "startup" dialog (file menu) to specify ! startup arguments.
<P> *************** *** 191,198 **** occasionally; this might be fixed in the "second edition".
- <P> Some NT and W98 drivers greet you with a constant trail of "resyncing - audio" messages. Sometimes you can fix this by invoking Pd with the "-noresync" - flag. - <H4> ASIO </H4>
--- 195,198 ---- *************** *** 204,208 **** frames.
! <H3> <A name=s1.2> 3.2. Installing Pd in Linux </A> </H3>
<P> What to do depends on which flavor of Linux you are running (e.g., Debian --- 204,208 ---- frames.
! <H3> <A name=s1.2> 3.3. Installing Pd in Linux </A> </H3>
<P> What to do depends on which flavor of Linux you are running (e.g., Debian *************** *** 312,323 **** Be forewarned: installing and testing audio and MIDI drivers in Linux can take days or weeks. There apears to be no single place where you can get detailed ! information on Linux audio. ! ! <P> ! Depending on your hardware and software, you might or might not be able to ! run "full duplex," i.e., use audio input and output at the same time. For ! many applications it's important to be able to do this, but if by any chance ! you don't need simultaneous input and output you will have much less trouble ! than if you do.
<P> --- 312,318 ---- Be forewarned: installing and testing audio and MIDI drivers in Linux can take days or weeks. There apears to be no single place where you can get detailed ! information on Linux audio. One good source of information lives at: ! <A href=http://www.djcj.org/LAU/guide/index.php> ! http://www.djcj.org/LAU/guide/index.php </A>.
<P> *************** *** 332,424 **** <P> ALSA is able to emulate OSS, so that you can usually run Pd using the default "OSS" settings even if it's actually ALSA that's running. ! ! <H4> Installing and configuring FREE OSS </H4> ! ! <P> ! OSS is really a collection of loadable device drivers. The commands ! for loading and unloading the drivers are "insmod" and "rmmod". ! You can see if the audio drivers are ! running using "lsmod" (as root.) If you see something like: ! <PRE> ! ! Module Pages Used by ! eepro100 3 1 (autoclean) ! opl3 3 0 ! opl3sa2 1 0 ! ad1848 4 [opl3sa2] 0 ! mpu401 5 [opl3sa2] 0 ! sound 15 [opl3 opl3sa2 ad1848 mpu401] 0 ! soundcore 1 [sound] 6 ! soundlow 1 [sound] 0 ! aic7xxx 23 2 ! ! </PRE> ! ! <P>then OSS is running, and if all you see is: ! ! <PRE> ! ! eepro100 3 1 (autoclean) ! aic7xxx 23 2 ! ! </PRE> ! <P>then it isn't. You can turn OSS off by running "rmmod" repeatedly, starting ! with "opl3" (or whatever) so as not to remove any module before you remove ! all the modules that depend on it. In the above listing, "opl3*" is device ! dependent and you might see different names. ! ! <P> ! The file, "/etc/modules.conf" apparently controls which sound drivers are ! started at boot time. The sndconfig program updates this file but you can ! also change things manually, for instance to switch between two different sound ! cards. In Redhat 6.x and earlier, the file is named "conf.modules." ! ! <P> Here is a modules.conf file for OSS: ! ! <PRE> ! ! alias eth0 e100 ! alias parport_lowlevel parport_pc ! alias char-major-81 bttv ! alias usb-controller usb-uhci ! alias sound-slot-0 i810_audio ! alias sound-slot-1 es1371 ! ! </PRE> ! ! <P>Here the two sound cards are the (motherboard resident) i810 driver and an ! ensoniq es1371. ! ! <P> In RedHat at least, the "sndconfig" program tries to automatically search ! for your soundcard. Unfortunlately it only finds the "first" one which is ! often not the one you want to use! ! ! <P> Under OSS, programs can stream sound using either ! "block" or "stream" mode. Stream mode is the more modern and better of the ! two, but the majority of drivers, even for new sound cards, only ! support "block." Pd makes "block" the default. ! ! <H4> ALSA (Advanced Linux Sound Architecture) </H4> ! ! <P> ALSA is newer, hence less stable and harder to use, than OSS. ! Alsa comes in a "finished" version (0.5.x) and a ! different, redesigned, "beta" version, 0.9. Installing ALSA can be tricky ! and/or confusing. ! ! <P> As of version 0.37 Pd works only with 0.9.x versions. ! The RPM version of Pd is compiled for 0.9.x.
<P> By default, Pd uses OSS. If you are running ALSA, Pd will use ALSA's OSS emulation. To make Pd use ALSA "natively", i.e., the way ALSA is designed ! to be used, include the "-alsa" flag in the command line.
! <P> In ALSA, you can specify which sound card to use using the "-alsadev" ! flag. So, for instance, "-alsadev 3" means your third card, counting from ! one. You can also specify it the ALSA way: "-alsadev hw:3,0".
! <H4> Which sound card? </H4>
<P> ! Here's a rundown on my experiences with sound cards so far. See also the Pd mailing list archives.
--- 327,348 ---- <P> ALSA is able to emulate OSS, so that you can usually run Pd using the default "OSS" settings even if it's actually ALSA that's running. ! ALSA is newer, hence less stable and harder to use, than OSS. ! Installing ALSA can be tricky and/or confusing.
<P> By default, Pd uses OSS. If you are running ALSA, Pd will use ALSA's OSS emulation. To make Pd use ALSA "natively", i.e., the way ALSA is designed ! to be used, include the "-alsa" flag in the command line or bang on the "media" ! menu items.
! <P> You can add ALSA devices by name on the Pd command line: ! <PRE> ! pd -alsaadd loupgarou ! </PRE> ! instructs Pd to offer the 'loupgarou' audio device in the Audio Settings panel.
! <H4> Experiences with particular soudcards </H4>
<P> ! Here are some of my own experiences with sound cards so far. See also the Pd mailing list archives.
*************** *** 430,435 **** NOT WORK WITH PD.
! <P> Word on the Pd mailing list is that the only way at present (7/04) to use ! Hammerfall boards in Pd is via ALSA and jack.
<H6> MIDIMAN </H6> --- 354,363 ---- NOT WORK WITH PD.
! <P> The easiest way to use ! Hammerfall boards in Pd is via ALSA and jack; but you can use ALSA alone: ! <PRE> ! pd -alsa -channels 26 ! </PRE> ! works for me. If you don't specify the number of channels correctly Pd crashes.
<H6> MIDIMAN </H6> *************** *** 437,441 **** <P>Midiman sells PCI devices (delta 44, 66, 1010, and 1010LT) with between 4 and 10 channels in and out, for ! which there are ALSA drivers. The driver name is "ice1712".
<P> Alsa provides an "envy24control" program (in "utils". You should run --- 365,370 ---- <P>Midiman sells PCI devices (delta 44, 66, 1010, and 1010LT) with between 4 and 10 channels in and out, for ! which there are ALSA drivers. These are also very good, and they are a ! bit cheaper than Hammerfalls. The driver name is "ice1712".
<P> Alsa provides an "envy24control" program (in "utils". You should run *************** *** 444,487 **** but don't take it for granted...
! <H6> i810/i815 </H6>
! <P>In RedHat 7.0, motherboards with native i810 audio systems don't work in ! full duplex (they crash linux). Either run Pd -noadc or else (better) install ! ALSA.
! <H3> <A name="s1.3"> 3.3. Installing Pd in Macintosh OSX </A> </H3>
<P>Pd version 0.35 and up support Macintosh OSX. You need the OSX Jaguar distribution (10.2) or later.
! <P> To install Pd you can always just download ! the sources and compile them yourself, or (easier) ! find a MacOSX-style "package". The first package was put together by Adam ! Lindsay; the most current one seems to be the one by Hans ! on ! <A href="http://www.pure-data.info/Members/hans/"> ! http://www.pure-data.info/Members/hans/</A>. ! The package simply installs itself ! and you needn't follow the directions below. ! </P>
! <H4> To install on OSX from the binary tarball: </H4>
! <P> The binary tarballs on ! <A HREF="http://www.crca.ucsd.edu/~msp/software.html"> ! http://www.crca.ucsd.edu/~msp/software.html</A> ! take more steps to install but are more "official". To install them:
! <P> If you haven't already, first download and install Tcl/Tk; there are pointers on ! Hans's page, or try: http://tcltkaqua.sourceforge.net/ ! <A href="http://tcltkaqua.sourceforge.net/"> ! http://tcltkaqua.sourceforge.net/</A>. Double click on what you ! get (a disk image opens) and then double click on the "package" icon, and the ! installer should tell you how to proceed from there.
! <P> Then download a tarball like pd-0.37-0.mac.tar.gz, and expand it ! (I think that's done just by clicking on the thing in OSX.) You can install ! it into your home directory for example. Then start a shell window and ! type "~/pd/bin/pd" to it, and pd should start.
<H4> To install on OSX from source: </H4> --- 373,405 ---- but don't take it for granted...
! <H6> warning about i810/i815 drivers...</H6>
! <P>As of RedHat 7.0, motherboards with native i810 audio systems didn't work in ! full duplex (they crashed linux). Either run Pd -noadc or else (better) ! install ALSA. This ought to be fixed by now...
! <H3> <A name="s1.3"> 3.4. Installing Pd in Macintosh OSX </A> </H3>
<P>Pd version 0.35 and up support Macintosh OSX. You need the OSX Jaguar distribution (10.2) or later.
! <P> To install Pd you can always just download the sources and compile them ! yourself, or (easier) just download the Mac binary from the download page:
! <A href="http://crca.ucsd.edu/~msp/software.html"> ! http://crca.ucsd.edu/~msp/software.html</A>.
! This is in the form of a compressed Tar archive; just click on it and the Max ! will extract the Pd application. Open this and you should be running.
! <P> The package by Hans-Christoph Steiner, on
! <A href="http://at.or.at/hans/pd/installers.html"> ! http://at.or.at/hans/pd/installers.html</A>, ! ! has many updates and extensions ! which are not included in the original Pd distribution. Download this and ! follow the (simple) instructions found there. ! </P>
<H4> To install on OSX from source: </H4> *************** *** 498,502 **** and /Library/Frameworks/Tk.framework and /Library/Frameworks/Tcl.framework.
! <P> First download and install TK for OSX as described above.
<P> Then, just as for linux, just unload pd-whatever.tar.gz into a directory --- 416,423 ---- and /Library/Frameworks/Tk.framework and /Library/Frameworks/Tcl.framework.
! <P> First download and install TK for OSX. I get it from: ! <A href=http://tcltkaqua.sourceforge.net/> ! http://tcltkaqua.sourceforge.net/. </A> !
<P> Then, just as for linux, just unload pd-whatever.tar.gz into a directory *************** *** 510,514 **** </pre>
! <P>in the file, ~/.tcshrc, so that you can later just type "pd" to a shell. (The shell only reads the ~/.tcshrc file on startup, so this won't take effect in any existing shells unless you specially type --- 431,436 ---- </pre>
! <P>in the file, ~/.tcshrc, so that you can later just type "pd" to a shell. ! (The shell only reads the ~/.tcshrc file on startup, so this won't take effect in any existing shells unless you specially type *************** *** 518,524 **** <P>to them.)
! <P> In some cases you have to explicitly give "-soundindev" and "-soundoutdev" ! flags for Pd to open audio correctly; "pd -listdev" should show you the ! correct device numbers.
<P> To get MIDI working, you have to do the Mac OSX magic to get a USB --- 440,445 ---- <P>to them.)
! <P> Follow the general directions above for testing audio and/or MIDI ! as needed.
<P> To get MIDI working, you have to do the Mac OSX magic to get a USB *************** *** 526,538 **** I think you just download the OSX driver and follow directions.
! <P> On the machine I tried, it was necessary to type, ! ! <pre> ! pd -midiindev 1 -midioutdev 2 ! </pre> ! ! <P>to get MIDI working. ! ! <H3> <A name=s1.4> 3.4. Installing Pd in IRIX (SGI machines) </A> </H3>
<P> (NOTE: as of release 0.35 I haven't had an IRIX machine to compile --- 447,451 ---- I think you just download the OSX driver and follow directions.
! <H3> <A name=s1.4> 3.5. Installing Pd in IRIX (SGI machines) </A> </H3>
<P> (NOTE: as of release 0.35 I haven't had an IRIX machine to compile *************** *** 637,654 **** something about how to deal with this.
! <H3> <A name=s3> 3.5. graphics rendering using GEM </A> </H3>
! <P> ! GEM, originally by Mark Danks but now supported by Iohannes Zmoelnig, is essentially an extension of Pd that allows you to do OpenGL programming ! using a suite of "GEM objects" roughly parallel to the tilde objects built ! into Pd for audio. Find out more from ! <a href="http://iem.kug.ac.at/~zmoelnig/index.html"> Johannes's page</a>.
! <H3> <A name=s4> 3.6. The Pd command line </A> </H3>
! <P>Pd is a "command line" program. The best way to run it is from your ! "terminal emulator," "shell," or "MSDOS prompt." The command line is:
<PRE> --- 550,613 ---- something about how to deal with this.
+ <H3> <A name=s4> 3.6. Preferences and startup options </A> </H3>
! <P> Pd's behavior may be customized to instruct it where to find files, which ! audio devices to open, what font size to use, and so on. Most of ! these may also be changed using the various dialogs you can open from Pd's ! menus. Others take effect only when Pd starts up; some of these appear ! on the ``startup" dialog and some of them, too cranky to put in a GUI, must ! be typed as <I> command line arguments </I>.
! <P> In addition to the Audio and MIDI settings (see ! <A href="#s1.0"> Audio and MIDI </A>), you can customize font size (from the ! ``edit" menu), directories to search for files (see ! <A href="#s5"> How Pd searches for files </A>), and additional startup ! parameters described below. ! ! <P> All of these settings may be saved automatically between Pd sessions. ! It is also possible to specify settings directly via the <I> command ! line </I>. (A third mechanism, using configuration files, is deprecated and ! isn't described here.) The Pd command line is described in the next ! section. Command line settings, if given, each override the corresponding ! setting that was saved from Pd.
+ <P> The startup settings (i.e., those that take effect only when Pd is started) + are controlled using the ``startup..." dialog from the File menu. The + dialog appears as follows:
! <CENTER><P> ! <IMG src="fig11.3.png" ALT="startup dialog"> ! </P></CENTER>
! The slots at top each specify a binary ``library" for Pd to load on startup. ! These may be for Gem, pdp, zexy, iemlib, cyclone, and so on. Typically, a ! single binary object (an ``extern") is left for Pd to load automatically; ! startup library loading is appropriate for collections of many objects ! specified by a single binary library. ! ! <P> The ``defeat real-time scheduling" contol, if enabled, makes Pd run without ! its usual effort to become a real-time process (whatever this means in the ! operating system you are using.) In Unix, Pd must usually be setuid to allow ! real-time scheduling at all. ! ! <P> The ``startup flags" allow you to add to Pd's command line on startup. This ! is specified as described below, except that the initial word, ``pd", is ! understood. For example, putting ``-rt" in this field sets real-time ! scheduling; ``-sleepgrain 1" sets the sleep grain to 1 (see under MIDI below), ! and typing "-rt -sleepgrain 1" does both. ! ! <P> You may save the current settings for future Pd sessions with the ! ``save all settings" button; this saves not only the path but all other ! settings as well. ! ! <H6> Command line arguments </A> </H3> ! ! <P>Pd may be run as a "command line" program from your "terminal emulator," ! "shell," or "MSDOS prompt." In Windows, if Pd is started using a "shortcut" ! it is also run from a command line which you can edit using the ``properties" ! dialog for the shortcut. In any operating system, Pd can be called from a ! script (called a <I> batch file </I> on Windows or a <I> shell script </I> ! on OSX or unix). The command line is just a line of text, which should be ! of the form:
<PRE> *************** *** 703,706 **** --- 662,667 ---- general flags: -path <path> -- add to file search path + -nostdpath -- don't search standard ("extra") directory + -stdpath -- search standard directory (true by default) -helppath <path> -- add to help search path -open <file> -- open file(s) on startup *************** *** 711,718 **** --- 672,682 ---- -d <n> -- specify debug level -noloadbang -- suppress all loadbangs + -stderr -- send printout to standard error instead of GUI -nogui -- suppress starting the GUI + -guiport <n> -- connect to pre-existing GUI over port 'n' -guicmd "cmd..." -- substitute another GUI program (e.g., rsh) -send "msg..." -- send a message at startup (after patches are loaded) -rt or -realtime -- use real-time priority (needs root privilege) + -nrt -- don't use real-time priority
</PRE> *************** *** 740,744 **** is a problem.
! <H4> audio buffer size, block size, and sleep grain. </H4>
<P>You can specify an audio buffer size in milliseconds, typically between 10 and --- 704,708 ---- is a problem.
! <H4> audio buffer size and block size </H4>
<P>You can specify an audio buffer size in milliseconds, typically between 10 and *************** *** 748,771 **** and/or control inputs (MIDI, GUI) and the audio coming out.
! <P> You can also specify the audio block size in sample ! frames. This is 64 by default (except for MMIO for which it's 256), and may ! be 64, 128, or 256. ! ! ! <P> The "sleepgrain" controls how long (in milliseconds) Pd sleeps between ! periods of computation. This is normally the audio buffer divided by 4, but ! no less than 0.1 and no more than 5. On most OSes, ingoing and outgoing MIDI ! is quantized to this value, so if you care about MIDI timing, reduce this to 1. ! ! <H4> MIDI </H4> ! ! <A> The "channel message" midi objects in Pd ! such as notein or pgmout will take channels 1-16 to mean the first open MIDI ! port, 17-32 the second one, and so on. The midiin, sysexin, midiout objects ! give you a separate inlet to specify which of the open MIDI port numbers ! you want.
! <P> System exclusive MIDI message inupt and output is theoretically supported ! in version 0.37 but has not been tested.
<P> In Linux, if you --- 712,719 ---- and/or control inputs (MIDI, GUI) and the audio coming out.
! <P> You can also specify the audio block size in sample frames. This is 64 by ! default (except for MMIO for which it's 256), and may be 64, 128, or 256.
! <H4> MIDI and sleepgrain</H4>
<P> In Linux, if you *************** *** 776,780 **** numbers as listed by "pd -listdev."
! <H3> <A name="s5"> 3.7. dealing with files </A> </H3>
<P>Pd has a search path feature; you specify the path on the command line --- 724,734 ---- numbers as listed by "pd -listdev."
! <P> The "sleepgrain" controls how long (in milliseconds) Pd sleeps between ! periods of computation. This is normally the audio buffer divided by 4, but ! no less than 0.1 and no more than 5. On most OSes, ingoing and outgoing MIDI ! is quantized to this value, so if you care about MIDI timing, reduce this to 1 ! or less. ! ! <H3> <A name="s5"> 3.7. How Pd searches for files </A> </H3>
<P>Pd has a search path feature; you specify the path on the command line *************** *** 784,796 ****
<P> You can see and edit the path while Pd is running using the "path..." ! item in the "File" menu. The path must be correctly set before you load ! a patch or it may fail to find abstractions, etc., that are needed to ! construct the patch.
! <P>When Pd searches for an abstraction or an "extern" it uses the path to try to find the necessary file. The "read" ! messages to qlists and arrays (aka tables) work the same way. NO SPACES MAY ! APPEAR ANYWHERE IN THE SEARCH PATH, e.g., "c:\my nonsense\goobers" won't ! work.
<P> Path entries may be relative to the patch directory; for instance, --- 738,761 ----
<P> You can see and edit the path while Pd is running using the "path..." ! item in the "File" menu:
! <CENTER><P> ! <IMG src="fig11.4.png" ALT="startup dialog"> ! </P></CENTER> ! ! <P> The path must be correctly set before you load ! a patch or it may fail to find abstractions, etc., that are needed to ! construct the patch. When Pd searches for an abstraction or an "extern" it uses the path to try to find the necessary file. The "read" ! messages to qlists and arrays (aka tables) do this too. ! ! <P> If ``use standard extensions" is enabled, the usual ``extras" directory ! is also searched. This contains standard external objects like ``expr" and ! ``fiddle", and perhaps much more depending on the distribution of Pd ! you're using. ! ! <P> You may save the current settings for future Pd sessions with the ! ``save all settings" button; this saves not only the path but all other ! settings as well.
<P> Path entries may be relative to the patch directory; for instance, *************** *** 802,808 ****
<P> Regardless of path, Pd should look first in the directory containing ! the patch before searching down the path. (However, sometimes, for ! reasons I can't explain yet, you have to put the entry "." in the ! search path for this to happen, as least within linux!)
<P> Filenames in Pd are always separated by (unix-style) forward slashes, even --- 767,773 ----
<P> Regardless of path, Pd should look first in the directory containing ! the patch before searching down the path. Pd does not automatically look ! in the <I> current directory </I> however; to enable that, include ``." in ! the path. The ``extra" directory, if enabled, is searched last.
<P> Filenames in Pd are always separated by (unix-style) forward slashes, even *************** *** 814,822 **** <P> If a filename specified in a patch has any "/" characters in it, the "path" is not used; thus, "../sounds/sample1.wav" causes Pd only to look relative to ! the directory containing the patch. (You may also invoke externs that way.)
<P> As of version 0.35, there may be spaces in the path to Pd itself; also, ! the "openpanel" and "savepanel" objects can handle spaces. But still not ! the search path.
</BODY> --- 779,787 ---- <P> If a filename specified in a patch has any "/" characters in it, the "path" is not used; thus, "../sounds/sample1.wav" causes Pd only to look relative to ! the directory containing the patch. You may also invoke externs that way.
<P> As of version 0.35, there may be spaces in the path to Pd itself; also, ! the "openpanel" and "savepanel" objects can handle spaces. Spaces in the ! path should work as of version 0.38.
</BODY>
Index: x2.htm =================================================================== RCS file: /cvsroot/pure-data/pd/doc/1.manual/x2.htm,v retrieving revision 1.3 retrieving revision 1.3.6.1 diff -C2 -d -r1.3 -r1.3.6.1 *** x2.htm 6 Sep 2004 20:20:25 -0000 1.3 --- x2.htm 3 Jan 2005 04:13:35 -0000 1.3.6.1 *************** *** 52,58 **** menu. The main window display is intended only to help you avoid clipping on input and output. You can turn the peak meters on and off using the ! control at bottom left.
! <P> At bottom right is a control to turn audio processing on and off globally. Turning audio off stops the computation and relinquishes any audio devices Pd is using. The "Media" menu is also provided, with accelerators --- 52,58 ---- menu. The main window display is intended only to help you avoid clipping on input and output. You can turn the peak meters on and off using the ! control at lower left.
! <P> At lower right is a control to turn audio processing on and off globally. Turning audio off stops the computation and relinquishes any audio devices Pd is using. The "Media" menu is also provided, with accelerators *************** *** 71,74 **** --- 71,77 ---- <a href="x3.htm#s2"> audio and MIDI support </A>.
+ <P> The bottom part of the Pd window is an area for printout from objects in + patches, and/or for messages from Pd itself. + <P> Pd documents are called "patches" or "canvases." Each open document has one main window and any number of *************** *** 87,93 ****
<P> ! Pd's printout appears on its standard output. Normally, you'll run Pd in a ! "shell" or "terminal" window which you'll keep open to see any printout or ! error messages.
<H3> <A name="s1.2"> 2.1.2. object boxes </A> </H3> --- 90,95 ----
<P> ! Pd's printout appears on the main ``Pd" window, ! unless you redirect it elsewhere.
<H3> <A name="s1.2"> 2.1.2. object boxes </A> </H3>
Index: fig11.2.png =================================================================== RCS file: /cvsroot/pure-data/pd/doc/1.manual/fig11.2.png,v retrieving revision 1.1 retrieving revision 1.1.8.1 diff -C2 -d -r1.1 -r1.1.8.1 Binary files /tmp/cvsGLfZwv and /tmp/cvsAajfqQ differ
Index: index.htm =================================================================== RCS file: /cvsroot/pure-data/pd/doc/1.manual/index.htm,v retrieving revision 1.2 retrieving revision 1.2.6.1 diff -C2 -d -r1.2 -r1.2.6.1 *** index.htm 23 Sep 2003 00:18:11 -0000 1.2 --- index.htm 3 Jan 2005 04:13:35 -0000 1.2.6.1 *************** *** 94,105 **** <LI> <a href="x3.htm" name=s3> getting Pd to run </A> <OL> ! <LI> <a href="x3.htm"> Overview </A> ! <LI> <a href="x3.htm#s1.1">Installing Pd in Microsoft Windows </A> ! <LI> <a href="x3.htm#s1.2">Installing Pd in Linux </A> ! <LI> <a href="x3.htm#s1.3">Installing Pd in MacOS X </A> ! <LI> <a href="x3.htm#s1.4">Installing Pd in IRIX (SGI) </A> ! <LI> <a href="x3.htm#s3"> graphics rendering using GEM </A> ! <LI> <a href="x3.htm#s4"> The Pd command line </A> ! <LI> <a href="x3.htm#s5"> dealing with files </A> </OL> <LI> <a href="x4.htm" name=s4> writing Pd objects in C </A> --- 94,104 ---- <LI> <a href="x3.htm" name=s3> getting Pd to run </A> <OL> ! <LI> <a href="x3.htm#s1.0"> audio and MIDI </A> ! <LI> <a href="x3.htm#s1.1">installing Pd in Microsoft Windows </A> ! <LI> <a href="x3.htm#s1.2">installing Pd in Linux </A> ! <LI> <a href="x3.htm#s1.3">installing Pd in MacOS X </A> ! <LI> <a href="x3.htm#s1.4">installing Pd in IRIX (SGI) </A> ! <LI> <a href="x3.htm#s4"> preferences and startup options </A> ! <LI> <a href="x3.htm#s5"> how Pd searches for files </A> </OL> <LI> <a href="x4.htm" name=s4> writing Pd objects in C </A>
Index: fig11.1.png =================================================================== RCS file: /cvsroot/pure-data/pd/doc/1.manual/fig11.1.png,v retrieving revision 1.1 retrieving revision 1.1.8.1 diff -C2 -d -r1.1 -r1.1.8.1 Binary files /tmp/cvsY5Id5M and /tmp/cvsKn3YOf differ
