
- Posts: 2490
- Joined: Fri Nov 13, 2020 11:03 pm
- Real Name: Maxwell Allington
Reposting this
https://forum.blackmagicdesign.com/viewtopic.php?f=36&t=132180
I just tested it now with a simple echo effect on one track, and the problem persists (for me at least) in Resolve 17.1 beta 10
Win 10
3080 - 461.xx
https://forum.blackmagicdesign.com/viewtopic.php?f=36&t=132180
Erik Jones wrote:I have a timeline called "webcams" with 8 video/audio tracks simulating a Video Conference call. I'm then nesting that timeline into the main timeline to add in overlays, an intro/outro and some special effects.
Because the various videos in the webcams timeline came from 8 different sources, I had to work with the audio quite a bit, noise filters, volume changes, dynamics, etc. None of these seem to be reflected in the main timeline though. I was able to export the webcam timeline and then import that video, but that means every change I need to make needs to be exported/imported again.
I'm just trying to not have to deal with 30 tracks all in one place, ya know?
montoulieu wrote:Hey Erik, I'm running into the same issue as you.
Took a second for me to realize, but none of the effects in my nested timelines work on my main timeline.
I'm running Resolve Studio 17 beta 7 on Windows 10.
waynieoaks wrote:Hi
I am also seeing what I think is the same issue in 17 B23
I have several timelines that I edit then join together in a main timeline.
- All audio adjustments in fairlight work on the individual timelines
- Exporting individual timelines audio is correct
- Adding timelines to main timeline and all the audio enhancements are lost
- Adding the exported file to the main timeline and audio is correct
So I can export all the timelines individually, then bring them back into the project to join them together but then if I tweak anything I have to repeat the process.
Screenshot shows the difference between the timeline in timeline and timeline exported and added to timeline.
I just tested it now with a simple echo effect on one track, and the problem persists (for me at least) in Resolve 17.1 beta 10
Win 10
3080 - 461.xx
Windows 10
v20b4
nVidia 3090 - Studio 576.52
v20b4
nVidia 3090 - Studio 576.52