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
I just tested this with VADrum2 and it’s great, all 16 voices on the 808 can now be used, compliments!
I need to try this. Love the Octachron sequencer far more than the in app one. Love the app itself though.
@TasTax @reinerspass
I tried the fixed Generate Scale feature.
(BTW, on the Generate Scale screen, I noticed that ‘Tracks’ can be set to 1-16. That’s a great improvement).
*
The following two crashes may be issues already reported.
*
Minor Issue
After using the Generate Scale feature, two duplication of set notes occur, probably only for ‘Diatonic’ scales.
*
My suggestion
It might be useful if after using Octachron's Generate Scale feature, it would be displayed on the screen as (EDITED) ‘C3 (60), D3 (62)’ instead of ‘C3, D3’. ‘C3, D3’ instead of ‘C, D’. (/EDITED)
(EDITED)
Corrected a misspelling of Splat-to-Clat app name.
(/EDITED)
@TasTax
I made two Octachron settings for Splat-to-Clat app. (Sorry if these are not helpful or if there are any mistakes.)
*
A.
notes.append(NoteListItem(note: 60, title: "C3"))
notes.append(NoteListItem(note: 61, title: "C#3"))
notes.append(NoteListItem(note: 62, title: "D3"))
notes.append(NoteListItem(note: 63, title: "D#3"))
notes.append(NoteListItem(note: 64, title: "E3"))
notes.append(NoteListItem(note: 65, title: "F3"))
notes.append(NoteListItem(note: 66, title: "F#3"))
notes.append(NoteListItem(note: 67, title: "G3"))
notes.append(NoteListItem(note: 68, title: "G#3"))
notes.append(NoteListItem(note: 69, title: "A3"))
notes.append(NoteListItem(note: 70, title: "A#3"))
notes.append(NoteListItem(note: 71, title: "B3"))
notes.append(NoteListItem(note: 72, title: "C4"))
notes.append(NoteListItem(note: 73, title: "C#4"))
notes.append(NoteListItem(note: 74, title: "D4"))
notes.append(NoteListItem(note: 75, title: "D#4"))
B.
notes.append(NoteListItem(note: 60, title: "Kick"))
notes.append(NoteListItem(note: 61, title: "Kick 2"))
notes.append(NoteListItem(note: 62, title: "Snare"))
notes.append(NoteListItem(note: 63, title: "Snare 2"))
notes.append(NoteListItem(note: 64, title: "Clap"))
notes.append(NoteListItem(note: 65, title: "Clap 2"))
notes.append(NoteListItem(note: 66, title: "Hihat"))
notes.append(NoteListItem(note: 67, title: "Hihat 2"))
notes.append(NoteListItem(note: 68, title: "Perc"))
notes.append(NoteListItem(note: 69, title: "Perc 2"))
notes.append(NoteListItem(note: 70, title: "Perc 3"))
notes.append(NoteListItem(note: 71, title: "Perc 4"))
notes.append(NoteListItem(note: 72, title: "Perc 5"))
notes.append(NoteListItem(note: 73, title: "Perc 6"))
notes.append(NoteListItem(note: 74, title: "Perc 7"))
notes.append(NoteListItem(note: 75, title: "Perc 8"))
*
- I think ‘A’ could probably be used for all S2C presets.
- ‘B’ is like the greatest common divisor(?), in a bad way.
There are many ‘B’-like presets in S2C.
However, except for ‘60, 61 / Kick, Kick 2’, the positions of loaded instrument sample name are not constant.
*
I can recommend ‘A’ to other users.
Because there are no mistakes or lies in it.
Whoever made a preset for S2C in Octachron, I think ‘A’ will be the deliverable. (I don't mean that my preset will be the winner, I mean that it will be the same preset no matter who makes it).
‘B’ is fine for my personal use, but I would not recommend it to other users.
It is my compromise(?), in a bad way.
Again, except for the ‘60, 61 / Kick, Kick 2’, the positions of the loaded instrument sample name are not consistent.
(To be precise, some presets load other instrument samples at the ‘60, 61 / Kick, Kick 2’ positions).
*
My taught
If Octachron becomes a universal app for iPad and iPhone in the future, it might be better to write the instrument name of each preset as Kick instead of KICK, or, snare or SNR instead of SNARE, to save screen space.
(But I’m not an iPhone user so I’m not sure).
Note: General advice for people trying the test flight version
I did not uninstall Octachron.
I went to the app store with the Test Flight version installed, or I went to the address where I downloaded Test Flight with the app store version installed.
In other words, in both cases, I installed Octachron over Octachron. Octachron was not uninstalled.
Uninstalling an app itself may erase user presets and other data.
*
@Poppadocrock
My iPad is on iPadOS v16.7.2.
I only mention AUv3 Octachron loaded into AUM.
(I don't use standalone Octachron, so I can't mention it.)
(This post is a bit long so I use the forum spoiler feature).
*
In this post, the app store version(?) of Octachron v1.7.1 is called 8OC. (meaning 8-track Octachron).
The test flight version of Octachron v1.8.0 (151) is called 16OC. (meaning 16-track octachron)
*
At 16OC
When a user preset of 8OC is loaded
(BTW, if you load an 8-track octachron user preset in a 16-track display, it automatically changes to an 8-track display.)
When an AUM session containing 8OC is loaded
*
At reinstalled 8OC
When a user preset of 8OC is loaded
When a 16 track user preset of 16OC is loaded
When an AUM session including a 16 track user preset of 16OC is loaded
*
At reinstalled 16OC
When a user preset of 8OC is loaded
When a user preset of 16OC is loaded
When an AUM session containing 16 OC was loaded
*
I reported the above two crashes to Octachron developers TasTax and reinerspass in my other post using [@].
The two crashes may be known issues for developers and users of the test flight version. However, I was not aware of those crashes, so thanks to @Poppadocrock's question for the debugging hint/tip.
*
I don’t think that the above two crashes will damage existing session data or user presets. However, I cannot guarantee that @Poppadocrock's data is absolutely safe.
@TasTax
I forgot to write something about the Octachron settings for Splat-to-Clat.
I think the value of Number of Tracks for Splat-to-Clat should be ‘12’. The rationale is as follows.
There are very few factory presets on the S2C side with 13 to 16 samples loaded.
There is one preset with 16 samples, Jungle Love 110 BPM.
There are 10 presets with 17 or more samples loaded.
In other words, 175/186 presets from S2C's ‘Factory Kits’ can be supported(?) by ‘12’ Octachron’s Number of Tracks.
My very personal thoughts
I have no strong argument that ‘12’ is absolutely the better value for Number of Tracks of Octachron preset for Splat-to-Clat, because Octachron users are free to customize the Number of Tracks for Octachrons.
OK, thank you very much. But your suggested splat mappings are with 16 tracks now, no?
How should they look with only 12 tracks then? 🙂
@TasTax
It means that 16 of S2C ‘notes.append’ settings are prepared, but the screen display of Number of Tracks is 12.
If users wants to use all 16 ‘notes.append’, they will change the Number of Tracks from 12 to 16 themselves, at that time.
In this case, if the following have already been set up, the users can change Octachron settings with minimal intervention.
notes.append(NoteListItem(note: 72, title: "C4"))
notes.append(NoteListItem(note: 73, title: "C#4"))
notes.append(NoteListItem(note: 74, title: "D4"))
notes.append(NoteListItem(note: 75, title: "D#4"))
However, I’m sorry if I have a wrong understanding of the Octachron setup. In that case, I cannot say anything with confidence about aforementioned values 12 and 16.
(EDITED)
It means that the users can avoid the hassle of user customization.
The users can use it for factory presets of S2C with 12 samples loaded.
It can also be used for user presets for S2C with 16 samples loaded.
Wow, thank you so much for testing that @cramdog that really helps both me and the developer. Cheers.
Thx, yes, the thing is, that it is not so easy to have the right missing 4 tracks in the background if you initially show only 12.
If you add more tracks as a user then, they will only be fallback tracks that You have to customize yourself.
This is why we mostly show the full range of tracks and the user then has the possibility to hide some of them.
So with this said, maybe it is better to show 16 tracks. or do you still think 12 would be better ?
Thx a lot 🙂
Tas
@TasTax
After reading the above quote, I understand.
I would prefer 16 tracks.
Sorry for making you spend your time. Thanks a lot.
Ok cool and no, you really don’t have to apologize. We really appreciate your detailed feedback and your ideas 😊 Even if we can’t realize everything. But you can’t know about the technical restrictions, of course.
So Thx again for your great engagement and support ✌️😊
Issue
TestFlight version of Octachron v1.8.0 (151) crashes when the SHIFT button is held down, all eye icons are tapped (= the diagonal lines are overwritten), and the SHIFT button is released.
@TasTax @reinerspass
Sorry. I forgot to write the two name tags in the above issue post.
I'm not sure if the message will reach if I edit it and add your name tags, so I post this as a new post.
@TasTax @reinerspass
Issue
Depending on the state of the Eye icon, loading a preset may cause Octachron to crash.
*
Steps to reproduce
Set Number of Tracks to 16.
Hold down the SHIFT button.
Tap all Eye icons from the 1st row to the 15th row, to add diagonal line segments(?).
Note: Do not tap the eye icon for 16th row.
Release the SHIFT button.
Tap the Octachron icon, then tap PRESETS - MIDI MAPPING - APPS - ANALOGUE RHYTHM 909.
Octachron crashes.
*
If (a) is replaced by (b), no crash occurs.
(a)
Tap all Eye icons from the 1st row to the 15th row, to add diagonal line segments.
Note: Do not tap the Eye icon for 16th row.
(b)
Tap all Eye icons from the 2nd row to the 16th row, to add diagonal line segments.
Note: Do not tap the Eye icon for 1st row.
*
Minor issue
If the preset ‘ANALOGUE RHYTHM 909’ above is AudioKit app, I guess ANALOG is the official app name, not ANALOGUE.
(I’m sorry if I’m referring to other/unrelated app).
@TasTax @reinerspass
Issue
On ‘CC (CC: 0)’, Octachron crashes when ‘+’ (plus) button is tapped.
Steps to reproduce
Load Octachron on AUM.
Tap 16-pads(?) icon.
Set Number of Tracks to 16.
Tap Octachron icon.
Tap CUSTOMIZE.
Scroll down the screen, and tap any ‘CC (CC: 0)’.
When ‘+’ (plus) button is tapped, Octachron crashes.
(EDITED)
All of the following may be issues that only occur in my iPad environment.
My iPad has recently been failing to load one of the apps on AUM when I load a session containing multiple apps. I have wondered if that could be due to my iPad not having enough processing power to handle the apps. (Or maybe my iPad's SSD is chaotic). If that same thing is happening when loading Octachron, then it is not an Octachron issue, but a issue with my iPad.
(/EDITED)
@TasTax @reinerspass
Issue
When AUM session save data containing TestFlight version Octachron is loaded, the loading of Octachron may succeed or fail, even though the same session save data was loaded.
*
Steps to reproduce
Press and hold the power button on the iPad and restart the iPad.
Load AUM.
Load Octachron on AUM.
Set Number of Steps value in Octachron's Sequencer Settings to 1.
Set Number of Tracks value in Octachron's Sequencer Settings to 1.
Save AUM session file.
Load this session file.
Then, either of the following will occur.
Success: Octachron is successfully loaded. Octachron AUv3 window opens automatically.
OR
Failure: Loading of Octachron fails, and the circle containing Octachron icon on AUM node turns red.
After confirming the above results, load the above session file again without closing/restarting AUM.
In this test, a tester should load the above session file again and again. If the tester find even one case of failure, the tester can stop the test at that point. (Because the purpose of the test is to make sure that failure occurs).
*
My test results
Only the first five load results of the three tests are shown.
The session data for Test 1, Test 2 and Test 3 are unique to each. In other words, three save datas of AUM session will remain after this test.
Test Start
Note: ‘➡️’ indicates that the save data of AUM session has been loaded.
Note: Success/Failure indicates the result of Octachron loading.
Reboot(?) iPad.
Test 1
Load AUM.
Perform the ‘Steps to reproduce’ above.
(EDITED)
Skip these two lines. Do the same for Test2 and Test3.
(/EDITED)
My test results:
Success ➡️ Failure ➡️ Failure ➡️ Success ➡️ Failure
Test 2
Reload AUM.
Perform the ‘Steps to reproduce’ above.
My test results:
Failure ➡️ Success ➡️ Failure ➡️ Success ➡️ Failure
Test 3
Reload AUM.
Perform the ‘Steps to reproduce’ above.
My test results:
Success ➡️ Success ➡️ Failure ➡️ Failure ➡️ Success
Test End
*
My thoughts
I’m not sure if there is a law(?) or not about the order in which Success and Failure occur. I guess it’s random.
*
Another Test (another issue?)
Note: This test does not require manual loading of Octachron.
Load AUM and then load the save data from the session file above.
(Of the three saved data above, probably any of them might be the same result, but I’m not sure. From the three saved data, I chose one and loaded it only).
After about (EDITED) 5 - 15 (/EDITED) repetitions of loading the same session file save data without restarting AUM, I got the following condition on my environment.
Octachron AUv3 window opens, but nothing is displayed. All of its window is painted the same color (moss green or gray or olive green?) as the top edge of AUv3 app’s window on AUM.
In the condition above, when the same saved data from the above session file is loaded, AUM itself (probably) always crashes and returns to iPad home screen.
*
My environment
TestFlight Octachron v1.8.0 (152)
iPadPro10.5
iPadOS v16.7.2
iPad screen is Portrait mode.
(This report is a bit long, sorry if it's hard to read due to my poor English writing. But even if I were to report it on video file, I guess I need to append the explanatory text above).
@TasTax @reinerspass
Issue
TestFlight Octachron v1.8.0 (152) freezes.
Steps to reproduce
Load TestFlight Octachron on AUM.
Enable ‘0 Pattern Marks Loop End In Song’ feature.
Enable Song feature.
Tap ▶️ switch on AUM.
TF-Octachron screen freezes. (It’s not a crash).
Unload TF-Octachron from AUM node, and reload TF-Octachron.
TF-Octachron is not loaded.
The brightness of the blue font of the message below keeps changing slightly.
Still loading…
Please wait!
In this state, AUM does not accept input.
This state continues, so unload AUM.
@TasTax @reinerspass
Issue
TestFlight Octachron v1.8.0 (152) crashes when 'Number of Tracks' value is reduced.
Steps to reproduce
Load TF-Octachron on AUM.
Set the value of ‘Number of Tracks’ to 2.
Hold down SHIFT button and tap Eye icon for ‘Kick’, then release SHIFT button.
Tap ‘Snare’ to change its state to yellow.
Set the value of ‘Number of Tracks’ to 1, then TF-Octachron will crash.
@TasTax @reinerspass
Issue
TestFlight Octachron v1.8.0 (152) crashes when Generate Scale feature is used.
Steps to reproduce
Load TF-Octachron on AUM.
Hold down SHIFT button and tap Eye icon for ‘Kick’, then release SHIFT button.
Set the value of ‘Track’ on Generate Scale feature to 1, then Octacron will crash.
Hey @cramdog ,
Thank you very much for your in depth testing. Luckily I think despite maybe the last one these are more edge cases. But it is good to know them and we will for sure check them out.
And also thx a lot again for your cool splat to clat mapping 🙂
Best greetings from snowy Munich ✌️😊
Tas
Hey, Thank you, glad you like our update. And yes, well, of course we would like to put even more mappings in. We just did a bunch, but of course you can tell us what you would like to have, and we see what we can do. Best thing would be though, if you post the mapping here yourself like eg cramdog did. Then it is very easy for us to implement. Just midi notes and track titles in the right order would also be enough.
Keep enjoying and best greetings from Munich ✌️😊
Tas
Hello @TasTax . I like your app.
I know that that it is possible to add swing per track.
I'm wondering if it would possible to add offset (or even better a push / pull like in zenbeat) in the parameter locks
Thanks,
👆
@TasTax And I have probably made this suggestion before, but shift/lane direction/ping pong of patterns would be awesome.
Thank you! 😊 And yes, unfortunately it’s not so easy to implement and we think due to the great demand, next step will be the iPhone version. But we definitely also have offset pretty high on our list.
And @Slush , yes play directions are on our list as well. But what do you mean exactly with the shift/ lane? 🙂
Maybe I don’t use the correct terminology for that, but what I mean is that you can move a step tot the left or right.
Thx for the follow-up!
It will be nice to have an iPhone version too
Mh, ok, but you don’t mean the move X and Y option we have in the pattern menu popup, no?
Oh! I had no idea it’s already there, must have overlooked that
My apologies.
iPhone version… 🤞😮💨🤞