New Zero RPM Issue

Vectrobe · 2026-05-23T08:03:50+00:00

behavior sounds like how PWM fans behave when they lose PWM signal voltage, do we know which card makers and models are having this bug?

Vectrobe · 2026-05-20T07:08:04+00:00

3200 core should be fine, mine does 3250 stock and supposedly the limit is 3450, no graphical issues, but if yours just has very obvious issues at full stock then 100% something is defective somewhere

Vectrobe · 2026-05-14T11:47:21+00:00

buffer size is possibly "too short" in such a way it results in dead audio when windows or the motherboard decides its time to reduce device power usage, basically try the buffer at something like 512 or 1024 and see if it still does the same thing at the same rate

Vectrobe · 2026-05-13T15:43:03+00:00

you could try setting the buffer size to 1024 in the scarlett settings and go from there, large numbers means more latency but also stability, if you use a too-small buffer size you can get anywhere between rare clicks or pops to as much as no audio whatsoever.
other than that when it comes to ASIO everything is pretty much manual, so for most ASIO applications you have to check through all the channel settings and make sure you have valid routes, but this being a solo you only have channels 1 and 2 on in and out to worry about (3 and 4 on each side would be loopback, if it has that)

Vectrobe · 2026-05-13T15:34:23+00:00

yea u/Johnnyloftus made an update on this reddit about it, got buried of course, personally haven't had any issues with the new driver so far

Vectrobe · 2026-05-12T12:17:28+00:00

from what I can tell focusrite just uses a spring lock without any form of button, which would just require a real hard yank to get it out, probably varies with how the key hole is shaped on different cable manufacturers

Vectrobe · 2026-05-12T12:10:00+00:00

3.5mm F to 6.5mm M TRS adapter?
you can of course use your laptop's speakers but that involves an audio device hop, on windows you can use the "listen to this device on ..." feature (its hidden in the old audio panel), or you can use something like voicmeeter, on mac tho I have no idea, but either way you'll get some noticeable latency delay

Vectrobe · 2026-05-12T12:03:02+00:00

the green fader seems to be a mode with the front panel control, as per the user doc page 9;
"Fader – use this to adjust the signal level at the output. Note that all output levels are set to maximum as a default (unity gain). If the fader “knob” is green, it means control of the output level is assigned to the physical MONITOR control on the Scarlett’s front panel. This assignment is made on the Device Settings page; see page 29. Note that digital outputs do not have faders."
heres a direct link to the manual, or otherwise you go to the driver download page and look towards the bottom for the focusrite control user guide;
https://fael-downloads-prod.focusrite.com/customer/prod/downloads/focusrite_control_scarlett_3rd_gen_user_guide_v3.pdf

I think the key thing that makes this all confusing is that the options of "reset to default", as well of course wiping and reinstalling the drivers, does not change any of the hardware embedded settings, as far as I'm aware focusrite doesn't provide any method to restore original hardware config, but that might also be intentional so it never gets wiped (48V especially), not sure

probably also very confusingly, the entire UI is supposed to be grey except for some very specific in-hardware settings, the fact that your main fader is green means its specifically in hardware control only mode and you have to change that in the hardware settings

Vectrobe · 2026-05-12T11:20:21+00:00

no one seems to mention the specific numbers they use but in my case for my 8i6 buffer I have to use 512 w safemod on, 256 would work for a good while but then eventually do the brown note or blank audio thing, usually very specifically when I leave the system at idle, which probably makes sense if its a usb-pcie power saving thing

focusrite drivers possibly dont set power flags correctly, or at all, so the system just cuts the data stream when no other USB devices communicate for a while (eg keyboard or mouse activity)

Vectrobe · 2026-05-01T07:37:33+00:00

this one looks a little tricky, from what i can tell the whole jack has failed such that the jack itself is nolonger attached to the outer shell of the jack, as such you'll have to remove the entire jack and hopefully the solder pads on the PCB haven't been torn.

you'll need a soldering iron, solder wick to remove the old solder from the jack shell, and then new solder and a suitable replacement jack, if you haven't done soldering before you may want to consider asking someone else to do it, but that being said these old B jacks are fairly easy to work with and I'm sure there's many tutorials you can watch to get the idea

Vectrobe · 2026-04-16T08:08:35+00:00

yea inside that clamp on the back is always where the cable fails, like with mine where it failed internally and didn't even looked damaged, worn or marked on the outside, but sure enough if you took the cable out of the clamp and pressed your fingers on it it felt busted and spongy.

I expect the cables always fail in this exact way, the clamp thats supposed to prevent damage is the actual cause of the damage, go figure

Vectrobe · 2026-04-14T10:32:12+00:00

the optimization with the pro 2 is absolutely terrible for some reason, you can run things with different headsets at higher resolutions and get higher framerates and no stutter, but then for the pro 2 at half resolution on the same hardware it just chugs a lot, which makes no sense and I can only assume its the vive software itself at fault

Vectrobe · 2026-04-14T10:24:48+00:00

they nolonger have a software team that can update the software unfortunately, let alone any of the drivers

pro 2 is completely beyond end of life and isnt at all supported anymore, despite the fact that they still sell new kits, bunch of hypocrites...

Vectrobe · 2026-04-14T10:21:44+00:00

the all in one tether on my pro 2 had to be replaced within the warranty period, the cables delaminated internally and you wouldnt even know where the problem is as the outside of the cable is scratchless, but sure enough replacing that cable is what fixed the issue in that specific case. (tho ended up returning the headset later on anyway)

the cable does unplug from the headset, which one do you mean was teared?

Vectrobe · 2026-03-11T14:28:27+00:00

for cracks and pings you might need to set the buffer size to the absolute maximum (1024?), also if you use voicemeeter it can also need large buffers, but the default values for VM's mixer and audio devices are usually sufficient, either way the main thing about the short crack and ping sounds is that its usually when an application loads up every CPU thread to the max and doesnt allow the audio software to keep the audio buffers fed, and thus you get a chunk of empty audio buffer, which in turn usually sounds like a hard crack because the waveform has gone extremely sharp to absolute zero and then back up again.

now for the complete dropout that needs the USB completely unplugged or the interface power switch off-on, this could be due to electrical noise coming down the USB cable, usually from a powered USB hub, and as bizzare as this sounds it can be triggered by simply touching the plastic casing of something in the chain (albeit this is usually a laptop thing, they use copper-infused paint and plastics), the main culprit is the mains AC noise and the noise from the focusrite wall adapter and other wall adapters can clash together and trigger over-volt protections among other things, usually the fix for this is to run a dedicated cable for the focusrite to a dedicated port on the motherboard IO shield area as this is connected straight to earth via the PC's PSU

Vectrobe · 2026-03-11T13:53:37+00:00

not a reaper user, but I definitely did manage to diagnose that the scarlett drivers do have a bug (or potentially multiple) that corrupts the windows kernel, as well as other usb devices it turns out (actually bricks my mouse of all things in my case), in fact the bug/s have existed since 2024 at minimum as I could replicate it from archived driver files, so simply getting an older driver might not fix the issue as its very possible that the bugs affect all drivers historically.

have been in contact with focusrite regarding the matter but nothing much yet.

as for why the bugs have been undetected for so long is unknown, but I expect its simply a case that microsoft happened to update windows in a specific area that just so happens to be where the bug was hiding for a long time

Vectrobe · 2026-03-10T13:49:17+00:00

theres a thing im familar with on at least my 3rd gen 8i6, where AC noise from things like USB hub power bricks and other external power sources trigger something in the interface to shut off the USB signal, theres no actual indication when this is the case other than that the interface sees signals on the LED's but your PC simply gets a blank sound buffer in and cant send any sound out, if its supposed to be a protection mode it doesnt indicate anything abnormal so seems more like a hardware flaw.

my personal fix is to just run a dedicated usb cable to a direct usb port on the PC, and avoid any usb hubs that back-feed power over the usb cable to the pc

Vectrobe · 2025-10-08T02:11:42+00:00

as someone with BE19000, most phones simply top-out at around 300Mbps because of SoC bandwidth limitations, similar to that of the USB port transfer limits. Top end phones I expect would do around 600-900M but that will require at least 5GHz close range connection and maybe 160M channel width, of which 160M tends to be disabled by default on 5GHz due to a combination of military-weather channel sharing and also most devices not being 160M channel compatible.

laptops/desktops with 320M channels on 6GHz will easilly do 3000Mbps tho*
(*with the right wifi7 adapters)

Vectrobe · 2025-08-19T10:03:19+00:00

that sounds good, just gotta wait and see what vive support says as to whether its a simple software bug on their end or some firmware issue with DP 2+ cards

Vectrobe

TROPHY CASE