Bug? Deliver timeline track solo indicators

Project with multiple timelines. Audio engineer creates single track mixes for destination requirements (e.g. -16db for Vimeo). When I go to deliver, I solo the appropriate track on Edit, click over to Deliver, and add to the queue. If I render just that one video, the appropriate track shows up as soloed. However, If I batch this process, adding multiple timelines to the queue, the solo indicator does not show when I render. This freaked me out.

solo-render.png (9.33 KiB) Viewed 605 times

I believe it still rendered with the channel soloed properly ... but I don't know.

Can we ensure that the settings you select, and how the project is exporting, display accurately for those of us who check on renders? It'd give me much more peace of mind [smile].

Thanks!

~Luke

I experienced this as well. Probably related: viewtopic.php?f=36&t=132127

As a workaround, I found that muting the opposite tracks worked in batch renders.


Sent from my iPad using Tapatalk

I experienced this as well. Probably related: viewtopic.php?f=36&t=132127

I had noticed that solo didn't save when I quit and came back, but I hadn't realized it also un-soloed when switching timelines. Now I'm even more concerned that the render was not done properly...

Thanks for sharing. This does look like it could be a related/larger issue.

~Luke

I just tested this with Resolve Studio 18.1.1. The solo and mute states do not appear to be saved with the render settings. Whatever you see is the current state of those buttons appears to apply to all render jobs.

Is this expected? I can't say. My guess is that if you, for example, setup a number of render jobs and for each job you disabled a different clip in the timeline before sending the job to the render queue and then once all the jobs were in the queue, clicked 'Render All', the most recent state of the timeline would apply to all render jobs (ignoring your other disabled clips in preference for whichever was most recently disabled). That makes sense to me so why would I expect anything different from things like the solo and mute buttons?

...the most recent state of the timeline would apply to all render jobs (ignoring your other disabled clips in preference for whichever was most recently disabled). That makes sense to me...

Thanks for jumping in here, Steve. I think I'm misunderstanding. I've created spots in the past with different Calls-to-Action so Marketing could test each one. I have one timeline with the different end cards on a different track. I setup render 1 to show the Track 2 animation. Render 2 has Track 3. Render 3, Track 4, etc...

To me, it would not make sense to hit Render All and have it render five copies of the same video (e.g. Track 5). I specifically setup different renders, and I expect Resolve to honor that. But is that not how it works? Have I saved myself by rendering things one-at-a-time? I honestly don't recall now if I've done batches like this or not, but this seems strange.

Am I an outlier on this? Am I "supposed" to make a new timeline for every possible render situation instead?

Thanks!

~Luke

Am I "supposed" to make a new timeline for every possible render situation instead?

It would seem so when the 'render situation' substantially changes the timeline content. When you change the solo/mute buttons you are changing the timeline, just as if you had replaced an audio or video clip, I suppose.

Where you don't need to make a different timeline is when the timeline doesn't change, just the render settings such as codec and resolution, etc.