Page 1 of 1
Data Burn-In seems to be broken in 18.0.4 (Mac)
Posted:
Wed Oct 05, 2022 5:15 pm
by JimCurtis
I was unable to delete the Data Burn-In on some clips in the latest build until I reverted Resolve back to 18.0.3.
Just reporting my experience.
Re: Data Burn-In seems to be broken in 18.0.4 (Mac)
Posted:
Wed Oct 05, 2022 5:51 pm
by Dwaine Maggart
What does that mean?
Did you have a project from an earlier version that had data burn-ins enabled, and in 18.0.4, you tried to turn off the enabled data burn-ins and you couldn't?
Were they Project or Clip burn-ins? Do you know what Resolve version the project was created in?
Re: Data Burn-In seems to be broken in 18.0.4 (Mac)
Posted:
Wed Oct 05, 2022 6:12 pm
by JimCurtis
Yes, I applied Data Burn-in to Clips in a previous version. It was around July 10 this year, so it was the current version around that date. It may have been a beta build.
I installed 18.0.4 yesterday, and noticed I couldn't remove the Data Burn-In today. After re-installing 18.0.3, I was able to remove the Data Burn-In.
Sorry that I wasn't clear.
I can apply the Burn-in in 18.0.4 and then remove it. So, this may only apply to Burn-Ins that were applied in a previous version.
Re: Data Burn-In seems to be broken in 18.0.4 (Mac)
Posted:
Wed Oct 05, 2022 7:16 pm
by Dwaine Maggart
Resolve 18.0 was the version in the July 2022 timeframe.
I installed 18.0 Studio on a Mac, and made a new project with several clips, and put clip data burn-ins on all the clips.
Then installed 18.0.4 Studio and loaded the project. No issue turning off the burn-ins.
So I don't know. Perhaps you did make the project with a beta version and that did something weird.
Re: Data Burn-In seems to be broken in 18.0.4 (Mac)
Posted:
Wed Oct 05, 2022 10:49 pm
by JimCurtis
Thanks for checking it out, Dwaine. After I've removed all the Burn-Ins in this project, I'll do the upgrade to 18.0.4 again. I have another project in waiting in which I sent time-coded screeners to our writer, likely using 18.0.3 as it was about two weeks ago.
Sorry for the false alarm, if that's what it was. At least I've validated a reason to keep older installers around.
Thanks again.