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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

OCTACHRON MIDI Drum Sequencer AUv3 by Markus Teufel

1…353637383941»

Comments

  • TasTaxTasTax

    @cramdog said:
    @TasTax
    I have come to my conclusion.
    I have no problem without Global CLOCK DIVIDER.
    Because I mistakenly confused Global CLOCK DIVIDER with the aforementioned fictitious "SHIFT button to select and edit all CLOCK DIVIDERs" feature and "pseudo-reset button of all CLOCK DIVIDERs" feature in my head. However, these two features do not actually work. So, I do not need the Global CLOCK DIVIDER, which I mistakenly thought I needed it to use these two features.
    (And I’m not going to request or suggest these two features [Practically one feature?].)

    Thx for your thoughts 🙂
    Does anybody else have an opinion on this?

  • cramdogcramdog

    @TasTax said:

    @cramdog said:
    @TasTax
    I have come to my conclusion.
    I have no problem without Global CLOCK DIVIDER.
    Because I mistakenly confused Global CLOCK DIVIDER with the aforementioned fictitious "SHIFT button to select and edit all CLOCK DIVIDERs" feature and "pseudo-reset button of all CLOCK DIVIDERs" feature in my head. However, these two features do not actually work. So, I do not need the Global CLOCK DIVIDER, which I mistakenly thought I needed it to use these two features.
    (And I’m not going to request or suggest these two features [Practically one feature?].)

    Thx for your thoughts 🙂
    Does anybody else have an opinion on this?

    By the way, after that I read a hardware groove box manual and probably realized/understood the aforementioned Global CLOCK DIVIDER may be overkill.
    In other words, three (= Global, Pattern, Track) CLOCK DIVIDERs may be too much as you said.
    Two (= Pattern, Track) would be enough. [Blade Runner meme]

  • cramdogcramdog
    edited February 25

    @TasTax
    The following 2 reports are about my confirming:

    1.
    I rechecked and confirmed the three issues below were fixed. Thanks.
    -After CLEAR feature of edited-VELOCITY or edited-STEP REPEATS or edited-OFFSET is used, OCTACHRON crashes.

    2.
    I tested and confirmed that both “Pattern's CLOCK DIVIDER value” and “Tracks' CLOCK DIVIDER values” are copied/pasted as is.
    (I consider the “copied/pasted as is” above is an improvement—not a fix—for Octachron users. Thanks.)

  • cramdogcramdog
    edited February 26

    @TasTax
    The following are 3 (or 4 or 5) issues of TestFlight Octachron v2.1.0 (202)
    (Note: I used the 2 Spoiler feature below for 4 screenshots and 1 after-mentioned ‘timeline’.)

    Issue #1
    “On or after a 2nd loop / On a 2nd and subsequent loops” of AUv3-Octachron, a first step’s “sound” (or all first steps’ “sounds”) of a pattern may not sound. However, I have no idea what exact conditions or procedures are necessary to reproduce this issue.
    [Incidentally, this issue probably does not occur when using AppleAppStore-Octachron v2.0.5.]

    I can reproduce this issue in my environment with the following settings.
    [Note: I routed(?) AUv3-Octachron with AUv3-Poison-202 synth on AUM (= host app).]

    AUv3-Octachron settings:
    Only the following 2 things need to be changed/edited in AUv3-Octachron. (No preset loading or other operations are required.)
    1. Only the 1st step in the 1st Track needs to be filled. However, for the purpose of this test, it is better to fill all 16 steps to auditorily(?) and visually confirm the issue/phenomenon of no sound.
    2. Set all 16 GATE LENGTH of the 1st Track to 0% using SHIFT button.

    AUM settings:
    -The only AUM’s Sample Rate I tested was 44.1 kHz. (It was a rough test using only an iPad, and I did not test at any other Sample Rate. So I have no idea if the issue can be reproduced in other environments.)
    -I think AUM Buffer Size larger than 512 (e.g., 1024 or 2048) are more likely to reproduce the issue. Incidentally, AppleAppStore Octachron v2.0.5 does not have this issue with any Buffer Size setting from 32 to 2048. However, I may be misunderstanding something about how TestFlight-Octachron's GATE LENGTH feature works. In other words, I may be reporting something as an issue now that is not an issue. In that case, I’m sorry.
    -The AUM’s tempo for my testing were 120 (= default) and 20 (= minimum). And the issue could/can be reproduced at either tempo.

    Routing:
    -Route AUv3-Octachron to any AUv3 synth. (I used AUv3-Poison-202 synth.)
    -If a synth preset for testing has low values for Atack and Release in ADSR, I guess it is easy to confirm the issue/phenomenon that no sound is output from the 1st step.

    Issue #2
    When loading a session save data including AUv3-Octachron on AUM, pre-edited steps of all patterns of AUv3-Octachron are not displayed at all. Because they are temporarily “invisible” due to this issue. However, the pre-edited steps exist, so the first loop can output “MIDI notes / routed synth app’s sounds” correctly.
    -After a first loop finished, all patterns (= pre-edited steps) are displayed.
    -Alternatively, tapping on any pattern will display all patterns (= pre-edited steps) even if the first loop is still unfinished, or even before AUM’s ▶️ button is tapped.

    Issue #3
    The “gray-moving-playback-position(?)” on “8th-Track of total-8-Tracks” appears and disappears with each loop**.
    Note:
    -I have no idea how to reproduce this issue. I’m sorry.
    -I have no idea if the same or similar issue occurs when the NUMBER OF TRACKS is other than 8.

    **The actual timeline of my test is below.

    I tapped AUM’s ▶️ button.
    1st loop: (I may have not realized this issue, and I did not take a screenshot.)
    2nd loop: (I may have not realized this issue, and I did not take a screenshot.)
    3rd loop: (I may have not realized this issue, and I did not take a screenshot.)
    4th loop: The gray-moving-playback-position of 8th Track disappears from screen. (I took the screenshot A below.)
    5th loop: The gray-moving-playback-position of 8th Track appears on screen. (I took the screenshot B below.)
    6th loop: The gray-moving-playback-position of 8th Track disappears from screen. (I took the screenshot C below.)
    7th loop: The gray-moving-playback-position of 8th Track appears on screen. (I did not take a screenshot, but I confirmed this phenomenon.)
    8th loop: The gray-moving-playback-position of 8th Track disappears from screen. (I did not take a screenshot, but I confirmed this phenomenon.)
    9th loop……
    10th loop……
    I tapped AUM’s ⏸️ button.

    Screenshot A

    Screenshot B

    Screenshot C

    [Sorry for my very poor explanation above.]

    Issue(?) #4
    When editing a step during pattern playback(?), all gray-moving-playback-position“s” disappear for a short time.

    Issue(?) #5
    The gray-moving-playback-position“s” are not displayed on tracks where MUTE buttons are enabled. (Having said that, this behavior of Octachron may be intended by the developers. In that case, I’m sorry, since it’s not an issue.)

  • TasTaxTasTax

    @cramdog said:
    @TasTax
    The following are 3 (or 4 or 5) issues of TestFlight Octachron v2.1.0 (202)
    (Note: I used the 2 Spoiler feature below for 4 screenshots and 1 after-mentioned ‘timeline’.)

    Heyhey! Thx again for your very detailed testing and feedback. This is very valuable to us. And we will definitely check these issues. ✌️😊

  • SamSamSamSamSamSam

    @TasTax said:

    1. Offset, back and forth, for microtiming
    2. Gate length, especially for longer sounds, like melody synthesizes
    (Double Tap on fader columns to reset every mod parameter now, + shift to reset all)
    3. Clock divider per pattern and per track, also allowing e.g. triplet rhythms

    Thanks @TasTax . Those are wonderful features. I was waiting for this.
    Offset works correctly for me and seems to be well implemented. Very cool!
    I still need to test more the clock divider. That's cool and I like the possibility to use it per pattern and per track, but I'm wondering if it should also have an impact on how it is represented visually (are you sure the larger space between columns should always be after 4 divisions? I'm just questioning here, not sure at all)
    Small remark: if I double tap on clock divider, It should certainly come back to 1

  • TasTaxTasTax

    @SamSamSam said:

    @TasTax said:

    1. Offset, back and forth, for microtiming
    2. Gate length, especially for longer sounds, like melody synthesizes
    (Double Tap on fader columns to reset every mod parameter now, + shift to reset all)
    3. Clock divider per pattern and per track, also allowing e.g. triplet rhythms

    Thanks @TasTax . Those are wonderful features. I was waiting for this.
    Offset works correctly for me and seems to be well implemented. Very cool!
    I still need to test more the clock divider. That's cool and I like the possibility to use it per pattern and per track, but I'm wondering if it should also have an impact on how it is represented visually (are you sure the larger space between columns should always be after 4 divisions? I'm just questioning here, not sure at all)
    Small remark: if I double tap on clock divider, It should certainly come back to 1

    Thank you, really glad you like it. And yes, we were thinking about another visual representation as well. But this comes with some issues. But we are still thinking about it.
    And yes, reset via double tap everywhere is also on our list 🙂

  • TasTaxTasTax

    @cramdog said:
    @TasTax
    The following are 3 (or 4 or 5) issues of TestFlight Octachron v2.1.0 (202)
    (Note: I used the 2 Spoiler feature below for 4 screenshots and 1 after-mentioned ‘timeline’.)

    Issue #1
    “On or after a 2nd loop / On a 2nd and subsequent loops” of AUv3-Octachron, a first step’s “sound” (or all first steps’ “sounds”) of a pattern may not sound. However, I have no idea what exact conditions or procedures are necessary to reproduce this issue.
    [Incidentally, this issue probably does not occur when using AppleAppStore-Octachron v2.0.5.]

    I can reproduce this issue in my environment with the following settings.
    [Note: I routed(?) AUv3-Octachron with AUv3-Poison-202 synth on AUM (= host app).]

    AUv3-Octachron settings:
    Only the following 2 things need to be changed/edited in AUv3-Octachron. (No preset loading or other operations are required.)
    1. Only the 1st step in the 1st Track needs to be filled. However, for the purpose of this test, it is better to fill all 16 steps to auditorily(?) and visually confirm the issue/phenomenon of no sound.
    2. Set all 16 GATE LENGTH of the 1st Track to 0% using SHIFT button.

    AUM settings:
    -The only AUM’s Sample Rate I tested was 44.1 kHz. (It was a rough test using only an iPad, and I did not test at any other Sample Rate. So I have no idea if the issue can be reproduced in other environments.)
    -I think AUM Buffer Size larger than 512 (e.g., 1024 or 2048) are more likely to reproduce the issue. Incidentally, AppleAppStore Octachron v2.0.5 does not have this issue with any Buffer Size setting from 32 to 2048. However, I may be misunderstanding something about how TestFlight-Octachron's GATE LENGTH feature works. In other words, I may be reporting something as an issue now that is not an issue. In that case, I’m sorry.
    -The AUM’s tempo for my testing were 120 (= default) and 20 (= minimum). And the issue could/can be reproduced at either tempo.

    Routing:
    -Route AUv3-Octachron to any AUv3 synth. (I used AUv3-Poison-202 synth.)
    -If a synth preset for testing has low values for Atack and Release in ADSR, I guess it is easy to confirm the issue/phenomenon that no sound is output from the 1st step.

    Issue #2
    When loading a session save data including AUv3-Octachron on AUM, pre-edited steps of all patterns of AUv3-Octachron are not displayed at all. Because they are temporarily “invisible” due to this issue. However, the pre-edited steps exist, so the first loop can output “MIDI notes / routed synth app’s sounds” correctly.
    -After a first loop finished, all patterns (= pre-edited steps) are displayed.
    -Alternatively, tapping on any pattern will display all patterns (= pre-edited steps) even if the first loop is still unfinished, or even before AUM’s ▶️ button is tapped.

    Issue #3
    The “gray-moving-playback-position(?)” on “8th-Track of total-8-Tracks” appears and disappears with each loop**.
    Note:
    -I have no idea how to reproduce this issue. I’m sorry.
    -I have no idea if the same or similar issue occurs when the NUMBER OF TRACKS is other than 8.

    **The actual timeline of my test is below.

    I tapped AUM’s ▶️ button.
    1st loop: (I may have not realized this issue, and I did not take a screenshot.)
    2nd loop: (I may have not realized this issue, and I did not take a screenshot.)
    3rd loop: (I may have not realized this issue, and I did not take a screenshot.)
    4th loop: The gray-moving-playback-position of 8th Track disappears from screen. (I took the screenshot A below.)
    5th loop: The gray-moving-playback-position of 8th Track appears on screen. (I took the screenshot B below.)
    6th loop: The gray-moving-playback-position of 8th Track disappears from screen. (I took the screenshot C below.)
    7th loop: The gray-moving-playback-position of 8th Track appears on screen. (I did not take a screenshot, but I confirmed this phenomenon.)
    8th loop: The gray-moving-playback-position of 8th Track disappears from screen. (I did not take a screenshot, but I confirmed this phenomenon.)
    9th loop……
    10th loop……
    I tapped AUM’s ⏸️ button.

    Screenshot A

    Screenshot B

    Screenshot C

    [Sorry for my very poor explanation above.]

    Issue(?) #4
    When editing a step during pattern playback(?), all gray-moving-playback-position“s” disappear for a short time.

    Issue(?) #5
    The gray-moving-playback-position“s” are not displayed on tracks where MUTE buttons are enabled. (Having said that, this behavior of Octachron may be intended by the developers. In that case, I’m sorry, since it’s not an issue.)

    Thx again. And yes #5 is on purpose.

    But actually, I can’t re-create any of the other issues.
    Does anybody else have this problems?

  • cramdogcramdog
    edited February 26

    @TasTax said:

    @cramdog said:
    @TasTax
    The following are 3 (or 4 or 5) issues of TestFlight Octachron v2.1.0 (202)
    (Note: I used the 2 Spoiler feature below for 4 screenshots and 1 after-mentioned ‘timeline’.)

    Issue #1
    “On or after a 2nd loop / On a 2nd and subsequent loops” of AUv3-Octachron, a first step’s “sound” (or all first steps’ “sounds”) of a pattern may not sound. However, I have no idea what exact conditions or procedures are necessary to reproduce this issue.
    [Incidentally, this issue probably does not occur when using AppleAppStore-Octachron v2.0.5.]

    I can reproduce this issue in my environment with the following settings.
    [Note: I routed(?) AUv3-Octachron with AUv3-Poison-202 synth on AUM (= host app).]

    AUv3-Octachron settings:
    Only the following 2 things need to be changed/edited in AUv3-Octachron. (No preset loading or other operations are required.)
    1. Only the 1st step in the 1st Track needs to be filled. However, for the purpose of this test, it is better to fill all 16 steps to auditorily(?) and visually confirm the issue/phenomenon of no sound.
    2. Set all 16 GATE LENGTH of the 1st Track to 0% using SHIFT button.

    AUM settings:
    -The only AUM’s Sample Rate I tested was 44.1 kHz. (It was a rough test using only an iPad, and I did not test at any other Sample Rate. So I have no idea if the issue can be reproduced in other environments.)
    -I think AUM Buffer Size larger than 512 (e.g., 1024 or 2048) are more likely to reproduce the issue. Incidentally, AppleAppStore Octachron v2.0.5 does not have this issue with any Buffer Size setting from 32 to 2048. However, I may be misunderstanding something about how TestFlight-Octachron's GATE LENGTH feature works. In other words, I may be reporting something as an issue now that is not an issue. In that case, I’m sorry.
    -The AUM’s tempo for my testing were 120 (= default) and 20 (= minimum). And the issue could/can be reproduced at either tempo.

    Routing:
    -Route AUv3-Octachron to any AUv3 synth. (I used AUv3-Poison-202 synth.)
    -If a synth preset for testing has low values for Atack and Release in ADSR, I guess it is easy to confirm the issue/phenomenon that no sound is output from the 1st step.

    Issue #2
    When loading a session save data including AUv3-Octachron on AUM, pre-edited steps of all patterns of AUv3-Octachron are not displayed at all. Because they are temporarily “invisible” due to this issue. However, the pre-edited steps exist, so the first loop can output “MIDI notes / routed synth app’s sounds” correctly.
    -After a first loop finished, all patterns (= pre-edited steps) are displayed.
    -Alternatively, tapping on any pattern will display all patterns (= pre-edited steps) even if the first loop is still unfinished, or even before AUM’s ▶️ button is tapped.

    Issue #3
    The “gray-moving-playback-position(?)” on “8th-Track of total-8-Tracks” appears and disappears with each loop**.
    Note:
    -I have no idea how to reproduce this issue. I’m sorry.
    -I have no idea if the same or similar issue occurs when the NUMBER OF TRACKS is other than 8.

    **The actual timeline of my test is below.

    I tapped AUM’s ▶️ button.
    1st loop: (I may have not realized this issue, and I did not take a screenshot.)
    2nd loop: (I may have not realized this issue, and I did not take a screenshot.)
    3rd loop: (I may have not realized this issue, and I did not take a screenshot.)
    4th loop: The gray-moving-playback-position of 8th Track disappears from screen. (I took the screenshot A below.)
    5th loop: The gray-moving-playback-position of 8th Track appears on screen. (I took the screenshot B below.)
    6th loop: The gray-moving-playback-position of 8th Track disappears from screen. (I took the screenshot C below.)
    7th loop: The gray-moving-playback-position of 8th Track appears on screen. (I did not take a screenshot, but I confirmed this phenomenon.)
    8th loop: The gray-moving-playback-position of 8th Track disappears from screen. (I did not take a screenshot, but I confirmed this phenomenon.)
    9th loop……
    10th loop……
    I tapped AUM’s ⏸️ button.

    Screenshot A

    Screenshot B

    Screenshot C

    [Sorry for my very poor explanation above.]

    Issue(?) #4
    When editing a step during pattern playback(?), all gray-moving-playback-position“s” disappear for a short time.

    Issue(?) #5
    The gray-moving-playback-position“s” are not displayed on tracks where MUTE buttons are enabled. (Having said that, this behavior of Octachron may be intended by the developers. In that case, I’m sorry, since it’s not an issue.)

    Thx again. And yes #5 is on purpose.

    But actually, I can’t re-create any of the other issues.
    Does anybody else have this problems?

    @TasTax
    I made a video about issues #1, #2, and #4.
    -About issue #3, I have no idea how to reproduce/recreate it. About issue #5, I understand now that it is not an issue but your purpose.

    Issues 1 and 2 and 4.MOV
    53.3MB
    Expires on 5 March, 2025

    https://we.tl/t-XVuCEuCjvi

    Regarding Issue #1: 00:00-
    Issue #2: 00:00-

    Issue #1: 00:13-
    Regarding Issue #2: 00:13-

    Issue #4: 00:39-

    *
    Note: If the aforementioned issues cannot be reproduced/recreated in other testers’ environments (≒ Apple devices and iPadOS/iOS), these issues may be specific to my test environment.

    My test environment in the video:
    TestFlight Octachron v2.1.0 (202) / The latest.
    iPadOS v16.7.2 (Note: The latest version on my device should be iPadOS v17.7.5. So I’m not an ideal tester. I’m sorry.)
    iPadPro10.5 (2017)

  • arnouarnou

    My wishlist:

    1. One Track sliding option. When you slide your finger it only affect the firstly touched track. No accidental steps to other tracks this way.

    2. Partial track randomization: Sliding your finger eg. from 1-7th steps of the 16steps track. After sliding, while holding your finger on 7th step you touch the screen anywhere with an other finger getting random steps on every hit.

    Same mechanism shown for a moment from 01:50

  • wimwim

    @TasTax - small bug in the App Store version. The TEST button doesn’t work in the customize mapping dialog.

  • reinerspassreinerspass

    Hi @cramdog,

    First of all, thanks a lot for your in depth testing! <3 I’ve been looking into the issues you reported and would appreciate some additional feedback to help narrow down the causes.

    For Issue #1 (First Step Without Sound), it’s possible that the synth could omit the sound with too short gate times. Could you test the issue with the app MIDISpy to see if MIDI notes are being sent through correctly when using a Gate Length of 0%? Also, if you have the chance, could you test with Zeeon or Dagger to see if the same issue occurs? An AUM preset that reproduces the issue would be really helpful.

    For Issue #3 (Playback Position Disappears), I thought the issue was already fixed, but I can’t reproduce it right now. Could you share an AUM project that shows the issue so we can investigate further?

    Again, thanks for your support!

    Cheers
    markus

  • cramdogcramdog
    edited February 28

    @reinerspass said:
    Hi @cramdog,

    First of all, thanks a lot for your in depth testing! <3 I’ve been looking into the issues you reported and would appreciate some additional feedback to help narrow down the causes.

    For Issue #1 (First Step Without Sound), it’s possible that the synth could omit the sound with too short gate times. Could you test the issue with the app MIDISpy to see if MIDI notes are being sent through correctly when using a Gate Length of 0%? Also, if you have the chance, could you test with Zeeon or Dagger to see if the same issue occurs? An AUM preset that reproduces the issue would be really helpful.

    For Issue #3 (Playback Position Disappears), I thought the issue was already fixed, but I can’t reproduce it right now. Could you share an AUM project that shows the issue so we can investigate further?

    Again, thanks for your support!

    Cheers
    markus

    Understood. But it may take some time, since I don't have enough energy to test and report about them right now.
    Once my test is complete, I will send PMs to your / @TasTax 's Loopy Pro forum members’ accounts.

  • cramdogcramdog
    edited March 1

    @reinerspass @TasTax
    I’ve sent PMs to both of you using Recipients feature(?) under New Message under Inbox on this Loopy Pro forum.

  • cramdogcramdog
    edited March 3

    @reinerspass @TasTax
    After that, I sent a total of 4 new PMs.
    (I'm not sure if a PM notification will reach you, so I'm writing this post on this thread just in case.)

    (EDIT)
    In my case, I was/am able to receive your PMs’ notifications.

Sign In or Register to comment.

© Vanilla Keystone Theme 2025