![]() This means it’s important to measure the delay for all your monitors and offset your playback accordingly. Sync is especially hard to get right – as just about every monitor has a different processing delay. The last thing you want during a grade review is a client asking ‘is this the right mix”’ or is that in sync or is it a bit off?’ ![]() Using Resolve 18 on an M1 Mac mini, under Ventura, 16Gb RAM, 256Gb internal, 500Gb external SSD.Tutorials / Getting Sync’d Up: Advanced Audio Monitoring In DaVinci Resolve Getting Audio Monitoring RightĪudio monitoring isn’t something we think about very often in the grading suite – but when there is a problem, clients can notice. But it would really improve the whole experience if audio weren't this issue. The good thing about this is that nested timelines are still useful for video, which is a godsend. Deleting the original tracks completely in the sub-timelines gave me a file that renders perfectly. This makes me think it's to do with something like a lost pointer to the original file that gets worse when there's a lot of previous files being tracked, but it's an assumption.Īnyway, the solution I found was to move all the audio out of the nested timelines, into the top level timeline, or one level down in one case. But once I rendered the entire top-level timeline, it returned. When I rendered just the section of my project where the problem showed up, from the top-level timeline, that actually fixed the problem. I started by clearing out all muted audio tracks, and minimizing tracks in general. I had a nested timeline that seemed to be the problem. It's the presence of audio, and particularly multiple audio tracks in nested timelines. In other words, using nested timelines isn't the problem, exactly. I've found that it's entirely audio-dependent. I wish I could find something more conclusive as directly pertaining to this even in the official reference materials. It may even be somewhat random (or seemingly random) - it might only happen on some renders, and/or it might depend on the state of Resolve when the render is done. I've just not yet found that X factor that triggers it. I've found several inconsistencies with audio rendering in nested situations - and even without nesting, if audio keyframes are used - but I haven't yet had it do the 'skipping' thing.īut it definitely exists in 17.3.2 because when I saw this thread a few days ago I rendered out my current project with nested timelines, then again decomposed, and compared the audio files and there was clearly skipping in it. I've spent several hours trying to reproduce the issue in a simple test project involving nested timelines, compound clips and multicam clips. TheBloke wrote:The test case does not go well. Is there something specific that I need to be tweaking further or changing up in Fairlight page? Any help is greatly appreciated. Others suggested playing around between CBR and VBR but that hasn't fixed the problem either. I've heard some suggest making key frames every 1 frame rather than auto and I've tried that but it didn't help. Not too heavy on fusion/composite effects either. Project is very light on the color correction and grading. Project music is all MP3 0hz and video file audio is either Linear PCM or AAC. Mixed format and codec source files but project is kept to 24 fps. Different cameras thus various resolutions and frame rates. It seems to happen no matter what I adjust in the delivery page.Ģ4 fps, 1080 project timeline. ![]() I've also tried encoding with both NVIDIA and Quick Sync but to no avail. ![]() I already tried switching between 4800 sample rates and alternating bit depths. No matter what format and audio or video codecs I choose, it seems to be at different random places in the video with each export attempt. So I'm having issues with the audio skipping or stuttering (similar to how a record or CD skips, remember those?) in the exported video file. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |