[?] dac~ and Buffer shuffler.

[Homebelly]

I've been breaking stuff open and having a look inside.
On my travels i have noticed that buffer shuffler has a dac~ object attached to the plugout~ object.
Why would that be necessary?
From what little i understand so far i get the impression that the dac~ object is for communication with the out side world, like if buffer shuffler were a stand alone device, not a plug in.

[stringtapper]

Good question.

[pid]

nothing of interest there. it was just left in after debugging etc i expect. someone forgot to take it out? you could delete it no probs, or leave it in. only would have any effect if open in full Max/MSP.

[Homebelly]

This kinda sorta peaks my interest in another query as i wondered if this might have been the case.

When i open max from live using one of the blank live devices a grey patcher opens and i can work on stuff and do things. I then i have the option of saving them and they appear in lives browser.
Now, after i close live Max stays open and I have noticed that i can start a new patch from Max using the white max patcher.

Now, If i try and open Max directly from my applications folder i get the expected nag screen asking if i want to open max in demo mode.

So, is this a bug, should max stay open after live has quite, and should i be able to work in it as though it where Max - as apposed to Max for Live - ?

Also, if i open max from live, then quit live but keep Max open am i able to save what ever i am doing as an .amxd file?
Do i gain any kind of advantage if i can?

[pid]

i am long time full max user, so admitedly not entirely sure of the details here in your case. however, having read around the forums a bit, it seems that yes, you CAN create .maxpat files to disk. i read one post recently suggestiong you could create a .maxpat for dealing with sysex and then run it in maxruntime behind live and m4l. all the editing crippling of certain features would still remain though, and you must always open max from within live. it makes sense as you have to be able to make your own .maxpat abtractions for using things like 'poly~' and 'pfft~' etc etc, not to mention all your own abstractions you may want to make. however, worth reading up on this issue to get more official line. there is a whole section in the max m4l documentation on it. hope that helps.

[emmanuel_2]

nothing of interest there. it was just left in after debugging etc i expect. someone forgot to take it out? you could delete it no probs, or leave it in. only would have any effect if open in full Max/MSP.

Indeed, it was there for debugging purposes from the early development age (prototype in Max only). It's not really a problem to leave it there since it does nothing.