Forums > MaxMSP

Can I open the original window associated with a bpatcher under program control?

Mar 05 2012 | 7:38 pm

I’ve been overhauling my live rig environment and I have better separation of functionality as well as having everything in a single window.

In particular (see picture), my main window contains mixer, control surface, available VSTs and then, most importantly, a bpatcher that contains the current "song", a loaded patcher that contains
(A) The persistance of all sliders, dials, VST settings
(B) Routing of input devices (keyboards, control surfaces) to output devices (external synths, VSTs, etc)

Essentially, the "song" that is loaded contains a dictionary that knows how to persist any changes made in the main console and reload them when that "song" is loaded again. The song is loaded into the bpatcher through a script that replaces whatever was previously in the bpatche with the new song patcher.

In my older version, that "song" patcher was not embedded in the console window and just got loaded on the fly upon receipt of a program change. If I wanted to change the routings, I could just unlock that patcher, make the changes and save again.

So my question is, is there a scripting command that I can send to that bpatcher that will open the original view of the song patcher so that I can edit/save it and then reload? Right now, all I can apparently do is get a new view of the underlying song (but editing is not saved) or I can get a brand new patcher window with the contents. I’d like to be able to easily just open the real underlying patcher?


Mar 06 2012 | 12:46 am

You can do that easily by sending the command ‘front’ to a thispatcher object in the patch that is hosted by the bpatcher. I attach it to a receive from a button in my main interface….

Mar 06 2012 | 2:42 am

No, that does not work, that just opens a new view of the underlying patcher (with the patcher name enclosed in square brackets in the titlebar) and it does not seem to be possible to save changes to the underlying patcher.

Mar 06 2012 | 10:25 pm

to edit the new view select "disable read-only" in the menu. Then you can edit and save it in place.

Mar 06 2012 | 10:49 pm

I had tried that. But when I save it and then go take a look at the original version, it hasn’t changed. This is with 6.0.4

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

Forums > MaxMSP