![]() If your device has any other DSP you probably won't have Realtek's audio console installed since the brand-name one would be there in its place, try checking for audio processing there. It's a cheap-ish laptop so there's no name-brand thing like Nahimic, MaxxAudio, … it was just Acer's TrueHarmony, but it was enough to mess things up. In my case, because I was using its built in ALC255 by Realtek I opened the audio console and disabled audio processing there under Speakers. Hi there, I registered just because I was experiencing this in my laptop and while I didn't get to the root of it (no access to the DSP code) I located the issue in the audio drivers it ships answer above was on point too, if you disable the ability for audio DSPs stemming from the audio card drivers you get "clean" or unaltered audio. So I am delighted to be able to use OBS to design, organize, and drive a program of mixed live and recorded video content (with music) through Zoom to remote attendees - with a client audio experience (as good as/no-worse than) the native Zoom mechanisms. Both recorded client tracks were identical - no more muffled sound in the OBS sourced version! With a second pc running the Zoom client, I captured its audio into Audacity and compared the result with a track recording of the same video shared with Zoom's screen sharing (with "use computer sound" and "optimized for video clip" options). And used the Zoom client audio setting of "use original sound' with 'stereo' and 'high fidelity' options - but not "echo cancellation". Then I set the VB HiFi Cable Output as the Zoom microphone.ĥ. I verified the output from OBS first by sending the monitor audio to Audacity, recording the track and comparing to the original.Ĥ. (For some reason 48 kHz produced unwanted noise?)ģ. I changed OBS sound to 44.1 kHz and set HiFi Cable to match. changing from VB Cable to VB HiFi Cable.Ģ. mp4 for editing or otherwise, then you can remux the recording afterward, either by doing this manually through the File menu, or automatically after each recording (which you can enable via the advanced options).Thank you! I appreciate the info and advice.ġ. crash, or badly behaving OS), then the entire recording will be corrupted. This container format requires metadata to be recorded at the end of the recording, and if the recording is interrupted prematurely for any reason (i.e. Your x264 encoding looks fine past the rendering lag, but honestly for recording there shouldn't really be any reason to not use NVenc as long as the issues are cleared up. That's the likely reason why you have extra encoding lag on top of rendering lag. This can be fixed by running OBS in administrator mode - this will tell windows to add OBS into the GPU priority so that it can perform the necessary scene compositing without being impeded by whatever other GPU functions are running (like your game).įor your nvenc recording, you're using Max Quality - this setting requires CUDA, so it uses extra GPU resources outside of the NVenc encoder (Look Ahead and Psychovisual tuning also do this, just for an fyi). The main issue you're running into is rendering lag. Skipped frames due to encoding lag normally mean that your encoder settings have a problem, or are set too high for your hardware.ĭropped frames are only encountered during streaming, and are always a network issue.ġ4:18:25.201: preset: fastġ4:18:25.201: profile: highġ4:18:25.201: settings:ġ4:19:01.357: Output 'adv_file_output': Total frames output: 2061ġ4:19:01.357: Output 'adv_file_output': Total drawn frames: 2060 (2169 attempted)ġ4:19:01.357: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 109 (5.0%)ġ4:19:01.357: = Recording Stop =ġ4:19:01.357: Video stopped, number of skipped frames due to encoding lag: 8/2168 (0.4%) There's no metric by that name in the OBS Stats dock.įrames missed due to rendering lag generally are due to an over-loaded GPU. empty padding eating up drive space to meet the set constant bitrate.ĭepends on which 'lost frames' you mean. You would gain zero benefit, and just load your recording drive down with superfluous 'dead' data. Running a ridiculously high CBR bitrate tailored to your highest possible motion scene could compensate to avoid choke, but that would be pointlessly and utterly wasteful. It's about intelligently using exactly as much bitrate as is needed at the moment. leading to a massive waste in the case of the static image, and severe video quality degradation in the high-motion scene.ĬQP isn't about saving space. So no matter if you're showing a single static image, or incredibly high-motion video, it will use the same bitrate regardless. It uses as much or as little bitrate as needed to maintain a consistent image.ĬBR uses a set rate regardless of what's happening in the video. CQP is an image-quality based encoding target.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |