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
Yeh, midi record would probably make it fully replace Drambo as drum sequencer (only) for me.
saw the OCTACHRON/Oneshot roundrobbin mapping on Facebook. I also saw that you guys sell merch. Stickers would be cool.
Thx for the round robin share
Hi, @TasTax @reinerspass.
The latest Octachron v2.0.5 (193) has two issues, in my environment.
*
Issue #1: Edited MIDI CC Name and CC Number of Octachron revert to their default/initial states, after Generate Scale feature of Octachron was used.
Note:
-I have no idea if this issue is universal or not. So, here is how to reproduce it for Octachron users, just in case.
-This issue was once fixed in 2022. And I guess the rollback of this issue probably occurred on or before April 2024.
*
Issue #2: The MIDI Note Number 46 in the preinstalled “ONESHOT KIT” MIDI MAPPING is duplicated.
Incorrect:
Hat Open : 46
Hat Pedal Open : 46
Correct (probably):
Hat Open : 46
Hat Pedal Open : 50
Here are screenshots of the context. (Sorry if I’m wrong about something.)
*
My environment:
Octachron v2.0.5 (193) / The latest.
iPadOS v16.7.2 / (up to v17.7.4)
iPadPro10.5 (2017)
AUM v1.4.7 (352) / The latest.
@TasTax @reinerspass
By the way, I probably forgot to say thank you on this thread for the improved functionalities described in the quotes below, I’m so sorry. (Needless to say, this does not mean that I was unaware of these improvements. I mean that I was aware of the improvements but forgot to say thank you. Anyway, I’m not polite.)
Thank you so much!!! @reinerspass @TasTax
*
October 2022
*
November 2022
(EDIT)
*
To be on the safe side (= I don't want to write inaccurate information here.), I have now rechecked all 47 scales on the latest Octachron.
Result: Only ‘Diatonic’ scale showed two Cs in a row. In other words, 46 out of 47 scales do not set two Base Notes in a row, in a good way. (My point is this feature was improved.)
Note: The result above can exclude extreme settings. (i.e., Base Octave: 8.0 / Base Note: B / Scale: Major / Tracks: 16)
[Note: This “EDIT” part is merely a report to readers of this thread, not a request or suggestion for an improvement on the setting of Diatonic scale to the developers of Octachron.]
(/EDIT)
Hello @TasTax, I have an issue when accessing the MOD params. The text for each of the parameter options in the list is unreadable - see the screenshot below.
Hello, I am reaching out with a few questions:
Yes.
You wouldn't need different instances. AUM would preserve the MIDI channel out.
Patterns can only be saved/loaded at the whole project level.
Thanks for the reply! So, AUM preserves the Octoachron mapping essentially?
And bummer on only saving patterns on the project level. I can envision a situation where hot swapping out some parts could be interesting from a performance standpoint.
Do you know of any drum sequencers on iOS tha either allow loading of patterns on the track level (so just for the kick, snare, ect.), or at some sort of "scene" level?
I'm not sure what you mean by mapping, but the output channel in Octachron is the channel that the midi goes out on in AUM.
I guess I can see that. Cross-instance copy and paste would work well for that. I tried though and it doesn't work.
I can't think of any.
Well, any of them can save a preset, so you could load a preset as a starter template. That doesn't suit your purpose really though.
I think what I would do is just leverage multiple instances. Load my preset patterns in a separate instance mix them together.
Hey everybody!
Happy new year to everyone and sorry for not being so active in this forum for the last few weeks. We were concentrating on finishing our next free update for you. Our new Beta is now including this exciting new features:
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
Also older user presets should load correctly now.
Dear Beta Testers: How do you like it? And does everything work as expected? Looking very forward to your opinions!
Enjoy, and best greetings from Munich ✌️🎶😊
Tas
Wooo! Fabulous news! Thanks for hard work on this!
Hi. @TasTax @reinerspass.
Great update! I’m looking forward to the completion(?) of the update. Thank you so much.
*
In my environment, Octachron crashes with the following steps.
Load AUM (= host app) on iPad.
Load “AUv3 TestFlight OCTACHRON v2.1.0 (201)” on AUM.
Tap VELOCITY in the lower left corner of the window of AUv3 Octachron.
Tap OFFSET.
Edit any vertical bars of OFFSET by any arbitrary amount(?).
Tap OFFSET in the lower left corner of the window of AUv3 Octachron to go to OFFSET window. (Or, tap and hold OFFSET to go directly to OFFSET window.)
Tap CLEAR.
Tap an area outside OFFSET window to make the OFFSET window disappear.
AUv3 TestFlight OCTACHRON crashes.
*
My test environment:
TestFlight OCTACHRON v2.1.0 (201)
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.)
iPadPro 10.5 inch (2017)
AUM / the latest v1.4.7 (352)
Oh yes, the same with iOS 18. We will check this, thx! 😊
@TasTax
Additional report:
When I do the same steps/procedures/tests on “VELOCITY, STEP REPEAT” as in the above-mentioned OFFSET, “VELOCITY, STEP REPEAT” crash, in my test environment.
@TasTax @reinerspass
Note: I’m not sure if the following is an issue or not, but I report it here just in case.
Issue(?) / TestFlight OCTACHRON v2.1.0 (201):
If a Pattern is copied/pasted, the value of CLOCK DIVIDER of the Pattern is not copied and pasted [or, not copied or pasted], and becomes “1”.
@TasTax @reinerspass
Note: I’m not sure if the following is an issue or not, but I report it here just in case.
Issue(?) / TestFlight OCTACHRON v2.1.0 (201):
There is no CLOCK DIVIDER in SEQUENCER SETTINGS.
Yes, thx. Would you like to have the clock setting copied with the pattern?
Yes, we thought that would be too much. But would you still like to have it?
I have no idea, I’m sorry.
I think you might want to ask opinions of Octachron users on this thread. (I’m very interested in their thoughts. Because I have no idea how a sequencer should work, and I’d love to read and learn from their thoughts.)
@TasTax
I have a 100% reproducible issue with Octachron failing to reload on Drambo. This is with latest shipping versions of Drambo and Octachron. Opening a saved session which has Octachron instances leads to "Error" being displayed in the plugin slot instead of the Octachron instances. Is this a known issue? Happy to help debug. Let me know what to do.
Wow! Really really great additions, especially the offset. Looks beautiful! Looking forward to trying it out when it’s ready for release.
Hey @isal ,
Thx for reporting. We will check this!
Wow! An amazing set of updates. Fantastic work @TasTax and team.
I thought about these questions again.
And I write my preferences at the moment.
Note:
The following are not requests/suggestions.
-For example, if there are multiple options suggested by the developers of Octachron (= @TasTax @reinerspass ) and I can choose any one of them, I would do so. However / On the other hand, I do not want to make any requests or suggestions that would increase the costs of developing Octachron.
*
If a CLOCK DIVIDER value(?) of a copied pattern is (for example) 3/2, then I would like the CLOCK DIVIDER value of the pasted pattern to be the same 3/2.
*
If a CLOCK DIVIDER value(?) of a particular row in a copied pattern is (for example) 3/4, then I would like the CLOCK DIVIDER value of the particular row in the pasted pattern to be the same 3/4.
*
I would prefer to have a global(?) CLOCK DIVIDER in SEQUENCER SETTINGS. In other words, I would prefer to have 3 different CLOCK DIVIDERs (= global[?], pattern, row) in Octachron.
[However, if having 3 different CLOCK DIVIDERs in Octachron would increase the costs of developing Octachron, then I have no problem with the loss of the global(?) CLOCK DIVIDER feature from SEQUENCER SETTINGS. In other words, I have no problem with the 2 types (= pattern and row) of CLOCK DIVIDERs chosen by Octachron developers @TasTax and @reinerspass.]
Oh man… This is like bad Deja vu…
Here comes 100 posts about people pushing Drambo…
Thx everybody and thx @cramdog for your thoughts. Also, thanks for thinking about the costs. But it isn’t that bad in this case, because we are already on this features.
And I think I agree with the first two points with copying the divider settings.
But why would you like to also have the global divider?
Just curious, to be able to make the best product for you 🙂
And what do the others think?
I may simply have a vague anxiety about the loss of a feature that is/was there.
And I don't think there is any rational basis, reason or logic for my concern.
(The following is 50% Off-topic.)
I guess I was asked a question by you before on this thread, ‘Do you think "1" is necessary for NUMBER OF STEPS?’ or something along those lines. (Note: It may not have been a question, but a rhetorical question.) And I was vaguely worried about the loss of "1" feature. Because I have no idea whether the loss of what is/was there would be good or bad for Octachron or Octachron users. (Even now, I have no idea if the "1" feature is necessary or not.) My concern about the loss of CLOCK DIVIDER from SEQUENCER SETTINGS is for the same reason as this "1" feature topic.
[Note to readers: The "1" feature is still there.]
(Note: I’m not trying to say that my anxiety is serious, I’m just trying to say that my anxiety is meaningless. Don’t get me wrong.)
@TasTax
If I had to say, I would consider the aforementioned Global CLOCK DIVIDER as a “SHIFT button to select and edit all CLOCK DIVIDERs” feature, or a “pseudo-reset button of all CLOCK DIVIDERs” feature, at the moment.
However, I’m not sure if this makes sense as a workflow or not.
(EDIT)
My apologies!! I realized that the idea of two features (Practically one feature) above is based on my incorrect assumption that ‘Global CLOCK DIVIDER’ overwrites ‘Pattern CLOCK DIVIDERs’ and ‘Row CLOCK DIVIDERs’. I’m super stupid.
@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?].)
Note to readers:
Having said that(?), please do not refer to what I wrote on my post on this thread above.
Because, on second thought, if users need the ‘previous / old’ workflow (≒ changing CLOCK DIVIDER of all Patterns at once) of Octachron in the future, then it may be better to have Global CLOCK DIVIDER.
I do not have enough knowledge or experience to think about this topic/subject, especially when it comes to workflows or use cases.
So I think it is important to share your opinions and thoughts with @TasTax (= One of two developers of Octachron) on this thread.