I’ve updated LFX-1310 to the latest version, and all my projects loads with default preset now. Also: “can’t load plugin” error appears randomly on loading LFX-1310.
I downloaded version 1_1_5 and so far I have found no problems with it. I did not have the previous version, so I cannot check preset compatibility between the two versions.
Now I found a problem. When setting up two tracks with insert instances of 1310, and storing a different library preset on each track, upon deactivation/reactivation of monitoring (to reload the plugins) they both were set to the same preset value, but still showing different preset names. It appears that the plugin is using some global data that spills over between the various instances. Soon after this occurred I managed to make the plugin perform an illegal action. It does not seem to be a healthy release. Could you revert to a previous version?
So, it’s plugin problem. Thanks for your help! I think that I must share this topic with Luxonix developers. By the way, this release is not working for me now at all, even in new projects…
Unfortunately I’ve lost the previous release installer.
I’ve been in touch with Luxonix, and we have sorted out the problem. The latest LFX-1310 1.1.5 release introduced a change in the preset recall system, to fix a “total recall problem with VST-RTAS Adapter”. This unfortunately broke compatibility with Podium and possibly other hosts. I’ve now added an extra security call in Podiums preset recall procedure which fixes this. Hopefully this doesn’t break compatibility between Podium and other plugins. Will be released in version 1.55. Luxonix is also considering a revision of their preset recall system, which may appear in a future update.
Good news! Thanks for your help. The only question is: will 1.55 solve the problem alone, or both Podium and LFX-1310 need to be updated for fine work?
.
