67 postsPage 4 of 4
1, 2, 3, 4
I'm trying to configure an X-Touch Mini, but my experimentation hit a quick road block: Even the tiniest edit to the XML file (eg. just saving it so the edit timestamp changes) causes the file to be no longer read by S1. Meaning when I reopen S1 the external devices edit window is empty.

To be clear, here is what I'm doing:
1. Create a new external device
2. In the external devices edit window discover controllers with midi learn
3. Close S1 and edit the created XML file
4. Reopen S1 to discover the mapping is no longer there. (The device is there, but there are no controllers)

Version 4.6.2.58729 on Windows 10

So what is going on? Is the file compared against a hash when read? Given the success of others in this thread I feel like I'm missing something obvious. :(

EDIT: I made it work by starting from niles' BCR mapping, though I still don't know why the S1 generated files were so touchy.
User avatar
by tshadgett on Fri Apr 30, 2021 3:49 am
Hi guys,

Semi-related...
I recently integrated an SSL UF8 into my workflow. Really enjoying it so far - I sold my Console 1 Fader in favour of this due to the lack of scribble strips and I generally found I wasn't really using it the way I felt it was intended...
Anyway, the displays on the UF8 are great and if I want to edit a plugin, I can see the parameter names and values clearly on the display, which is much nicer.
However, two issues:
1) I can only control 8 parameters (hopefully SSL change this operation as there is plenty of scope to expand that through paging - which it does when controlling Cubase)
2) (this is where you talented folk come in) I find some plugins parameter names to be somewhat unfriendly. Ironically, the SSL Native Channel Strip is a good example where the parameter names are "Compressor Threshold", "Compressor Ratio", Compressor Release" etc. this means that the UF8 displays comprssr, comprssr, comprssr as the parameter names which is not helpful at all...

What I'm wondering is whether there is a way to define a "Friendly" name for the parameters on a per plugin basis?

TIA - Tim
User avatar
by Lokeyfly on Fri Apr 30, 2021 1:53 pm
Nice surface. I posted a heads up here on the UF8 a few weeks back. It went thru like you know what through a goose.

As awsome as the UF8 is (and it is), and the scribble strips are, there is a character limitation that the SSL software can't overcome due to HUI protocol. The character limit being one of them. It's nothing I believe can be fixed through Studio One.

You may have to rename busses or effects to:
CompT1, CompT2, CompR1, etc.
OpAir1 (Open Air), Omni1, Omni2 (Schepps Omni Channel), etc.

Having an 8 char. limit will do that.
You can rename instruments and effects in the right column [F5], so that you at least have a consistent start, or prefix. Then use instruments like Gtr, Sax, Bas, B3, etc.

S1-6.2.1, HP Omen 17" i7 10th Gen, 32 GB,512 GB TLC M.2 (SSD),1 TB SSD. Win10 Pro, Audient iD14 MkII, Roland JV90, NI S49 MkII, Atom SQ, FP 8, Roland GR-50 & Octapad. MOTU MIDI Express XT. HR824, Yamaha HS-7, NS-1000M, Yamaha Promix 01, Rane HC-6, etc.

New song "Our Time"
https://youtu.be/BqOZ4-0iY1w?si=_uwmgRBv3N4VwJlq

Visit my You Tube Channel
https://youtube.com/@jamesconraadtucker ... PA5dM01GF7

Latest song releases on Bandcamp -
 
Latest albums on iTunes

All works registered copyright ©️
User avatar
by tshadgett on Fri Apr 30, 2021 5:32 pm
Thanks Mate,

Yeah, track names and FX names themselves are fine and I can work with that and honestly, I don't find it too limiting.
I'm more concerned about the actual parameter names inside the plugin itself, like "compressor ratio".
I found the file where the parameters are linked to controls - Mackie Control.surfacedata and I thought there may be a way to add a name to the link so that it would display it.
Currently a linked plugin looks like this in the file:

<SurfaceDeviceAssignment deviceID="{56535453-4E43-5373-736C-206E61746976}" friendlyName="SSL SSL Channelstrip v6"
activePage="0">
<List x:id="pages">
<SurfaceAssignmentPage>
<Association key="vpot[0]" value="{56535453-4E43-5373-736C-206E61746976}/vstp1706566249"/>
<Association key="vpot[1]" value="{56535453-4E43-5373-736C-206E61746976}/vstp205320832"/>
<Association key="vpot[2]" value="{56535453-4E43-5373-736C-206E61746976}/vstp734111228"/>
<Association key="vpot[3]" value="{56535453-4E43-5373-736C-206E61746976}/vstp1404864214"/>
<Association key="vpot[4]" value="{56535453-4E43-5373-736C-206E61746976}/vstp1192057446"/>
<Association key="vpot[5]" value="{56535453-4E43-5373-736C-206E61746976}/vstp32000326"/>
<Association key="vpot[6]" value="{56535453-4E43-5373-736C-206E61746976}/vstp1065420706"/>
</SurfaceAssignmentPage>
</List>
</SurfaceDeviceAssignment>

I was kinda hoping I might be able to do something like this:
<Association key="vpot[0]" value="{56535453-4E43-5373-736C-206E61746976}/vstp1706566249" name="Ratio"/>
<Association key="vpot[1]" value="{56535453-4E43-5373-736C-206E61746976}/vstp205320832" name="Thresh"/>

But that has no effect unfortunately. I tried name= and friendlyName= but no joy...
User avatar
by tshadgett on Fri Apr 30, 2021 6:06 pm
I should say also that I hooked up the UF8 to Cubase Pro 10 to see how that behaved.

Cubase automatically sends all parameters to the UF8 and links them all without doing anything and you get pages of parameters to scroll through. This is good and bad, in S1, you decide which parameters you link and in what order - however at this point in time you can only link 8 in S1 with UF8.

Curiously in Cubase, the Parameter names are different from the same parameter in S1 (I would have thought this was dictated in the VST 3 file itself??) In Cubase, a parameter may show up as "Ratio", but in S1 the same parameter on the same plugin is called "Compressor Ratio". No idea why that is the case...
User avatar
by Lokeyfly on Fri Apr 30, 2021 7:47 pm
I see. So Cubase and Studio One send a different label.
There's no way I know of to alter that, but someone who delves in scripts could likely help you. So hang in there on responses.

S1-6.2.1, HP Omen 17" i7 10th Gen, 32 GB,512 GB TLC M.2 (SSD),1 TB SSD. Win10 Pro, Audient iD14 MkII, Roland JV90, NI S49 MkII, Atom SQ, FP 8, Roland GR-50 & Octapad. MOTU MIDI Express XT. HR824, Yamaha HS-7, NS-1000M, Yamaha Promix 01, Rane HC-6, etc.

New song "Our Time"
https://youtu.be/BqOZ4-0iY1w?si=_uwmgRBv3N4VwJlq

Visit my You Tube Channel
https://youtube.com/@jamesconraadtucker ... PA5dM01GF7

Latest song releases on Bandcamp -
 
Latest albums on iTunes

All works registered copyright ©️
User avatar
by bitsoundstudio on Sun Jun 20, 2021 1:29 pm
niles wrote
leonseaman wrote
niles wroteSince Studio One now also support pages (this way you can assign the same CC independent to multiple parameters of a VST) the amount of controls the BCR offers maybe is an overkill if you don't mind to bank back and forth a little. Benefit then is only a row of e.g. 8 controllers is shown in the mapping window.

Any idea how to use that system for generic controllers though? As far as i'm aware only the faderports can do it and i presume that's a part of additional coding via a javascript module or something.
Just add 'pageable' to the options of the controls you want to be pageable.

Like:
Code: Select all
    <Control name="myControlName" title="myControlTitle" type="button" options="pageable">
      <MidiMessage status="Controller" channel="1" address="#1"/>
Banking can be done with:
Code: Select all
    <Global>
   <using device="Editor/Paging">
      <Toggle control="myPrevPageControl" param="prevPage"/>
      <Toggle control="myNextPageControl" param="nextPage"/>
   </using>            
    </Global>


Hi!
I'm still a newbie in this stuff. I was trying to replicate this behaviour on a midi device. I'm using an XTouch Mini, and wanted to make the V-Pots pageable in order to control more plugin parameters.
I tried two methods, both without success.
1st:
Created a New Control Surface;
With MIDI learn assigned the XTouch MINI encoders and buttons.;
Edited the XML file with each encoder
Code: Select all
<Control name="controlb0100" title="Control1" type="relative" options="pageable">
         <MidiMessage status="#B0" channel="1" address="#0"/>

On the same surface file created 3 buttons
Code: Select all
<Control name="buttonPaging" title="Paging"   type="trigger" options="pageable"> 
         <MidiMessage status="#90" address="#64"/>
      </Control>
      <Control name="buttonPagingUp" title="Paging Up"   type="trigger" options="pageable">
         <MidiMessage status="#90" address="#0F"/>
      </Control>
      <Control name="buttonPagingDown" title="Paging Down"   type="trigger" options="pageable">
         <MidiMessage status="#90" address="#0E"/>
      </Control>


And then on the same file
Code: Select all
<Mappings>
   <Global>
         <using device="Editor/Paging">
            <Toggle control="buttonPagingDown" param="prevPage"/>
            <Toggle control="buttonPagingUp" param="nextPage"/>
         </using>                   
    </Global>
</Mappings>
 


As I was expecting, this didn't worked. The knobs and buttons show on SO, I can assign the encoders to plugin parameters, but there's no pagging.

I then tried another method. Instead of a "New Control Surface" I've create a MCU device. The XTouch MINI has an MCU profile that automatically assigns its 8 encoders to the MCU V-Pots.
Then I edited the mackieShared.surface.xml file replacing
Code: Select all
<Control name="vpot[0]" title="V-Pot 1" type="relative" options="transmit"/>

with
Code: Select all
<Control name="vpot[0]" title="V-Pot 1" type="relative" options="pageable"/>

This doesn't work either, as I'm getting a script error when trying to load a song.
I'm sure I'm way out of the right path! Can anyone point me in the right direction?
Thanks in advance!

67 postsPage 4 of 4
1, 2, 3, 4

Who is online

Users browsing this forum: No registered users and 65 guests