How to force the use of the correct abstraction after unfreezing a device?

Rivanni's icon

I have a Max for Live device that uses an abstraction. The Max device is frozen.

I adjusted the abstraction to add some improvements.

When I open and unfreeze the Max device, it still uses the old abstraction, which now lives in the Max for Live Devices folder. The new version of the abstraction is located inside the discarded subfolder. I would expect the opposite. Why discard another/newer version of a patcher that was not even part of the device?

Replacing the old patcher file with the new one breaks existing objects. Creating new ones works, of course. Even if replacing files would work, it would kind of defeat the purpose of abstractions as reusable objects. I shouldn't deal with file management.

What is the best way to have devices always use the abstractions from my Library folder rather than unfrozen ones? 

mattyo's icon

This whole issue with m4l devices, abstractions, and paths is a nightmare, as can be attested from posts I've made to the forum in the past, including the problem you're having. Mattijs Kneppers has some useful tips in this thread I found very helpful (one of which was to use as few abstractions as possible!):

He's also got some good production guidelines here:

But I'm with you, the whole thing is very annoying, and hard to make sense of.

Good luck,

\M

Rivanni's icon

It's good to see that it's truly a nightmare and I wasn't overlooking anything.

The only relevant takeaway from the first link is to never freeze your device unless you're distributing it, and then never unfreeze it.

I don't read anything about using as few abstractions as possible. Good thing too, because such a recommendation doesn't make sense at all.

I'm familiar with the guidelines. Useful info, but they don't address this issue. It could be more explicit about not freezing your device until distribution, and about freezing a copy.

It's hard to believe that this all hasn't been improved. At least the process of automatically making a copy when freezing could have been implemented as a band-aid. There will definitely be a moment when I freeze a device instead of its copy, especially since that's what I'm used to.