Masa

Let's say you have your own M4L instrument device. You want to use the device with different settings in track A and track B.

You have configured the value of the instance of the device in track A, and move onto track B. While setting the device in track B, you feel like modifying something minor within the Max patch of the device, so you click the Edit Button in track B, edited the patch, and saved. Then the setting of track A is overwritten by the setting of track B...!

Let's say you have your own M4L instrument device. You want to use the device with different settings in track A and track B.
You have configured the value of the instance of the device in track A, and move onto track B. While setting the device in track B, you feel like modifying something minor within the Max patch of the device, so you click the Edit Button in track B, edited the patch, and saved. Then the setting of track A is overwritten by the setting of track B...!
How do you usually avoid this to happen?


value-of-m4l-device-is-overwritten-by-saving-the-related-max-patch-elsewhere

Save should give you the option to save changes for the edited device only, if it's something that needs to be saved for each patch then there is no workaround...

- I have several instances of the same device with different values saved in an Ableton Project file

- I want to update something about the device for every instance, but with keeping the different values

Hi S4RACEN, thanks for your reply.
Yes, it's about the situation where:
- I have several instances of the same device with different values saved in an Ableton Project file
- I want to update something about the device for every instance, but with keeping the different values


It would be great if this will be improved in a future update.

Sure, thanks for your confirmation.
It would be great if this will be improved in a future update.


Value of M4L device is overwritten by saving the related Max patch elsewhere