pastelclouds
New Member
Whether recording or streaming, I have a recurring issue where my Scarlett works fine with OBS Studio + Streamlabs before beginning recording - meters respond, monitoring the sound works fine. Whenever a recording or a stream is commenced, however, the input will work for an indefinite amount of time until it suddenly cuts out. The gain meters on the Scarlett show that sound is being recorded, but when I look at both the meters on OBS and in Windows, the gain will either be frozen at a specific point or be at 0, in both cases outputting no audio.
As you can see, this also is the case when I look at it under the Sound settings on Windows.
Restarting OBS fixes the problem, until I start a new recording/stream and it occurs again. This adds to the certainty that the problem is located within OBS, as I have never had a problem with audio input from the Focusrite using any other software (Ableton, Audacity, Discord, etc)
Changing to another audio device and then back to the Scarlett within OBS does not work to fix the issue.
This is a problem exclusively with my Scarlett. Other devices (I have experimented with my USB webcam) have no problem interacting with OBS.
I have reinstalled the drivers for my Scarlett, yet encountered the same issue.
I have attached a text file with the log for a recording session where this bug occurred.
As you can see, this also is the case when I look at it under the Sound settings on Windows.
Restarting OBS fixes the problem, until I start a new recording/stream and it occurs again. This adds to the certainty that the problem is located within OBS, as I have never had a problem with audio input from the Focusrite using any other software (Ableton, Audacity, Discord, etc)
Changing to another audio device and then back to the Scarlett within OBS does not work to fix the issue.
This is a problem exclusively with my Scarlett. Other devices (I have experimented with my USB webcam) have no problem interacting with OBS.
I have reinstalled the drivers for my Scarlett, yet encountered the same issue.
I have attached a text file with the log for a recording session where this bug occurred.