Audiotool board archive

I MADE A DISCOVERY (Possibly lag-reducing)

Jetdarc · started 2019-06-16 20:06 · updated 2019-06-21 16:50

---so um i had audiotool (with booster on) and fl 20 open at the same time and im like
---doesnt this usually lag?
---so i closed fl and the lag came
---opened fl again and the lag is mostly gone
---i tried playing my biggest project in audiotool with fl open and audiotool booster open and it only has minor lag
---i don't know how exactly this works but holy shit

video for proof that it at least works for me: https://drive.google.com/file/d/1oupsyS8n_I5GZa8KsD96SWUMbzDcmnox/view?usp=sharing

also my voice sounds bad but thats just me i guess

Comments (21)

2019-06-16 22:41 · 2019-06-16

I'd look in the task manager to see what's up

2019-06-17 00:23 · 2019-06-17

Saw that on Discord - pretty strange/weird/funny :D
Thanks a lot for the explanation and that video!

Besides the overall counter-intuitivity: I'm really impressed that this works without having to restart the Bosster.

@andremichelle we should definitely try to see what we can make out of that. I assume FL configures the sound driver in a 'special way' which affects our Booster's behavior as well (maybe thread priority, internal buffers?).

@jetdarc can you test if this also affects AT in 'worker' or 'worklet' mode (without Booster)?

Jetdarc · reply
2019-06-17 01:15 · 2019-06-17

Alright i'll try it out

Jetdarc · reply
2019-06-17 01:29 · 2019-06-17

So this is what I got:
WITH WORKLET
--FL 20 + booster + Worklet on = little to no lag
--Booster + Worklet = Noticeable Lag
--Just worklet = Major lag
--Nothing= Major lag x3

WITHOUT WORKLET
--FL 20 + booster= Little to no lag (same as with worklet on)
--Booster= Noticable lag (a bit worse than with worklet)
--Nothing= Major lag x100
Jetdarc · reply
2019-06-17 03:30 · 2019-06-17

well when i have fl studio on with audiotool, my cpu usage is around 30%, but without fl, its more like 50-60%

Jetdarc · reply
2019-06-17 13:29 · 2019-06-17

ooohh I see my bad

Jetdarc · reply
2019-06-17 13:43 · 2019-06-17

Okay so here's the correct test without the booster:
FL20 + Worker = A lot of lag
FL20 + Worklet = Very little lag on smaller projects (but not no lag); a lot of lag on bigger projects
There is way more lag without FL20 open

Known As I · reply
2019-06-17 13:47 · 2019-06-17

Thank you. So every mode benefits from FL being opened in the background, right?

Known As I · reply
2019-06-17 13:48 · 2019-06-17

Are you using ASIO drivers or some other special 'tuning' for musicians?

Jetdarc · reply
2019-06-17 14:17 · 2019-06-17

yep, they all benefit, and the only driver that i know of that i use for music is ASIO4ALL

Jetdarc · reply
2019-06-17 14:18 · 2019-06-17

but i also tested opening FL20 on games that are also usually laggy and it also reduced the lag in those games so it may not just be audiotool

Jetdarc · reply
2019-06-17 14:18 · 2019-06-17

its just so ironic to me

Known As I · reply
2019-06-17 14:22 · 2019-06-17

I expected this to be a global (anti-)problem with the driver; that's why I asked for the worker/worklet modes.
I'll try to do some research on how ASIO4ALL works and how we could benefit from your findings. I'm pretty sure we cannot do anything for the worker/worklet but the Booster might have some options.

Jetdarc · reply
2019-06-17 14:23 · 2019-06-17

alrighty

2019-06-20 20:50 · 2019-06-20

So in other words guys... if you want less lag, go out and spend around $800 to $900 dollars on FL, get the audiotool booster, and start up audiotool.

anonymous user
2019-06-21 02:37 · 2019-06-21

i tried it. didn't reduce any lag for me. prolly gonna try again.r

Known As I · reply
2019-06-21 09:46 · 2019-06-21

What driver do you use? Some ASIO?

2019-06-21 16:48 · 2019-06-21

not to discredit the argument, but i don't know how people think fl is $900. The Producer Edition (the only one you'll need) is only $200 bucks

kurp · reply
2019-06-21 16:50 · 2019-06-21

I think it was sarcasm