View previous topic :: View next topic |
Author |
Message |
TheDoctor Full Member
Joined: 28 Mar 2019 Posts: 162
|
Posted: Thu Jun 13, 2019 11:35 am Post subject: Electribe 2 MFX automation |
|
|
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] |
|
Back to top |
|
|
russellclarke Junior Member
Joined: 07 Jun 2019 Posts: 59
|
|
Back to top |
|
|
TheDoctor Full Member
Joined: 28 Mar 2019 Posts: 162
|
Posted: Thu Jun 13, 2019 2:32 pm Post subject: |
|
|
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? |
|
Back to top |
|
|
russellclarke Junior Member
Joined: 07 Jun 2019 Posts: 59
|
|
Back to top |
|
|
TheDoctor Full Member
Joined: 28 Mar 2019 Posts: 162
|
Posted: Thu Jun 13, 2019 3:13 pm Post subject: |
|
|
russellclarke wrote: | Yes, same name. |
Thanks for your help Electribe lovers |
|
Back to top |
|
|
TheDoctor Full Member
Joined: 28 Mar 2019 Posts: 162
|
Posted: Fri Jun 14, 2019 1:38 pm Post subject: |
|
|
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. |
|
Back to top |
|
|
russellclarke Junior Member
Joined: 07 Jun 2019 Posts: 59
|
Posted: Fri Jun 14, 2019 3:18 pm Post subject: |
|
|
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'. _________________ https://freesound.org/people/bangcorrupt/
http://ccmixter.org/people/bangcorrupt
https://github.com/bangcorrupt
Last edited by russellclarke on Fri Jun 14, 2019 3:26 pm; edited 2 times in total |
|
Back to top |
|
|
TheDoctor Full Member
Joined: 28 Mar 2019 Posts: 162
|
Posted: Fri Jun 14, 2019 3:20 pm Post subject: |
|
|
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! |
|
Back to top |
|
|
|