LayR Love: (update)Use Function Performance

RUST( i )K

AFTER DAYS IF NOT WEEKS OF ELIMINATING AND TRYING TO FIGURE THIS OUT I WANT TO SAY THAT THE CRACKLING HAS ABSOLUTELY NOTHING TO DO WITH LAYR CAUSING IT. I HAVE NARROWED THE ISSUE DOWN INTO 2 OR 3 POSSIBLE SCENARIOS WHICH I AM NOW EXPERIMENTING AND ATTEMPTING TO REACH AN UNDENIABLE CONCLUSION THROUGH REPLICAION AND VALIDATION THROUGH OTHER USERS.

SO, TO BE CLEAR, THERE IS NO ISSUE WITH THE LAYR APP. IT IS A UNIQUE AND PESKY SITUATION INVOLVING AND AUDIO INTERFACE AND POTENTIALLY ANOTHER APP. I ONLY THOUGHT IT WAS LAYR BECAUSE IT IS ONE OF THE ONLY APPS I USE.

THANK YOU FOR YOUR UNDERSTADING AND APOLOGIZE FOR ANY CONFUSION.

I love this app in a big way. Tad frustrated sometimes lately.

I am wondering, how many other apps can you use while using LayR? Which?

Audiobus 2 or 3.

Do you get any crackling?

I have something going on I can't figure it out so would love your help.

[Deleted User]

The user and all related content has been deleted.

RUST( i )K

@tja said:
More details would help.
Anything I should try out?

Run multiple apps while using LayR

Open other apps first. Then Layr.

Any crackle?

How many apps can you use without getting issues with Layr?

brice

Hmmm, I don't believe I've ever encountered any overloads or crackles in any of my LayR scenarios on an iPad Pro 12" from last year. I've never tried running it with something like a big Auria session, that might cause some issues, but I'd expect it to. Day to day stuff; multiple effects apps, other synths, Patterning, Fugue, none have caused any problems on this end.

Outline a scenario and I'll try and replicate it here.....? I probably have some or most of the apps you're using. Send me a LayR preset(s) too if you'd like. Also, I know I am stating the obvious here, but just in case, what buffer setting are you using in LayR and what is your max voices amount set to? Background audio on / off? Link on or off? And what about "ignore MIDI clock?"

One other thing, if you're running a fair amount of layers / instruments with long release times, that might be a part of the resource demands. When I say long release times I mean considerably long. Maybe take note of that and see if that might be at play?

RUST( i )K

@brice said:
Hmmm, I don't believe I've ever encountered any overloads or crackles in any of my LayR scenarios on an iPad Pro 12" from last year. I've never tried running it with something like a big Auria session, that might cause some issues, but I'd expect it to. Day to day stuff; multiple effects apps, other synths, Patterning, Fugue, none have caused any problems on this end.

Outline a scenario and I'll try and replicate it here.....? I probably have some or most of the apps you're using. Send me a LayR preset(s) too if you'd like. Also, I know I am stating the obvious here, but just in case, what buffer setting are you using in LayR and what is your max voices amount set to? Background audio on / off? Link on or off? And what about "ignore MIDI clock?"

One other thing, if you're running a fair amount of layers / instruments with long release times, that might be a part of the resource demands. When I say long release times I mean considerably long. Maybe take note of that and see if that might be at play?

First thing in am

AB2

AUM audio from interface
Genome
Animoog
Reclice
Layr

all into loopy

RUST( i )K

So had AUM open with interface input audio

Had Genome open
Had Animoog open
Loopy in multiple out puts.

Open LayR and press keys.........crackle distortion

Then I close LayR and the whole session is left crackling.

Need to restart

This is what happens on my Air 2 with LayR

I just can't fgure this out.

LivingMemorySoftware

@Rustik: I've just seen your comments here:

I don't have Genome or Reslice but I have all the other apps you mention and I'm seeing 57% on my Air 2.

I have a couple of suggestions:

By any chance have you turned the number of voices in LayR up to 256? It's best at 128 with other apps running on an Air 2.

It doesn't matter how many layers are active in LayR it will always use a constant amount of CPU. On an Air 2 this should be averaging between 40-47% @ 128 voices.

If the crackling is still happening after LayR is quit that suggests to me the issue is away from LayR itself.
Could it be one of the apps is running at the wrong sample rate and the system is doing rate conversion?

This event that happened to me might be of interest though. After a recent iOS update all apps started significantly using more CPU one evening and a single restart made no difference. In frustration I just force restarted twice more and the problem cleared. Other system processes run in the background eating CPU sometimes, e.g. it could be Spotlight indexing the iPad and if it hasn't finished it will start up again when you restart.

Using AUM as the meter, I've found on my Air 2 that if the CPU rises above 70% then crackling will sometimes appear. An average of 70% can mean that there are occasional spikes of over 100% when the system occasionally delays the core-audio rendering thread.

[Deleted User]

@LivingMemorySoftware thx for the update(s), have a nice day!

brice

FWIW.....Animoog playing chords, while LayR and ReSlice are playing Arp patterns inside of AUM I'm hovering around 50% DSP (44.1 / 512 Buffer in AUM). 25% of that total usage is going to ReSlice alone, with Animoog and LayR contributing to the other half. That's on an iPad Pro. If something like Loopy were to be added in the mix where I'm having to write / record realtime audio to disk then I imagine my usage would go up pretty significantly.

RUST( i )K

@LivingMemorySoftware said:
@Rustik: I've just seen your comments here:

I don't have Genome or Reslice but I have all the other apps you mention and I'm seeing 57% on my Air 2.

I have a couple of suggestions:

By any chance have you turned the number of voices in LayR up to 256? It's best at 128 with other apps running on an Air 2.

It doesn't matter how many layers are active in LayR it will always use a constant amount of CPU. On an Air 2 this should be averaging between 40-47% @ 128 voices.

If the crackling is still happening after LayR is quit that suggests to me the issue is away from LayR itself.
Could it be one of the apps is running at the wrong sample rate and the system is doing rate conversion?

This event that happened to me might be of interest though. After a recent iOS update all apps started significantly using more CPU one evening and a single restart made no difference. In frustration I just force restarted twice more and the problem cleared. Other system processes run in the background eating CPU sometimes, e.g. it could be Spotlight indexing the iPad and if it hasn't finished it will start up again when you restart.

Using AUM as the meter, I've found on my Air 2 that if the CPU rises above 70% then crackling will sometimes appear. An average of 70% can mean that there are occasional spikes of over 100% when the system occasionally delays the core-audio rendering thread.

I really appreciate you commenting.

I think your app is the most important synth in years for what it brings.

I will look into the sample rate thing tonight.

I am just glad to know there is something that is happening which may still be on the periphery of LayR but guilt by association at this point.

With my due diligence I will explore the matter and implore all of your recommendations.

Thanks so much

audiblevideo

Definitely turn down the number of voices as recommended.

thesoundtestroom

In this I had the buffer set at max 1024, and the cpu is still over 50% all the time, but I never noticed any latency problems when playing

RUST( i )K

@thesoundtestroom said:
In this I had the buffer set at max 1024, and the cpu is still over 50% all the time, but I never noticed any latency problems when playing

Thanks Doug

LivingMemorySoftware

@thesoundtestroom said:
In this I had the buffer set at max 1024, and the cpu is still over 50% all the time, but I never noticed any latency problems when playing

@thesoundtestroom
Hey Doug, pretend this is Facebook. I just pressed the Like button