Helpful ReplyMackie Control protocol source now available [scroll to p3]

Page: < 12345 Showing page 5 of 5
Author
jwp9350
Max Output Level: -90 dBFS
  • Total Posts : 8
  • Joined: 2010/11/19 07:35:49
  • Location: Amsterdam
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/04/21 20:16:58 (permalink)
Hey Alexey,
I own a MCU (not Pro) and use Platinum. I downloaded your latest driver and installed it.
The Macky is working like it did under the Sonar MCU-drivers. Selecting, Faders, Panning, Soloing, Muting etc.
Only the abbreviation in the scribble-strips is a littlebit different, no problem!
What do you want me to test in 5 minutes?
I would like to control the Equalizer (and more) in the ProChannel but didn't trie that yet.
Jan Willem

Jan Willem
=================
Sonar Platinum D 64bits
Windows Professional 8.1 x64
HP Elitebook i5  8gb
MOTU 896 Firewire
Mackie Control

smallstonefan
Max Output Level: -48 dBFS
  • Total Posts : 2724
  • Joined: 2003/11/20 11:41:35
  • Location: Papillion, Nebraska
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/04/21 21:09:45 (permalink)
Where can we find the latest driver? My MCU is still flakey in Sonar and locks up at times. I bought a brand new MCU and it has the same issues as my old one - very frustrating. I really wish Cakewalk would address this.
azslow3
Max Output Level: -42.5 dBFS
  • Total Posts : 3297
  • Joined: 2012/06/22 19:27:51
  • Location: Germany
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/04/22 03:57:32 (permalink)
Dear Jan,
jwp9350
Hey Alexey,
I own a MCU (not Pro) and use Platinum. I downloaded your latest driver and installed it.
The Macky is working like it did under the Sonar MCU-drivers. Selecting, Faders, Panning, Soloing, Muting etc.

Thank you! That was my question.

Only the abbreviation in the scribble-strips is a littlebit different, no problem!

I use my own abbreviation algorithm.

What do you want me to test in 5 minutes?

You have already done that. And you are the only one so far

I would like to control the Equalizer (and more) in the ProChannel but didn't trie that yet.

EQ/EQ FG modes have "primitive" implementation. But they should work.
"Dyn" (former compressor mode) should switch device into ACT mode. You can control any plug-in then and configure what each control does (see ACT Learning in the CW documentation, on my site there is more with workarounds for ACT assignment bugs).
 
If something does not work or you just want it different way, please let me know. The preset is too complicated at the moment to propose you change it yourself, I have plans to significantly rework it toward simplification. But there was no interest from community and I do not have the device, so the priority was pretty low.

Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro
GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB
RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc.
www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
sylent
Max Output Level: -84 dBFS
  • Total Posts : 309
  • Joined: 2013/04/01 16:37:54
  • Location: Dallas, Texas
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/04/22 04:37:59 (permalink)
I'll eyeball it also, but it may be several days.
I have a remote prod gig and everythings packed and stacked atm.
327

http://twisteddrive.com
Windows 7 Pro 64, i5-3570k 3.40GHz, 32Gb ram, NVIDIA Quatro 4000, 2x SSD, 2x 2Tb Dedicated storage and misc high-capacity HHD Storage, Sonar Platinum, Adobe CS6 Master Suite, Misc 3D, video, audio software. Focusrite Liquid Saffire 56/octapre, Mackie MCU, other MIDI/control, rack effects, and more.
smallstonefan
Max Output Level: -48 dBFS
  • Total Posts : 2724
  • Joined: 2003/11/20 11:41:35
  • Location: Papillion, Nebraska
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/04/22 07:33:02 (permalink)
I'm not sure how I missed this, but I just installed it and initial test confirms that it is working - I need to dig into it deeper and I already have some questions, but I am up and running.
 
Having solid MCU Pro functionality is VERY important to me, so thank you!
azslow3
Max Output Level: -42.5 dBFS
  • Total Posts : 3297
  • Joined: 2012/06/22 19:27:51
  • Location: Germany
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/04/22 13:33:08 (permalink)
smallstonefan
I'm not sure how I missed this, but I just installed it and initial test confirms that it is working - I need to dig into it deeper and I already have some questions, but I am up and running.

Second reply within one day! I am happy
 

Having solid MCU Pro functionality is VERY important to me, so thank you!

Original plug-in and my MCU preset are complicated. In case you use just a subset of possible modes/operations but want them rock solid, we can make stripped version of preset.


Let say you want control 6 tracks and 2 buses volume/pan unconditionally and you can survive without display. I guess that will work stable.
 
Most instability comes from Sonar itself. It "does not like" some operations at some moments... The last spotted problem: if you arm several automations (but not all) simultaneously during complicated project playback, Sonar crashes. At the same time it is possible to arm "all" automations without problem. So, every single operation should be tested on big project and if it crash sonar it should be reworked (since most probably we can wait another 10 years for fix from CW).

Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro
GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB
RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc.
www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
adam.cherrill
Max Output Level: -90 dBFS
  • Total Posts : 5
  • Joined: 2015/04/22 15:05:51
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/04/22 18:49:51 (permalink)
Hello all,
 
I am new to this forum and am trying to solve what should be a straightforward MIDI control surface installation issue.
 
I'm not looking to do fancy ACT plug-in control; i just want a continuous bank of 16 faders...
 
I have connected my MCU Pro and eXtender using the USB connection to the MCU Pro - all per the Mackie instructions.

Unfortunately the two surfaces are pointing to the same tracks, essentially duplicating each other.
 
The MCU is connected to MIDI port MCU Pro USB v3.1
The XT is connected to MIDI port MIDIIN2 (MCU Pro USB v3.1)
 
It appears that the same MIDI instructions are being sent to both units.
 
Am i missing something fundamental in the setup?
 
Any advice would be most welcome.

Thanks
Adam
 
I'm using SONAR Platinum on a WIN 7 (64) machine with UAD Apollo as my audio interface.
sylent
Max Output Level: -84 dBFS
  • Total Posts : 309
  • Joined: 2013/04/01 16:37:54
  • Location: Dallas, Texas
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/04/22 19:25:38 (permalink)
adam.cherrill
Hello all,
 
I am new to this forum and am trying to solve what should be a straightforward MIDI control surface installation issue.
 
I'm not looking to do fancy ACT plug-in control; i just want a continuous bank of 16 faders...
 
I have connected my MCU Pro and eXtender using the USB connection to the MCU Pro - all per the Mackie instructions.

Unfortunately the two surfaces are pointing to the same tracks, essentially duplicating each other.

The MCU is connected to MIDI port MCU Pro USB v3.1
The XT is connected to MIDI port MIDIIN2 (MCU Pro USB v3.1)

It appears that the same MIDI instructions are being sent to both units.

Am i missing something fundamental in the setup?

Any advice would be most welcome.

Thanks
Adam
 
I'm using SONAR Platinum on a WIN 7 (64) machine with UAD Apollo as my audio interface.


I'm working blind and from memory atm, but once they are on and recognized as you say, push the first knob on the main unit and rotate it to change the track settings on the controller.
You can see the choice in the scribble strip to have the extender be numbered before or after the main unit as well.
 
Sorry I can't be more exact but things are packed right now, and my memory is far from pure lol.
 
354

http://twisteddrive.com
Windows 7 Pro 64, i5-3570k 3.40GHz, 32Gb ram, NVIDIA Quatro 4000, 2x SSD, 2x 2Tb Dedicated storage and misc high-capacity HHD Storage, Sonar Platinum, Adobe CS6 Master Suite, Misc 3D, video, audio software. Focusrite Liquid Saffire 56/octapre, Mackie MCU, other MIDI/control, rack effects, and more.
adam.cherrill
Max Output Level: -90 dBFS
  • Total Posts : 5
  • Joined: 2015/04/22 15:05:51
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/04/22 20:54:29 (permalink)
sylent -- not sure i'm following... any change i make on the main unit is duplicated on the extender -- any fader movement or track button/encoder change is duplicated.  They are in unison rather than being on separate MIDI channels.  It appears that whatever I do on MIDI channel 1 is being duplicated to MIDI Channel 2.
 
sylent
Max Output Level: -84 dBFS
  • Total Posts : 309
  • Joined: 2013/04/01 16:37:54
  • Location: Dallas, Texas
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/04/22 22:31:17 (permalink)
I hope I'm not forgetting a step.
I had the same problem, but can't find where I found the solution.
Pushing in a knob and rotating scrolled through the channels .. 1 thru 8 on the LCD . ... and the same but 9-16 on the other unit.
 
Since you have them working, but just mirrored, it's just that simple last step... but without mine setup hard to assure which, etc.
Just like it also scrolls through DAW configs to choose "sonar".
Apologies.
I am looking for the details for you now.
371

http://twisteddrive.com
Windows 7 Pro 64, i5-3570k 3.40GHz, 32Gb ram, NVIDIA Quatro 4000, 2x SSD, 2x 2Tb Dedicated storage and misc high-capacity HHD Storage, Sonar Platinum, Adobe CS6 Master Suite, Misc 3D, video, audio software. Focusrite Liquid Saffire 56/octapre, Mackie MCU, other MIDI/control, rack effects, and more.
sylent
Max Output Level: -84 dBFS
  • Total Posts : 309
  • Joined: 2013/04/01 16:37:54
  • Location: Dallas, Texas
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/04/22 22:49:58 (permalink)
ok, yes step missing... oops.
In controller/surface properties, (on menu bar in Plat, dont remember about x3 though), choose the main unit and click the little properties button.. on the bottom right of the new window there is a layout button.
click that, then use the first pot/knob to scroll through channel choices on both the unit and ext.
When set, press that button again.
It should save the setup and you should have 16 channels in the order you chose.
 
I always had issues until Platinum, now it works great.
https://www.cakewalk.com/...xternalDevices.07.html
25
post edited by sylent - 2015/04/22 23:02:02

http://twisteddrive.com
Windows 7 Pro 64, i5-3570k 3.40GHz, 32Gb ram, NVIDIA Quatro 4000, 2x SSD, 2x 2Tb Dedicated storage and misc high-capacity HHD Storage, Sonar Platinum, Adobe CS6 Master Suite, Misc 3D, video, audio software. Focusrite Liquid Saffire 56/octapre, Mackie MCU, other MIDI/control, rack effects, and more.
adam.cherrill
Max Output Level: -90 dBFS
  • Total Posts : 5
  • Joined: 2015/04/22 15:05:51
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/04/23 11:12:04 (permalink) ☄ Helpfulby wolfstudios53 2015/05/18 19:44:51
FastBikerBoy
You just need to assign each surface to it's own bank of tracks in the Mackie properties box.
 
  1. In the Sonar main menu click on "Utilities--->Macke Control -1"
  2. Click on the configure layout button (Bottom right corner)
  3. Use V-pot 1 on each unit to assign the banks
  4. Click on the "Press again when done" button in the Mackie properties box
 
That should sort it. You can also set a lot of other preferences there such as what the f-keys control.
 
HTH


Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/05/17 19:14:46 (permalink)
I have a question, how do you get these DLL's working?

I tried backing up the shared surface folder and copying over the dll files from here:
https://github.com/Cakewalk/Cakewalk-Control-Surface-SDK/tree/master/Bin/x64

It does not work - everytime I hit apply in preferences -> Control surfaces the setting disappear (for VS700 and Mackie control).
 
I'm using Dorchester. (I was surprised to see that the latest DLL's do not ship with Sonar?)
LunaTech
Max Output Level: -85 dBFS
  • Total Posts : 273
  • Joined: 2012/02/04 09:58:46
  • Location: Atlanta, GA
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/05/17 19:59:51 (permalink)
Doktor Avalanche
I have a question, how do you get these DLL's working?

I tried backing up the shared surface folder and copying over the dll files from here:
https://github.com/Cakewalk/Cakewalk-Control-Surface-SDK/tree/master/Bin/x64

It does not work - everytime I hit apply in preferences -> Control surfaces the setting disappear (for VS700 and Mackie control).
 
I'm using Dorchester. (I was surprised to see that the latest DLL's do not ship with Sonar?)


Hello,
 
I believe if these were not present on you system before you may have to use "regsvr32" to register the dlls. IHTH

"Life could capture me with songs of innocence...
And enrapture me with pleasures galore...
Suddenly it could all quickly fade away...
But I'm not surprised any more...."

Sonar Platinum Pro- Win 10 64- I7 6800k - Asus - 32gb DDR4-SB ZX sound card (cd output to mixer)- Toshiba 960gb SSD (OS - Audio APPs)- 4TB Seagate (Storage/ App Content)- M-Audio Keystation 88 Pro - Akai MPD 232 - Zed R16 - PT 12 - A&H QU 24- Axiom 61 - XD 80usb
 
"When He is all you have, He is everything you need"
azslow3
Max Output Level: -42.5 dBFS
  • Total Posts : 3297
  • Joined: 2012/06/22 19:27:51
  • Location: Germany
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/05/18 03:42:54 (permalink)
I have tried with ACTController.dll, and it works ok.
 
If you see the plug-in name in parentheses (like "(VS-700)"), Sonar could not load it. Either it was not found, you attempt to use it in 32bit Sonar or some DLL which is used by plug-in is not found (MS Runtime).
 
 

Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro
GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB
RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc.
www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/05/18 10:04:00 (permalink)
Yeah that's exactly what I did...  I downloaded and tried ACTController.dll... Everything is 64 bit inc what I downloaded. I don't think I need to register the DLL in this instance as an earlier version is already there (which I had renamed to .old previously). I guess I'll try again....

The issue was that I could set it all up in preferences correctly, but it would then disappear after hitting apply. If I reverted back to the earlier DLL things would be back to normal...
post edited by Doktor Avalanche - 2015/05/18 10:11:31
azslow3
Max Output Level: -42.5 dBFS
  • Total Posts : 3297
  • Joined: 2012/06/22 19:27:51
  • Location: Germany
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/05/18 12:21:13 (permalink)
For me it really has triggered some rescanning first... Sonar memory consumption was over 1.5G (when empty, it is normally under 0.5). But it worked than.
 
I have installed the latest MS runtimes (all versions!) when fighting against RP bug (as suggested by CW). So may be you have something outdated (the DLLs was obviously compiled several years after the original plug-in, but before Platinum, can be some intermediate VC).
 
Not that I understand why you want to use that limited, outdated and not supported DLLs without future...The alternative is in active development and supersede any of these plug-ins  in functionality, especially for not genius VS700 and MCU devices.
post edited by azslow3 - 2015/05/18 12:31:01

Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro
GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB
RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc.
www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/05/18 13:07:02 (permalink)
azslow3
I have installed the latest MS runtimes (all versions!) when fighting against RP bug (as suggested by CW). So may be you have something outdated (the DLLs was obviously compiled several years after the original plug-in, but before Platinum, can be some intermediate VC).
 

 
Yup maybe.
 
azslow3
Not that I understand why you want to use that limited, outdated and not supported DLLs without future...The alternative is in active development and supersede any of these plug-ins  in functionality, especially for not genius VS700 and MCU devices.



The whole point of github is to give it a future. Cakewalk DLL's are dated 2011 ot 2013 from memory? The DLL's appear to be more up to date:
https://github.com/Cakewalk/Cakewalk-Control-Surface-SDK/commits/master
 
If Cakewalk distributed updated DLL's that in turn would encourage developers to submit patches (the usual open source incentives). It would still probably have to go through their QA.

BTW 12419 Views on this thread.
post edited by Doktor Avalanche - 2015/05/18 13:23:34
tonydean
Max Output Level: -87 dBFS
  • Total Posts : 177
  • Joined: 2008/03/05 18:15:23
  • Location: Melbourne, Australia
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2015/06/04 13:55:33 (permalink)
So, has anybody got the fixes for the VS-700 yet? I'm not a programmer, so I have no idea how code works, but I'm wondering if anyone has fixed the fader issues of the VS-700 for use in Sonar X3e? Thanks in advance!

Intel Core i7 920, 8GB DDR3 1600 RAM, Windows 7 Ultimate 64bit, Dual screen,   Sonar X3e, Producer64bit, BFD2 64bit with Andy Johns
Waves Mercury, M-Audio Profire 610, Fender Strat Guitar, Cole Clark, Angel 2 Acoustic, Takamine G-Series Acoustic Guitar
Jackson Skulls Guitar, Rode NT-2 Condenser Mic
2 TB, Samsung pro840 256 gig SSD, USB 3.0 WD external HD, Sonar V-Studio 700c.
lgmab
Max Output Level: -89 dBFS
  • Total Posts : 93
  • Joined: 2015/07/06 14:24:02
  • Location: Canada
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2016/01/16 11:49:45 (permalink)
Hello, I am using 2 MAckie Control Universals with Sonar Platinum. Cannot get them to work independently.
YOu mention reassigning when you open a project. Would you please let me know what you mean by that?
thanks
azslow3
Max Output Level: -42.5 dBFS
  • Total Posts : 3297
  • Joined: 2012/06/22 19:27:51
  • Location: Germany
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2016/01/17 19:44:34 (permalink)
I do not think 2 MCU devices can work independently under Mackie Control plug-in... only as MCU+XT.

Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro
GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB
RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc.
www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
lgmab
Max Output Level: -89 dBFS
  • Total Posts : 93
  • Joined: 2015/07/06 14:24:02
  • Location: Canada
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2016/01/17 19:59:28 (permalink)
Actually, after several hours, a plethora of bad words, and several reboots....i was able to get them to both work concurrently. The sad thing howeve, is that they are prone to crashes. I am not sure exactly what initiates the crashes. One definate cause is access to plugin edits.
For those interested in getting two mcu to work, i would gladly share the procdure i followed successfully.
azslow3
Max Output Level: -42.5 dBFS
  • Total Posts : 3297
  • Joined: 2012/06/22 19:27:51
  • Location: Germany
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2016/01/18 05:12:01 (permalink)
lgmab
Actually, after several hours, a plethora of bad words, and several reboots....i was able to get them to both work concurrently. The sad thing howeve, is that they are prone to crashes. I am not sure exactly what initiates the crashes. One definate cause is access to plugin edits.
For those interested in getting two mcu to work, i would gladly share the procdure i followed successfully.

Crashes I have seen even with one single instance, not often but still.
 
Till you modify the source code, there are really working "concurrently". That is implemented to support XT/C4. I do not think that 2 "major" units was ever tested and that can cause problems.
 
If you want, I can compile yet another "Mackie Control 2" which can be used really independently (even with own XTs).

Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro
GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB
RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc.
www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
lgmab
Max Output Level: -89 dBFS
  • Total Posts : 93
  • Joined: 2015/07/06 14:24:02
  • Location: Canada
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2016/01/18 08:20:25 (permalink)
Hello, i use one mcu and a c4 regularily. I also have a second mcu which i wish to use as an extender for faders only. The crashes seem to occur when using the mcu (even when used as a single mcu) to edit plugins or other parameters, other than simple vol and pan.
Do you know of a fix for this issue? I guess what i really want is for the mcu to be stable accross the entire edit range within sonar.
Thank you kindly for your response!
azslow3
Max Output Level: -42.5 dBFS
  • Total Posts : 3297
  • Joined: 2012/06/22 19:27:51
  • Location: Germany
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2016/01/18 08:59:13 (permalink)
So you in fact want them to cooperate... What happens if you use in/out from the second MCU with "Mackie XT" plug-in? There is one place where XT different from MCU from software perspective, its "ID" (MCU has 0x14, XT has 0x15). I am not sure either that is important, if things are not working as expected, I can make a mod where XT also has 0x14.
 
About crashes... I guess that is coming from within Sonar. MCU is not working throw ACT Dyn. mapping with VST plug-ins,  as all other surfaces do. And there are some problems in parameter names (MCU tries to display them). It is just a guess, unconfirmed and not reported so far (while at least you and I have seen that effect). So no fix at the moment. I do not have MCU and I am not using an emulator (TouchDAW) for plug-in control. If you can collect some statistic when that happens, for example with which plug-ins that happens more often, may be I or Cakewalk can find the bug (in plug-in/in sonar/in both).

Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro
GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB
RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc.
www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
patm300e
Max Output Level: -74 dBFS
  • Total Posts : 845
  • Joined: 2007/09/28 09:14:18
  • Location: USA - Maryland
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2016/01/19 10:01:50 (permalink)
eric_peterson
I have been able to make the Presonus work for us. At age 50 and with a wife and four kids there's now way I can practice enough remember the chords/lyrics for almost 100 songs, not and hold down the day job too. So, I use a two page open facing PDF binder on my VAIO and flip pages with foot pedals. IOW, the VAIO is already there anyway on stand I built which includes the router and my guitar DSP which is all pre-wired. Given that, it's no big deal to just run the single cable bundle over to the mixer, the bundle includes: 16 foot firewire, guitar DSP output, and my vocals. I'm an Aerospace Hardware/Software/Systems guy and tend to get carried away, a prime example is our band's wiring harnesses: everything is shrink wrapped, has braided cable sleeving, and every connection is labelled. A bit over the top, but super helpful when setting up. 


Would have expected our band set up to use something like this:
http://www.connector-techals.com.au/images/MIL-C-38999-2.gif
 
LOL
 

SPLAT on a Home built i3 16 GB RAM 64-bit Windows 10 Home Premium 120GB SSD (OS) 2TB Data Drive.  Behringer XR-18 USB 2.0 Interface. FaderPort control.
BlixYZ
Max Output Level: -74 dBFS
  • Total Posts : 805
  • Joined: 2010/12/31 16:45:54
  • Location: Barrington, NJ
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2016/01/20 12:14:30 (permalink)
How do you control prochannel modules with TouchDAW?
 
When i press "plugin", i just get parameters for the first module (which is great) but i can't get past that first plugin, or module, rather.

James W
BlixYZ Recording Studio
BlixYZ Records

Audient ASP800 thru Focusrite Saffire Pro 40
Mackie Control Universal + C4
Yamaha HS50's plus Matching Sub, Tannoy 501a
Blue Baby Bottle, AT 4050, Neumann TLM 103, etc.
UA 610, Focusrite/ART/Neve 2CH.
Windows 10
eric_peterson
Max Output Level: -68 dBFS
  • Total Posts : 1103
  • Joined: 2003/11/25 10:24:05
  • Location: The jungles of Oregon ...
  • Status: offline
Re: Mackie Control protocol broken in Sonar X1/X2/X3 2016/01/20 14:17:13 (permalink)
patm300e
 
Would have expected our band set up to use something like this:
http://www.connector-techals.com.au/images/MIL-C-38999-2.gif
LOL

 
I considered something like that because it would be very slick, but opted out after I imagined a pin failure scenario during a gig. I've seen MIL standard plugs fail WAY too many times in the lab. I'd much rather have the ability to quickly solve a problem with standard cables. During a gig is not the best time to have to break out the magnifying glass, soldering iron, wiring diagrams, and to start mumbling "Great Scott!" like Doc Brown. You know, while the rest of the band wants to play ...
Page: < 12345 Showing page 5 of 5
Jump to:
© 2024 APG vNext Commercial Version 5.1