|
|
Post by Stray on Mar 27, 2014 16:02:23 GMT -5
When using PXT-General's Fixed MCU option in Studio One (as of 2.6.1), when the Pan mode is selected via the Pan button, the Encoders will control panning, but the Display will show Volume values instead of Pan values. I'm not sure if this is intentional or a bug in Studio One. In either case, you can rectify this by making a slight change to one of the files in Studio One. The name of the file is MackieShared.js.
On Windows, you'll find this file in: Studio One 2.x.x\devices\Mackie\Control
On OS X, you should be able to find this file in: Studio One 2.x.x/Contents/devices/Mackie/Control
Before modifying this file, you should first back it up in the event that you make a mistake and need to revert it. You should also close Studio One.
To modify the file, go all the way to the bottom and find the section that reads:
else // kPanMode
{
channelInfo.setLabel (channelElement, "label");
channelInfo.setValue (channelElement, flipped ? "pan" : "volume");
channelInfo.setPot (channelElement, flipped ? "volume" : "pan");
channelInfo.setFader (channelElement, flipped ? "pan" : "volume");
}
The bolded part there needs to be flipped around, so that you end up with this:
else // kPanMode
{
channelInfo.setLabel (channelElement, "label");
channelInfo.setValue (channelElement, flipped ? "volume" : "pan");
channelInfo.setPot (channelElement, flipped ? "volume" : "pan");
channelInfo.setFader (channelElement, flipped ? "pan" : "volume");
}
|
|
|
|
Post by daslicht on Nov 23, 2014 9:27:31 GMT -5
Studio One is looking the PXT ports setup on each time you open S1: As you can see my other controlelr is being rememberd:  |
|
|
|
Post by Stray on Nov 23, 2014 11:06:28 GMT -5
There's a Troubleshooting topic in the manual ("On OS X, the application I’m using PXT-General with doesn’t remember the settings I selected related to PXT-General.") that covers how to resolve this.
|
|
|
|
Post by daslicht on Nov 26, 2014 12:51:02 GMT -5
Is it possible to use the Push Knobs in Relative Mode with Studio One somehow ?
|
|
|
|
Post by Stray on Nov 26, 2014 22:52:47 GMT -5
Sure, just select the Relative type in the User Assignments Editor or the MCU type (or Fixed MCU).
|
|
|
|
Post by daslicht on Nov 27, 2014 10:31:03 GMT -5
Hm that doesn't work properly. If I switch to Relative I can lern parameters, but knobs just jump frm 0 to 127 and do not inc/or decrement ?! Do I need to configure something else? I tried Both MCU and Relative and I just get: screencast.com/t/Ibu838l2ER8 |
|
|
|
Post by Stray on Nov 27, 2014 13:16:36 GMT -5
First of all, for the sake of clarity, the encoders are sending the values they should be sending here (1 – 64 for increase and 127 – 63 for decrease). The problem is that Studio One is interpreting these values as absolute, not relative. It doesn’t look like there is a way within Studio One itself to indicate whether the knob/encoder of a custom control surface sends absolute or relative values. Sorry, I wasn’t aware of that.
The easiest option would be to use the Fixed MCU option in PXT-General and the Mackie Control control surface in Studio One. This works with Control Link and the relative values of the encoders are properly interpreted.
It’s also possible to get Studio One to properly interpret relative values for custom control surfaces, but it takes some hacking. First, create your custom control surface in Studio One and make sure to give the control surface a unique name like StraysControlSurface. Then close Studio One and find the *.xml file associated with the control surface. Not sure exactly where that will be on your Mac, but it will be named StraysControlSurface.surface.xml, so just search for that. This file will list each control. Something like this:
<?xml version="1.0" encoding="UTF-8"?>
<ControlSurface>
<Controls>
<Control name="controlb0010" title="Control1" type="knob" options="receive public">
<MidiMessage status="#B0" channel="0" address="#10"/>
</Control>
<Control name="controlb0011" title="Control2" type="knob" options="receive public">
<MidiMessage status="#B0" channel="0" address="#11"/>
</Control>
<Control name="controlb0012" title="Control3" type="knob" options="receive public">
<MidiMessage status="#B0" channel="0" address="#12"/>
</Control>
<Control name="controlb0013" title="Control4" ="knob" options="receive public">
<MidiMessage status="#B0" channel="0" address="#13"/>
</Control>
</Controls>
</ControlSurface>
Change every knob that sends relative values to relative and add options="reversed" at the end of each entry. Like so:
<?xml version="1.0" encoding="UTF-8"?>
<ControlSurface>
<Controls>
<Control name="controlb0010" title="Control1" type="relative" options="receive public">
<MidiMessage status="#B0" channel="0" address="#10" options="reversed"/>
</Control>
<Control name="controlb0011" title="Control2" type="relative" options="receive public">
<MidiMessage status="#B0" channel="0" address="#11" options="reversed"/>
</Control>
<Control name="controlb0012" title="Control3" type="relative" options="receive public">
<MidiMessage status="#B0" channel="0" address="#12" options="reversed"/>
</Control>
<Control name="controlb0013" title="Control4" ="relative" options="receive public">
<MidiMessage status="#B0" channel="0" address="#13" options="reversed"/>
</Control>
</Controls>
</ControlSurface>
|
|
|
|
Post by daslicht on Nov 28, 2014 11:27:59 GMT -5
Thank you very much ! I will try both options.
Originally I tried the fixed MCU but I haven't got it working, I think it do not let you learn controller, just select them like on a real Mackie Control which is just tedious.
I keep you posted
|
|
|
|
Post by daslicht on Nov 28, 2014 12:25:10 GMT -5
There we go:
https://gist.github.com/daslicht/b6cf690276c527dc4cfd
Works like a charm , and even more precise than absolute mapping.
That way we could even mix types eg: first Knob Absolute for fast tweakings and some others relative for precise tweaking ,
yeah !
Thank you Stray !
|
|
|
|
Post by Stray on Nov 28, 2014 14:08:48 GMT -5
Good to hear that works for you and thanks for sharing your customized xml.
|
|
|
|
Post by daslicht on Dec 1, 2014 10:01:11 GMT -5
Is there a way to modify how big the inc/dec are ? When I control the Cutoff of Kontakt the steps are double as high as you get compared to using the mouse ? Controlling Kontakts filter at moderate resonance will give you zipper noises  |
|
|
|
Post by Stray on Dec 1, 2014 13:36:17 GMT -5
I suppose it's possible that there may be an option that allows for resolution modification within the script in Studio One, not sure on that honestly.
|
|
|
|
Post by daslicht on Dec 2, 2014 18:30:11 GMT -5
HM , I think my old Evolution uc16 does not suffer from these glitches. I retry absolute , probably its more accurate.
|
|
|
|
Post by Stray on Dec 2, 2014 19:46:57 GMT -5
Absolute is certainly preferable to relative for certain sorts of parameters. This is why PXT-General gives you the choice.
|
|
|
|
Post by thongumabob on Jan 3, 2015 7:12:23 GMT -5
Stray, I couldn't figure a way of using MCU with StudioOne midi-learn for knobs. So far I've only succeeded in making the knobs send Absolute values and contrary to what's been said above I'd prefer Relative behaviour for them. So, I'm trying to hack it as suggested by you - I've created my own Control Surface, but for some reason it's not searchable on OS X (named it Knobs, searched for knobs.surface.xml, nada). Please help!
|
|
