Buggy timeline operation

Bet 8. I'm mostly working in the Color Page on a complex feature length doc...which is fortunatR because the color page seems more stable than the other pages. But when I swith to the Edit page to tweak someting it frequently is unresponsive. I usually can't move the timeline cursor at all. A Resolve restart is required.

In general it seems like at this stage of the beta theres a giant's raft of things that aren't working well.

I don't think that's normal.

What kind of media? Internal drives only? It might be a PITA, but a test without the Decklink may be in order.

I don't think that's normal.

What kind of media? Internal drives only? It might be a PITA, but a test without the Decklink may be in order.

All kinds of 4k and larger media. Fast internal M2 drives except for the fast TB3 array. It's certainly been normal here since switching from 16 to 17.

Can you specify the "all kinds"?

Can you specify the "all kinds"?

FWIW RED 5k-6.5k, Varicam 35 4k, GH4 4k, GH5 4k, BM CDNG 4.6k-4k, BMRAW 4k, Stills.

Alright.

My only idea at this point is the test without the Decklink, trying to eliminate variables.

Alright.

My only idea at this point is the test without the Decklink, trying to eliminate variables.

I did notice a Jan 21 update to Desktop Video so I'll try that but the issue has never effected Decklink output....which is kinda necessary for Color Grading

It is, but we are working out the bugs of a Beta here, so...

It is, but we are working out the bugs of a Beta here, so...

Yes, but I don't have the time to chase down possibilities that seem very unlikely. I think Support is aware of this timeline issue as I've mentioned it in passing in PM's. No offense, but I'll try switching off the Decklink card if and when they ask.

[Shrinivas Ramani]

David,

Any logs we can take a look at?

We haven't come across this anomaly in our testing, even with large projects with network drives. So some information - like specific actions rendering it inoperable - or turning off (say) the inspector and media pool - being a workaround - would help.

someting it frequently is unresponsive. I usually can't move the timeline cursor at all.

Thanks
Shrinivas

David,

Any logs we can take a look at?

We haven't come across this anomaly in our testing, even with large projects with network drives. So some information - like specific actions rendering it inoperable - or turning off (say) the inspector and media pool - being a workaround - would help.

someting it frequently is unresponsive. I usually can't move the timeline cursor at all.

Thanks
Shrinivas

I'll PM you the logs. As for what triggers it, it happens frequently after working in the Color page for 3 or so hours and then switching to the Edit Page. So nothing I can definitely put my finger on. I use a large fixed node tree which normally has 5 to 10 nodes in use with 3 or 4 Resolve OFX and NR commonly in play. So a lot of cache renders going on.