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
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]
@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.)
@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.)
Heyhey! Thx again for your very detailed testing and feedback. This is very valuable to us. And we will definitely check these issues. ✌️😊
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 🙂
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)
My wishlist:
One Track sliding option. When you slide your finger it only affect the firstly touched track. No accidental steps to other tracks this way.
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
@TasTax - small bug in the App Store version. The TEST button doesn’t work in the customize mapping dialog.
Hi @cramdog,
First of all, thanks a lot for your in depth testing!
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.
@reinerspass @TasTax
I’ve sent PMs to both of you using Recipients feature(?) under New Message under Inbox on this Loopy Pro forum.
@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.
Hi,
Very excited for the upcoming new features, they'll all be very useful.
I can't see it elsewhere, but I'd really like an inverse trigger condition setting.
e.g. you could have a snare play on repeat 1,2,3 and not on 4, in addition to the current mode where you can set it to play only on repeat 4 and not on 1,2,3.
It probably has been suggested many times, but an random function for laying out steps would be great. I see how much fun and helpful it is in Playbeat, jAmp Percussive and DM10.
@Slush mind sharing your midi mapping for jamp percussive? I will totally beg you for it.
“POOOOOOOlease MR.SLUSH”
I haven’t used Percussive with Octachron yet, so sorry. But thanks for calling me MR.
Right on. I spent an hour mapping it, but it didn’t stick for some reason.
I’ve been plenty busy with the Osaka drum sounds from Module Pro within Octachron using the Midi 16 template.
@reinerspass @TasTax
I've been using the Beta version in Grooverider 2 with Oneshot for a couple weeks now.
1) I add Octachron, move to left in GR2 (before OneShot) - but then it doesn't trigger any sound. I then have to delete it and re-do it and that seems to work. This happens quite a lot of time for me (not working on first attempt).
There also seems to be an issue that it doesn't play if GR2 is stopped and you press play for the first time.
I have found that sometimes just having it already playing before adding it to GR2 makes it work.
However (open and testing right now) I just stopped it. And Pressed play again - this time it's no longer working. And the playhead isn't moving across each step in Octachron.
2) I have also experienced it not triggering sounds whilst playing a bar sequence. For example it may trigger a snare but then not trigger the snare on its 3rd time round (no probability being used at all). I've also found that it can happen to a sound of more than one sound is being triggered on the same step. This has been intermittent - no real pattern on when/why this happens.
3) Feature Request for OFFSET: I would be really useful to offset all hits by the exact amount at the same time rather than one by one. For example I might want to offset all the highhats by -12%. It's really fiddly to do this for all of them one by one.
The advantage is we can offset all, then tweak each on individually if we want to make changes.
How I think this could work:
This could be added where the Mutation/Actions section is as this works well as a dial (like chance/range) - Start it at 12 o'clock = no offset - then -/+ % by turning the dial left/right.
Overall so far I've found it a bit hit and miss on whether it will work consistently in Grooverider 2
@dmori - fwiw, I'm having no such problems as you describe above in the App Store version of GR-2. It would be a good idea to revert to the App Store version to see if the problems you describe are isolated to the GR-2 beta. They may indicate a problem with the GR-2 beta rather than with Octachron.
To revert to the App Store version, just go to your purchased items, find GR-2, and install it. When you want to go back to the beta, just install it through TestFlight.
I'm using Octachron beta version, not GR2 beta.
Sorry, I misunderstood - read "in" as "of".
Hey @dmori
Thanks a lot for your report! I’ll look into it as soon as possible. I’m moving apartments right now so I’m a bit busy right now, but I hope I can have a look on the weekend!
For your feature request, to change all offset parameters at the same time, you can press shift key while changing the offset for one step, this will affect all steps. This also works for other mod parameters like velocity and such.
Cheers
Markus
Thanks Markus for the tip of changing all offsets at the same time. Look forward to trying it out.
No rush, just giving some feedback as a beta user.
All the best with the move. I know this always take even more energy than we anticipate
@reinerspass @TasTax
Hi! I have a request.
I made a MIDI mapping of “drum module in Category Drums of KORG Module✳️” for OCTACHRON, using the latest TestFlight Octachron v2.1.0 (205).
I will send the exported mapping file to you via PM feature of Loopy Pro forum.
If you have no problem with the mapping, I would appreciate it if you could pre-install it in the APP category/list(?) of Octachron.
In that case, you don't need to pre-install the mapping with the next latest update of Octachron. I think the moving apartments is hard.
✳️ Note: I have no idea if the information I checked/confirmed about “drum module of AUv3 Module Pro” is applicable to “drum module of AUv3 KORG Module (not Pro) + IAP”.
*
For more details/context/background of the mapping I made, see my posts at the three URL links of other thread on this Loopy Pro forum below.
-In my opinion, I think it is possible to consider/regard the mapping file I made as an almost verbatim port of the virtual pads of GUI of drum module of “KORG Module Pro (or KORG Module + IAP?)” described in the 2️⃣ below.
-If you read the 3️⃣ below, you can understand why the MIDI mapping I made this time doesn’t have ‘Global parameters/effects set by me’ and ‘MIDI CC parameters/numbers for each instrument set by me’ at all.
1️⃣
https://forum.loopypro.com/discussion/comment/1394629/#Comment_1394629
2️⃣
https://forum.loopypro.com/discussion/comment/1394630/#Comment_1394630
3️⃣
https://forum.loopypro.com/discussion/comment/1394631/#Comment_1394631
*
When naming the above-mentioned ‘MIDI mapping for Octachron’ I made, I think "Module Drum" is the correct and unproblematic one.
[Note: I’m now talking about the case where this MIDI mapping is pre-installed in a KORG category/list/menu/page of Octachron app. In other words, "Module Drum" is the name of the MIDI mapping for when it is pre-installed in the same place as the Gadget mappings in Octachron.]
*
Incidentally, if the name of MIDI mapping I made includes any one of the following 4 words, the mapping name may be inaccurate. And it may mislead users who see the mapping name about features/specs of ‘The MIDI mapping for OCTACHRON I made’, ‘KORG Module Pro’, ‘KORG Module’, and ‘KORG Gadget 3’.
So I think it is better not to include the following 4 words in the name of the MIDI mapping I made.
Gadget
Osaka
Pro
Drums
[Since this post is a bit long, I use the Spoiler feature below.]
*
About the above-mentioned problematic words, “Gadget” and “Osaka”:
The background/context of my thought:
If both✴️ ‘KORG Module Pro [or KORG Module (not Pro)] app’ and ‘KORG Gadget 3 app’ are installed on a device, then Osaka Gadget appears within standalone KORG Gadget 3. (This is a feature added in a recent update.)
-Having said that, to be honest, I have no recollection of whether the ‘Korg Module (not Pro) app’ I own is completely “vanilla (= no IAPs)” or it has some unlocked features.
✴️ In other words, if only ‘KORG Gadget 3 app’ is installed and ‘KORG Module Pro or KORG Module (not Pro) app’ is NOT installed on a device, then the Osaka gadget does NOT appear within standalone KORG Gadget 3. (I tested and confirmed it in my environment.)
So, I guessed that AUv3 Osaka (gadget) might exist. I tested with both KORG Module Pro and KORG Gadget 3 apps installed on my iPad. As a result, I confirmed that AUv3 Osaka (gadget) does NOT exist.
The following screenshot of a drum module does not include the word "Osaka (gadget)". This is because it shows AUv3 Module (Pro). [I repeat, there is no AUv3 Osaka (gadget). Because AUv3 Osaka (gadget) does NOT exist in this world in the first place.]
Note:
So, you must never give the words "Gadget" and "Osaka" to the MIDI mapping I made. You must not include either one of them in the mapping name, and you must not include both of them. Because, it misleads users who see its mapping name. In the worst-case scenario, there is a risk that users will mistakenly buy KORG Gadget 3 app.
[The Spoiler below shows the one of the worst-case scenarios.]
[Start]
One day, one iPad/iPhone user purchases an AUv3 MIDI sequencer app from Apple App store.
The user finds a pre-installed MIDI mapping named “Gadget Osaka” in the AUv3 MIDI sequencer app. At this moment, “AUv3 Gadget Osaka” was born in this user’s head.
As a result, the user plans to use "AUv3 Gadget Osaka that exists in this user's head" in combination with the “Gadget Osaka” MIDI mapping pre-installed in the (above-mentioned) AUv3 MIDI sequencer app.
So, the user purchases KORG Gadget 3 app.
However, the user finds that ‘AUv3 Gadget Osaka’ does NOT appear on the host app for some reason.
As a result, next, the user purchases KORG Module Pro app.
However, the user finds that AUv3 Gadget Osaka still does NOT appear on the host app for some reason.
“What’s going on?” the user says.
After 10 years, the user suddenly realizes that “AUv3 Gadget Osaka” does NOT exist in this universe in the first place.
And the user suddenly realizes that the original of AUv3 Gadget Osaka is the drum module of AUv3 KORG Module Pro. AUv3 Osaka does NOT exist, but AUv3 KORG Module Pro does exist.
And the user suddenly realizes that in order to use the AUv3 KORG Module Pro, the user does NOT need to purchase KORG Gadget 3 app in the first place.
The user requests a refund for the purchase of KORG Gadget 3 app on Apple App Store.
For some reason Apple does not allow it.
[Fin]
☝️
So, why did this tragedy occur?
It was because the above-mentioned MIDI sequencer app that the user purchased had the pre-installed MIDI mapping named "Gadget Osaka", maybe.
*
For the record I would like to emphasize the following.
-The MIDI mapping I made is for the above-mentioned (and after-mentioned) drum module of AUv3 (KORG) Module, not for the AUv3 (KORG) gadget.
-The mapping I made has nothing to do with KORG Gadget 3 or AUv3 (KORG) gadget.
-Something like ‘AUv3 Osaka (gadget)’ does not exist in this world at the moment. Even if you install both KORG Module Pro and KORG Gadget 3 on your device, something like ‘AUv3 Osaka (gadget)’ never appears.
*
By the way, I’m sorry for explaining the same thing over and over again in this post. (I previously requested pre-installation of mappings of AUv3 KORG Gadget[s] on this thread. So, I’m concerned that “this” request regarding AUv3 KORG Module might be mistaken for a request regarding AUv3 KORG Gadget.)
*
About the above-mentioned problematic word “Pro”:
I think the mapping name "Module Pro Drum" may lack versatility/universality. If the mapping name includes the word “Pro”, it may give users the impression that the combination of "AUv3 KORG Module (= not Pro) + IAP" will not work.
I consider that the MIDI mapping I made corresponds to both AUv3 KORG Module Pro and AUv3 KORG Module + IAP. So I think it would be better not to include the word “Pro”, as it would appear to correspond to both the former and the latter.
[Having said that, I don't own the “KORG Module (= not Pro) + IAP” combination, so I couldn't test the AUv3 version of the drum module of the combination. So my understanding/explanation of the “KORG Module (= not Pro) + IAP” combination—especially about AUv3 thing—may be something wrong.]
-Incidentally, as you may know, KORG Module (not Module Pro) [and AUv3 Module (not Module Pro)] is a free app.
-By the way, as you may know, the current KORG Module Pro app was formerly called KORG Module. And the current KORG Module app was formerly called KORG Module Le.
*
About the above-mentioned problematic word “Drums”:
I see nothing wrong with the above-mentioned mapping name "Module Drum".
However, in contrast, “Module Drums” is an incorrect mapping name, and I think it is problematic. In this case, it makes a difference whether the mapping name includes the "s" or not.
“drum module” is the name of the “module” of KORG Module (Pro).
On the other hand, “Drums” is the name of the KORG Module (Pro)’s “Category”.
So, if the name of the mapping I made is “Module Drums”, users might associate it with the above-mentioned “Category Drums”. And in this case, it may give a false impression to the users that the MIDI mapping I made corresponds to both modules, “drum module” and “hybrid module”, which are included in the above-mentioned “Category Drums”. However, the MIDI mapping I made is for “drum module”, not for “hybrid module”.
The following screenshot shows the hybrid module.
-Incidentally, factory presets for “hybrid module” in the ‘Category Drums’ of KORG Module is not for drum, but for synthesizer. In other words, the presets of “hybrid module” in the ‘Category Drums’ have MIDI notes 0-127.
*
My supplementary explanation for readers of this post:
By the way, I wrote "AUv3 KORG Module" many times in this post. However, it is also possible to play/control a Standalone KORG Module app with a Standalone Octachron app.
-In this case, enabling the "Background Audio" feature in the Advanced Settings of the standalone KORG Module may be easier to play/control. However, in this case, unless you unload the standalone KORG Module, your device's battery may continue to run down even if you don't use the standalone KORG Module.
Just FYI, I just had the same Octachron "crash on loading an existing project" problem in GR2 that I also still see once in a while in AUM. Latest version (I always keep up to date), latest ios 17, chunky ipad pro.
Loving Octachron, but I have a problem when I use “instant pattern switch”. It more or less always creates a flam-like effect (not in a cool way, unfortunately), when the patterns switch. Am I the only one experiencing this? It’s especially noticeable, if I have two relatively similar patterns, but one of them has a fill at the end.
@TasTax Hiya, this thread is very long and search doesn't not work as it should, so: I'm curious, and surprised why there are no app map for BeatHawk (Uvi)? Is it possible to get one implemented? Thanks for a great app either way.