Hi,
I’ve been loading OM_ASX for years, and it actually works with OM6.16 and OM6.18, but I can’t open it with 6.17 (within which all my stuff currently is). I get the following error message:
Hi Jimmie,
this has nothing to do with OM versions but with conflicting libraries. OM_ASX is completely outdated and should not be used. It conflicts with omsupervp.
[the error message indicates that trans-melody which is redefined in OMSuperVp doesn’t have the same definition is comflicting once you load OM_ASX]
We are planning to merge OM_ASX in OMsupervp ASAP, taking the most significant and compliant functions with supervp since AudioSculpt is dead for the time being. So PLEASE don’t use OM_ASX for the time being.
Best
K
Hi Karim,
Thanks a lot for the quick response!
I’ll be careful with these old librairies, then, thank you.
Just to provide all the details, if it can be useful: apparently, it’s when my patch wants to load Pareto that this occurs. But the same error message also occurs when I try to launch OM_ASX alone – are these two related?
This being said, I notice the incompatibility with SuperVp in OM6.18, as you point out, where I can load either ASX or SuperVP, but not at the same time. Surprisingly, though, there’s no problem for having them both simultaneously in OM6.16…
Anyway, at least I can work it out for what I need for now.
Thanks again!
Jimmie
Hi Jimmie,
Usually the reason of this is conflicting code and happens with outdated libraries such as Pareto and OM_ASX. The issue with ASX and SuperVP, working on 6.16 and not 6.18 seems to me a little bit odd. There is no reason this conflict is happening with OM version changes, unless you are using old libraries version. PLease do check if they are the latest (ie. OM_ASX and OMSuperVP).
Best
K
Thanks Karim, here are the libraries versions I’m using, with all my OM versions:
Pareto 1.3
ASX 2.2
I think they’re the latest.
Thanks,
Jimmie
Thanx Jimmie,
I will look into that.
Best
K
