Questions & Answers

Is there a way to stop changing the fader in Logic X effect the preamp gain the the Studio 192?

0 votes
asked Jan 11, 2017 in Studio 192 USB 3.0 Interfaces by johnsherrill (270 points)
As I understand it, in Logic X, if a channel is selected and the volume fader is adjusted, then midi info is send to the preamp gain control on the Studio 192. Conversely, if the preamp gain is adjusted (either on the unit itself or via Universal Control) and a channel is selected in Logic that has that preamp as input, then the volume fader of the selected channel moves in Logic.

There is a post on the Sweetwater website that addresses this: Unfortunately, the prescribed solution doesn't seem to work for me and it also seems more like a hack solution anyway. Is there a way for Logic and the 192 to NOT communicate midi data or something?

I'm surprised I haven't found anyone else asking this question as it seems like a really big deal to me. Like, I can't track like this. The mixer faders in Logic are fundamentally not preamp gain controls.

2 Answers

+1 vote
answered Jan 12, 2017 by AlexTinsley (925,100 points)
selected Jan 23, 2017 by butchrichard
Best answer

The reason this is happening is because Logic is always scanning for possible new devices (audio or MIDI) that might get plugged in mid-project. In our case, Logic X interprets the embedded MIDI Input and Outputs for Preamp Control on the Studio 192 as a Control Surface of some kind, it tries to manage the messages like a control surface and we get this odd behavior that no other DAW shows where the first 8 channels are controlled by the encoder on the Studio 192 / 192 Mobile. We reported it as an issue to Apple in 2015, it's still an open issue. Logic should let you turn off the auto-scan function, but it doesn't. 

Logic has what is called the Environment, once enabled from Advanced Properties menu it's really easy to just redirect the MIDI Stream from the Studio 192 to a MIDI Monitor Window that will sit harmlessly redirecting MIDI from S192 (or wherever you want it to go if you want to). 

Here is a step by step tutorial on how to setup the work around: 

Step 1) Open Logic Properties (Apple + Comma) or click on Logic Preferences:

Logic X Prefs

2) Next Make sure at least these to boxes are checked 

  • Show Advanced Tools
  • MIDI

Logic X Adv Prefs MIDI

3) Close the Advanced Properties window

4) Click "Command + 0" on Apple Keyboard or on the Toolbar click on Window and select "Show MIDI Environment" to open the Environment Window. 


5) It will now look like this: 

Logic X MIDI Environment Window Default View for Studio 192

6) Click on the MIDI Environment Menu where it says "New" and select Physical Input: 

Logic X MIDI Environment New Physical Input

7) This will place a window on top of your MIDI Mixer View, drag it down below the mixer so it looks like this:

Logic X MIDI Physical Input Window

8) Go back to the MIDI Environment New Menu and select Monitor from the list

Logic X MIDI Environment New Monitor

9) This will put the monitor on the screen either on your mixer or near your other New Physical Input. Drag it down so it's looks like this:

Logic X MIDI Environment Physical Input and MIDI Monitor

10) Here's the tricky part if you're new to the environment in Logic. 

You see that little tail sticking up from the upper right corner of the Physical Input box: 

Logic X Environment Patch Connector

Grab it with your mouse and it will turn from a pointer into a patch cable. Drag it over to the right like this: 

Logic X MIDI Environment Click and Drag

11) Drag and Drop it on the right side of the Monitor where the little triangle is like this: 

Logic X MIDI Environment PI to MIDI Monitor

12) The completed setup will look like this:

Logic X Environment Physical Input to MIDI Monitor Completed Setup

If you have more than the Studio 192 present in your MIDI Input Devices list, see the Appendix at the end of this section for an additional step you need to do to make this a success. 

13) That's it your done!

Now when you move the encoder on the Studio 192, the MIDI coming over USB to the USB MIDI Input in Logic will be sent to a dedicated MIDI Monitor. It will display bits about the data stream, so the next question you might ask, what next? What happens to this data? Nothing, it's going to this MIDI Monitor. It's just a window looking at the data stream. It's not interfering with the channel controls in your mix. 

14) When you move the encoder the MIDI Monitor will look like The Matrix with data streaming by. 

Logic X MIDI Environment Studio 192 Data Stream

15) Last but not least you should save this as a blank Project that you set as a Project you can select so every time you start Logic, this will load up with it and you don't have to do it again. 

Logic X Save As Template

Here's another forum's topic on saving Template Projects in Logic X. 

Appendix - Multiple MIDI Ports in Addition to Studio 192

If you have more than one MIDI Port on your system, you may still be having issues because in the this tutorial we are having you take the Sum of all MIDI Inputs and sending it to a MIDI Monitor. If you're using a MIDI Keyboard like a DX7 or K2000 to send MIDI In to your Interface for Soft Synths, then this work around will not work unless you specifically pick out which Physical MIDI Input you want to redirect. 

In this example I have a MOTU Fast Lane USB connected on the same system as my Studio 192. In the environment window you will need very carefully pick the triangle just below where it says Sum and pick JUST the Studio 192 MIDI Output and drag it to the monitor as shown in step 11. Right click and download this picture if you have to and zoom in to see that I have NOT selected where it says SUM. I have ONLY selected where it says PreSonus Studio 19 (and then the text is cut off, this is a throwback to the older days of Logic (aka Creator where file names had to be 8 characters or less) so longer device names don't fit. 

Once you have your Studio 192 MIDI sent to the MIDI Monitor, then as described in Step 12 - 15, you're done. 

Pick this one not that one

The final screen looks like this when the encoder on the Studio 192 is moved. 

Logic X Multi-MIDI Ins with Studio 192 Redirected to MIDI Monitor

0 votes
answered Feb 11, 2018 by jakebabineau1 (150 points)

Hey there!

I also recently had this issue and PreSonus's solution didn't seem to fix it for me. Although it seems to work for some people my issue persisted after making this change in the midi environment. As far as I can find I'm the only one to post this Alternate solution so if Presonus wants to add this to their solution it may be useful, as this particular issue essentially cripples the functionality of the 192 in logic.

This issue occurs when Logic Pro confuses your audio interface for a midi device and auto assigns a knob on the 192 (the preamp knob on the 192 in this case) to change a parameter in Logic. In most cases, it seems to always move the selected tracks volume fader although I'm guessing there are other things it could mess with as well.

To fix this, first open up Logic’s Controller Assignments window (shift + alt + K, or Logic Pro X > Control Surfaces >…..). Here you should see the Studio 192 listed in the zones tab. After clicking that you will see the 192's buttons and functions as assignable midi commands and technically every field SHOULD be blank for things to run as intended because as you may have guessed the 192 is not meant to send midi functions to logic. When I went into this menu, however, I ended up finding that my volume fader was linked to the preamp level knob. I'm not sure how or when this happened. It's possible I accidentally hit the "learn new midi assignment" key command in logic and then tweaked a fader which auto saves that for controlling logic's faders but as long as you're able to delete the 192's parameters out of this window this problem should be fixed.

It's worth noting in addition to this I also had already done the PreSonus midi environment fix before I tried the midi assignment fix I just wrote about. So both are active on my computer and I haven't tested if undoing the PreSonus fix would bring the issue back (I doubt it would) so make sure you try both if my fix doesn't work but it was definitely a lightbulb moment for me when I checked this window!

Hope this helps.