-
-
Notifications
You must be signed in to change notification settings - Fork 8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Glitching/distorted audio on DeckLink Quad 2 output #10731
Comments
I have had this same issue, I believe. The audio has very frequent, very short dropouts when it happens: This screenshot is from a recording where I played a file using a media source (48KHz audio in the file, OBS also set to 48KHz) and output that scene through the decklink output (using the filter plug-in, though this happens also with the default output) and looped that output back over SDI and captured that input, while also recording the source audio directly to a second track. So the top track in the screenshot is the looped-back decklink output while the bottom track is the direct output of the media source in OBS's recording. (Obviously I set this loop up specifically to test this -- the problem also occurred with the signal sent elsewhere.) Stopping and re-starting the output temporarily (for a few minutes) solves the problem. It did not seem to happen to me when I swapped the media source's source file out for one with 44.1KHz audio, but this could be a coincidence as it doesn't always happen in general. As for the CasparCG note: CasparCG outputs 32-bit audio while OBS outputs 16-bit audio. |
Thank you for the confirmation and visual on what's happening @CyBeRoni One other thing that's rather curious is that in both the outputs from CasparCG and OBS, neither of them seem to be setting the DeckLink configuration so that they report correctly the frequency, and 'Ch Status CRC' reports 'error'. However, if I connect the output from an ATEM switcher into the WebPresenter's inputs, it correctly shows the frequency as 48kHz and the error status changes to being ok. So it seems there's something being omitted in configuring the DeckLink I'd guess. No idea if that's related to the dropouts or not, but, it IS a bit concerning. |
when video standard mismatch, audio output from sdi is bad.
|
I am using a Decklink Quad 2. i have this audio issue on output 8. however, on output 7, i do not have this issue. I also had this issue in vMix with a similar setup. 8 had crackling, 7 was clean. |
Operating System Info
Windows 10
Other OS
No response
OBS Studio Version
30.1.2
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/tLPaxbIJtyP72JJa
OBS Studio Crash Log URL
No response
Expected Behavior
Audio should not glitch when playout is happening of video content
Current Behavior
Audio output exhibits seemingly random glitching / dropouts.
Steps to Reproduce
Windows claims the system audio is set to 48K sampling, as is OBS.
The OBS Settings -> Audio -> Advanced section has not got the low latency mode enabled, although I have tried it, and it appears to make no difference.
If I play out the exact same video clip using CasparCG 2.4.0, the audio is not a problem. Sounds fine.
I have a BlackMagic WebPresenter 4K, and, observing the outputs from both OBS and CasparCG, I notice that the number of bits being used for audio are different between the two, with the OBS audio using fewer bits - ie: the first 8 bits seemingly being always showing 'L', while the CasparCG output shows only the first 4 bits constantly being 'L'.
Image of audio section of BMD WebPresenter 4K for the OBS audio:
Image of the audio section of BMD WebPresenter 4K for the CasparCG audio:
I don't know if that's the entirety of the issue or not, but, the OBS audio issue does come and go. It's not always distorted.
Here is a sample of the resulting audio:
distorted audio.zip
IF the audio is played out on the local computer monitor, it sounds just fine.
I also tried using Handbrake to re-encode the audio to use FLAC-16 at 48KHZ, but the result was the same.
So, perhaps this is not just about audio bit depth, but something else, like dropping audio data somewhere along the way.
Very strange. The issue persists.
Anything else we should know?
No response
The text was updated successfully, but these errors were encountered: