2016/05/30 19:10:59
Blades
It's been a while since I've been out here and involved, but I'm trying to spend some time with my music stuff again and I came back to see if there were any changes to the Mackie Control support.  I've got a BCF2000 still and I just downloaded your dll and ini file, replaced the originals and I've attempted to use.
 
I am able to get the BCF control surface up and running, but I can't really make it do anything more than it was doing before.  I don't know what should be controllable in the compressor or FX sections.  I really just wanted the EQ mode 3 to work.  This is the one where the four left faders control the four bands gain levels where the four left knobs control the gain for each of those bands.  I believe the Q is also adjustable with the remaining knobs.  This does not work at all with the ProChannel EQ or the Sonitus EQ in the ProChannel position for me.
 
Any thoughts on the EQ, and tips on how I can see if the Comp and FX sections are doing anything different?
 
Thanks for your work on these things - you seem to be the only one who does anything in this regard :)
 
Still surprised that Cakewalk has not addressed these Mackie Shortcomings within their own product yet, even with all the updates that have happened in the Platinum series of things.  I'm still on X3 here, but considering plat - issues like this make me think twice about what things are being addressed.
2016/05/31 03:48:12
azslow3
There are 2 problems with original plug-in and PC EQ, and only one you could not fix yourself:
1) if PC EQ is not in the first position, MackieControl operates whatever module is the first position instead of EQ. My mod suppose to solve exactly this problem (the same for Compressor)
2) the mapping for parameters was changes since original Filter EQ. The mapping is in .INI and in my version EQ and compressor are mapped correctly (also there are 6 strips in EQ3 mode for 6 bands, including HP/LP)
 
So, put PC EQ in the first position. Switch to EQ mode 2 or 3.
a) if you turn encoders, do the control SOME EQ parameters? If not, your BCF setup is somehow incorrect ("normal" MCU has the display for indication what is going on, with BCF there is no way to see that). It can be that EQ button on BCF is not really EQ button for Mackie or other hardware mapping issues
b) in mode 3, does the mapping looks reasonable? If not, most probably you are not using my INI file
c) if you move the EQ from the first position, does BCF still control it in EQ mode? if not, you most probably are not using my mod
 
Plug-ins inside FX chains can not be controlled by design of FX chains.
 
FX bin plug-ins was always (and still are) controllable, including EQs and Compressors in the corresponding modes. But you should map your plug-ins yourself in the INI file, delivered stock mapping (also my INI) has no definitions for up to date plug-ins delivered with Sonar.
 
So in general MackieControl plug-in with my mod has no known shortcomings. There can be problems with installation and/or hardware setups (especially with "compatible" devices like BCF), but such problems are user setup specific and can be solved case by case.
2016/06/01 22:24:32
Blades
Thanks for your response.  I'll take another look when I get back in front of the DAW and get you some more detailed answers.
2016/06/05 22:07:16
Blades
Hey AzSlow - I got the files copied into my newly installed copy of Sonar Platinum.  I think the issue was that I had not properly created the mackiecontrol.ini file in the folder or something.  At any rate, it seems to be working now as I'd expect it.
 
There is one difference from the way it used to work in EQ mode 3 and that is that the first channel on the BCF controls something different and the band gain/freq for the four active bands are controlled by channels 2-5 on the BCF.  The compressor on the ProChannel also worked, though I'm not sure if I'll use it.
 
The BCF rides again! :)
 
Thanks for your efforts.  Is there anything I can test about this for you on my end since you don't have a BCF hardware device to test with?
2016/06/06 04:31:44
azslow3
Blades
Hey AzSlow - I got the files copied into my newly installed copy of Sonar Platinum.  I think the issue was that I had not properly created the mackiecontrol.ini file in the folder or something.  At any rate, it seems to be working now as I'd expect it.

Good to know it works for you now, thanks for the feedback.
 

There is one difference from the way it used to work in EQ mode 3 and that is that the first channel on the BCF controls something different and the band gain/freq for the four active bands are controlled by channels 2-5 on the BCF. 

Channel 1 is HP, channel 6 is LP.
 

Thanks for your efforts.  Is there anything I can test about this for you on my end since you don't have a BCF hardware device to test with?

Not at the moment. But please let me know in case something does not work / crashes / other strangeness.
2016/07/16 16:26:19
azslow3
Bumping the thread because of new change in this mod. Added "Disable handshake" option can help go throw "Connecting..." frustration, which many users observe with (in)compatible devices.
 
2016/07/17 15:56:20
Klaus
Thank you!
I used your MackieControl.dll mod with my new X-Touch Compact and it worked flawlessly.
 
Now, with "Disable handshake" checked, the status display of ACT Module no longer shows "Connecting..." when I don't use the X-Touch. Great!
 
2016/07/31 11:36:24
Astartes
I case i missed something/to be shure (and for newbies when it come to controller set-up and Sonar): Where to put the .ini File? I have copied it in the same Dir as the .dll and it seems to work.....but ACT does nothing, so i´m not shure if i´m right.
 
Thanks in advance
2016/07/31 14:46:35
azslow3
What you mean by "ACT does nothing"? .ini file is just affecting mapping for ProChannel EQ and ProChannel Compressors (standard). If the file is not correct, the mapping is wrong. The rest should work without it. But you was right, the file should be near MackieControl.dll.
 
Which device you try to use with this plug-in? If that is not Mackie original nor X-Touch, you will get "Connecting..." till you set "Disable handshake" in the options.
Which version of Sonar are you using? If that is not the latest, there is a change your Windows do not have MS Runtime 2015 (see the link in the first post).
2016/08/01 06:03:51
Astartes
azslow3
What you mean by "ACT does nothing"? .ini file is just affecting mapping for ProChannel EQ and ProChannel Compressors (standard). If the file is not correct, the mapping is wrong. The rest should work without it. But you was right, the file should be near MackieControl.dll.
 
Which device you try to use with this plug-in? If that is not Mackie original nor X-Touch, you will get "Connecting..." till you set "Disable handshake" in the options.
Which version of Sonar are you using? If that is not the latest, there is a change your Windows do not have MS Runtime 2015 (see the link in the first post).


I use Ableton Push together with Native Kontrol´s PTX General Script. The Script includes a Mackie Cotrol Emulation for the knobs of the Push. "Disablae Handshake" is checked in the prefs. Newest Platinum Release and The MS Runtime you metiones in your first Post.
 
(To avoid Confiosion: All Mode-Names that follow are Taken from the PTX General description/Manual for the Mackie Control integration)
Volume, Send, and Pan Modes work as they Should. "Plug-In" Mode, that should control ACT displays EQ Parameters, changes some EQ Parameters but does not change to the Highlighted Device (Absynth for Example), Act Learn don´t work as well.
 
"EQ" Mode displays and changes EQ Parameters. "Instr." Mode displays and Changes the Copmressor Parameters.
 
Hope it helps a bit (i´m at work atm). If you have anymore questions i can answer tham later when i´m at home and in front of my PC
© 2024 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account