Much disorientation with device and preset relocation

Learn about building and using Max for Live devices.
Post Reply
cassiel.com
Posts: 92
Joined: Mon Aug 14, 2006 6:12 pm
Location: London
Contact:

Much disorientation with device and preset relocation

Post by cassiel.com » Sun Oct 25, 2009 4:04 pm

I'm not sure this counts as a bug - I don't know if this behaviour is even documented, but I'm finding it counter-intuitive to say the least...
  • Create and save a simple Max for Live device: all fine, can be stored anywhere, name foo.amxd.
So far, so good.
  • Collect All and Save: device goes into Project (good).
So far, so good.
  • Save a preset: goes into Library.
This is different to conventional devices, which put their presets into the current project.
  • Hot swap a preset back into the device: the device itself migrates to the library.
For anyone keeping score, that's now three copies of the Max code. Why can't I keep the device in the project?
  • Create a preset, move it (in the browser) into the project, hot-swap it: again, we end up with the device in the library.
I don't follow why this is happening. I want to keep stuff local to projects, and not alter the library at all. Is there some rationale to this inexorable globalisation process?

cassiel.com
Posts: 92
Joined: Mon Aug 14, 2006 6:12 pm
Location: London
Contact:

Re: Much disorientation with device and preset relocation

Post by cassiel.com » Sun Oct 25, 2009 4:08 pm

A follow-up: after a *second* Collect All and Save (perhaps once I've created a preset), everything is well-behaved and the device stays in the project.

Post Reply