Implement the ability to use values of properties as a value of another property

[pawa2401]

Describe the new feature: Implement the ability to use values of properties as a value of another property

Describe the solution you'd like: Making so that it's possible to input for example "tracker.x1" as a value of "Location X" of the video clip can allow stabilizing to a tracker point. Also allowing math to be used directly would be great (for example "-(tracker.x1)" for reversing the value) When using other properties values, also allow linking so that each time the initial parameters value changes the inherited value also updates like if it was keyframed.

[Colorjet3]

Have you looked into using the Parent attribute?

1. Drag two clips onto the timeline. Doesn't matter if they are on 2 different tracks.
2. Right click on one of the clips and select Properties.
3. In the Properties window find the Parent attribute.
4. Right click in the empty field next to it, select Clips and find the other image you want to be the parent.
5. Now when you make a change to the Parent clip those changes will apply to the other.

Note: Not all changes made are Parented. If this is the functionality you are looking for then may be experiment and see what other attributes you want to be applied. This is kind of linking two clips together.

[pawa2401]

Does this feature work with the tracker? I can't test it right now but this is the main problem I've stumbled upon. I could've created an issue about the tracker itself being kinda useless, but my approach is definitely way more flexible, and could allow some cool effects, especially with math involved.

Also, parent feature from your description seems to sync the parameters between two instances of an object, for example a video. And I'm guessing that only the parameters with the same name can be synced?

[Colorjet3]

Hello @pawa2401 I don't believe the Tracker works that way.

[stale[bot]]

Thank you so much for submitting an issue to help improve OpenShot Video Editor. We are sorry about this, but this particular issue has gone unnoticed for quite some time. To help keep the OpenShot GitHub Issue Tracker organized and focused, we must ensure that every issue is correctly labelled and triaged, to get the proper attention.

This issue will be closed, as it meets the following criteria:

• No activity in the past 180 days
• No one is assigned to this issue

We'd like to ask you to help us out and determine whether this issue should be reopened.

• If this issue is reporting a bug, please can you attempt to reproduce on the latest daily build to help us to understand whether the bug still needs our attention.
• If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant.

Thanks again for your help!