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
Maybe dumb question, but wasnt able to find am answer yet:
How to Control the Pure Acid drums with octachron in aum or cubasis?
In rozeta Rhythm there is already midi channel 10 activated and ist just works. Don’t know How to do it with octa. Please help me
You da peeps, @reinerspass & @pxlhg! Looking forward to the update.
>
The matrix icon to the right of the octopus allows you to set the midi out to channel 10.
Thanks.
I can scroll in there...
Now i can See
Here is the array of midi values below, arranged in the same order as the Pure Acid screen.
This is used to sequence PA drums in Octachron, and was tested within AUM.
36 35 38 40 41 43 45 47 37 39 56 44 42 46 49 51
(The numbers above may be useful only as my notes: ......)
From here on down is a different topic.
I wrote earlier in this thread about a behavior that may be a bug in Octachron.
The problem is that the input and output of Step repeats do not match.
The following is a continuation of that post.
I tested the output from Octachron to Atom2 yesterday.
Regardless of whether the tempo was 20 or 21, the number of consecutive notes was recorded exactly as set in Atom2.
(However, I haven't done a rigorous test, so I don't know yet what happens with different settings.)
I remembered seeing a post somewhere on this forum that Atom2 is very accurate when dealing with tempo and timing.
I wondered if that meant that the mfxMonitor and Ruismaker groups were using different programs and algorithms for midi processing than the Atom2 and Octachron groups.
Atom2 and Octachron have newer release dates than Ruismaker.
So, is it possible that there is some kind of technology update, including an iOS update, that causes a difference in the processing of consecutive notes in the midi signal?
If this is the case, will the problem with the accuracy of the note output be solved without an update to Ruismaker?
I have only emailed the Octachron developers about the above problem with the output of the couplets. In this case, was it correct to send an email to Brambos?
I would appreciate it if both the developers of Octachron, @TasTax, and Brambos, @brambos, could take a look at my post above this thread and this post to clarify what the problem is.
(I'm not sure how to use the @ symbol in this forum)
Could you please elaborate on what you'd like me to look into? My plugins all use sample-accurate timing, and use Apple's own native code/algorithms for MIDI handling without intermediate frameworks etc.
Timing should be identical to what Atom does.
I apologize for that.
I was unclear in my question.
I don't have the knowledge to understand what @brambos wrote.
I'll try to make it as simple as possible.
What I want to know is how to solve the following problem.
If this is a bug, I would appreciate it if you could improve it in an update.
The number of tuplet in the Octachron sequencer does not match the number of notes in the Ruismaker output.
This happened when I set the tempo in AUM to 20, and I set 2 and 4 tuplet.
When the tempo is 21, the problem does not occur.
I would like to know if this is caused by Octachron or by Ruismaker.
I have never bumped into timing issues with Ruismaker or Ruismaker FM...
Here's an 'idiot test' with AUM running at 20BPM and Atom 2 running 10x speed triggering Ruismaker...
https://www.dropbox.com/s/1jfdgauitv2lpjo/speed.mp4?dl=0
There's absolutely ZERO timing issues and this is an old iPad Air 2
Have you tried other sound sources, drums and/or synths driven by Octachron?
You’ve mentioned Atom 2. What was the result of your test in Atom 2 w/ Ruismaker?
@Samu and @xor, thanks for the responses.
I didn't realize about the synthesizer test until you pointed it out.
I have just tested it with Octachron and Poison-202.
The same bug(?) still appeared.
I mentioned Ruismaker's name because I used Ruismaker first.
I apologize to @brambos for that.
I have no intention of using Ruismaker and FM with any sequencer other than Octachron.
So the thought was fixed in my mind that this event was a problem between specific apps.
(Sorry for my poor writing).
As a result, I came up with the idea that the problem might be with Octachron.
Even when the tempo was at other values, the output of the tuplet was sometimes accurate and sometimes inaccurate.
But in my case, I may have overlooked something.
Therefore, I will withdraw my question.
Thank you very much for your help and advice.
Hey @cramdog, first of all thanks for taking the time to write this feedback!
I was not able to reproduce the issue you are describing. Could you have a short look at this video I’ve recorded? Is this the correct setup you are describing?
Cheers
Markus
@reinerspass, thanks for the response.
Nice to meet you, are you one of the developers of Octachron?
I've never sent a video before, but I'll try.
I tried using the upload file feature on this forum, but I couldn't attach the file.
I have tried uploading a video to the following link.
https://d.kuku.lu/6e165a9ef
The environment for the video is an iPad Pro 10.5.
I used Octachron and Ruismaker with AUM.
I repeated the loop at tempo 20, stopped, played it at tempo 21, and then back to tempo 20.
Although I did not record it in the video, there are tempo numbers other than 20 that increase the number of pronunciations.
As far as I have experienced, the problem occurred when the tuplet were 2 or 4.
Even when I change the decimal point in the AUM tempo, some tempos have the exact number of pronunciations and some have the incorrect number of pronunciations.
This could not be checked completely.
(As I was writing this text, I realized that there may be a problem with the tempo output on the AUM side.
Or it may be a problem that occurs only on my iPad.
I'm not a good debugger.)
Atom2 is difficult for me to use, and I'm not familiar with it.
I have very little knowledge about DAW and midi.
This video was shot without using Atom2, and with as clear and concise a setup as I could find.
Hey @cramdog, thanks for your reply! I think I got it! It's definitely related to Octi, I'm sorry. Did you change the value for SWING by any chance? Thats what sometimes triggers the issue for me.
@reinerspass, thanks for the reply.
I have not changed the swing values.
I have not changed any parameters in AUM, Octachron and Ruismaker since I started them all.
Only the tempo setting of AUM and the Step Repeats setting of Octachron were changed as shown in the video.
Here is another verification video.
https://d.kuku.lu/feaa6b639
I turned off my iPad by pressing and holding the power button.
Then I turned it on by pressing and holding the power button.
This is the video that was recorded right after that.
The iPad OS version is the latest.
The versions of AUM, Octachron, and Poison-202 are all the latest.
The AUM sample rate could only be set to 44100hz.
The tempo is 20.6.
This is the number of Step Repeats that I set and the number of sounds that were actually output.
4 became 5.
3 became 4.
2 became 3.
1 is output as 1.
When the tempo was 20, 3 remained 3.
At a tempo of 20.6, all Step Repeats output one more sound.
This was the first time I did this kind of verification work in my own serious way.
I am suffering from strong nausea and headache.
I think this is just hard physical work.
Good luck to you and all the developers in this world.
I think I may have used the wrong English expression.
It's different from what I imagined, but it's hard work that involves general fatigue.
Would that be correct?
I wanted to give a nuance like "the developers are amazing," but I'm not an English speaker, so I'm not sure.
Dear Octachron community,
Hope you all are doing good.
Due to some nasty bugs it took quite longer than we hoped but finally today we released the Beta version of another free update for you.
It includes:
Improved pattern selection and song mode design:
— New play indicator
— Drag and drop patterns to change their order. Including countdown of played repeats.
— Play and edit patterns via single-tap
— Edit-only via tap-and-hold or shift-and-tap
— By default, patterns which are set to 0 repeats in song mode are skipped. Go to settings to activate the previous „0 pattern marks loop“ function again
Completely new move x and y function in the pattern menu for more experimental grooves
And more little changes and improvements for better performance ...
To make sure everything is sound it would be nice to have some more beta testers. So are you seriously interested into testing and bring Octachron quality to the next level?
Then please install the TestFlight app from the app store and then click on the second link to get invited to our Beta program:
https://apps.apple.com/de/app/testflight/id899247664
https://testflight.apple.com/join/aH3r4QMz
Then please send your Feedback via the "Send Beta-Feedback" Link in the Testflight App. Also added screenshots can be very helpful for us.
And if you have any questions or suggestions please drop them here in the forum.
Looking very much forward to your responses and
best greetings from Munich
Tas
Thanks.. will give it a test..
Exciting, I’ll be interested to see how it’s changing, nice one 👍👍
Did click on the link… nothing happened…?
Have you installed the Testflight app first?
Click it again.
Got it working now… Much thanks..
I had to click it twice as well for some reason
Are there any plans for this to come to the iPhone ?
Love this app
Can’t see why it wouldn’t work on a phone screen, it’s got a clean interface
Nice.. more using it for melodic Seq. Will love ‘tie’… yep Tie is a must..
hey @Gdub,
Thx for your question. And of course a phone version would also be cool. But it is actually more effort to develop than you might think. And our little Octachron survey with over 450 participants now (thx A lot for that!) says that for most users experimental and song features are even more important.
So we will concentrate on that at the moment, hope you understand.
But I hope you keep enjoying Octachron and send best greetings from sunny Munich
✌️😊
Tas
I’ve always loved Octachron. Happy to test out the update. Cheers.
@TasTax
Thanks for the reply
I certainly wouldn’t argue with the survey results
Keep up the good work
Hey, first of all, also thanks from my side to everybody who considers becoming a beta tester! This will hopefully help to make releases more stable! 🙇♂️
Also @cramdog thanks for reporting the issue! Over the weekend I was able to hopefully fix it 🙏 It's not in current beta but for sure in the next one!
Cheers, Markus
Hey, dear Octachron users and beta testers!
Thx a lot for testing. Luckily we didn't get reports of any crashes yet
How was your experience? What do you think about the new features? And did you have any issues with the beta? Please tell us.
Thx a lot again for the great support
And best greetings from Munich
Tas