Electribe 2 MFX automation

TheDoctor · Post by **TheDoctor** » Thu Jun 13, 2019 11:35 am

Try to record the MFX Hold on/off and see if you have the light feedback when you play back.
MFX send and IFX on/off give you light feedback.
Can you please check for me if it's a bug or is my unit?[/i]

russellclarke · Post by **russellclarke** » Thu Jun 13, 2019 1:31 pm

In the pattern file, 'mfx hold' is recorded as 'pad touched', so the light won't come on.
Activating 'mfx hold' after it has been motion sequenced should defeat the on/off motion and hold the effect constantly on. If 'mfx hold' is on when the pad is motion sequenced, 'pad touched' motion will not be recorded, only x/y.

TheDoctor · Post by **TheDoctor** » Thu Jun 13, 2019 2:32 pm

russellclarke wrote:In the pattern file, 'mfx hold' is recorded as 'pad touched', so the light won't come on.
Activating 'mfx hold' after it has been motion sequenced should defeat the on/off motion and hold the effect constantly on. If 'mfx hold' is on when the pad is motion sequenced, 'pad touched' motion will not be recorded, only x/y.

Thanks man! Are you the guy on Reddit?

russellclarke · Post by **russellclarke** » Thu Jun 13, 2019 2:54 pm

Yes, same name.

TheDoctor · Post by **TheDoctor** » Thu Jun 13, 2019 3:13 pm

russellclarke wrote:Yes, same name.

Thanks for your help Electribe lovers

TheDoctor · Post by **TheDoctor** » Fri Jun 14, 2019 1:38 pm

russellclarke wrote:In the pattern file, 'mfx hold' is recorded as 'pad touched', so the light won't come on.
Activating 'mfx hold' after it has been motion sequenced should defeat the on/off motion and hold the effect constantly on. If 'mfx hold' is on when the pad is motion sequenced, 'pad touched' motion will not be recorded, only x/y.

Update: it can't be possible since the Electribe send the MFX X as 102 midi cc,Y as 103 and the MFX on/off as 106.

russellclarke · Post by **russellclarke** » Fri Jun 14, 2019 3:18 pm

Copied from reddit:

They send MIDI separately but record the same motion sequence, motion sequences do not send MIDI. You can check this in the pattern file. Motion sequences start at byte 0x200. First 24 bytes are target channels, next 24 bytes are target parameters. Then 64 bytes for each of the 24 motion sequences.

Like this:

https://pastebin.com/Dsu5L5uw

Parts are numbered 0x01 - 0x10, MFX motion sequences are given channel number 0x11.

Parameters are numbered:
https://pastebin.com/t6bLPGmn

'pad touched' and 'mfx hold' will both create a motion sequence on channel 0x11 with target 0x13 and values of 0x01 for 'off' , 0x02 for 'on'.

TheDoctor · Post by **TheDoctor** » Fri Jun 14, 2019 3:20 pm

russellclarke wrote:Copied from reddit:

They send MIDI separately but record the same motion sequence, motion sequences do not send MIDI. You can check this in the pattern file. Motion sequences start at byte 0x200. First 24 bytes are target channels, next 24 bytes are target parameters. Then 64 bytes for each of the 24 motion sequences.

Like this:

https://pastebin.com/Dsu5L5uw

Parts are numbered 0x01 - 0x10, MFX motion sequences are given channel number 0x11.
Parameters are numbered:
https://pastebin.com/t6bLPGmn

'pad touched' and 'mfx hold' will both create a motion sequence on channel 0x11 with values of 0x01 for 'off' and 0x02 for 'on'.

Thanks for the detailed explanation. Good job!