Re: [PD] .pdrc midi woes

2017-08-29 Thread Peter P.
* IOhannes m zmölnig [2017-08-29 12:06]: > On 08/29/2017 12:02 PM, Peter P. wrote: > > Adding [...] to ~/.pdrc > [...] > > Is this intentional? > > > i do not know, but i'm very sure that you shouldn't use .pdrc at all. > .pdsettings has superseded it with Pd-0.38-0, released

Re: [PD] .pdrc midi woes

2017-08-29 Thread IOhannes m zmölnig
On 08/29/2017 12:02 PM, Peter P. wrote: > Adding [...] to ~/.pdrc [...] > Is this intentional? i do not know, but i'm very sure that you shouldn't use .pdrc at all. .pdsettings has superseded it with Pd-0.38-0, released in january 2005. support for .pdrc has been kept for *legacy* settings for

[PD] .pdrc midi woes

2017-08-29 Thread Peter P.
Hi, Adding -alsamidi -mididev 1 to ~/.pdrc has Pd not create midi output port and lets Pd default to OSS-Midi, while $ pd -alsamidi -mididev 1 does. Is this intentional? Thank you! P ___ Pd-list@lists.iem.at mailing list

Re: [PD] .pdrc?

2017-04-15 Thread Peter P.
* zmoel...@iem.at [2017-04-14 08:48]: [...] > this is mainly because ~/.pdsettings works differently from .pdrc (which > just had one-cmdline-arg per line). > instead, .pdsettings uses key/value pairs with the "keys" being > predefined and not corresponding to any cmdline args,

Re: [PD] .pdrc?

2017-04-14 Thread IOhannes m zmölnig
On 04/14/2017 12:56 AM, Peter P. wrote: > Does pd write into .pdsettings itself by the way? yes. > What if I don't want > that? then you shouldn't click on "save" in any of the properties/settings dialogs. >> oh, and btw: autopatching is *really* nice (mostly). > Oh absolutely! There is

Re: [PD] .pdrc?

2017-04-14 Thread zmoelnig
On 04/14/2017 12:58 AM, Peter P. wrote: > Strangely neither setting > > -noautopatch > > nor > > noautopatch > > in my ~/.pdsettings disables autopatching. Specifying it on the command > line does work though. Can anyone else reproduce this? sure thing. this is mainly because ~/.pdsettings

Re: [PD] .pdrc?

2017-04-13 Thread Peter P.
Strangely neither setting -noautopatch nor noautopatch in my ~/.pdsettings disables autopatching. Specifying it on the command line does work though. Can anyone else reproduce this? best, P ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and

Re: [PD] .pdrc?

2017-04-13 Thread Claude Heiland-Allen
Hi, With no ~/.pdsettings, putting -noautopatch into my ~/.pdrc works as expected. Tested with: $ pd -version Pd-0.47.1 ("") compiled for Debian (0.47.1-3) on 2016/11/28 at 20:56:10 UTC On 13/04/17 23:58, Peter P. wrote: > Strangely neither setting > > -noautopatch > > nor > > noautopatch

Re: [PD] .pdrc?

2017-04-13 Thread Peter P.
* zmoel...@iem.at [2017-04-13 18:36]: > On 04/13/2017 10:39 PM, Peter P. wrote: > > Hi, > > > > I find that my Pd does do autopatching despite > > -noautopatch > > being specified in my ~/.pdrc which makes me wonder if that file is read > > at all? Or has the name/location

Re: [PD] .pdrc?

2017-04-13 Thread zmoelnig
On 04/13/2017 10:39 PM, Peter P. wrote: > Hi, > > I find that my Pd does do autopatching despite > -noautopatch > being specified in my ~/.pdrc which makes me wonder if that file is read > at all? Or has the name/location of pd's config file changed by now? > This is with Pd-0.47.1 ("")

[PD] .pdrc?

2017-04-13 Thread Peter P.
Hi, I find that my Pd does do autopatching despite -noautopatch being specified in my ~/.pdrc which makes me wonder if that file is read at all? Or has the name/location of pd's config file changed by now? This is with Pd-0.47.1 ("") compiled for Debian (0.47.1-3) installed via Debian