Question about the calf/veal transition

[trebmuh]

If I understood it right, the 1.2 version will have an internal forked version of the CALF-ladspa re-named VEAL which will avoid the calf.so clash which has been put in lights with the debian stretch package of LMMS. I think it's a great move and will help a lot of users.

Imagine a user which has made a LMMS project using some CALF-ladspa with the current version of LMMS he runs and then, saved this LMMS project. Then, he will probably update sometimes to a future version of LMMS which will include this VEAL-ladspa plugins instead of the former CALF-ladspa ones.

My question is: what will then happen when he will try to open & play his previous project? Will the ancient CALF-ladspa settings in this project will automatically update to the VEAL ones or is the user will be expected to replace all the CALF-ladspa plugins & parameters in his project to the VEAL ones in any way?

Please, note that I'm not a daily user of LMMS (using it every now and then) so it might be a wrongly anxious question. If someone could shed some light on it, it'll really be appreciated.

[tresf]

If I understood it right, the 1.2 version will have an internal forked version of the CALF-ladspa re-named VEAL which will avoid the calf.so clash which has been put in lights with the debian stretch package of LMMS. I think it's a great move and will help a lot of users.

Yes, but 1.3.0, NOT 1.2.0.

My question is: what will then happen when he will try to open & play his previous project? Will the ancient CALF-ladspa settings in this project will automatically update to the VEAL ones or is the user will be expected to replace all the CALF-ladspa plugins & parameters in his project to the VEAL ones in any way?

Yes, the upgrade has already been written, but lives on the master (future home of 1.3.0) branch.

[trebmuh]

OK thanks for the quick answer @tresf . I'm closing this issue now.