The clock has drop outs with a simple one track loop.
Currently Cubasis is not useful.
More info plus a sample clip is needed to see if your problem can be replicated.
Hardware, operating system, versions you’re running, etc.
Only Cubasis and the Screen Recorder App 720p 4 Mbps 60fps are running.
It is only one track.
4 bars.
One plug-in Microwave.
The problem is with every instrument.
It has nothing to do with Microwave or a specific plug-in.
1st video
Every first note lags (see also the 2nd video)
Between 0:15-0:17 a dropout.
Between 0:32-0:34 it seems to work “sometimes” properly.
Otherwise dropouts and lags.
2nd video
Only one pitch was used here, to recognize the problems.
Every first note lags.
You can also hear other pitches, that should not be there.
Between 0:05-0:06 once again a dropout.
INFORMATION
-
Operating System
System : iOS 16.2
System Build : 20C65
Multitasking Support : YES
Kernel : Darwin 22.2.0
Kernel Build : 18446744073709551615
System Boot : 2025/06/08 12:26:48
Uptime : 06h 49m 23s -
Device Information
Device : iPad
Device ID : iPad7,5
Model : J71bAP
Name : iPad
LocalizedModel : iPad
Hostname : -
CPU Information
CPU Model : Apple A10
GPU Model : PowerVR Series7XT Plus
Core Number : 2
CPU Frequency : 2.31 GHz
TB Frequency : GHz
L1 Cache Size : 64.0 KB
L1D Cache Size : 64.0 KB
L2 Cache Size : 3.0 MB
Byteorder : 1234
Cacheline : 128 -
Disk:
Total Disk Space: 119.2 GB
Disk Free: 85.7 GB -
Hardware Features
Display Resolution : 1536 x 2048
Pixel Density : 264 ppi
Battery Voltage : 3.73 V
Battery Capacity : 8820 mAh
Rear Camera : 8 MP
Front Camera : 1.2 MP
Wi-Fi : 802.11 a/b/g/n/ac
Bluetooth : v4.2,A2DP,EDR
@LSlowak Lars would be the one to ask if your model iPad meets the minimum requirements of whatever version of Cubasis you’re running.
The specs of that model indicate it was never designed for demanding apps like Cubasis. It was aimed at education and schools for routine daily tasks, with its 2Gb RAM and 32Gb storage, both of which are minimal. iPadOS 16.2 probably takes up over half of the storage. So, be prepared to consider upgrading to a more powerful iPad, if you want to run Cubasis.
The good news is that the current base model iPad is $329 with an A16 Chip, 5-core CPU, 4-core GPU, 16-core Neural engine, 128Gb of storage, 4Gb of RAM, and its listed as being iPadOS 26 compatible, which will be out this fall. It’s also Apple Pencil compatible.
If your budget permits, then I’d try to upgrade to an iPad with the newer M-series Apple Silicon chips, but on a tight budget the one above will work for Cubasis, for now. Eventually, we’ll probably all be on the newer M-series chips to get all the features they make available to developers.
For $329, the base model iPad looks like a lot of value for the price.
John
Why do i get this?
ons. 11. jun. 2025, 08.11 skrev Johne1 via Steinberg Forums <notifications@steinberg.discoursemail.com>:
Wrong Lars? My apology. It said @steinberg
Hi @BinaryTubes
Did I understand correctly that you’re using the Microwave AUv3 plug-in with Cubasis?
If so, there’s no need to use MIDI Clock at all.
Instead, please follow the steps for using AUv3 instruments in Cubasis, as demonstrated in our “Getting Started with Cubasis” tutorial (linked below).
In addition, I gave cycle recording a short check with Cubasis on the iPad Mini 6 using the external SynthMaster AUv3 plug-in. Here are two example clips:
Example 1 - Arpeggiator
Example 2 - Synth Bass Sequence
You may give it a check to choose higher latency value (located under Setup/Audio) to see if it helps resolving the problem.
Best,
Lars
At the Cubasis page they says:
iOS 13 or later, iPadOS 13 or later
iPad Mini 4 or later, iPad 5th gen. or later, iPad Air 2 or later, iPad Pro
The iPad is far away from these requirements.
Unless they are wrong.
Or they specify that you can start the program. But not use it.
The hardware has 128 GB of storage. Maybe even the app that reads out the specifications can’t even do that right.
No large studio setup is expected. But maybe 8 tracks that run cleanly, would be a solution.
You can start 64 instances of Acoustic Piano and have a load of 18-20% CPU and 12-16% DSP.
You can run 5 instances of Microwave before the iPad quits. This also shows a utilization of 18-20% CPU and 12-16% DSP.
So I don’t understand that here where a problem with the hardware. Or this information on the part of Cubasis and its load on iOS is wrong.
iPad and iOS is also a one way street. Hardware and software are purchased without any prospect of success or improvement. It appears that even the minimum requirements do not match.
With software, it’s also the case that you can’t go back to an older version if you have a problem.
When we talk about load, we also mean that a screen recording program is also running here. These usually require a lot of resources.
But, the iPad works well. It doesn’t matter whether the program is running or not.
If the hardware were the problem, the issue would change as the load increased. But that doesn’t.
If it is operated with an external sequencer, e.g. the Cirklon, this problem does not exist.
Midi sequencer for one track, 16 steps, 1 beat, as shown, typically doesn’t require so many resources.
No, I don’t think so. I use it as audio units (internal). I think like in the tutorial.
So I don’t know what I do differently than in the tutorial. I use it like there. I then have a pattern with notes that Cubasis should play. I don’t think it makes any difference whether you set notes or play them.
How do you define “using MIDI clock”?
If you have a pattern for an instrument, it goes output via Cubasis as MIDI notes. Depending on the speed of the clock that is set, the notes are sent to the instrument (microsonic or Audio Units (internal) Model 15, Microwave, … . If the MIDI clock does not run smoothly, there are problems as I have shown. This is how I define “Using MIDI Clock”.
For me it runs longer in Cubasis. I only cut the video. That it doesn’t was so long.
The Problem starts at about 1:30 for me. It can also happen that things go well for 1-2 minutes and then it happens again. You can’t provoke it either. But maybe you cut it too?
It may not occur with an arpeggiator. This is because the sequence does not come from the Cubasis MIDI sequencer. The arpeggiator in Model 15 does not have this problem either. Neither does an external sequencer.
What latency value have you set on the iPad 6?
My setting is: 21.3 ms
Extra Guard Buffer: Max
If I change the buffers to 42.7ms , it is even worse.
If I change the buffers to 5.3, it is better.
That makes no sense.
Which iOS is running on your iPad 6?
Maybe that’s the reason.
Hi @BinaryTubes
I’d love to help you out, but unfortunately, I haven’t been able to reproduce the issue (as I mentioned in my previous reply and demonstrated in the two videos).
Here are a few additional comments:
MIDI Clock is often used to keep hardware devices like synthesizers, drum machines, samplers, and sequencers in sync when making music or performing live.
If you use the internal instruments of Cubasis, or third-party AUv3 instruments or similar, using MIDI Clock is not required at all.
Below, please find links to the appropriate chapters on how to add and use internal and external AUv3 instruments in Cubasis.
I suggest starting with an empty project and following the steps shown in the tutorial. Before proceeding, please try selecting a lower Latency value (found under Setup > Audio > Latency) and set Multi-core Processing to its default value.
In addition, our Getting Started with Cubasis tutorial is a great way to quickly dive into the app and learn how to use it easily and effectively.
Hope that helps.
Best,
Lars
Adding MIDI Instruments
Using AUv3 Instruments