RT CPU......Stuuu-ttt-ttt-eee-rrrr--*cough*

[effitall]

Originally Posted by pepe44

Can you make exact same test using another daw ?
Dont get me wrong. If there is a problem in reainsert, as it should probably be, we all would like it to get fixed.

I only use Reaper myself. Have been solely Reaper since 2009 I think. I left SONAR as it was a steamy pile then...I heard it only got worse.

What DAW should I try out? What works without iLok that would be a good test platform?

[ninjedi]

Hello- fwiw i really support using 96k for tracking and even final renders- mixing at 48khz seems to be the happier medium here.
Impulses,filters,eq's all have a lot going on realtime,so printing to committed renders and mixing them stems/clips of audio might ease system hogging..mixing might be easier with even lower buffer settings,giving better responses with any final mix automations?

Once your 2 channel or multichannel is final mixed you can still go 96k for the mastering and any final eq tweaks?
A single stereo file being mastered at 96k is very light weight on cpu. lots of mastering fx will still get the higher resolution renders.

[effitall]

Originally Posted by ninjedi

Hello- fwiw i really support using 96k for tracking and even final renders- mixing at 48khz seems to be the happier medium here.
Impulses,filters,eq's all have a lot going on realtime,so printing to committed renders and mixing them stems/clips of audio might ease system hogging..mixing might be easier with even lower buffer settings,giving better responses with any final mix automations?

Once your 2 channel or multichannel is final mixed you can still go 96k for the mastering and any final eq tweaks?
A single stereo file being mastered at 96k is very light weight on cpu. lots of mastering fx will still get the higher resolution renders.

If I had a visible CPU power issue, I'd be inclined to agree with you. At most though, my test project that I've been using the past week to tweak Reaper at most hits 30% CPU. It just doesn't seem like a CPU issue.

Once playback starts, it's perfectly fine (now). I did have some other stuttering/glitching on playback, but that has been resolved by fixing some buffers in Reaper.

[todoublez]

Originally Posted by effitall

I set Anticipative FX processing Render-Ahead to 1000ms up from 200ms.

Yep, to me ,"Anticipative FX processing Render-Ahead" is the key.
It saves me from audio stuttering every time

[effitall]

Originally Posted by todoublez

Yep, to me ,"Anticipative FX processing Render-Ahead" is the key.
It saves me from audio stuttering every time

This does seems to help a little bit at start...But after a point, it just delays the inevitable startup glitch.

I'm 100% convinced that my problem is solely caused by ReaInsert. Bypassing it makes all my Reaper problems go away. It does not matter how much buffer tweaking I do in preferences, nor what I do with latency inside ReaInsert, it just glitches.

[pepe44]

Looking at your routing :

GTR Bus (ReaInsert, EQ, Maybe some sort of spatial processor)
-->GTR DDL (Delay, maybe EQ)
-->GTR Room (Reverb, maybe reainsert)
-->GTR CHRS (Modulation, Maybe reainsert)
-->Clean GTRS (Sends to FX above)
---->Intro GTR (IR, Maybe EQ)
---->Bridge GTR1 (IR, Maybe EQ)
---->Bridge GTR2 (IR, Maybe EQ)
-->Grit GTRS (EQ might be applied here instead of on the individual tracks)
---->Grit1 (IR, Maybe EQ)
---->Grit2 (IR, Maybe EQ)
---->Octaves1 (IR, Maybe EQ)
---->Octaves2 (IR, Maybe EQ)
-->HVY GTR
---->Main1 (EQ might be applied here instead of on the individual tracks)
------>Amp1 (IR, Maybe EQ)
------>Amp2 (IR, Maybe EQ)
---->Main2 (EQ might be applied here instead of on the individual tracks)
------>Amp1 (IR, Maybe EQ)
------>Amp2 (IR, Maybe EQ)
-->Solo (Sends to above effects)
---->Main (IR, Maybe EQ)
---->Harmony (IR, Maybe EQ)

lets try to do ths:

Move the:
-->GTR DDL (Delay, maybe EQ)
-->GTR Room (Reverb, maybe reainsert)
-->GTR CHRS (Modulation, Maybe reainsert)

out of the GTR Bus. Create a new bus only for GTR Fxs

Freeze all actual tracks with media items, being:

---->Intro GTR (IR, Maybe EQ)
---->Bridge GTR1 (IR, Maybe EQ)
---->Bridge GTR2 (IR, Maybe EQ)

---->Grit1 (IR, Maybe EQ)
---->Grit2 (IR, Maybe EQ)
---->Octaves1 (IR, Maybe EQ)
---->Octaves2 (IR, Maybe EQ)

------>Amp1 (IR, Maybe EQ)
------>Amp2 (IR, Maybe EQ)

---->Main (IR, Maybe EQ)
---->Harmony (IR, Maybe EQ)

Just for a start.
Make a new save as and try this routing and see if it gets any better

[effitall]

Originally Posted by pepe44

Looking at your routing :

GTR Bus (ReaInsert, EQ, Maybe some sort of spatial processor)
-->GTR DDL (Delay, maybe EQ)
-->GTR Room (Reverb, maybe reainsert)
-->GTR CHRS (Modulation, Maybe reainsert)
-->Clean GTRS (Sends to FX above)
---->Intro GTR (IR, Maybe EQ)
---->Bridge GTR1 (IR, Maybe EQ)
---->Bridge GTR2 (IR, Maybe EQ)
-->Grit GTRS (EQ might be applied here instead of on the individual tracks)
---->Grit1 (IR, Maybe EQ)
---->Grit2 (IR, Maybe EQ)
---->Octaves1 (IR, Maybe EQ)
---->Octaves2 (IR, Maybe EQ)
-->HVY GTR
---->Main1 (EQ might be applied here instead of on the individual tracks)
------>Amp1 (IR, Maybe EQ)
------>Amp2 (IR, Maybe EQ)
---->Main2 (EQ might be applied here instead of on the individual tracks)
------>Amp1 (IR, Maybe EQ)
------>Amp2 (IR, Maybe EQ)
-->Solo (Sends to above effects)
---->Main (IR, Maybe EQ)
---->Harmony (IR, Maybe EQ)

lets try to do ths:

Move the:
-->GTR DDL (Delay, maybe EQ)
-->GTR Room (Reverb, maybe reainsert)
-->GTR CHRS (Modulation, Maybe reainsert)

out of the GTR Bus. Create a new bus only for GTR Fxs

Freeze all actual tracks with media items, being:

---->Intro GTR (IR, Maybe EQ)
---->Bridge GTR1 (IR, Maybe EQ)
---->Bridge GTR2 (IR, Maybe EQ)

---->Grit1 (IR, Maybe EQ)
---->Grit2 (IR, Maybe EQ)
---->Octaves1 (IR, Maybe EQ)
---->Octaves2 (IR, Maybe EQ)

------>Amp1 (IR, Maybe EQ)
------>Amp2 (IR, Maybe EQ)

---->Main (IR, Maybe EQ)
---->Harmony (IR, Maybe EQ)

Just for a start.
Make a new save as and try this routing and see if it gets any better

Or...If I disable all ReaInsert, it works pretty much flawlessly. It doesn't seem like it's the routing that's causing the issue.

[mattmenck]

I can feel you, since I´m having the exact same thing.

Some weeks ago I switched from Logic to Reaper because the Multithreading in Logic is pretty poor.
I got quite long bus chains filled with cpu hungry mastering plugins and logic just put almost everything onto 1-2 from 16 cores aka 32 threads.

Anyway, long story short Reaper can handle all my plugins and bus chains without problems, even on highest oversampling rates (16X /32X). Impossible in Logic.

But when it comes to ReaInsert to integrate my mastering outboard it is just a mess of glitchy things, beatjupmps and crackling noises, also on start stop, solo and whatever tasks. Its rather impossible render a project clean out without any interruptions.

On my current project it was just one instance of ReaInsert, but enough to ruin the hole project.

Same like yours, when bypassing ReaInsert, everything runs fine.
This makes it impossible to work with any of my mastering hardware gear in Reaper.

I have have tried so many setups /settings and buffers up to 4096, pre fx buffering until 5000.
Sometimes you can get lucky, but in 99% of the cases the printing is unusable cause of glitches and stuff like that.

CPU is running on 15% /real time CPU 0,3%
Mac Pro (Model 2019 /16Core)
Running just 44.1 or 48kHz.

It drives me crazy..
Logic can't address all cores in a balanced way what Reaper does so well, but Reaper can not handle my outboard gear through Reainsert.

Btw. have you noticed, that the render window shows a speed up x-number when printing online.
This is wired. Online rendering should be real time but it starts at x 0,0 correctly and then goes up to x1,0 or something, which is quite confusing.

I was full of hope that Reaper can become my new mastering DAW to leave the CPU issues from Logic behind. But its unlikely like running from one problem into a new one.

Please keep this thread updated if anyone got a solution. I will do the same.

We hope for the best !
Thanks guys, take care

[SteveK_Germany]

related to the original thread:

You use 5ms latency @ 96kHz and wonder why you have glitches?
not many systems will do that at all - unless you have pro sound gear.

I have a very powerful CPU where tons of synths and FX will cause 10-20% CPU only. But when I lower latency all the glitches and stutter appears - even at 10% CPU usage (I have a "cheap" Yamaha USB sound device for 150$).

It is not only the CPU that needs to be fast - but also the sound device or driver. You can solve this with more pro gear hence more expensive gear.

Sometimes legacy VSTs cause that too because they slow down - check to use VST3 instead of VST(x86).

General test: Try to lower latency to 20ms or slower and look what happens. If it works then it is the sound gear.