cebec

It's extremely frustrating that Max/MSP cannot remember previously used filepaths when navigating to open patches, sound files, etc. Wouldn't it help if we could set some defaults, or have a dedicated browser window in Max, a la Reaktor, for navigating?

Also, I think it'd be nice if Max/MSP patchers, for e.g., could float freely outside of the Max app. window rather than being confined to it.

maxmsp-should-remember-file-paths

> Also, I think it'd be nice if Max/MSP patchers, for e.g., could 

> float freely outside of the Max app. window rather than being 

You can fix this by switching to the Mac version. (Sorry I couldn't 

On Feb 13, 2006, at 1:12 PM, matt wrote:
> Also, I think it'd be nice if Max/MSP patchers, for e.g., could  
> float freely outside of the Max app. window rather than being  
> confined to it.

You can fix this by switching to the Mac version.  (Sorry I couldn't  
resist.)  :)

-----
Nathan Wolek
nw@nathanwolek.com
http://www.nathanwolek.com


Why don't you just build a browser window using jit.cellblock and folder, you'd think that this wasn't MAX or something. That's what makes it better than Reaktor, right? Restoring data shouldn't be too hard if you figure out some neato spiffy way to store previous states based on whatever file is active or what not.

I've done this, but its defintely not in a form that I'd want to put up on the maxlist ;)

and lets not forget the "thispatcher" window messages,mmkay... float is in there, so is savewindow..

Quote: cebec wrote on Mon, 13 February 2006 11:12

----------------------------------------------------

or have a dedicated browser window in Max, a la Reaktor, for navigating?

the reaktor browser sucks hard, max is much more flexible.

Quote: cebec wrote on Mon, 13 February 2006 11:12
----------------------------------------------------
 or have a dedicated browser window in Max, a la Reaktor, for navigating?
----------------------------------------------------

the reaktor browser sucks hard, max is much more flexible.


ok, i appreciate the lively comments, but i don't even know where to start re: building my own browser and it seemed like this is something that could be included in a very basic form so that we don't have to build it from scratch. at least something integrated into max, itself, to designate specific directories for particular file-types... ya ya, i know, reaktor sux0rs, which is why i sold it and have dedicated my time to max, but i think this may border on reinventing the wheel.

ok, i appreciate the lively comments, but i don't even know where to start re: building my own browser and it seemed like this is something that could be included in a very basic form so that we don't have to build it from scratch.  at least something integrated into max, itself, to designate specific directories for particular file-types... ya ya, i know, reaktor sux0rs, which is why i sold it and have dedicated my time to max, but i think this may border on reinventing the wheel.


I just have one folder with sub folders - which are patches, 

sub-patches, useful stuff, even sound files for "cycle~, parts of 

i have aliases of this folder in many places - on the desktop, in the dock etc

of course items in this folder can be aliases themselves

much more easy than the reaktor's browser - and takes just a few 

the folder itself is in the max's search path

I just have one folder with sub folders - which are patches, 
sub-patches, useful stuff, even sound files for "cycle~, parts of 
patches or other things etc etc etc

i have aliases of this folder in many places - on the desktop, in the dock etc
of course items in this folder can be aliases themselves

much more easy than the reaktor's browser - and takes just a few 
minutes to make

-- 
  Kasper T. Toeplitz
noise, composition, bass, computer
http://www.sleazeArt.com


thanks, kasper... that's what i'll do, then...

Don't forget the pattr & preset objects for saving & restoring patcher states. Takes a little extra effort to add them to a patch but it pays off.

Max/MSP should remember file paths