Jump to content
Blades

Presonus Faderport 8 in use in Cakewalk by Bandlab

Recommended Posts

23 hours ago, Craig Anderton said:

The biggest problem I've had with MCU and Sonar is after switching to control buses, it's difficult to get back to controlling tracks. This happened with the SSL Nucleus and other MCU-compatible devices, including the FP8. I could just be doing something wrong...

In my studio, the FP8 replaced two Avid Artist Series controllers. Although the FP8 doesn't do 16 channels, I love the compact size - the small footprint is a big deal for me. It sits to the right of my keyboard/mouse, and Maschine Mk3 sits to the left. 

If you have a Sonar overlay on it there is a section called Control Group. The buttons are from left to right Track, Aux, and Main.  This is where you move from tracks to buses and back.  Without an overlay it is the top three buttons under Functions. Labeled Undo, Cancel, and Enter. Undo =Tracks. Enter = Bus.

This was the only weakness with the Mackie Control. Each DAW developer was suppose to give Mackie a layout to create an overlay.  

Share this post


Link to post
Share on other sites

Speaking about small controllers, there's the relatively new icon platform m+. Do we have anybody, trying to connect that one with Cakewalk, on the forum?

Share this post


Link to post
Share on other sites
5 hours ago, John said:

If you have a Sonar overlay on it there is a section called Control Group. The buttons are from left to right Track, Aux, and Main.  This is where you move from tracks to buses and back.  Without an overlay it is the top three buttons under Functions. Labeled Undo, Cancel, and Enter. Undo =Tracks. Enter = Bus.

This was the only weakness with the Mackie Control. Each DAW developer was suppose to give Mackie a layout to create an overlay.  

 The Mackie protocol was developed in collaboration with E-Magic using Logic, hence Logic is the only DAW that doesn't require an overlay. It was written to be a simple open source standard MIDI language very much like GM (general MIDI) is used for a standard for controlling all MIDI synths developed in collaboration between Microsoft, Roland, and Cakewalk.

 But then Apple bought out E-Magic, dropped support for Windows during a bitter rivalry, and orphaned Mackie from any further opensource collaboration nonsense with Logic. And they decided to push hard for HUI protocol which was originally developed for Pro Tools.

Apple wasn't down with sharing any technology, especially where Microsoft and Windows was concerned, and didn't until it became painfully obvious that they didn't have a choice.. Both HUI and Pro Tools are very late starters for Windows, and neither have ever fully got of the ground with Windows users, and most likely never will. Even die hard Windows users and supporters like myself use Pro Tools on a Mac, and ONLY when I get paid to do it, LoL, I really LOVES me some Cakewalk..

The Control Group written for Mackie protocol for Cakewalk is actually Track, "BUSS", Main. And when CbB hangs in the Buss section the Buss light stays lit and the track and Main buttons do nothing when the problem occurs.

 Auxilary channels are completely different channels that run in parallel to the channels they are fed from. They can be set for pre or post fader signal paths and can but don't necessarily have to be sent to the buss.

 But I figured out a good work around, you don't need to use the Control Group section, you can assign track and buss focus selection to any of the "F" (function) less important keys assignments you can live without in Mackie Control Panel window. Getting stuck in Buss control is certainly something that can be hard to live with..

 Click on the function buttons you want to configure and the commands will be found about 3/4 the way down in the dropdown menu.

 Being MCU uses standard programable "Function" key command protocol  I see no reason it shouldn't work FP 8, as it does work well with the X Touch.

1036830999_Mackiecontrol.jpg.2b6705e8fd787fae3a0d6077ebf671c9.jpg

 

BUT that is an assumption, and I'm not really fond of trusting in assumptions, we all know how Mackie's assumption for creating an opensource one size fit's all collaboration with Logic turned out.

 It turned out they had to have a gaggle of templates made up for every other DAW and include them for free with every purchase of the Mackie Universal DAW Controller.. Which is in fact is very universal, just it's patented labeling isn't, and by the time truckloads of units and printed manuals were manufactured shipped, it seemed it was too late and too expensive to recall.

More assumptions on my part, and that doesn't explain why Behringer, after so meticulously cloning the original Mackie continued on labeling the buttons like the original, and never bothering to include templates for all the other DAWs. 

 Anyway it would be interesting to see if my work around does in fact work out for Presonus FP 8 like I'm assuming it should.

 Here's to hoping it will!🥤

Edited by Steev

Share this post


Link to post
Share on other sites

So...

I tried again this evening.  Here's what seems to be happening/working: (and I also found a different version of the manual on my PC from what I was looking at from the office Internet.

If you press the Bus button, it shows busses.  Before pressing that, you would see the lit Track button at the top and no other buttons lit on that column.  

In Studio One, you would press the All button at the bottom of that column of buttons, but in Cakewalk, that button lights but performs not function (as the manual indicates).  If you press the Audio button in Cakewalk, you get ALL of the tracks.  The MIDI tracks show in this mode as well.  So, even though there were no buttons lit on the bottom section when Cakewalk was started and it was showing ALL tracks, once Bus is pressed, hitting Audio seems to put it back to the same mode.  

Also, the manual says that if you press the VI/Midi button, you would get MIDI tracks.  You don't.  It seems to take you to the Hardware Outputs - like Shift-Bus should do.

There are definitely some things in here that don't act like you would expect, but it DOES seem to do more than the surface items.  You can't (apparently) count on the manual to tell you what those things are, however. :)

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...