Octatrack + Soleman midi foot controller

[resonotter]

The reset fonction could be useful

but what input tells the OT to reset?
Is it just a MIDI Reset message?

[albadort]

SW1 = PC 0, 1, 2 etc…
SW2 = reset @ 0 every switches
SW3 & 4 = Scene A & B of the OT CC55 & CC56 from 1 to 127 (i just need value between 1 and 16)

[albadort]

Yes Midi reset message

[resonotter]

@albadort

SW2 = reset @ 0 every switches

Soleman SW2 sends out Midi reset message too? (ie not a CC?)

[albadort]

Soleman Sw2 sends out what we ask him between PC/NOTE/CC.
I would like midi hub to do a reset midi here.

[resonotter]

OK,
As far as I can make out you can put it altogether:

Switch number:

1. sends PC as is thro’ Midihub to OT
2. sends MIDI Note/CC to Midihub which Transforms to Reset
3. sends CC55=127 to Midihub. Adapted (1+16) Dispatcher pipeline changes it to different Scene value each time in a cycle
4. same for CC56

Oh, and Soleman converts the Exp pedal to whatever CC the OT wants for its Scene fader

[albadort]

Hi there! Thank you Resonotter for help. This is my patch for the moment. Row 1 @ 2 are for the scene A & B of the OT and affected on the Switches 3 & 4 of the Soleman. It works fine! Row 4 & 5 of the patch is for a play/stop of the sequencer affected on SW2 of my soleman, works fine too!
Row 6 of the patch is to increment PC from 0 to 15 on Switch 1 of the Soleman (= PATTERNS A1 to A16 of the OT). It also works fine but i’m wondering how to set it for going up to 64?
SOLEMAN OT.mhp (1.1 KB)

[albadort]

Any idea how to make a “Reset all” to value 0?
A CC/NOTE (whatever the value it can be set up In soleman’s editor) coming from soleman in another page resetting Scene A & B & PC (rows 1, 2 & 6 of this patch) to value 0.
This reset is usefull to begin a new song with all values at the start point.
thank you!

[resonotter]

@albadort

A CC/NOTE (whatever the value it can be set up In soleman’s editor) coming from soleman in another page resetting Scene A & B & PC (rows 1, 2 & 6 of this patch) to value 0.

Pipeline with 3 Transforms?
(all What = “Soleman SW output”):

1. Mode =Insert After, Into = “CC for Scene A → 0”
2. Mode =Insert After, Into = “CC for Scene B → 0”
3. Mode =Replace, Into = “PC → 0”

(plus any filters to keep tidy)

[albadort]

Row 6 of the patch is to increment PC from 1 to 16 on Switch 1 of the Soleman (= PATTERNS A1 to A16 of the OT). It also works fine but i’m wondering how to set it for going up to 64?

[resonotter]

I was just writing you an explanation pointing you to patch 2 here:

Program Change patches

This topic is just to show explanatory diagrams for two patches on patchstorage If you’re a regular reader you’ll have already seen them here and here. Both use loopback techniques, so if this is being read after the next major firmware update, hopefully they are both redundant! EDIT: If you have a 8 (or fewer) states and want to cycle through them up and down, you might want to try adapting the patch here first (it needs no loopback) There’s also a simpler patch further up the thread that …

but then I had another thought…

…give me a moment…

[resonotter]

---

EDIT: before I think on that, a question comes to mind:
do you want to be tapping through 64 patterns in practice?
The nice thing about your patch is it’s customisable for a given "set:

• one preset version could go in the sequence 0,1,2,etc
• while another could go 6, 7,23, whatever

If you do want cycle through 64 patterns see above…
…in meantime, I’ll see whether my new idea “holds water”!

[resonotter]

@resonotter

but then I had another thought…

…give me a moment…

OK. Give this a try (not tested myself cos not near Midihub)

Basic idea is your your last pipeline adapted:

All line 1 does is Dispatch created note to 4 channels and send to vH
vH pipelines picks up each of 4 channels in turn:

and then do their own Dispatches

---

you would set the sequence 0,1,2 looking vertically as it were

[albadort]

For the moment i keep the idea to progress +1 patterns on each pressure, but for sure a custom set is great too! On the OT, 16 Patterns are stored into Banks (A, B, C…), so calling a bank could also be used as calling a “song” if there is no more than 16 patterns into it.
I’ll have a look on your links, i should have reading on the forum before to ask
Many thanks!

[resonotter]

Fair enough.

Check out my pics above before resorting to a loopback approach.

Should work, but test with a small sample of Transforms first: it will be very boring to set up all 64!

@albadort

Patterns are stored into Banks (A, B, C…), so calling a bank could also be used as calling a “song” if there is no more than 16 patterns into it.

could be a shortcut?

---

PS.
re:

I’ll have a look on your links, i should have reading on the forum before to ask

I deliberately didn’t mention them to start, cos I think it’s best to avoid loopbacks if one can!

[albadort]

could be a shortcut?

great idea!

[albadort]

I’m up to finish my m.Hub patch to control an Octatrack with the Soleman midi footswitch. There is still one thing i do not get : how to set the MSB & the LSB of a program change in midi hub editor?

[albadort]

Here is the CC of the soleman’s editor to be transform in PC in midi hub editor’s :

[albadort]

[albadort]

MSB & LSB in midi hub’s editor

PC chart of the OT :

So my set up of the Soleman’s footswitch is : SW1 = Pattern up (up to H16, i’d like to reach P16 with the good MSB value), SW2 = Play/Stop, SW3 = Scene A up, SW4, = Scene B up, CC48 scene fade = expression pedal