Thanks for the practical tips! Appreciated! It´s also good to be able to change the font and fontsize to a good windows standard, also another thing that was annoying when switching from Pd Extended to Pd Vanilla overcome! Consolas 12 seems like a good choice!
I think upon uninstall of Pd the extra folders are left untouched, so I think I will continue to have extra libraries there (pd/extra). Sometimes I read upon the importance of using /user/AppData/Roaming/Pd or Program/Common Files/Pd . How to think and act upon these considerations? I bet this been discussed alot before, maybe a new thread if not? Of course it is platform dependant and now here I am speaking windows considerations.
Here is pd -help list btw: C:\pd\bin>pd -help usage: pd [-flags] [file]...
audio configuration flags: -r <n> -- specify sample rate -audioindev ... -- audio in devices; e.g., "1,3" for first and third -audiooutdev ... -- audio out devices (same) -audiodev ... -- specify input and output together -audioaddindev -- add an audio input device by name -audioaddoutdev -- add an audio output device by name -audioadddev -- add an audio input and output device by name -inchannels ... -- audio input channels (by device, like "2" or "16,8") -outchannels ... -- number of audio out channels (same) -channels ... -- specify both input and output channels -audiobuf <n> -- specify size of audio buffer in msec -blocksize <n> -- specify audio I/O block size in sample frames -sleepgrain <n> -- specify number of milliseconds to sleep when idle -nodac -- suppress audio output -noadc -- suppress audio input -noaudio -- suppress audio input and output (-nosound is synonym) -callback -- use callbacks if possible -nocallback -- use polling-mode (true by default) -listdev -- list audio and MIDI devices -asio -- use ASIO audio driver (via Portaudio) -pa -- synonym for -asio -mmio -- use MMIO audio API (default for Windows) (default audio API for this platform: MMIO)
MIDI configuration flags: -midiindev ... -- midi in device list; e.g., "1,3" for first and third -midioutdev ... -- midi out device list, same format -mididev ... -- specify -midioutdev and -midiindev together -midiaddindev -- add a MIDI input device by name -midiaddoutdev -- add a MIDI output device by name -midiadddev -- add a MIDI input and output device by name -nomidiin -- suppress MIDI input -nomidiout -- suppress MIDI output -nomidi -- suppress MIDI input and output
other 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 file search path -open <file> -- open file(s) on startup -lib <file> -- load object library(s) -font-size <n> -- specify default font size in points -font-face <name> -- specify default font -font-weight <name>-- specify default font weight (normal or bold) -verbose -- extra printout on startup and when searching for files -noverbose -- no extra printout -version -- don't run Pd; just print out which version it is -d <n> -- specify debug level -loadbang -- do not suppress all loadbangs (true by default) -noloadbang -- suppress all loadbangs -stderr -- send printout to standard error instead of GUI -nostderr -- send printout to GUI instead of standard error (true by default) -gui -- start GUI (true by default) -nogui -- suppress starting the GUI -guiport <n> -- connect to pre-existing GUI over port <n> -guicmd "cmd..." -- start alternatve GUI program (e.g., remote via ssh) -send "msg..." -- send a message at startup, after patches are loaded -prefs -- load preferences on startup (true by default) -noprefs -- suppress loading preferences on startup -sleep -- sleep when idle, don't spin (true by default) -nosleep -- spin, don't sleep (may lower latency on multi-CPUs) -schedlib <file> -- plug in external scheduler -extraflags <s> -- string argument to send schedlib -batch -- run off-line as a batch process -nobatch -- run interactively (true by default) -autopatch -- enable auto-connecting new from selected objects (true by default) -noautopatch -- defeat auto-patching new from selected objects -compatibility <f> -- set back-compatibility to version <f>
/Björn Eriksson
On Thu, Aug 4, 2016 at 10:01 PM, Lucas Cordiviola lucarda27@hotmail.com wrote:
Hi Björn, David:
There's a good windows way to manage loading libs and path.
Mainly is a .cmd file that is used to start pd with whatever options.
With this folder structure:
Some parent folder (A)
A/externals
A/pd
A/x.cmd
(this folder struc keeps things in a modular way, so when the next Pd is released you can easily delete and replace.)
the .cmd file is just a text (saved as .cmd) that you can edit for whatever, it must be only one line and separeted with space (and also a TAB for better spacing) for example:
%CD%\pd\bin\pd -noprefs -path %CD%\externals\cyclone -lib %CD%\externals\zexy -path %CD%\externals\mrpeach
%CD% passes the full path, so you can use it in a USB stick.
For an up-to-date list of startupflags browse the explorer to the pd/bin dir an do Shift-right-click in the white space until you get the option “open command window here” there type “pd -help” without “ “.
Try :
-font-face Consolas -font-weight normal -font-size 12
Consolas is a system font since win vista, it fits well in the boxes.
Salutti, Lucarda
Mensaje telepatico asistido por maquinas.
*From:* Pd-list pd-list-bounces@lists.iem.at on behalf of Björn Eriksson miulew@gmail.com *Sent:* Thursday, August 4, 2016 12:23 PM *To:* Pd-List *Subject:* Re: [PD] Trying to get GEM going on Pd Vanilla / Win10
Thanks for clarifications IOhannes! I would really prefer to not declare anything with specific path references like this one with the Gem-0.93.3 folder. I understand it will induce problems if shared and if drives/sticks changes places, OS´s. The reason the versioned folder got there was due to the suggestion from Oliver to unzip all Gem.zip into the "extra" folder, which I did and got it there. I also tried to set path preferences (from menu - File-Preference-Path, also File-Preference-Startup, but it seems that neither of them are remembered after restart of Pd.
Will try to rename the versioned folder to just Gem.... instead of Gem-0.93.9 so to get rid of the dependecies. I hope it will work like that.
Guess I was happy that Gem finally started to work on this machine I am at, so didn´t see the fatalities of the versioned folder. (why is it anyway included in the zip-file if it causes this instabilties?)
All the best! Björn Eriksson
On Thu, Aug 4, 2016 at 1:25 PM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
On 2016-08-04 03:23, Björn Eriksson wrote:
In the patch I do have to [declare -lib /Gem-0.93.3/Gem] or with direct path where Gem is installed, on my external harddrive that is [declare
-lib
G:/pd/extra/Gem-0.93.3/Gem].
well, that sounds like a bad layout. the point of using [declare] is to create patches with dependency information that is platform independent and sharable.
for instance it makes little sense to use [declare -lib D:\bjoern\Pd-Projects\Gem-0.89\Gem]: while it might work, the patch will break as soon as you give it away (or port it to another computer, that is not running windows ANDOR has a cd-drive occupying the "D:" letter rather than yoiur USB-stick ANDOR has a different filesystem layout ANDOR ...
sp, if you put your externals into extra/, then you shouldn't use version-prefixes. if you do want to organise the directories the way you like, use the preferences to add additional paths.
e.g. extracting Gem to D:\bjoern\Pd-Projects\Gem-0.89\Gem\ you could add "D:\bjoern\Pd-Projects\Gem-0.89" to your search-paths (in the Pd-preferences) and then use [declare -lib Gem] in your patch. then, if you want to migrate the patch to another machine, install Gem to /home/bobby/projects/2018/external-pool/Gem/ and add "/home/bobby/projects/2018/external-pool" to your Pd-preferences. then run your patch. without any modifications!
fgasdmr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/li stinfo/pd-list