Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
Oh yes, that sounds interesting. We will put this on our list.
What we already got in our modulation menu (tap the “velocity” label) is probability and trigger condition. Also, of course, mutation of trigger and internal and CC modulation.
Maybe that also helps a bit ✌️😊
Yes, thank you, of course. It’s one of the main features of Octachron.
Actually, you can reach it via long press or shift + tap on a pattern alias.
It is also described in the manual.
But if you have any more questions, just ask here 🙂
Not yet, but it will pretty soon ✌️🎶😊
So cool, thank you very much ✌️🎉🤩
@TasTax @reinerspass
I have added my request to my previous post.
It is the part highlighted in bold font below.
@TasTax @reinerspass
My apologies. My above request post was not clear enough.
My request does not mean that I want the ‘CC ON EVERY STEP’ feature to be enabled in the initial state immediately after AUv3-Octachron is loaded.
I mean that I would like the ‘CC ON EVERY STEP’ feature to be enabled when a user loads a mapping/preset I made that has a note with a numerical value of "0" as shown below.
notes.append(NoteListItem(note: 0, title: "exampleEXAMPLE"))
By that I mean that I would like you to make the mappings/presets I posted with the "CC ON EVERY STEP" feature enabled setting.
(Edited)
However, if the "CC ON EVERY STEP" enable/disable state can only be loaded/saved in USER PRESETS at this time, and Octachron program must be changed to do so in the APPS in MIDI MAPPING in Octachron, I cancel the request above.
In this case, as before, my request is that the mapping B I posted be added to Octachron in one of the Octachron updates.
(/Edited)
Hey @cramdog ,
Yes, thx for your deep thoughts.
I could imagine, that it could make sense for your presets.
But don’t you think it could be a little confusing for other users? Because they expect that the cc on every step option is disabled intianally.
I never realized it until now! I’m sorry. After reading your explanation I changed my mind. What you said is reasonable. So I cancel the request.
Ok, thx, but no problem at all.
We can talk about it .
Thx a lot again for your engagement in Octachron 🙂
@TasTax @reinerspass
I made a version of mappings where all CC parameters set in that mapping/preset work fine even if CC ON EVERY STEP is in the initial state (= disabled).
Since the total number of pads/parts in AUv3 Korg Gadget is ‘Equal’ to the total number of rows in the Octachron UI, I call them mapping(s) ‘E’. (Personally, I hope it is also an ‘E’ for ‘Easy’ to use).
'Mapping E' may be a better initial preset than 'mapping B' that I posted earlier, because of the simplicity of the screen/UI. (In other words, I have been very much too conscious of having to have all parameters in mappings).
Advantages of mapping E
-There are the same total number of rows in Octachron UI as the total number of pads (number of instrument parts) in the Gadget. So the screen is easy to see.
-No need to change Octachron settings. This means that even if ‘CC ON EVERY STEP’ feature is disabled state, all CC parameters that the mapping has will work fine.
Disadvantages of mapping E
-Master levels and master effects cannot be controlled from Octachron.
(However, I feel that those master/global[?] parameters of AUv3 Korg Gadget would be better set by user customization in Octachron rather than by an initial mapping prepared in Octachron).
-There are omitted parameters.
(-However, I am mainly referring here only to ‘Group, EG Mode and Mute’ in London gadget. ‘Group and EG Mode’ seem to me to be hard to control intendedly[?] from Octachron. [Of course/Needless to say, whether it is worthwhile to control them or not depends on how the users use them].
-There may be some good use for ‘Mute’, but I am not sure.)
*
The parameters I omitted are listed below.
-Except for ‘Group, Mute and EG Mode’ in London gadget, they are all parameters that have an master/global(?) effect(?), like ‘Master Level’.
*
Amsterdam
FX Edit 1
FX Edit 2
Master Level
FX Type
total 4
*
Bilbao
FX Edit 1
FX Edit 2
Master Level
FX Type
total 4
*
London
FX Edit 1
FX Edit 2
Master Level
FX Type
Group
Mute
EG Mode
total 7
*
Recife
FX Edit 1
FX Edit 2
Master Level
FX Type
total 4
*
Tokyo
FX Edit 1
FX Edit 2
FX Type
total 3
-Tokyo gadget has no ‘Master Level’ parameter.
*
Gladstone
Comp Thresh
Comp Ratio
Comp Gain
Comp Drive
EQ Freq Lo
EQ Freq Mid
EQ Freq Hi
EQ Gain Lo
EQ Gain Mid
EQ Gain Hi
Amb Mix
Master Level
total 12
-Gladstone gadget has no ‘FX Edit 1’, ‘FX Edit 2’, and ‘FX Type’ parameters.
Amsterdam MIDI note ‘mapping E’
EDITED 4 rows version
Parameters order were EDITED from MIDI #CC Assign.
Intent of the EDITED version
-I considered ‘EG Mode’ to be hard to control.
-I thought 'EG Time' and 'Reverse' were related.
Level
Pan
Tune
EG Mode
EG Time
Reverse
FX Send
⬇️
Level
Pan
Tune
EG Time
Reverse
FX Send
EG Mode
*
notes.append(NoteListItem(note: 36, title: "1"))
notes.append(NoteListItem(note: 37, title: "2"))
notes.append(NoteListItem(note: 38, title: "3"))
notes.append(NoteListItem(note: 39, title: "4"))
\
Amsterdam MIDI CC mapping
*
1st row
1 Level
1 Pan
1 Tune
1 EG Time
1 Reverse
1 FX Send
1 EG Mode
CC#
4
5
9
16
18
11
15
2nd row
2 Level
2 Pan
2 Tune
2 EG Time
2 Reverse
2 FX Send
2 EG Mode
CC#
20
21
23
27
29
25
26
3rd row
3 Level
3 Pan
3 Tune
3 EG Time
3 Reverse
3 FX Send
3 EG Mode
CC#
31
33
35
40
42
37
39
4th row
4 Level
4 Pan
4 Tune
4 EG Time
4 Reverse
4 FX Send
4 EG Mode
CC#
44
45
47
50
53
60
50
London MIDI note ‘mapping E’
EDITED 8 rows version
Parameters order were EDITED from MIDI #CC Assign.
Intent of the EDITED version
-London gadget itself has 3 pages of skin/UI. I used that as a reference to determine the order of the parameters. (Please see attached three image files for details).
-I considered ‘EG Mode’ to be hard to control.
-I thought 'EG Time' and 'Reverse' were related.
-I guessed that 'Mute' might be substituted to some extent with other parameters or features.
Level
Pan
Mute
Tune
Group
FX Send
EG Mode
EG Time
Punch
Reverse
Low Boost
⬇️
Tune
EG Time
Reverse
FX Send
Punch
Low Boost
Pan
Level
*
notes.append(NoteListItem(note: 36, title: "01"))
notes.append(NoteListItem(note: 37, title: "02"))
notes.append(NoteListItem(note: 38, title: "03"))
notes.append(NoteListItem(note: 39, title: "04"))
notes.append(NoteListItem(note: 40, title: "05"))
notes.append(NoteListItem(note: 41, title: "06"))
notes.append(NoteListItem(note: 42, title: "07"))
notes.append(NoteListItem(note: 43, title: "08"))
\
London MIDI CC mapping
*
1st row
1 Tune
1 EG Time
1 Reverse
1 FX Send
1 Punch
1 Low Boost
1 Pan
1 Level
CC#
9
15
18
11
17
19
10
4
2nd row
2 Tune
2 EG Time
2 Reverse
2 FX Send
2 Punch
2 Low Boost
2 Pan
2 Level
CC#
23
27
29
25
28
30
21
20
3rd row
3 Tune
3 EG Time
3 Reverse
3 FX Send
3 Punch
3 Low Boost
3 Pan
3 Level
CC#
35
40
42
37
41
43
33
31
4th row
4 Tune
4 EG Time
4 Reverse
4 FX Send
4 Punch
4 Low Boost
4 Pan
4 Level
CC#
47
51
53
49
52
54
45
44
5th row
5 Tune
5 EG Time
5 Reverse
5 FX Send
5 Punch
5 Low Boost
5 Pan
5 Level
CC#
58
62
65
60
63
66
56
55
6th row
6 Tune
6 EG Time
6 Reverse
6 FX Send
6 Punch
6 Low Boost
6 Pan
6 Level
CC#
70
74
76
72
75
77
68
67
7th row
7 Tune
7 EG Time
7 Reverse
7 FX Send
7 Punch
7 Low Boost
7 Pan
7 Level
CC#
81
85
87
83
86
88
79
78
8th row
8 Tune
8 EG Time
8 Reverse
8 FX Send
8 Punch
8 Low Boost
8 Pan
8 Level
CC#
92
102
104
94
103
105
90
89
Recife MIDI note ‘mapping E’
16 rows version
Parameters order were not edited from MIDI #CC Assign.
*
notes.append(NoteListItem(note: 36, title: "1"))
notes.append(NoteListItem(note: 37, title: "2"))
notes.append(NoteListItem(note: 38, title: "3"))
notes.append(NoteListItem(note: 39, title: "4"))
notes.append(NoteListItem(note: 40, title: "5"))
notes.append(NoteListItem(note: 41, title: "6"))
notes.append(NoteListItem(note: 42, title: "7"))
notes.append(NoteListItem(note: 43, title: "8"))
notes.append(NoteListItem(note: 44, title: "9"))
notes.append(NoteListItem(note: 45, title: "10"))
notes.append(NoteListItem(note: 46, title: "11"))
notes.append(NoteListItem(note: 47, title: "12"))
notes.append(NoteListItem(note: 48, title: "13"))
notes.append(NoteListItem(note: 49, title: "14"))
notes.append(NoteListItem(note: 50, title: "15"))
notes.append(NoteListItem(note: 51, title: "16"))
\
Recife MIDI CC mapping
*
1st row
1:Decay
1:Pitch
1:Pan
1:Level
1:Repeat
1:Speed
CC#
8
9
10
11
4
5
2nd row
2:Decay
2:Pitch
2:Pan
2:Level
2:Repeat
2:Speed
CC#
20
21
22
23
18
19
3rd row
3:Decay
3:Pitch
3:Pan
3:Level
3:Repeat
3:Speed
CC#
26
27
28
29
24
25
4th row
4:Decay
4:Pitch
4:Pan
4:Level
4:Repeat
4:Speed
CC#
33
34
35
36
30
31
5th row
5:Decay
5:Pitch
5:Pan
5:Level
5:Repeat
5:Speed
CC#
40
41
42
43
37
39
6th row
6:Decay
6:Pitch
6:Pan
6:Level
6:Repeat
6:Speed
CC#
46
47
48
49
44
45
7th row
7:Decay
7:Pitch
7:Pan
7:Level
7:Repeat
7:Speed
CC#
52
53
54
55
50
51
8th row
8:Decay
8:Pitch
8:Pan
8:Level
8:Repeat
8:Speed
CC#
58
59
60
61
56
57
9th row
9:Decay
9:Pitch
9:Pan
9:Level
9:Repeat
9:Speed
CC#
65
66
67
68
62
63
10th row
10:Decay
10:Pitch
10:Pan
10:Level
10:Repeat
10:Speed
CC#
71
72
73
74
69
70
11th row
11:Decay
11:Pitch
11:Pan
11:Level
11:Repeat
11:Speed
CC#
77
78
79
80
75
76
12th row
12:Decay
12:Pitch
12:Pan
12:Level
12:Repeat
12:Speed
CC#
83
84
85
86
81
82
13th row
13:Decay
13:Pitch
13:Pan
13:Level
13:Repeat
13:Speed
CC#
89
90
91
92
87
88
14th row
14:Decay
14:Pitch
14:Pan
14:Level
14:Repeat
14:Speed
CC#
95
102
103
104
93
94
15th row
15:Decay
15:Pitch
15:Pan
15:Level
15:Repeat
15:Speed
CC#
107
108
109
110
105
106
16th row
16:Decay
16:Pitch
16:Pan
16:Level
16:Repeat
16:Speed
CC#
113
114
115
116
111
112
Tokyo MIDI note ‘mapping E’
4 rows version
Parameters order were not edited from MIDI #CC Assign.
*
notes.append(NoteListItem(note: 36, title: "BD201"))
notes.append(NoteListItem(note: 37, title: "SD302"))
notes.append(NoteListItem(note: 38, title: "TOM404"))
notes.append(NoteListItem(note: 39, title: "PCS503"))
\
Tokyo MIDI CC mapping
*
1st row
BD201 Wave
BD201 Tune
BD201 Decay
BD201 Bend
BD201 Boost
BD201 Pan
BD201 Level
BD201 FX SW
CC#
81
82
83
84
85
86
87
114
2nd row
SD302 Tune
SD302 Decay
SD302 Noise
SD302 Snappy
SD302 Punch
SD302 Pan
SD302 Level
SD302 FX SW
CC#
88
89
90
91
92
93
94
115
3rd row
TOM404 Tune
TOM404 Decay
TOM404 Bend
TOM404 Noise
TOM404 Pan
TOM404 Level
TOM404 FX SW
CC#
95
102
103
104
105
106
116
4th row
PCS503 Tune
PCS503 Decay
PCS503 Shape
PCS503 Speed
PCS503 Depth
PCS503 Pan
PCS503 Level
PCS503 FX SW
CC#
107
108
109
110
111
112
113
117
Bilbao MIDI note ‘mapping E’
EDITED 16 rows version
Parameters order were EDITED from MIDI #CC Assign.
Intent of the EDITED version
-The order of Pitch and Pan is aligned with the skin/UI of the gadget.
Start
Hold
Decay
Pan
Pitch
Level
⬇️
Start
Hold
Decay
Pitch
Pan
Level
*
notes.append(NoteListItem(note: 36, title: "01"))
notes.append(NoteListItem(note: 37, title: "02"))
notes.append(NoteListItem(note: 38, title: "03"))
notes.append(NoteListItem(note: 39, title: "04"))
notes.append(NoteListItem(note: 40, title: "05"))
notes.append(NoteListItem(note: 41, title: "06"))
notes.append(NoteListItem(note: 42, title: "07"))
notes.append(NoteListItem(note: 43, title: "08"))
notes.append(NoteListItem(note: 44, title: "09"))
notes.append(NoteListItem(note: 45, title: "10"))
notes.append(NoteListItem(note: 46, title: "11"))
notes.append(NoteListItem(note: 47, title: "12"))
notes.append(NoteListItem(note: 48, title: "13"))
notes.append(NoteListItem(note: 49, title: "14"))
notes.append(NoteListItem(note: 50, title: "15"))
notes.append(NoteListItem(note: 51, title: "16"))
\
Bilbao MIDI CC mapping
*
1st row
1:Start
1:Hold
1:Decay
1:Pitch
1:Pan
1:Level
CC#
4
5
8
9
10
11
2nd row
2:Start
2:Hold
2:Decay
2:Pitch
2:Pan
2:Level
CC#
18
19
20
21
23
22
3rd row
3:Start
3:Hold
3:Decay
3:Pitch
3:Pan
3:Level
CC#
24
25
26
27
29
28
4th row
4:Start
4:Hold
4:Decay
4:Pitch
4:Pan
4:Level
CC#
30
31
33
34
36
35
5th row
5:Start
5:Hold
5:Decay
5:Pitch
5:Pan
5:Level
CC#
37
39
40
41
43
42
6th row
6:Start
6:Hold
6:Decay
6:Pitch
6:Pan
6:Level
CC#
44
45
46
47
49
48
7th row
7:Start
7:Hold
7:Decay
7:Pitch
7:Pan
7:Level
CC#
50
51
52
53
55
54
8th row
8:Start
8:Hold
8:Decay
8:Pitch
8:Pan
8:Level
CC#
56
57
58
59
61
60
9th row
9:Start
9:Hold
9:Decay
9:Pitch
9:Pan
9:Level
CC#
62
63
65
66
68
67
10th row
10:Start
10:Hold
10:Decay
10:Pitch
10:Pan
10:Level
CC#
69
70
71
72
74
73
11th row
11:Start
11:Hold
11:Decay
11:Pitch
11:Pan
11:Level
CC#
75
76
77
78
80
79
12th row
12:Start
12:Hold
12:Decay
12:Pitch
12:Pan
12:Level
CC#
81
82
83
84
86
85
13th row
13:Start
13:Hold
13:Decay
13:Pitch
13:Pan
13:Level
CC#
87
88
89
90
92
91
14th row
14:Start
14:Hold
14:Decay
14:Pitch
14:Pan
14:Level
CC#
93
94
95
102
104
103
15th row
15:Start
15:Hold
15:Decay
15:Pitch
15:Pan
15:Level
CC#
105
106
107
108
110
109
16th row
16:Start
16:Hold
16:Decay
16:Pitch
16:Pan
16:Level
CC#
111
112
113
114
116
115
Gladstone MIDI note ‘mapping E’
10 rows version
Parameters order were not edited from MIDI #CC Assign.
*
notes.append(NoteListItem(note: 36, title: "Kick"))
notes.append(NoteListItem(note: 37, title: "Snare"))
notes.append(NoteListItem(note: 38, title: "Snare 2"))
notes.append(NoteListItem(note: 39, title: "HH Close"))
notes.append(NoteListItem(note: 40, title: "HH Open"))
notes.append(NoteListItem(note: 41, title: "Tom Hi"))
notes.append(NoteListItem(note: 42, title: "Tom Mid"))
notes.append(NoteListItem(note: 43, title: "Tom Lo"))
notes.append(NoteListItem(note: 44, title: "Crash"))
notes.append(NoteListItem(note: 45, title: "Ride"))
\
Gladstone MIDI CC mapping
*
1st row
1:Tune
1:Decay
1:Pan
1:AmbSend
1:DryLevel
CC#
9
8
10
4
11
2nd row
2:Tune
2:Decay
2:Pan
2:AmbSend
2:DryLevel
CC#
21
20
23
18
22
3rd row
3:Tune
3:Decay
3:Pan
3:AmbSend
3:DryLevel
CC#
27
26
29
24
28
4th row
4:Tune
4:Decay
4:Pan
4:AmbSend
4:DryLevel
CC#
34
33
36
30
35
5th row
5:Tune
5:Decay
5:Pan
5:AmbSend
5:DryLevel
CC#
41
40
43
37
42
6th row
6:Tune
6:Decay
6:Pan
6:AmbSend
6:DryLevel
CC#
47
46
49
44
48
7th row
7:Tune
7:Decay
7:Pan
7:AmbSend
7:DryLevel
CC#
53
52
55
50
54
8th row
8:Tune
8:Decay
8:Pan
8:AmbSend
8:DryLevel
CC#
59
58
61
56
60
9th row
9:Tune
9:Decay
9:Pan
9:AmbSend
9:DryLevel
CC#
66
65
68
62
67
10th row
10:Tune
10:Decay
10:Pan
10:AmbSend
10:DryLevel
CC#
72
71
74
69
73
Because it’s already “borrowing” Elektrons TrigConditions, just go all the way and duplicate the ones that rely on neighbor/not neighbor
Oh yes, that’s also an idea.
Have put it on the list ✌️😊
I noticed that this is not possible change patterns in AUv3 mode with midi program change, but only in standalone mode. Will be fixed in a future version?
Thx! We will check that out! ✌️😊
Hey @Xain , I checked it out . But no, It is intentional this way. You’re supposed to use AUv3 properties, which in AUM can map from MIDI actually. So it’s not a bug, but a feature in a way. 🙂
Best from Munich
Tas
We had the great honor to be invited to Sketch Talk by @sketchaudio_ to talk about our concepts and motivations on OCTACHRON ✌️☮️😊 THX so much for having us!
https://youtu.be/BLkFRB4ixBM?si=44I3Rg8dOc_tfbjm
Hey @TasTax , how impossible would it be to have the clock rate be able to be applied per track?
Soooo edit+track : clock rate (overrides global setting)?
I’d loooove this. Also, it would be cool if clock rate could be set for odd numbers, not just even. So we could all crank out drum parts to Take 5 and become WaltzMasters.
I would like to be able to change patterns via MIDI notes - as indicated in the manual - but this does not seem to be an option when used as an AUv3? The MIDI button does not appear...
Am I missing something?
Yes, please see my second last post and answer to Xain.
Oh yes, sorry - I did see that, but my question is slightly different.
The Octochron manual discusses the ability to trigger pattern via MIDI notes but I was not aware that it was only in standalone. It would be handy feature to have in AuV3 - using a sequencer to sequence the patterns changes.
Anyway, I cannot find a way to access the necessary AuV3 properties in Drambo, it's mapping system is not as open as AUM's. Perhaps some Drambo guru can correct me?
Ha ha, yes. As you might guess, only very little things seem impossible to us 😊
But next things are iPhone version and nudging. So we have to concentrate on that at the moment. But it could definitely be a nice feature. We already have it on our list. But did you try out trigger condition in the modulations part?
For some cases, it could do something a bit similar I would say.
Enjoy, and best greetings from Munich ✌️🙂
Tas
Hello, @stim
I will now make two posts about the configuration(?) in the combination of Standalone-Drambo and AUv3-Octachron.
(Note: I’m not a Drambo guru, and I’m an eternal newbie about MIDI).
*
-The 1st post will be taken directly from the method posted on this thread by Octachron developers. @TasTax @reinerspass
-The 2nd post is an improvement on the method I posted earlier. (However, I am very bad at explaining things).
-The context of each method is different in the 1st and 2nd posts.
-The youtube video by Octachron developers may help users learn how to use P-Lock(?) feature of Drambo. (As a Drambo novice, I slowed down the playback speed of the video and watched it several times).
-The method I will describe in the 2nd post is how to switch AUv3-Octachron pattern from host-Drambo's built-in virtual MIDI keyboard.
However, users can switch pattern by tapping directly on AUv3-Octachron’s pattern itself, without having to go through such a tedious setup.
So there may be no real meaning or usefulness in doing my method.
However, by applying my explanation, you may or may not be able to use it in some other way on Drambo, but I’m not sure.
1st post
https://forum.audiob.us/discussion/32757/octachron-midi-drum-sequencer-auv3-by-markus-teufel/p21
https://forum.audiob.us/discussion/32757/octachron-midi-drum-sequencer-auv3-by-markus-teufel/p23
2nd post
I write an improved version of my earlier post on page 23 of this thread, ‘How to switch AUv3-Octachron pattern from Drambo's built-in virtual MIDI keyboard’ below.
-The improvement is that a ‘flickering’ caused by ‘MIDI feedback’ no longer occurs.
-There is no need to read the earlier post of mine in order to read this latest post of mine.
*
-The two attached ‘.zip’ files are ‘.mov’ video files. One video file recorded with iPadOS feature was split in two to circumvent(?) the file size limit for uploading to this forum.
-To circumvent the limit on the size of files that can be uploaded to the forum, ‘Video Compressor･’ app was used to reduce the size of the two video files. The two video files could be played using iPadOS feature.
-As the video files could not be uploaded to the forum, the extension was changed to a ‘.zip’ file using iPadOS compression feature.
*
Supplementary explanation of Drambo's initial state about the attached ‘Video File 1’
-When you tap the hamburger icon on Drambo and tap ‘New’, multiple templates are displayed. In my case, I chose the template that is probably the top one, on the video file. This choice was random and had no meaning or intent.
-AUv3-Octachron was loaded into ‘Audio Unit MIDI Processor’ module in DEVICE in MIDI in Library in Drambo.
*
Video file 1
at 00:05
Be sure to put a check mark on from ACTIVATE PATTERN 1 to/through 8, in that order. Otherwise, the order of the attached virtual knobs will be switched.
at 00:15
After tapping ‘A’ in the attached ‘image file 1’, tap ‘B’ twice.
at 01:29
Tap the left ‘<‘ button on the virtual MIDI keyboard several times.
*
Video file 2
after 01:07
The ‘flickering’ problem:
Suppose a MIDI note that is not set in ‘MIDI NOTE FILTER’ module is input from Drambo's built-in virtual MIDI keyboard. In this case, whether Drambo's ▶️ switch is disabled or enabled, the red circle in the attached ‘image file 2’ keeps flickering.
(As a MIDI novice, I thought the flickering might cause some trouble. However, when I posted the method earlier on page 23 of this thread, I could not figure out how to turn off the flickering).
*
Information other than the attached two video files on this post
-Incidentally, when AUv3 ‘KB-1’ app was configured in front of MIDI OUTPUT module and MIDI notes were input from the KB-1 virtual MIDI keyboard instead of from Drambo's built-in virtual MIDI keyboard, no flickering occurred. (Please see the attached ‘image file 3’).
-Even if the MIDI OUTPUT module is not loaded on Drambo, it is ‘probably’ possible to switch Octachron’s pattern with MIDI note from a hardware MIDI controller, but I’m not sure.
(In the first place, situations where ‘flickering’ occurs may be rare cases.
If the user [= me] does not intend to use Drambo's built-in virtual MIDI keyboard to change Octachron’s pattern, there might be no need to use MIDI OUTPUT module and set MIDI feedback mode there).
*
If you want to use only certain keys of Drambo's built-in virtual MIDI keyboard for AUv3-Octachron pattern switching
For example:
C-2, D-2, E-2, F-2, G-2, (Edited) F-2 A-2 (/Edited), B-2 and C-1
If Drambo is configured to the states in the attached ‘image files 4 and 5’, it might work just fine.
(There may be a smarter way to set up Drambo's modules, but I’m not familiar with Drambo so I have no idea).
*
If you want to know more about Drambo, you might want to ask in BeepStreet forum.