Blackmagic Forum

In DR16, we can now see the timelines in tabs on the EDIT page, on top of the working timeline.
We can rearange the order of tabs, but this state is not saved.
I would like to report this as a bug.
Because I work with many timelines (versioning) and it is a mess after I reopen DR.
Believe me, I made so many project mistakes because of this...

For example, I create timeline1, timeline2, timeline3 and I see them in that order in the tabs.
I close timeline2 with clicking the cross on the tab,
so now I see only timeline1 and timeline3 in the tabs.
If I open timeline2 again, it opens in the last tab,
so I see this order timline1, timeline3, timeline2.
I move the tab with timeline2 to the left, so I have timeline1, timeline2, timeline3 in tabs again.
But if I close DR and open it again, the position is not saved.

The only workaround is to close all timelines and open them back in the requered (right) order.

Thank you.

+1

Just wanted to start a new thread about this.
We often work with 10-15 tabs open at the same time (timelines & compound clips) and every time DR is opened again, we have to rearrange the tabs all over again.

Please let DR save the last arranged order of open tabs when closing the program.

Milan Michalik wrote:We can rearange the order of tabs, but this state is not saved.

I've never seen that happen in any version of Resolve for Windows. It's not a commonly reported issue.

Not sure what might cause that.

I see it here on macOS. Moving a tab on Edit then saving and reloading will not persist the position change. Then if you happen to close a tab by mistake, causing it to be the last tab when you re-open it, it'll then be stuck at the end of the list next time you open the project.

Just to clarify: Is this a bug or a (maybe) missing feature?
If it gets saved for @Jim, the feature is there and it seems like a bug.

Doesn't seem to be a Windows only problem, as @TheBloke is on MacOS.

Could it have something to do using the DR DB on our server and not locally?

Jim Simon wrote:I've never seen that happen in any version of Resolve for Windows. It's not a commonly reported issue.

So Jim you're confirming that on Edit, the order of your stacked timeline tabs persists across save/load? You can open a project, rearrange the tabs, save, reload, and the adjusted order is restored?

DerPaule13 wrote:Could it have something to do using the DR DB on our server and not locally?

I'm using local project database, not an SQL server, so it's not that.

DerPaule13 wrote:Could it have something to do using the DR DB on our server and not locally?

That may be relevant. I use only Disk database on internal drives. No Collaboration.

TheBloke wrote:So Jim you're confirming that on Edit...

Every time. Every project. Every database. Both machines.

OK, thanks.

So it's not OS, and not Local vs Postgres. I have used Collaboration in the past, but not since v16 and never on this project (which was newly created in v17.1) and Enable Collaboration is greyed out in the menu, presumably because it's a local database.

I'll do some testing, see if I can find anything that affects it.

I have had this same issue too (never had the new/last position saved) and I have never collaborated.

What OS, Ray?

What version(s) of Resolve had the issue?

Jim Simon wrote:What OS, Ray?

What version(s) of Resolve had the issue?

Hey Jim, Windows 10 and its's been since DR 16 that I noticed (or had the situation where I was trying to move a timeline tab and the new position wouldn't save). I am running 17.3 Studio now. Thanks.

Edit: I just realized that I hadn't tried to change the position of a tab in 17.3 so I just went into a project and changed the position of one tab and saved my project and when I went back in, it had returned to its original position.

I'm still suffering from this problem in 17.4.2 and it's getting increasingly annoying. I've also realised that it's not only when I restart Resolve, but also when I use Switch Projects.

Here's a quick demonstration of the issue triggering after a Switch Project:



If anyone knows why this is happening and has any idea how to fix it, I'd be most grateful. I have 20+ active timelines and will have 30+ by the time I'm done on this project, and it's very frustrating that I can't preserve the order.

Instead of posting a new thread, I'm just going to bump this one and say that I'm also having this issue with version 17.4.6, build 4 on Windows 10. Still a problem.

andrea.vingamer wrote:Instead of posting a new thread, I'm just going to bump this one and say that I'm also having this issue with version 17.4.6, build 4 on Windows 10. Still a problem.

Yep, it was recently in 17.4.X for me too, and now also in 18 still.

i have a same problem

I have the same problem.

I have a Resolve project I frequently use for batching dozens of short videos. It has a shared timeline with the info that needs changing which is deep in the timeline tab order. I always move it up front (to the left) but it never saves.

A little quality of life annoyance.

Same here. Really annoying that the order of these tabs isn't saved.

I have episodes that I sort in the Edit page from next to be released to 'later down the road.' That and sub edits with their tabs just after the episode they go in.

Having the same problem. I'm using DR Studio 18.6.5 and the bug (?) is still there.
Very annoying !

Only here to bump this up. People are complaining for 4 years now. It's unreal that this thing is still persisting!

Having the same issue, I really REALLY hope this gets patched on the 19 version

Still not resolved in August 2024 version 18.6

Same issue now in 19.1, you would imagine this is an easy fix ?

Saving state across app invocations can be done ad hoc - as in the devs decide to save this or that and write code for it - or it can be done systematically by adding save/restore code to the root UI element.

With the latter approach everything “just gets saved” by default as Jim and others have requested. So once you fix it the fix carries through to new features. But it does require coming up with the framework code and adding exceptions where preferable.

I THINK Resolve currently uses the ad hoc approach.