Re: [PD] prevent opening of patches

2013-09-24 Thread Marco Donnarumma
yes, exactly what I was thinking about. thanks Ivica.

M

--
Marco Donnarumma
New Media + Sonic Arts Practitioner, Performer, Teacher, Director.
Embodied Audio-Visual Interaction Research Team.
Department of Computing, Goldsmiths University of London
~
Portfolio: http://marcodonnarumma.com
Research: http://res.marcodonnarumma.com
Director: http://www.liveperformersmeeting.net


On Mon, Sep 23, 2013 at 4:53 AM, Ivica Ico Bukvic  wrote:

> FWIW, the latest pd-l2ork release has a “-unique” flag (disabled by
> default) so whenever you open a new file by double-clicking inside a file
> browser, it will open it inside an existing instance (if any) or spawn a
> new instance (if none). Spawning instances with –unique flag will force
> creation of a new instance.
>
> ** **
>
> *From:* pd-list-boun...@iem.at [mailto:pd-list-boun...@iem.at] *On Behalf
> Of *Marco Donnarumma
> *Sent:* Sunday, September 22, 2013 7:14 AM
> *To:* pd-list@iem.at
> *Subject:* Re: [PD] prevent opening of patches
>
> ** **
>
> That's useful, but up until recently you had to create a second instance
> of Pd from the command line anyway, since OSX would show you the instance
> you already had if you tried to open it from the operating system.
>
> Or...have I missed the point? My friend and collaborator always needs two
> Pd's, one for Gemnotes and one for audio processing, to play my
> musioc...and we wrote a BASH script to launch the gemnotes one after the
> audio one was set up.
>
> ** **
>
> well, personally most times, when developing, I need to create
> abstractions and use global variables just to experiment with stuff. And if
> two instances of Pd are opened when you don't want it, it can be very
> annoying.
>
> Even worst scenario when you are teaching, student might open 4 patches at
> a time, and as 4 Pd instances are launched, and it's a mess.
>
> I always wondered whether we could have a flag in Pd GUI that set this
> kind of configuration. Like, "always open a new Pd instance", "always use
> one Pd only"... something like that. imho it would be useful.
>
> cheers,
> M
>
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] prevent opening of patches

2013-09-22 Thread Ivica Ico Bukvic
FWIW, the latest pd-l2ork release has a "-unique" flag (disabled by default)
so whenever you open a new file by double-clicking inside a file browser, it
will open it inside an existing instance (if any) or spawn a new instance
(if none). Spawning instances with -unique flag will force creation of a new
instance.

 

From: pd-list-boun...@iem.at [mailto:pd-list-boun...@iem.at] On Behalf Of
Marco Donnarumma
Sent: Sunday, September 22, 2013 7:14 AM
To: pd-list@iem.at
Subject: Re: [PD] prevent opening of patches

 

That's useful, but up until recently you had to create a second instance of
Pd from the command line anyway, since OSX would show you the instance you
already had if you tried to open it from the operating system.

Or...have I missed the point? My friend and collaborator always needs two
Pd's, one for Gemnotes and one for audio processing, to play my musioc...and
we wrote a BASH script to launch the gemnotes one after the audio one was
set up.

 

well, personally most times, when developing, I need to create abstractions
and use global variables just to experiment with stuff. And if two instances
of Pd are opened when you don't want it, it can be very annoying.

Even worst scenario when you are teaching, student might open 4 patches at a
time, and as 4 Pd instances are launched, and it's a mess.

I always wondered whether we could have a flag in Pd GUI that set this kind
of configuration. Like, "always open a new Pd instance", "always use one Pd
only"... something like that. imho it would be useful.

cheers,
M

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


Re: [PD] prevent opening of patches

2013-09-22 Thread Ed Kelly
>That's useful, but up until recently you had to create a second instance of Pd 
>from the command line anyway, since OSX would show you the instance you 
>already had if you tried to open it from the operating system.
>>
>>Or...have I missed the point? My friend and collaborator always needs two 
>>Pd's, one for Gemnotes and one for audio processing, to play my musioc...and 
>>we wrote a BASH script to launch the gemnotes one after the audio one was set 
>>up.
>>
>>
>
>
>well, personally most times, when  developing, I need to create abstractions 
>and use global variables just to experiment with stuff. And if two instances 
>of Pd are opened when you don't want it, it can be very annoying.
>
>
>Even worst scenario when you are teaching, student might open 4 patches at a 
>time, and as 4 Pd instances are launched, and it's a mess.
>


Ah yes, students. 

Student: "But why can't I just double-click on the patch? It works for 
everything else?"

Tutor: "Because the audio driver will only work with the first instance of Pd 
you opened."

Student: "This software is rubbish. I hate Pd. Can we do something easier? It's 
too hard."

Fortunately I've just been made redundant from the institution where these 
words were spoken /;-/

Cheers,
Ed

>
>I always wondered whether we could have a flag in Pd GUI that set this kind of 
>configuration. Like, "always open a new Pd instance", "always use one Pd 
>only"... something like that. imho it would be useful.
>
>
>cheers,
>M
>
>
>  

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


Re: [PD] prevent opening of patches

2013-09-22 Thread Marco Donnarumma
>
> That's useful, but up until recently you had to create a second instance
> of Pd from the command line anyway, since OSX would show you the instance
> you already had if you tried to open it from the operating system.
>
> Or...have I missed the point? My friend and collaborator always needs two
> Pd's, one for Gemnotes and one for audio processing, to play my
> musioc...and we wrote a BASH script to launch the gemnotes one after the
> audio one was set up.
>
>
well, personally most times, when developing, I need to create abstractions
and use global variables just to experiment with stuff. And if two
instances of Pd are opened when you don't want it, it can be very annoying.

Even worst scenario when you are teaching, student might open 4 patches at
a time, and as 4 Pd instances are launched, and it's a mess.

I always wondered whether we could have a flag in Pd GUI that set this kind
of configuration. Like, "always open a new Pd instance", "always use one Pd
only"... something like that. imho it would be useful.

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


Re: [PD] prevent opening of patches

2013-09-21 Thread Ed Kelly
That's useful, but up until recently you had to create a second instance of Pd 
from the command line anyway, since OSX would show you the instance you already 
had if you tried to open it from the operating system.

Or...have I missed the point? My friend and collaborator always needs two Pd's, 
one for Gemnotes and one for audio processing, to play my musioc...and we wrote 
a BASH script to launch the gemnotes one after the audio one was set up.

Ed
 
Ninja Jamm - a revolutionary new music remix app from Ninja Tune and Seeper, 
for iPhone and iPad
http://www.ninjajamm.com/


Gemnotes-0.2: Live music notation for Pure Data, now with dynamics!
http://sharktracks.co.uk/ 


- Original Message -
> From: Matthias Kronlachner 
> To: pd-list 
> Cc: 
> Sent: Thursday, 19 September 2013, 14:06
> Subject: Re: [PD] prevent opening of patches
> 
> One more thing can be annoying on OSX:
> If you open a second instance of Pd, the same patch as in the first will 
> be opened.
> 
> One good thing to do is to create an AppleScript for opening Pd from the 
> Terminal:
> 
> * Open AppleScript Editor and past the line: (of course adapt Pd-.app)
> 
> tell application "Terminal" to do script 
> "/Applications/Pd-0.45-2.app/Contents/Resources/bin/pd"
> 
> * Export as Application and put wherever you want.. Now you can open 
> multiple instances of Pd with that .app, and patches won't be loaded 
> automatically.
> 
> Actually funny how complicated things get because of "user experience 
> optimizations".
> 
> Matthias
> 
> On 9/18/13 6:22 PM, Peter Venus wrote:
>>  Hello
>> 
>>  i assume, you are working on OSX:
>>  got to system preferences,
>>  click on the General Settings tab
>>  un-tick the box "restore windows when quitting and re-opening 
> apps"
>>  cheers,
>>  Peter
>> 
>>  Am 18.09.13 17:05, schrieb IOhannes m zmölnig:
>>>  On 09/18/13 16:01, Olivier Baudry wrote:
>>>>  Dear all
>>>> 
>>>>  Is there any function to prevent the opening of last patch when you
>>>>  start pd or pd-extended?
>>> 
>>>  how do you trigger that behaviour?
>>>  it doesn't do that here.
>>> 
>>>  fgmasdr
>>>  IOhannes
>>> 
>>> 
>>> 
>>>  ___
>>>  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
> 
> 
> ___
> 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] prevent opening of patches

2013-09-19 Thread Matthias Kronlachner

One more thing can be annoying on OSX:
If you open a second instance of Pd, the same patch as in the first will 
be opened.


One good thing to do is to create an AppleScript for opening Pd from the 
Terminal:


* Open AppleScript Editor and past the line: (of course adapt Pd-.app)

tell application "Terminal" to do script 
"/Applications/Pd-0.45-2.app/Contents/Resources/bin/pd"


* Export as Application and put wherever you want.. Now you can open 
multiple instances of Pd with that .app, and patches won't be loaded 
automatically.


Actually funny how complicated things get because of "user experience 
optimizations".


Matthias

On 9/18/13 6:22 PM, Peter Venus wrote:

Hello

i assume, you are working on OSX:
got to system preferences,
click on the General Settings tab
un-tick the box "restore windows when quitting and re-opening apps"
cheers,
Peter

Am 18.09.13 17:05, schrieb IOhannes m zmölnig:

On 09/18/13 16:01, Olivier Baudry wrote:

Dear all

Is there any function to prevent the opening of last patch when you
start pd or pd-extended?


how do you trigger that behaviour?
it doesn't do that here.

fgmasdr
IOhannes



___
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



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


Re: [PD] prevent opening of patches

2013-09-19 Thread Marco Donnarumma
> i assume, you are working on OSX:
> got to system preferences,
> click on the General Settings tab
> un-tick the box "restore windows when quitting and re-opening apps"
> cheers,
> Peter
>
>
Yes, it's a new "feature" of Lion OSX 10.7 and 10.8. It is extremely
annoying with Pd, because as soon as Pd try to reopen some already dead
sockets everything crashes without warning or log.

You can lock the pd folder, so to keep the configuration saving system
running for other software. Here's the how-to on puredata.org by Dan Wilcox:

http://puredata.info/docs/tutorials/HowToTurnOffResumeWindowsForPDOnMacOSX107Lion

I don't have Mac, but had to solve this issue all the time in my last
workshop this past months.

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


Re: [PD] prevent opening of patches

2013-09-18 Thread IOhannes m zmölnig
On 09/18/13 16:01, Olivier Baudry wrote:
> Dear all
> 
> Is there any function to prevent the opening of last patch when you
> start pd or pd-extended?

how do you trigger that behaviour?
it doesn't do that here.

fgmasdr
IOhannes



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


Re: [PD] prevent opening of patches

2013-09-18 Thread Peter Venus

Hello

i assume, you are working on OSX:
got to system preferences,
click on the General Settings tab
un-tick the box "restore windows when quitting and re-opening apps"
cheers,
Peter

Am 18.09.13 17:05, schrieb IOhannes m zmölnig:

On 09/18/13 16:01, Olivier Baudry wrote:

Dear all

Is there any function to prevent the opening of last patch when you
start pd or pd-extended?


how do you trigger that behaviour?
it doesn't do that here.

fgmasdr
IOhannes



___
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


[PD] prevent opening of patches

2013-09-18 Thread Olivier Baudry
Dear all

Is there any function to prevent the opening of last patch when you
start pd or pd-extended?


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