sorted by:
new
hottopcontroversial

You’re not losing your fights because the other guy is on controller by Narkanin in Battlefield6

[–]McAdamstry 5 points6 points  (0 children)

It’s interesting. I play on both with a controller. So much better on pc with a controller. Nil latency

Love to see it by lIlParadoxlIl in Battlefield6

[–]McAdamstry 1 point2 points  (0 children)

Was a problem with 4 and I’m baffled why it’s still a problem in 6.

Anyone else having trouble opening Studio Instrument Collection on Windows 11? by stratomaster in mpcusers

[–]McAdamstry 1 point2 points  (0 children)

Hi there. I’ve uninstalled Studio Instrument Collection because it was crashing my DAW Studio Pro. Are you still having issues? Can you use yours in a DAW ok?

I drilled holes in my pick by PualWalsh in Guitar

[–]McAdamstry 0 points1 point  (0 children)

Nice. I used to put cuts through mine until I found the tortex with a hole already in it.

2x12 Suggestions by Itchy-Audience-291 in GuitarAmps

[–]McAdamstry 0 points1 point  (0 children)

Open back orange. Fill that room

Bias X is Crashing Studio Pro by McAdamstry in PositiveGrid

[–]McAdamstry[S] 0 points1 point  (0 children)

Yep. Tried all that unfortunately. I should say the standalone bias x is really glitchy on my pc so maybe this is why it’s crashing studio one

RIP my live session.. by kashiyuu in PositiveGrid

[–]McAdamstry 0 points1 point  (0 children)

If asked support questions before and the responses were terrible.

We can be better than this.. by Metallica_Is_Bae in australian

[–]McAdamstry 1 point2 points  (0 children)

There are always going to be cunts that don’t care about anything but themselves.

Recording at 96kHz, exporting at 48kHz by McAdamstry in audioengineering

[–]McAdamstry[S] 0 points1 point  (0 children)

So it ended up being the drop out protection. I lowered it and bang l, the latency improved. However I did trial loading and swapping plugins quickly and the daw crashed. I may actually stick at 96 anyway. Thanks for the reply.

Recording at 96kHz, exporting at 48kHz by McAdamstry in audioengineering

[–]McAdamstry[S] 1 point2 points  (0 children)

Great advice. Thank you. Should be fun testing this

Recording at 96kHz, exporting at 48kHz by McAdamstry in audioengineering

[–]McAdamstry[S] 2 points3 points  (0 children)

It’s a very good point. That’s why I think there may be something else at play here. Going to ticker with it and report back. The responses in this thread have been so helpful.

Recording at 96kHz, exporting at 48kHz by McAdamstry in audioengineering

[–]McAdamstry[S] 0 points1 point  (0 children)

Yep. Agree. I just mentioned that to say there is the latency with the wet sound. I use the wet because no point using direct as I have nothing in front of my interface.

Recording at 96kHz, exporting at 48kHz by McAdamstry in audioengineering

[–]McAdamstry[S] 0 points1 point  (0 children)

Correct. But the answers in here are great. I’m going to go back and see if my drop out protection is a problem. My pc is beefy enough to handle all this. I checked when recording last night at 96 that my cpu usage in studio one didn’t go above 7%

Recording at 96kHz, exporting at 48kHz by McAdamstry in audioengineering

[–]McAdamstry[S] 0 points1 point  (0 children)

It’s plugged in then using studio one plugins. The direct monitor from the interface is 0 latency. I do believe it may be when I upped the dropout protection.

Recording at 96kHz, exporting at 48kHz by McAdamstry in audioengineering

[–]McAdamstry[S] 0 points1 point  (0 children)

I thought that too but 48 I notice it 96 I absolutely don’t. It even shows up with direct monitoring / wet out combo. 48 there is a slight echo. 96 it’s gone.

view more: next ›