Forums > MaxMSP

Stop Loadbang upon Launch – Feature Request?

July 25, 2007 | 10:04 pm

Hi,
I’ve recently connected a loadbang to an object that causes my patch to crash upon load. Is there a way to stop th loadbang from triggering upon launch so that I may rectify the problem and continue with my patch and not have to revert to an older version of it? If not this might be a nice fail safe addition in a future release.

Cheers

Andy



Dan
July 25, 2007 | 10:10 pm

Hold Cmd + Shift (on Mac) right after opening to stop loadbangs or
open the patch as text and edit it manually.

d


July 25, 2007 | 10:13 pm

Nice one cheers. Have already solved my issue by editing the text but this is a very clunky way of doing it which often leads to connections completely f**cking up. The command and shift way sounds much better.

Cheers for that

Andy


July 25, 2007 | 10:14 pm

On 26 juil. 07, at 00:04, Andy Brennan wrote:

> Hi,
> I’ve recently connected a loadbang to an object that causes my
> patch to crash upon load. Is there a way to stop th loadbang from
> triggering upon launch so that I may rectify the problem and
> continue with my patch and not have to revert to an older version
> of it? If not this might be a nice fail safe addition in a future
> release.

Press command+shift (ctrl+shift on windows) when you open the patch.
Luckily, it has been there for years ;-)

ej


July 25, 2007 | 10:16 pm

Open it as text, find the loadbang line and remove it. It’s kind of
hacky but should work.

wes

On 7/26/07, Andy Brennan wrote:
>
> Hi,
> I’ve recently connected a loadbang to an object that causes my patch to crash upon load. Is there a way to stop th loadbang from triggering upon launch so that I may rectify the problem and continue with my patch and not have to revert to an older version of it? If not this might be a nice fail safe addition in a future release.
>
> Cheers
>
> Andy
>


July 25, 2007 | 10:23 pm

Open it as text, edit out the offending object, resave.

On Jul 25, 2007, at 4:04 PM, Andy Brennan wrote:

>
> Hi,
> I’ve recently connected a loadbang to an object that causes my
> patch to crash upon load. Is there a way to stop th loadbang from
> triggering upon launch so that I may rectify the problem and
> continue with my patch and not have to revert to an older version
> of it? If not this might be a nice fail safe addition in a future
> release.
>
> Cheers
>
> Andy

—-
Steven M. Miller
Professor, Contemporary Music Program
College of Santa Fe

Home < http://pubweb.csf.edu/~smill>
SFIFEM <
http://sfifem.csf.edu>
Atrium Sound Space <
http://atrium.csf.edu>
OVOS <
http://pubweb.csf.edu/~smill/ovos.html>
CMP <
http://www.csf.edu/csf/academics/cmp/index.html>


July 27, 2007 | 11:44 am

Andy Brennan schrieb:
> Nice one cheers. Have already solved my issue by editing the text but
> this is a very clunky way of doing it which often leads to
> connections completely f**cking up. The command and shift way sounds
> much better.

If you don’t want "connections completely f**cking up" you must not just
delete the line with the offending object, you should rename it to
something non existing: "loadbang" to "loadcrang" for example. Then all
connections will remain, and the loadcrang object will show up as bogus
object (as it cannot be found)…
As only loadbangs are not fireing with cmd-shift, but all patcherargs
and loadmesses still fire, this technique is still necessary sometimes…

I’d like to be able to stop ALL load activities with cmd-shift, I
requested it long ago, maybe Max 5 will do it…

Stefan


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


July 27, 2007 | 12:27 pm

Quote: Stefan Tiedje wrote on Fri, 27 July 2007 05:44
—————————————————-
> something non existing: "loadbang" to "loadcrang" for example. Then all
> connections will remain, and the loadcrang object will show up as bogus
> object (as it cannot be found)…

Good call. Don’t know why I didn’t think of that myself.

Cheers

Andy


Viewing 8 posts - 1 through 8 (of 8 total)