Audiobus: Use your music apps together.

What is Audiobus?Audiobus is an award-winning music app for iPhone and iPad which lets you use your other music apps together. Chain effects on your favourite synth, run the output of apps or Audio Units into an app like GarageBand or Loopy, or select a different audio interface output for each app. Route MIDI between apps — drive a synth from a MIDI sequencer, or add an arpeggiator to your MIDI keyboard — or sync with your external MIDI gear. And control your entire setup from a MIDI controller.

Download on the App Store

Audiobus is the app that makes the rest of your setup better.

OCTACHRON MIDI Drum Sequencer AUv3 by Markus Teufel

12829303234

Comments

  • Hi @cramdog

    Thank you, I really appreciate the detailed instructions. Indeed I got it to work and learned something valuable about Drambo in the process.

    However - and I don't mean to sound churlish or ungrateful - this solution is rather long-winded and 'hacky'. It would be so much easier if the note to pattern change functionality was built-in to Octachron. Since it's available in standalone, how difficult would it be to implement in Auv3? (a genuine question, no sarcasm intended!).

    The benefit would be to allow the user to sequence rapid switches between patterns, or to just to jam live with the keyboard from within a single drambo pattern. I think it would take Octachron to the next level, and in fact I must admit was surprised we couldn't already do it, as it is a pretty standard feature on some other drum sequencers that I have used.

  • edited February 13

    I agree. Additionally, this will enable the change of patterns in Cubasis or other hosts where the Auv3 parameters are not accessible.

  • Hi, @stim. Thanks for your reply.
    I can understand what you are saying very well. (I don't mean this in a negative way, as in “I can understand it, but I don't agree with it”).
    I was wary of my post interrupting/inhibiting a request/suggestion from you to Octachron developers. That is why I did not quote your entire post, but cut out and quoted only the Drambo part.

  • @cramdog said:
    Hi, @stim. Thanks for your reply.
    I can understand what you are saying very well. (I don't mean this in a negative way, as in “I can understand it, but I don't agree with it”).
    I was wary of my post interrupting/inhibiting a request/suggestion from you to Octachron developers. That is why I did not quote your entire post, but cut out and quoted only the Drambo part.

    Hey @cramdog

    Thanks again, I do appreciate and respect that you are aiming to help. That's what makes communities like this so great! :)

  • @TasTax said:

    @Xain said:
    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?

    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

    Well ok, but I'm not use AUM. I use Camelot Pro to manage my live hardware setup and I can't change pattern from there.

  • @TasTax said:

    @Xain said:
    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?

    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

    Well ok, but I'm not use AUM. I use Camelot Pro to manage my live hardware setup and I can't change pattern from there.

    Hey @Xain , @stim and @ShadeCR ,

    Ok, I see. We will think about it.
    And @cramdog , thx a lot for your help again!

    Best greetings from Munich
    Tas

  • Hey Everybody!

    OCTACHRON is now also on Apple Vision Pro! ✌️👀😎 Yes, at least it works in the emulator. But does it really make sense? It’s still optimized for touch, of course. Does anyone maybe have the chance to test it on the actual device? Should we keep it activated for Vision Pro in the AppStore or better deactivate it? Love to hear your opinion. THX so much for your support! 🙏😊

  • @TasTax said:

    Hey @Xain , @stim and @ShadeCR ,

    Ok, I see. We will think about it.
    And @cramdog , thx a lot for your help again!

    Best greetings from Munich
    Tas

    Hi Tas,

    That's great, thank you for considering this!!

    While I'm here, allow me to suggest a few more cheeky requests, just to throw into the mix:

    • allow cc control of the swing parameter
    • Indeed, allow swing per track. Swing and offset per track were possible on the old Emu command stations and made for some very interesting patterns.
    • I see mutes per track, but I miss track solo. I know I can do this at the sound source, but would it would be cool to control everything from a single touch interface.

    Anyway, I must say that you have done a really great job on Octachron so far, all credit to you!

    Kind regards from Greece,
    stim

  • @stim said:

    @TasTax said:

    Hey @Xain , @stim and @ShadeCR ,

    Ok, I see. We will think about it.
    And @cramdog , thx a lot for your help again!

    Best greetings from Munich
    Tas

    Hi Tas,

    That's great, thank you for considering this!!

    While I'm here, allow me to suggest a few more cheeky requests, just to throw into the mix:

    • allow cc control of the swing parameter
    • Indeed, allow swing per track. Swing and offset per track were possible on the old Emu command stations and made for some very interesting patterns.
    • I see mutes per track, but I miss track solo. I know I can do this at the sound source, but would it would be cool to control everything from a single touch interface.

    Anyway, I must say that you have done a really great job on Octachron so far, all credit to you!

    Kind regards from Greece,
    stim

    Thank you, and yes, added to our (quite long) list 😊

  • edited February 18

    @TasTax @reinerspass
    I made Otorii gadget and Abu Dhabi gadget versions of AUv3-Korg Gadget latest ‘mapping E’ for Octachron.

    -I’ve never posted mappings of Otorii gadget and Abu Dhabi gadget on this thread before.
    -Both Otorii and Abu Dhabi are IAPs, but I didn’t purchase them so I copy-pasted parameters from the linked page below. (Thanks to forum members solador78, uberhaus, wim).
    -The linked page below was probably made before Korg Gadget supports AUv3, so there may be some differences from latest AUv3-Korg Gadget(s) parameters. In that case, I apologize.

    https://wiki.audiob.us/doku.php?id=korg_gadget_2

  • Otorii MIDI note ‘mapping E’

    -12 rows version: Parameters order were not edited from MIDI #CC Assign.

    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"))

    \

    Otorii MIDI CC ‘mapping E’

    *
    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
    22
    23

    *
    3rd row

    3:Start
    3:Hold
    3:Decay
    3:Pitch
    3:Pan
    3:Level

    CC#
    24
    25
    26
    27
    28
    29

    *
    4th row

    4:Start
    4:Hold
    4:Decay
    4:Pitch
    4:Pan
    4:Level

    CC#
    30
    31
    33
    34
    35
    36

    *
    5th row

    5:Start
    5:Hold
    5:Decay
    5:Pitch
    5:Pan
    5:Level

    CC#
    37
    39
    40
    41
    42
    43

    *
    6th row

    6:Start
    6:Hold
    6:Decay
    6:Pitch
    6:Pan
    6:Level

    CC#
    44
    45
    46
    47
    48
    49

    *
    7th row

    7:Start
    7:Hold
    7:Decay
    7:Pitch
    7:Pan
    7:Level

    CC#
    50
    51
    52
    53
    54
    55

    *
    8th row

    8:Start
    8:Hold
    8:Decay
    8:Pitch
    8:Pan
    8:Group

    CC#
    56
    57
    58
    59
    60
    61

    *
    9th row

    9:Start
    9:Hold
    9:Decay
    9:Pitch
    9:Pan
    9:Level

    CC#
    62
    63
    65
    66
    67
    68

    *
    10th row

    10:Start
    10:Hold
    10:Decay
    10:Pitch
    10:Pan
    10:Level

    CC#
    69
    70
    71
    72
    73
    74

    *
    11th row

    11:Start
    11:Hold
    11:Decay
    11:Pitch
    11:Pan
    11:Level

    CC#
    75
    76
    77
    78
    79
    80

    *
    12th row

    12:Start
    12:Hold
    12:Decay
    12:Pitch
    12:Pan
    12:Level

    CC#
    81
    82
    83
    84
    85
    86

  • Abu Dhabi MIDI note ‘mapping E’

    -16 rows version: Parameters order were not edited from MIDI #CC Assign.

    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"))

    \

    Abu Dhabi MIDI CC ‘mapping E’

    *
    1st row

    1:Attack
    1:Reverse
    1:Decay
    1:Pitch
    1:Pan
    1:Level

    CC#
    4
    5
    8
    9
    10
    11

    *
    2nd row

    2:Attack
    2:Reverse
    2:Decay
    2:Pitch
    2:Level
    2:Pan

    CC#
    18
    19
    20
    21
    22
    23

    *
    3rd row

    3:Attack
    3:Reverse
    3:Decay
    3:Pitch
    3:Level
    3:Pan

    CC#
    24
    25
    26
    27
    28
    29

    *
    4th row

    4:Attack
    4:Reverse
    4:Decay
    4:Pitch
    4:Level
    4:Pan

    CC#
    30
    31
    33
    34
    35
    36

    *
    5th row

    5:Attack
    5:Reverse
    5:Decay
    5:Pitch
    5:Level
    5:Pan

    CC#
    37
    39
    40
    41
    42
    43

    *
    6th row

    6:Attack
    6:Reverse
    6:Decay
    6:Pitch
    6:Level
    6:Pan

    CC#
    44
    45
    46
    47
    48
    49

    *
    7th row

    7:Attack
    7:Reverse
    7:Decay
    7:Pitch
    7:Level
    7:Pan

    CC#
    50
    51
    52
    53
    54
    55

    *
    8th row

    8:Attack
    8:Reverse
    8:Decay
    8:Pitch
    8:Level
    8:Pan

    CC#
    56
    57
    58
    59
    60
    61

    *
    9th row

    9:Attack
    9:Reverse
    9:Decay
    9:Pitch
    9:Level
    9:Pan

    CC#
    62
    63
    65
    66
    67
    68

    *
    10th row

    10:Attack
    10:Reverse
    10:Decay
    10:Pitch
    10:Level
    10:Pan

    CC#
    69
    70
    71
    72
    73
    74

    *
    11th row

    11:Attack
    11:Reverse
    11:Decay
    11:Pitch
    11:Level
    11:Pan

    CC#
    75
    76
    77
    78
    79
    80

    *
    12th row

    12:Attack
    12:Reverse
    12:Decay
    12:Pitch
    12:Level
    12:Pan

    CC#
    81
    82
    83
    84
    85
    86

    *
    13th row

    13:Attack
    13:Reverse
    13:Decay
    13:Pitch
    13:Level
    13:Pan

    CC#
    87
    88
    89
    90
    91
    92

    *
    14th row

    14:Attack
    14:Reverse
    14:Decay
    14:Pitch
    14:Level
    14:Pan

    CC#
    93
    94
    95
    102
    103
    104

    *
    15th row

    15:Attack
    15:Reverse
    15:Decay
    15:Pitch
    15:Level
    15:Pan

    CC#
    105
    106
    107
    108
    109
    110

    *
    16th row

    16:Attack
    16:Reverse
    16:Decay
    16:Pitch
    16:Level
    16:Pan

    CC#
    111
    112
    113
    114
    115
    116

  • Is it possible to trigger smart randomize via midi/AUV3 msg? Either standalone or plugin?

  • @GUB said:
    Is it possible to trigger smart randomize via midi/AUV3 msg? Either standalone or plugin?

    Hello, @GUB.
    At this time, the feature you mentioned is not available in either Standalone Octachron or AUv3 Octachron.
    So if you want to request the feature, you might want to use ‘@‘ to Octachron developers’ names ‘TasTax’ and ‘reinerspass’ on this thread.
    (Of course I have no intention of coerce[?] you to do so.)

    *
    Note: I wrote the above not only for GUB but also for those who are new to this thread.

  • edited March 12

    Note: The following is not an issue or bug with the apps (Octachron and AUM). It is a report of what I experienced and realized due to my personal human error.

    *
    The radio switch to the left of Octachron icon loaded on a node on AUM is automatically assigned Octachron’s Activate Pattern 3 feature/parameter by default.

    If users save (and load) an AUM session after mistakenly checking the radio switch, Octachron’s pattern 3 will automatically(?) be played when users tap the ▶️ switch on AUM.
    So, users might want to pay a little attention to it. I could not figure out the cause of the issue and had to struggle with it for about 10 minutes.

  • @GUB said:
    Is it possible to trigger smart randomize via midi/AUV3 msg? Either standalone or plugin?

    Hey @GUB , no, unfortunately that is not possible yet.

    And @cramdog , thx, again for the mappings. Very cool. We will work them in pretty soon.

    Best from Munich 🙂
    Tas

  • "Additionally

    It would be nice to have a way to add ghost notes
    Ability to set individual velocity on ratchet steps
    Ability to set which ratchet steps play to allow more unique patterns"

    • Yes!!!

    @Djw66 said:
    I'm starting to use Octachron for sequencing now and after using Stochas & Seaquences (Reason Rack) on PC and wish that it had one missing feature that no other ISO sequencer has (that I can find) and that is Note Rules.

    Note rules allow you to tie playing or not playing notes based on another note and its chance/probability

    i.e. Set a % chance of Drum A playing on a step and if this Drum plays Drum 1, 2 etc.. on the same step do not play or on preceding steps do not play, but Drum 3, 4 do play.

    This allows setting up fills based on chance/probability

    From Stocahs documentation:

    Additionally

    1. It would be nice to have a way to add ghost notes
    2. Ability to set individual velocity on ratchet steps
    3. Ability to set which ratchet steps play to allow more unique patterns
  • Thanks. I'm not interested in the feature so much for performance, rather for the convenience of reduced menu-diving.

    Enjoying the app!; carry on.

    @TasTax said:

    @GUB said:
    Is it possible to trigger smart randomize via midi/AUV3 msg? Either standalone or plugin?

    Hey @GUB , no, unfortunately that is not possible yet.

    And @cramdog , thx, again for the mappings. Very cool. We will work them in pretty soon.

    Best from Munich 🙂
    Tas

  • Thank you for the info!

    @cramdog said:

    @GUB said:
    Is it possible to trigger smart randomize via midi/AUV3 msg? Either standalone or plugin?

    Hello, @GUB.
    At this time, the feature you mentioned is not available in either Standalone Octachron or AUv3 Octachron.
    So if you want to request the feature, you might want to use ‘@‘ to Octachron developers’ names ‘TasTax’ and ‘reinerspass’ on this thread.
    (Of course I have no intention of coerce[?] you to do so.)

    *
    Note: I wrote the above not only for GUB but also for those who are new to this thread.

  • easy jams/noodlings with OCTACHRON
    Octachron’s SONG MODE switch was enabled on every jam.

    *
    jam 1, image: ‘canis-a-rhythm (101 to 0)’, an abandoned maledict scummy track on a floptical disk found in a bando, unknown authorship
    The composer of the track is said to have expired from a very rare form of sepsis. The first discoverer of the floptical disc bought the farm from an unknown tick bite. People who hear the track say they feel itches in canals. In fact, this ‘itches in canals’ is singular, not plural. It is unclear whether the itching sense that people share/feel is that of the first discoverer of the floptical disc or the unknown composer of the track.

    Apps
    Octachron x3
    -Octachron-1 controlled(sequenced?) Dagger’s notes, Rate[Freq], and AUM’s LP/HP Filter.
    -Octachron-2 controlled Dublin’s notes.
    -Octachron-3 controlled Splat-to-Clat drums.
    Dagger synth (lead), Dublin Korg Gadget synth (bass), Splat-to-Clat, UA Bass Mint, UA lo-fi-af, Saturn 2, TB Barricade, AUM, Wavebox

    *
    jam 2, image: THIS IS A TRUE STORY. (™️ Coen brothers)
    It was a first and last garage punk band formed in a history of our little hamlet. The band was disbanded because of a dispute over a distribution of future appearance fee. Apparently it happened two minutes after the band was named GG Allin Revival. In our lifetimes we called it GGR in our minds.

    Apps
    Octachron x3
    -Octachron-1 controlled Dagger’s notes.
    -Octachron-2 controlled same Dagger’s Frequency[Cutoff].
    (Octachron-1 and Octachron-2 had different CLOCK DIVIDER values for one Dagger synth).
    -Octachron-3 controlled Splat-to-Clat drums.
    Dagger synth, Saturn 2 x2, TB Barricade, AUM, Wavebox

    (The ‘jam 2.mp3’ is a LUFS-edited version. An original version had too high LUFS value, so I deleted it from this thread before)

  • @cramdog said:
    easy jams/noodlings with OCTACHRON
    Octachron’s SONG MODE switch was enabled on every jam.

    *
    jam 1, image: ‘canis-a-rhythm (101 to 0)’, an abandoned maledict scummy track on a floptical disk found in a bando, unknown authorship
    The composer of the track is said to have expired from a very rare form of sepsis. The first discoverer of the floptical disc bought the farm from an unknown tick bite. People who hear the track say they feel itches in canals. In fact, this ‘itches in canals’ is singular, not plural. It is unclear whether the itching sense that people share/feel is that of the first discoverer of the floptical disc or the unknown composer of the track.

    Apps
    Octachron x3
    -Octachron-1 controlled(sequenced?) Dagger’s notes, Rate[Freq], and AUM’s LP/HP Filter.
    -Octachron-2 controlled Dublin’s notes.
    -Octachron-3 controlled Splat-to-Clat drums.
    Dagger synth (lead), Dublin Korg Gadget synth (bass), Splat-to-Clat, UA Bass Mint, UA lo-fi-af, Saturn 2, TB Barricade, AUM, Wavebox

    *
    jam 2, image: THIS IS A TRUE STORY. (™️ Coen brothers)
    It was a first and last garage punk band formed in a history of our little hamlet. The band was disbanded because of a dispute over a distribution of future appearance fee. Apparently it happened two minutes after the band was named GG Allin Revival. In our lifetimes we called it GGR in our minds.

    Apps
    Octachron x3
    -Octachron-1 controlled Dagger’s notes.
    -Octachron-2 controlled same Dagger’s Frequency[Cutoff].
    (Octachron-1 and Octachron-2 had different CLOCK DIVIDER values for one Dagger synth).
    -Octachron-3 controlled Splat-to-Clat drums.
    Dagger synth, Saturn 2 x2, TB Barricade, AUM, Wavebox

    (The ‘jam 2.mp3’ is a LUFS-edited version. An original version had too high LUFS value, so I deleted it from this thread before)

    Cool, thank you very much! Would love to here this somewhere on social media! :blush:

  • @cramdog said:
    Gladstone gadget mapping

    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"))

    *

    Attention

    HH Close and HH Open and Tom Hi and Tom Mid and Tom Lo were written as they appeared on the screen when AUv3-Gladstone loaded.
    However, I think people have different writing preferences for those, such as OPHH, OPHh, ClHh, CLHH, HI TOM, Mid Tom, etc.
    So, if my mappings are adopted, I would appreciate it if the developers of Octachron (@TasTax @reinerspass) could edit them to their preferred notation.

    Others
    I tested a combination of AUM, AUv3-Octahcron and AUv3-Gladstone.
    The sound from AUv3-Gladstone was not output from the iPad speakers as per the pattern from Octahcron.
    It seems that AUM's sample rate of 48 kHZ causes this problem in my environment.
    When I changed the sample rate of AUM to 44.1 kHZ, the sound was output smoothly.
    (I think I’ve read a report similar to this somewhere on the forum, but I’m not sure).

    Hey @cramdog ,

    thx so much again for the mappings. I am just about to integrate them in OCTACHRON. The thing is, we now apply them in the JSON format. So the first lines of this would be like:

    {
    "notes": [
    {
    "note": 36,
    "title": "Kick",
    "ccModel": [
    {"name": "Tune", "address": 9},
    {"name": "Decay", "address": 8},
    {"name": "Pan", "address": 10},
    {"name": "AmbSend", "address": 4},
    {"name": "DryLevel", "address": 11}
    ]
    },
    {
    "note": 37,
    "title": "Snare",
    "ccModel": [
    {"name": "Tune", "address": 21},
    {"name": "Decay", "address": 20},
    {"name": "Pan", "address": 23},
    {"name": "AmbSend", "address": 18},
    {"name": "DryLevel", "address": 22}
    ]
    },
    {
    "note": 38,
    "title": "Snare 2",
    "ccModel": [
    {"name": "Tune", "address": 27}, ...

    So this is our format, we can handle the best, if you would like to post more mappings.
    We do this to enable save and shareable user mappings in the the next update :smile:
    So far so good.

    But I don't own the Korg gadget myself yet, so my questions are:

    1. I applied the CC values in the order of the instruments so in your screenshots No.1 to Kick, No.2 to Snare, No.3 to Snare 2 and so on. Do you think this is correct?

    2. After No. 10 you also show some CC values for Comp Thresh, Comp Ratio ans so on. I don't know if you can say this, but do they not also have to be assigned to a midi note? And if yes to which? Or do you maybe got screenshots of OCTACHRON how you assigned it here? Or do you in best case maybe even have an idea how our code should look like here?

    Would be great to hear back from you again

    Thx again and best greetings from Munich :smile:
    Tas

  • edited March 22

    @TasTax said:
    But I don't own the Korg gadget myself yet, so my questions are:

    1. I applied the CC values in the order of the instruments so in your screenshots No.1 to Kick, No.2 to Snare, No.3 to Snare 2 and so on. Do you think this is correct?

    I think the order is correct.

    Note: It is possible that I have misunderstood the context and meaning of what you mean by "correct".

    *
    What I realized when I read your question is that my choice of names—Kick and Snare and Tom Mid and etc.—is not a good one. For this I must apologize to you.
    I think Octachron’s row names should be "1" and "2" and……and "9" and "10" instead of Kick and Snare and……and Crash and Ride.

    Context
    I have realized before that when I have AUv3 Splat-to-Clat and AUv3 Octachron displayed side by side on AUM screen, the 1st pad name (C3) on the former and the 1st row name (C3) on the latter are the same, making it easier to locate the notes and samples.
    So, to make AUv3 Gladstone Gadget pad names match AUv3 Octachron row names in a clear way, I think Octachron row names should be ‘1, 2, 3, 4, 5, 6, 7, 8, 9, and 10’, instead of Kick and Snare and……Crash and Ride. I’m so sorry.

    -In addition, some Gladstone’s factory(?) drum kits load a ‘percussion’ sample instead of a ‘kick’ in position of pad 1.
    -In addition, there is the possibility for users to use user-customized Gladstone mappings. (Example: User preset with no kick sample)

    @TasTax said:
    2. After No. 10 you also show some CC values for Comp Thresh, Comp Ratio ans so on. I don't know if you can say this, but do they not also have to be assigned to a midi note? And if yes to which?

    Sorry if the following was not the answer to your question.

    I tested sending MIDI CC (⬅️ instead of MIDI note. please check attached screenshot 1.) from KB-1 to Comp Gain knob of AUv3 Gladstone gadget.
    I loaded AUv3 KB-1 (as Audio Unit MIDI Processor) and AUv3 Gladstone gadget on AUM. (screenshot 2)
    I made a Continous knob for CC 77 in KB-1 app and confirmed that the CC 77 knob could control actual/real Comp Gain (CC#77) knob of AUv3 Gladstone gadget’s UI. (screenshot 3 and gif)

    *
    My another answer

    I think that the following "MIDI CC parameters that effect all parts" in AUv3 Gladstone gadget will work at any MIDI Notes value from 0 to 127.

    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

    After setting some MIDI note values (0, 36, 127) to AUv3 Octachron, on AUM, I tested the MIDI CC parameters above. As a result, I confirmed that they do work.

    -However, I did not do any detailed testing or edge case testing. So it is possible that I may have missed something.

    *
    Note: I’m not positive about including "MIDI CC parameters that effect all parts" in mapping. Here is a brief history of how it happened.

    I have posted the following three versions of Octachron mappings for the AUv3 Korg Gadget on this thread.

    Mapping (unnamed): They don’t contain MIDI CC parameters.
    ⬇️
    Mapping "B": They contain all MIDI CC parameters, but have multiple shortcomings.
    ⬇️
    Mapping "E": From them, "MIDI CC parameters that effect all parts" were omitted. They include MIDI CC parameters that "effect only each part". (e.g.. for Kick only, for Snare only, and etc.)

    I was going crazy trying to include the "MIDI CC parameters that effect all parts" in the mapping until I posted mapping "B" on this thread. However, I was unaware that the "MIDI CC parameters that effect all parts" would not work without the CC ON EVERY STEP feature enabled on Octachron. I saw that as a problem.
    -I made mapping "E" out of that regret.
    -In mapping "E" which I posted on this thread, all "MIDI CC parameters that effect all parts" were omitted.
    -I personally would like to see Mapping "E" adopted when updating Octachron.

    @TasTax said:
    Or do you maybe got screenshots of OCTACHRON how you assigned it here?

    (Sorry if I have misunderstood something.)
    There are no screenshots. This is because I have not made a complete and finished mapping on AUv3 Octachron.
    So instead(?), I made and tested fragmented Octachron mappings for AUv3 Korg Gadget on AUM. And I posted them on this thread as virtual (or hypothetical?) mappings.

    @TasTax said:
    Or do you in best case maybe even have an idea how our code should look like here?

    (Sorry if I have misunderstood something.)
    Does this mean I have an idea about a MIDI CC template for this thread? If so, I’m not confident in my ability to answer this. It is a question beyond my ability to answer.
    So I would like to leave it to forum members to answer.

    (EDITED)
    I now think this is probably a question meaning "Can you write a Mapping B for AUv3 Gladstone gadget with the above ‘MIDI CC editable template’ style and post it on this thread?". (⬅️ If I am mistaken, I am sorry, @TasTax.)
    My answer is "I can probably do that".
    Mapping B (probably) works fine on Octachron. However, for reasons mentioned on my next post, I do not want to recommend Mapping B to Octachron users.
    (/EDITED)

    1.jpg 301.1K
    2.jpg 212.4K
    3.jpg 451.8K
  • edited March 21

    @TasTax said:
    2. After No. 10 you also show some CC values for Comp Thresh, Comp Ratio ans so on. I don't know if you can say this, but do they not also have to be assigned to a midi note? And if yes to which? Or do you maybe got screenshots of OCTACHRON how you assigned it here? Or do you in best case maybe even have an idea how our code should look like here?

    My apologies!
    Now I probably got the meaning of the above quote correctly.
    The reason I needed some time to figure it out is because in the latest mapping “E” I posted, the following parameters are not included in it.

    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

    I would like to cancel my request for mapping "B", which includes the above parameters (Comp Thresh, Comp Ratio, etc.).
    The reason is stated in the following quote. However, I have not explained it well enough to you. I am very sorry.
    I only want to request the mapping "E".

    @cramdog said:
    @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.

    https://forum.audiob.us/discussion/32757/octachron-midi-drum-sequencer-auv3-by-markus-teufel/p31

  • Hey @cramdog ,

    Ok, great, thank you. We will check this out! ✌️😊

  • @TasTax @reinerspass
    Issue
    When an AUM session with the below Octachron’s mapping for Ruismaker is saved and it is loaded, CC MODULATION parameter names (TUNE, DECAY, PERSONALITY, LEVEL, PAN, BITCRUSH, DELAY SEND, DRIVE) are displayed as "CC".

    AUM//AUv3 OCTACHRON//Octachron icon//PRESETS/MIDI MAPPING/APPS//LOAD APPS MAPPING/RUISMAKER

    *
    I confirmed that something similar happens with Octachron’s mapping for Ruismaker FM.

    *
    App store Octachron v1.8.1(160)
    iPadOS v16.7.2
    iPad Pro 10.5 inch

    *
    It seems similar to my earlier report below, but I'm not sure.

    @cramdog said:
    @TasTax @reinerspass
    Issue
    A name entered in SETTINGS in CC MODULATIONS is not saved.

    *
    How to reproduce
    Load Octachron on AUM.
    Tap ‘VELOCITY’ of Octachron and tap EDIT button of CC in CC MODULATIONS in MODULATIONS.
    Enter any name on SETTINGS.
    Tap Octachron icon in AUv3-Octachron.
    Tap SAVE in USER PRESETS in PRESETS and enter any name to save the preset.
    Then the user preset is loaded, the name entered in the above SETTINGS will not be displayed and will be displayed as ‘CC’.

    *
    Octachron v1.8.1 (Apple App Store)
    iPadOS v16.7.2
    iPadPro 10.5 inch

    https://forum.audiob.us/discussion/32757/octachron-midi-drum-sequencer-auv3-by-markus-teufel/p30

  • @cramdog said:
    @TasTax @reinerspass
    Issue
    When an AUM session with the below Octachron’s mapping for Ruismaker is saved and it is loaded, CC MODULATION parameter names (TUNE, DECAY, PERSONALITY, LEVEL, PAN, BITCRUSH, DELAY SEND, DRIVE) are displayed as "CC".

    >

    Ok, thx!

  • 😍😍😍📲📲📲🤳🏼

  • edited March 25

    Heyhey everybody!

    OCTACHRON Beta version is now also on iPhone + save and sharable MIDI mappings. (Please check the save option under Presets > Midi Mapping. After you saved one mapping you get a new option “User” there to load them again.)
    Please test it and use the Testflight beta feature for bug reporting ✌️🎶😎
    For effort reasons we had to concentrate on the landscape view and do a little compromise on the popups. But we think it works quite well and hope you like it too of course.
    And please have fun but please don’t publish jams with it until the official version is on the AppStore, hope you understand.

    Enjoy and best greetings from Munich 😊
    Tas

  • @TasTax said:
    Heyhey everybody!

    OCTACHRON Beta version is now also on iPhone + save and sharable MIDI mappings. (Please check the save option under Presets > Midi Mapping. After you saved one mapping you get a new option “User” there to load them again.)
    Please test it and use the Testflight beta feature for bug reporting ✌️🎶😎
    For effort reasons we had to concentrate on the landscape view and do a little compromise on the popups. But we think it works quite well and hope you like it too of course.
    And please have fun but please don’t publish jams with it until the official version is on the AppStore, hope you understand.

    Enjoy and best greetings from Munich 😊
    Tas

    Just tried hosting in loopy pro on iPhone 15 pro max and all was perfect 👌

    Portrait would be great if there was a way to side scroll the grid.

Sign In or Register to comment.