On one system I have kept the 32-bit plug-ins (from v15) for project compatibility. I now wish to update the 64-bit plug-ins using MPluginManager. But the Manager reports that it will delete the v15 plug-ins too.
How can I proceed?
Keeping v15 32-bit plugins and the MPluginManager
-
- KVRAF
- 10366 posts since 2 Sep, 2003 from Surrey, UK
-
martin-meldaproduction martin-meldaproduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=583716 - KVRist
- 273 posts since 6 Oct, 2022
The final MeldaProduction release with 32-bit plugin support was v15. Beginning with v16, only 64-bit builds are provided. The transition was necessary due to several factors:
- Address space limitations inherent to 32-bit processes.
- The MeldaProduction plugin kernel now depends on modern OS and compiler features available exclusively in 64-bit environments.
- Integration of external modules that are distributed in 64-bit form only.
and others.
Because of these constraints, mixed 32-bit and 64-bit MeldaProduction plugins cannot coexist within the same project on a single host system. The only viable solution is to isolate environments—for example, by running a virtual host or separate DAW instance - with one installation locked to v15 for legacy 32-bit projects, and another installation using the current release (v17).
- Address space limitations inherent to 32-bit processes.
- The MeldaProduction plugin kernel now depends on modern OS and compiler features available exclusively in 64-bit environments.
- Integration of external modules that are distributed in 64-bit form only.
and others.
Because of these constraints, mixed 32-bit and 64-bit MeldaProduction plugins cannot coexist within the same project on a single host system. The only viable solution is to isolate environments—for example, by running a virtual host or separate DAW instance - with one installation locked to v15 for legacy 32-bit projects, and another installation using the current release (v17).
Martin
MeldaProduction
MeldaProduction
-
- KVRAF
- Topic Starter
- 10366 posts since 2 Sep, 2003 from Surrey, UK
Sorry if I was not clear.
I have some projects that were created in a 32-bit DAW and others that use a different 64-bit DAW. When v16 was current, I had v15 32-bit plug-ins and v16 plug-ins both installed and working fine in the respective projects.
Porting those projects from the 32-bit DAW to the other 64-bit DAW would be quite a task. So I would really like both the v15 32-bit and v17 64-bit plug-ins to be available. This seems to be a constraint introduced with MPluginManager (I am not expecting MPluginManager to handle v15 at all).
I have some projects that were created in a 32-bit DAW and others that use a different 64-bit DAW. When v16 was current, I had v15 32-bit plug-ins and v16 plug-ins both installed and working fine in the respective projects.
Porting those projects from the 32-bit DAW to the other 64-bit DAW would be quite a task. So I would really like both the v15 32-bit and v17 64-bit plug-ins to be available. This seems to be a constraint introduced with MPluginManager (I am not expecting MPluginManager to handle v15 at all).
-
- KVRian
- 851 posts since 24 Mar, 2021
My suggestion is to create a virtual machine with your old software, and use newer one in your bare metal pc.
That way you have a dedicated virtual machine with your old daw and plugins, able to load whatever older project, and the newer one for new stuff
That way you have a dedicated virtual machine with your old daw and plugins, able to load whatever older project, and the newer one for new stuff
-
- KVRAF
- Topic Starter
- 10366 posts since 2 Sep, 2003 from Surrey, UK
Thank you for the suggestion. But it seems quite a way to go to get round the constraint in MPluginManager. After all, it is fine with v16 64-bit plug-ins installed.