I would typically edit all my clips and cut out all the useless stuff out so I always end up with 100's of clips on my timeline. You can use automation to replicate all the cuts on your timeline. That way you'll be able to see where the cuts are.ĥ. Take that compound clip and put it on the track above all your original clips. The reason you do that is because once those clips have been converted into a compound clip Resolve now treats that new compound clip you just created as an original clip and when using the "export as individual clips" option Resolve always exports the original clip's audio (which in this case is the audio of the compound clip which references the EDITED audio).Ĥ. Select the new copies and turn them into one big compound clip. Every time there is a cut - that becomes a new clip.ģ. Make as many cuts as you want to as long as you always cut both video and audio together. Edit your clips on the timeline however you want - both video and audio.Ģ. Sharing it here in case it might help someone else out there:ġ. Thank you x 10000.After spending a whole day trying to figure this out and reading all the comments from other threads talking about this same issue I've come up with a workaround that is actually pretty good. Thanks so much for this, I really thought I was going to have to re-edit this entire interview. I tried everything - going back through autosave, clearing caches, deleting caches manually - everything. My computer ran out of space and it seemed the corrupt SOMETHING. I know this may be an older post, but I ran into this issue with a clients project. In my case it worked perfectly, make sure that you have installed the new Version and check before copiyng evrything, that your footage is running in the new Project without issues.įelix Werder wrote:With today's updated DR17, i finally found an workaround! Trying to explain the way, actually not that complicated.Īfter opening Davinci, right click on any of your Projects -> enable Dynamic Project settings (than you can should see the little check mark icon ) -> open a new Project and set timeline framerate and playback framerate to the same number (in my case 50) -> create a new timeline also with the same Framerate (make sure its open) -> now click on your project overview again and chose your DR16 project -> go to your current timeline and copy everything from there -> look on the top, under the Edit page, between sound libary and Mixer you can see your Project name, on the right side you should see a little arrow, click on it and chose the Timeline of the new project -> now you should be back on your new empty timeline, and there you can paste everything. With today's updated DR17, i finally found an workaround! Running on an old but solid laptop, MacBookPro late 2013 2.3GHz i7 with 16GB RAM and GT750M GPU w/1.5GB RAM. Maybe this is just a revision 1 issue that will sort itself out pretty quickly? Shouldn't break a sweat really, so I'm kind of surprised. Note that there is no video at all in this project, only audio. Audio I/O is the same as before, Metric Halo ULN-8 3d with 8 channels enabled in the driver, configured as 5.1 output in Resolve. There are a few changes to my system, I've hooked up the Fairlight console controllers and LCD, although I wouldn't expect them to take bandwidth from audio playback, and the new v17 audio engine is supposed to be better optimized compared to before. I do notice that Resolve is taking less CPU resources when running compared to before (as seen in Activity Monitor), which is a nice improvement. I've set it to several settings to test, including the largest, and get the same problem (in fact largest setting gives immediate crackle and stutter). If I stop and restart it, it's fine again, which leads me to suspect a buffer issue. Playback starts fine, but after a few seconds starts stuttering. Playing back a project that played fine in 16.2.7.Ībout 42 stereo tracks of 48kHz 24bit audio, some submix busses, a few plugins and effects, nothing major.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |