Mackie MCU pro causes Sonar Platinum to crash. SOLVED, Thanks to Azslow3

I have same problem but with a X-Touch. This is the error I get. 
 
Error - unhandled exception
A Fatal Error has Occurred.
Module: C:\windows\system32\vcruntime140.dll
Exception Code: c0000005
 
Tried already to fix by reinstalling VC libraries without luck. 
 
Any idea is welcomed. 

There are several reports that Sonar crash when Mackie units control plug-ins. And in all such threads I write the same: till someone is more precise and publish reproducible procedure for such crashes, it is unlikely that something is fixed.
 
In my short tests with emulator it does not crash, controls EQ/Compressor as expected (on all strips). But I do not have any real device and do not use the emulator for music, I just try to help other. Since no one from device owners has helped me to help them so far, I have no reason to dig into that.
 
Carefully configuring MackieControl to support plug-ins someone use every day takes at least hours, with 20-30 plug-ins it can take weeks (for every user separately!). That can pay back only in case the result is intensively used. Helping me to understand the problem will probably take a half an hour for ONE user in the whole community. Years (!) are passing, every 2-3 months a new thread is created with the same text. And so far no volunteers found.
 
You can imagine which priority the problem can have for CW after observing such "huge" (no) interest.

klaw35ekac
I don't fully understand what your saying but if I can help you just say what you need to see as further info

MackieControl is an Open Source plug-in on GitHub. So virtually anyone can "fix" something in it. In practice the number of such people is limited, but I am one of them.
 
To fix the problem I have to understand where it is.
1. The best will be reproducible bug report. I mean if you can create one track project with one FX (better included into Platinum, since I do not have other), with which MCU stable crash Sonar once you start to control some particular parameter, and I will be able to reproduce that behavior. In this case I am almost sure I will find what to fix or make a workaround (inside MackieControl code).
 
2. If (1) is not possible, f.e. it crash unpredictably, once in a while. I need everything you can say when that usually happens: your Sonar version, your Windows version, which version of MCU plug-in you are using, have you tried the one from CW GitHub, have you tried my mod of it (while the code is almost the same, they are compiled with different MS run-times), with which FXes that happens more, for ProChannel, in which order you have modules in it, is there any dependency from the project size, does that happens when the transport is stopped or during playback/recording.

Hello Azlow,
 
I am the brother of Toon, who knows a little bit more about the technical side, so I'll join in at some points of the conversation.
 
We get an fault report every time sonar crashes, including a dmp file
 
It 's always the same message all the time it crashes.
 
the error states the following:
           A fatal error has occurred.
 
Module: c:\windows\system32\vcruntime140/dll
 
A crashdump file has been created here:
C:\.......\minidumps\.....dmp
 
Exception code: c0000005
Addres: 00007FF94CD9C887:0000000054F7D000:0000000000000045
 
Would you like to have the dmp file, to examine that? And I understand you would also want to use the project file to reproduce the error, is that correct?
and also, in what way can we send the dmp file, because the is very large as you would expect.
 
the computer runs Windows 10 x64 and the latest version of Platinum.

It looks like you are using a 32 bit plug-in based on that .dll path.  What 32 bit plugs do you have in your project?

I stand corrected.

Azslow3, thanks for the info. We tried some stuff using all three versions of mackiecontrol.dll.
so the original, the github and your version.
 
We created a project with 1 drum track, and in that project we tried changing some settings.
And with all three dll's, sonar faulted when we selected the compressor in the prochannel for that track.
even without enabling the compressor, just waiting for a few seconds had the application fault.
we are using Addictive drums for the track.
 
hopefully this helps you a little.
 

My mod (dyneq) supposes to fix the problem with the compressor. At least I was letting Mackie emulator show Compressor parameters on one AD2 track project for a half an hour without the issue.
 
Please confirm if you also no longer get Sonar crash when using ProChannel Compressor.
 
The link to my files is still the same, but since the original thread here is "locked", I have moved the post to my forum:
http://www.azslow.com/index.php/topic,341.0.html
 
Do not forget to download the .INI file referenced there. Without that file the mapping for EQ and Compressor is wrong (stock mapping is for old EQ/Comp filters).

it seems to work! way to go AZSLOW! at least for the last 10 minutes it is not crashing, i keep my fingers crossed :)
I hope everyone else is getting the same result so far. 
 
Nick

Thanks very much Azslow3,
Sonar doesn't crash anymore when tweaking the compressor with the Mackie control it allready worked fine with the EQ module and when I put the EQ on top in the pro channel the EQ and compressor work also BUT...............now rotary knob 5 on both the master mcu and the extender causes the master fader to to go down to INF even when the mackie is in track mode.
 
Toon.

I can try to reproduce knob5 mystery, but a bit more precise description can help: what you expect this knob in this mode does? I mean do you have more then 4 strips, so Fader 5 is controlling the volume fine and you expect controlling the Pan of track 5 with this knob and get Master volume -INF?
 
YES exactly that! Toon.
 
Only fader moves down or corresponding parameter in Sonar is also changed ?
 
Master fader on the mackie moves down and the master fader in Sonar goes down to too and also the volume.
Ican get the fader on the mackie manually though but as soon as I turn the 5 knob it goes down again. Panning on track 5 works also.  
 

SuperG
I've noticed an issue with the Mackie Control surface where the  READ ON/OFF button (I'm using an X-Touch with Sonar labels) seems to get out of step with the [R!] button in Mix control bar module.

[R!] button in Sonar is "Bypass read automation", corresponding button in MackieControl calls "Toggle bypass read automation". But there is no known way to ask Sonar about current state of it.
Note that "bypass all" is not the same as "disable" read automation, they are like "effect enable" and "bypass all effects".
 
If you really want to help, you can participate in identifying bugs as ongoing in this thread. Help me to reproduce problems reported by other (as for programmer, it should be simpler for you to understand what and why I am asking...). As with [R!] indication, there are many limits/bugs in Sonar. Many of them I already know. You are I can not solve that inside plug-ins.

 
 

I have tried, but I could not reproduce the effect.
 
Probably stupid question, but... Have you ever used "Remove control..."? Right click on the fader which is jumping to 0, and select "Disable remote control", if it is enabled (so you have used it). I am asking since Knobs are sending normal CC messages and the value when you turn it right is 1-3 (almost 0 since the max is 127).
Also check the fader is not "grouped" with something.
 
Since you have not mentioned your audio interface, if it is "smart" one (RME, X32, etc.) please check that you are not routing MCU to it (at least not when controlling Sonar).
 
Otherwise lets narrow when that happens: how many tracks your projects have (where that happens and where that does not happened)? MIDI, Audio, Instrument (Especially the track 5)? When that happens in the Track mode, do you see "TR" or "TR." (with dot) on small display? What strip 4 display is showing?
 
What is jumping, your audio interface output or Master bus (that is the setting in the plug-in preferences)? Try to change it, so set to "Master" if it was "Bus" and set to "Bus" if it was Master. Is jumping parameter different then?
 
Are you using any external MIDI loopbacks/translators?

I am glad it works now
 
Please update the thread title with [Solved] so other users notice it has the happy end (unlike similar old threads).
Thank you for not giving up in the middle.
 
Merry Christmas Toon!