Fixed with MUX Vst 5.2.16: Error loading MUX VSTi module(s) with SONAR X2a

[MuTools]

Thanks for the projects. I could indeed repeat the problem. After research this looks like a bug in Sonar to me. Also the fact that this problem only happens with Sonar confirms this suspicion. I've emailed Cakewalk again with the details of my research.

[Hermu]

Thanks for the projects. I could indeed repeat the problem. After research this looks like a bug in Sonar to me. Also the fact that this problem only happens with Sonar confirms this suspicion. I've emailed Cakewalk again with the details of my research.

No response from Cakewalk over one month ?

if not, we have finaly to accept MUX is incompatible with Cakewalk ...

[MuTools]

Thanks for the projects. I could indeed repeat the problem. After research this looks like a bug in Sonar to me. Also the fact that this problem only happens with Sonar confirms this suspicion. I've emailed Cakewalk again with the details of my research.

No response from Cakewalk over one month?

I first received a quick response which was aimed to include a tech guy from their team. No news after that, unfortunately. I also emailed them a gentle follow up reminder 2 weeks ago, but still no news.

if not, we have finaly to accept MUX is incompatible with Cakewalk ...

Based on the research i did, i say it's the other way around. But i'm open for technical discussion. A pity they didn't continue the communication on this.

[MuTools]

News from Cakewalk: It has been confirmed to be on Sonar's side. The problem will be fixed in the next Sonar update. For even faster solution try to grab the latest Sonar X2 quick fix. I've also added an extra protection in the next MUX Vst interface to protect itself against improper reported samplerates by the host.

[Hermu]

News from Cakewalk: It has been confirmed to be on Sonar's side. The problem will be fixed in the next Sonar update. For even faster solution try to grab the latest Sonar X2 quick fix. I've also added an extra protection in the next MUX Vst interface to protect itself against improper reported samplerates by the host.

That's good news for SONAR X2 users

thanks for your MUX Vst support

[pgranier81]

I have the same problem. I hope the update of sonar will arrive soon...

[Hermu]

two more months ago ... nothing happens and it's not to expect that Cakewalk will fix it, because MUX is the only VSTi, which crashes with SONAR X2a!

i'm using several professional and freeware VSTi without any problems with SONAR X2a.

[sorohanro]

To me, that's a reason to switch to MuLab There will be no problems using MUX there.

[MuTools]

two more months ago ... nothing happens and it's not to expect that Cakewalk will fix it, because MUX is the only VSTi, which crashes with SONAR X2a! i'm using several professional and freeware VSTi without any problems with SONAR X2a.

I have the impression you're blaming MuTools for something which is on Cakewalk's side. True impression?

Besides the above thought, note that:

1) Cakewalk themselves were able to reproduce the issue with other plugs too.
You don't have to doubt the fact that it's a on their side.

2) Even when it's something on Cakewalk's side, i've added an extra protection in the VST interface to protect MUX Vst from this specific 'illegal case' problem. As you might know, MuLab and MUX evolve in parallel. Now MuLab 5.2 is in test phase and the holiday break came in between the M5.2 R&D phase. I'm currently working on finalizing M5.2.9 which will feature some extra improvements upon M5.2.8. New test version can be expected soon (1 or 2 weeks i think). Then when M5.2 is released, MUX Vst 5.2 will be released too.

[Hermu]

two more months ago ... nothing happens and it's not to expect that Cakewalk will fix it, because MUX is the only VSTi, which crashes with SONAR X2a! i'm using several professional and freeware VSTi without any problems with SONAR X2a.

I have the impression you're blaming MuTools for something which is on Cakewalk's side. True impression?

it's not blaming MuTools, but i have reported this bug already last year for MUX v1.
SONAR X2a with MUX v5 with this crashes is waste.
i like to make music and not to keep struggling with crashes.

in the meantime i think, that Cakewalk is not realy interrested to fix this bug, because they have some other known bugs from previous versions also not fixed which was reported, e.g. more than one VST midi instance crashes SONAR, unsolved since as i had used SONAR 8.

why should they realy fix it?

i have also posted some reproduceable bugs to Cakewalk, but without reply ...

SONAR X2 is a sensitive DAW and must be handled with care

[EvilDragon]

SONAR X2 is an unstable crap DAW and must be handled with care

FTFY.

[liquidsound]

SONAR X2 is an unstable crap DAW and must be handled with care

FTFY.

True.
I couldn't deal with the demo several times.

[Hermu]

two more months ago ... nothing happens and it's not to expect that Cakewalk will fix it, because MUX is the only VSTi, which crashes with SONAR X2a! i'm using several professional and freeware VSTi without any problems with SONAR X2a.

I have the impression you're blaming MuTools for something which is on Cakewalk's side. True impression?

Besides the above thought, note that:

1) Cakewalk themselves were able to reproduce the issue with other plugs too.
You don't have to doubt the fact that it's a on their side.

2) Even when it's something on Cakewalk's side, i've added an extra protection in the VST interface to protect MUX Vst from this specific 'illegal case' problem. As you might know, MuLab and MUX evolve in parallel. Now MuLab 5.2 is in test phase and the holiday break came in between the M5.2 R&D phase. I'm currently working on finalizing M5.2.9 which will feature some extra improvements upon M5.2.8. New test version can be expected soon (1 or 2 weeks i think). Then when M5.2 is released, MUX Vst 5.2 will be released too.

The new MUX Vst 5.2.15 release candidate works now stable with SONAR X2a
http://www.kvraudio.com/forum/viewtopic.php?t=391555

thanks for this great job, jo!