Help! Bring back Motion!

[Paul_Gringo]

Help! Bring back Motion! Properties are not working either

[R Neil Haugen]

Weird ... with a clip selected with the 25.x run, this is my ECP.

 

[Paul_Gringo]

I encountered this problem on Reddit. There is no solution. Creating a new project and transferring files there does not help; developers need to understand the cause. The problem persists in the new beta! This is a terrible problem

[R Neil Haugen]

Please give the data needed to sort this! OS/CPU/GPU, probably. There has to be some specific thing setting this off, as most users clearly do not have this.

[Paul_Gringo]

Even if 50 people have this problem, you need to look for it in the program code. My hardware specifications won't help here; I know my way around hardware.

[R Neil Haugen]

Wow ... you must realize the code is different depending on the OS, right? 

The devs for this, for Resolve, for Nuke, always want full specs ... OS/CPU/RAM and etc. 

You're suggesting hunting across all different code sections possible ... I don't understand why you wouldn't prefer to get them started on a much faster process.

[John22368521k4cl]

I've seen that with sequences imported from XMLs (Resolve, etc).  Apparently its a known issue that will be fixed in the next release. 
One workaround is to export the sequence that has clips without motion properties as an XML and then immediately import the XML.  The clips in the new sequence created from the XML you just exported will have their motion property controls restored.

[R Neil Haugen]

Thanks for the information!

[MyerPj]

For me, it's working fine in beta 26.0 b14 and shipping 25.5

Win11 24H2