Live Guitar MultiFX with Line6 POD XT Live as Controller/Audio Interfc

[Igorrr]

Hi all,

I started with Usine Free yesterday and am already loving it, although sometimes very confusing. Took me 2 hours to actually find out how to remove objects/connections...

Anyway what I am trying to do is since I am using Amplitube 2 and Revalver MK II for recording and seeing how far advanced these options are compared to the Line6 Pedal I was thinking about moving to a Laptop as FX/Modeler solution.

Seeing that the Line6 POD XT Live can be used as an ASIO interface and send MIDI data when every button is pressed it's the obvious solution compared to buying an additional Audio/MIDI interface with another MIDI Controller board.
Only Bad news is the MIDI commands from the POD can not be configured.

Now what I have been trying to do is translate the MIDI commands sent from the POD to Usine... I have been able to filter commands and also through Math functions to manipulate the sent data (e.g. the board only sends 0 or 127 values on switches but some VST switching plugins need custom values for routing (e.g. dispatcher).

But I have not found a way to filter the CC commands. I tried the midi filter but it seems to only filter the command type but not the Code values.
At the moment every switch I set is sent to every module. E.g. commands that come from CC25 and CC50 end up being the same.

How can I set a filter that CC25 commands are sent to one seperate module and CC50 to another?

I guess in the end this is a really Newb question, but believe me in 5 hours I did not find a way to do that.

[antwan]

Hi,

Welcome to the world of Usine. You will love it once you get the hang of it!

Assuming the Line6 control in question is - let's say the expression pedal - why not create a fader (interface design) and midi learn that to the pedal. I didn't quite get what you wanted to be done with the incoming midi messages but this midi learnt fader you could then route anywhere.
If it's a switch on your Line6 then why not create a Switch (interface design) and midi learn that...

Just one more example: Let's say you have a VST plugin and you want to control a certain parameter with your pedal. Control+drag from the plugins parameter inlet nicely creating an appropriate interface element (fader / switch). Right-click that interface element and select midi learn - then move or press the control on the pedal and voila, all should be working.
Remember to select the midi port / device in Setup>Midi in.

Let me know if this is of any help or give more details and we can help you further.
And as I said, welcome on board.

Cheers,

antwan

[Igorrr]

Hi Antwan,

thank you for you reply..... why do it complicated when there's an easy solution.... I am going to try that out once I get home...

I thought I'd need to add the MIDI Input and rout the signal to the faders and switches. I was completely oblivious to the fact I could perform Midi Learn directly on the fader or switch objects.

Just a question. Am I in this case still able to perform code value translations? E.g. 1 in 4 out switch accepts the MIDI values 1-4 for routing but each pedal sends on a different CC* the value 127 when pressed. How can I translate then the 127 to a 1-4 value each?

Thank you again

[bsork]

Hi Igorrr, I'm not quite sure if I have understood you last question correctly, but if what you want is to send 4 different CCs and end up with values between 1 and 4 - here's a recipe:

Create Interface Design/Button * 4 and do MIDI learn on them, Math/A*B * 4, Event Control/Pass Event Flow * 1. Connect the buttons separately to A on the A*B modules, and set the B parameters to 1, 2, 3, and 4. Connect all the A*B modules to In on the Pass Event Flow, and all the buttons to the Pass input. Now the output of Pass Event Flow switches between 1 and 4.

Another thing you could try if you want more "milage" out of your available swithces, is to go binary...: You can switch between four different values using only two CCs, and the patch is even easier than the above, although it's maybe a bit clumsy if your going to control it with your feet...:

Create Interface Design/Switch * 2 and do MIDI learn on them, Math/A*B * 2, Math/A+B * 1. Connect the switches separately to A on the A*B modules, and set the B parameters to 1 and 2. Connect both A*B modules to A on the A+B, and set B to 1. There you have it:

Sw1 Sw2 A+B.out
--------------------
Off Off 1
On Off 2
Off On 3
On On 4

Note the differences between buttons and switches. The buttons send trigger type signals; a 1 immediately followed by a 0, while the switches send 1 when on and 0 when off.

And here's a little tip that I'm not sure is mentioned in the manual which comes in very handy when you're creating patches: Select a connection by clicking the little dot in the middle of it, and the part where the modules' parameter list is normally shown changes to show the values going through the "wire". Useful both to learn and understand more of what's happening as well as for debugging.

Happy patching!

[Igorrr]

Wow thanks for the info. Especially the debug part... there are some switches (actually the program change buttons) that send many commands at once and I was until now only able to see the last one... this debug info will help me A LOT!!!

Too bad I have to spend another 8 hours here at work before being able to play some more.

[bsork]

I just thought of something that might be just what you're looking for: the conductor. With the conductor you can save the state of whole workspace as one big preset, and the good thing is that every snapshot or scene has it's own MIDI and key learn. In fact you can recall snapshot 0 with a CC, 1 with a NoteOn and 3 with a key. No patch programming needed, whatsoever.

The Conductor is part of the Global Remote, so you should remember to save the remote file. The nice thing about storing all those controls separately is that it's easy to switch between different hardware setups. The same also applies to the setup and master files.