GUI-related CPU spikes - help me find the culprit

edited July 27 in Known issues

Hi,

I love Drambo. It is the sequencing brain and mixer for my modular. I'm currently building a live set.

I tend to keep my projects running lean, hovering around the 2-3bars of DSP usage <50%, which allows enough headroom for occasional CPU spikes.

Everything was going fine until about one week ago, after I purchased the Visualisation suite (which is amazing btw - great job!).

I now find that if I change the Drambo GUI elements - for example move the clip pane or rename a clip lane when the sequencer is running - the CPU jumps significantly and often chokes, causing a loud zipper noise.

I can 'force' these cpu spikes by re-sizing the clip panel up and down in quick succession. Obviously I won't do this normally, but it might be a pointer to the problem. Perhaps someone else can replicate this?

Now, I am not saying that the Visual suite is the culprit, but I am trying to rule it out as I have stress-tested the AUv3s I am using and they all appears to be OK, cpu-wise.

I am not actually using any visualisation modules in my projects yet, it is just installed.

Is there a way to temporarily uninstall the visual suite so I can test?

Can anyone provide suggestions on how I can test this further and are there any logs I can access and provide, etc.? I am happy to provide clarifications as needed.

I am using a M1 ipad pro 5th Gen. OS version 18.3.

Thanks in advance for any help!

J

Comments

  • Is there a way to temporarily uninstall the visual suite so I can test?

    reinstall the store version without restoring the IAP?

  • CPU and GPU are two distinct worlds, you could theoretically be taxing one and not the other, regardless

  • edited July 27

    @Jarly if you're not using dRambo visual then it shouldn't affect the audio DSP side of things.

    The visuals run on the GPU and the audio is on the CPU.

    It's when the Projector window is open and is rendering complex visuals (3D fractals for example) that the CPU will start spiking.

    Have you changed your buffer settings or sample rates at all?

    Do you have a 3rd party auv3 that you use consistently across your projects that may also have had a recent update?


    I'll keep an eye on the Clip lane GUI elements to see if I can replicate whilst I'm doing my stuff.


    Edit.


    Can you do a screen recording showing the issue?

  • edited July 27

    Thanks for the quick comebacks!

    I understand the differences between CPU and GPU. My (untechnical) brain just linked the two because the problem occurs only when I do something to the Drambo GUI - the clip panel being the most obvious source.

    I tested with different buffer settings and it made no impact. Even at 1024 sample buffer the problem still occurs.

    As mentioned, the problem arose in a project that was working fine a few weeks ago. I checked recent AuV3 updates and there was only one that I could point to - Waldorf Microwave 1. I know this can use lot of CPU - I checked on the loopy forum and had independent verification that this was probably not the cause. In any case I stress-tested it and in the end removed it from the project. But the cpu spikes persist.

    What I have been doing to test is sequentially removing each auv3 then moving the clip panel up and down quickly (using the up arrow on the top left of the pane) - the cpu always shoots up.

    I will keep fiddling to see if I can pin it down. I'm also checking general ipad settings to ensure it is optimised for music production. I'll come back with the results.

    Throwing it out there in case anyone experiences a similar phenomenon.

  • Thank you for giving us the heads up.

    Okay, as well as making a screen recording showing the issue, can you share one of the projects that is causing the spikes?

    You can upload a dRambo project directly in to the comments here.

  • That should not happen, but you seem to have several pugins in the equation so who knows

    can you make a simple reproducible project? Attach it here

  • edited July 27

    OK, thanks for your advice! I have been able to create a project and a video that demonstrate the issue.

    The project is 5 instances of Zeeon, each playing a 3-note D minor chord. Send A has a Dubstation instance, Send B has a Blackhole reverb.

    These Auv3s were chosen because they're common and have always been stable on my ipad. I wanted a project that would utilise around 50% stable CPU with sequencer running so that I could show the spikes.

    There's also a 'wildcard' track that I was using to test other Auv3s, but it is empty for this test.

    As you can see in the video, I set the buffer at 512 samples, and the CPU meter is at 2 bars.

    I start the sequencer then move the clip launcher pane up-and-down. Watch the CPU meter. After a few seconds the CPU chokes, audio cuts out, and the 5 Zeeons crash (but not the Dubstation or Blackhole).

    I realise that moving the clip pane frantically like this is an unrealistic situation, however the point is that the effect seems to be cumulative. In normal use - as I am creating clips, moving the panel and renaming - initially all is fine but after a few minutes even one movement can cause spikes and stutters. 

    For the test I made sure that all background ipad processes that could suck resources (location services, etc.) were turned off, and the ipad is in airplane mode.

    Finally, and seemingly related, afterwards my ipad charging was put on hold: 'Charging will resume when ipad returns to normal temperature'. That has never happened before.

    Here's a link to the video: Drambo_GUI_CPU_Test

    The project file is attached.

    Does this help or am I being silly? πŸ˜€

  • No you’re doing fine, I’m stranded in the desert so forgive me if I can’t check your files right now, maybe someone else can, otherwise I’ll get back to you

  • Thanks Pedro, and no worries. Enjoy the desert if you can, i'm something of a xerophile myself πŸ˜ƒ

  • @Jarly

    Here's your culprit;

    "Finally, and seemingly related, afterwards my ipad charging was put on hold: 'Charging will resume when ipad returns to normal temperature'."

    Both my ipad Air and macbook Air M1 started getting cpu spikes recently, my AIR 4 had the "Charging will resume..." come up.

    My macbook was spiking all over the place, projects that were running perfectly okay started getting tearing sounds etc,

    once I had placed my macbook Air M1 on a cooling fan it started playing ball again.

    Many iDevice users have been experiencing the same issues because of the heatwave here in the U.K.

  • @gravitas

    Plausible for sure, but I think this is not the cause, for the following reasons:

    1. I'm in Greece. It's 34 Celsius outside, but I'm inside in an air conditioned apartment, the thermometer currently reads 24 Celsius.
    2. I use my ipad for music production all the time, including at much higher temps, and I have never encountered an overheating issue before.
    3. Before I did the test I shut down my ipad for 10 minutes, The test was performed on a freshly booted device. As you can see, the test took less than a minute, so I think it's improbable that the ipad could have overheated due to external conditions in that short time (considering point 1)

    I'm happy to be proven wrong on this point, but I do believe that there is something going on within Drambo, and particularly related to the GUI, since I think I have ruled-out a rogue AuV3 as culprit.

  • Fair point.

    We will be testing dRambo regardless and all of the information you've provided will assist in tracking down the issue.

  • Thanks! 😎

    Please let me know if there's any more info I can provide. I'll be interested to see if anyone can replicate this.

    If not, I will accept the possibility that my ipad is dying in its arse, but I haven't noticed any problems elsewhere, and this issue only popped-up last week.

    πŸ‘οΈ

  • I tried your project on an old iPad (5th gen). Didn't have your plugins so i substituted them (Zeeon -> sunrizer; Blackhole -> Altispace 2). Tried what you did in the video at 128 samplerate but couldn't reproduce the issue. The project only crackled a couple of times but no plugins crashed. I do hope it gets resolved though.

  • edited July 27

    @oben 

    Thank you very much for testing this! You have provided a pointer that seems to have improved my situation!!! πŸ‘οΈ

    I remembered that my M1 Ipad Pro runs at 120Hz refresh rate by default. I used to have this set to 60Hz (default on your 5th Gen), but when I checked just now it was back at default 120Hz. So I reverted to 60Hz (Settings > Accessibility > Motion) and voila - I can wiggle the clip pane like a madman and there is no crash. 

    The CPU does still visibly spike, but it is within acceptable ranges for now.

    I still think there may be value in the devs checking it out. It seems oddly specific to the clip panel - if I move it the cpu jumps one or two bars. Interestingly, if I rename a clip lane, the cpu jumps two bars while I am typing! Though I also notice CPU spikes when moving knobs on Zeeon. Abusing other GUI elements doesn't have such a marked effect.

    I'll continue to keep an eye on it and report back.

    Fair play to you man, and everyone who chipped-in to now. I really appreciate all of your help.

    Did I mention that I love Drambo? 😍

  • @oben and @Jarly Thank you for finding the issue.

    We'll add that on to the things that need to be checked.

    By the way there's only one dev and a bunch of dRambonauts who love dRambo. ;)

  • dRambonauts!

    We need a T-shirt !! 😊

  • Yeah, that we do.

    That'll happen soon enough, I'm in touch with a printing company that can do this.

    I just need enough orders. :)

  • Would never have thought of that. Glad to hear that you got it working :)

  • Sign me up for one of those t-shirts guys if you please. Size L

  • πŸ˜‚ we really should, I’d wear it proudly

  • I'm not joking.

    I've been wokring off and on with a printer friend of mine for the past couple of years.

    That's how I learnt how to do 3D printing.

    I've got a couple of designs floating for stands for synths and drum machines.

    Simple stands however effective also they're the ones who will be handling the physical prints for my artwork.

  • edited July 27

    Put me down for a T-shirt, a Hoodie and a mug πŸ˜€

    OK guys, I have something further to report. I can now say with some confidence that the Visual IAP is/was the cause of my troubles. Let me explain:

    After changing the refresh rate back to 60Hz I was feeling chuffed and loaded up my live project to have a play. But after a few minutes the issue re-emerged. Whenever I would interact with the Drambo or Auv3 GUis I would get horrendous glitches. When not touching the GUIs, things would stabilise. As soon I touched the GUI, the problem would manifest.

    So I did what any self-respecting desperado would do - I consulted Google Gemini to get a list of general Ipad settings to make sure I was squeezing the most GUI resources for Drambo. These tweaks made no difference whatsoever.

    Next I purged Drambo from my ipad, rebooted and re-installed, but without the Visual IAP.

    NOW everything is working as expected - smooth as butter. My CPU meter is at 2 bars and steady. I've been playing for nearly an hour with no issues whatsoever and no visible spikes. Hell, I even loaded up a Microwave with an 8-voice multi and everything works like a champ.

    Happy days. Thanks again for all the positive input. Hit me up with any questions. I notice that ipad does keep app logs - I see some for Drambo - so these can be supplied if helpful.

    Cheers for now,

    J

  • edited July 28

    I'm back from a short holiday and catching up on this. The interesting part is that the presence of visual library shouldn't affect anything, when not used. It's only a visible list, so I suspect it must be something else. (reinstall simultaneously reset caches, preferences, saved UI state)

    I plan to release the update within a week.

    Thanks for reporting.

Sign In or Register to comment.