search

MrKepzie / Natron

Open-source compositing software. Node-graph based. Similar in functionalities to Adobe After Effects and Nuke by The Foundry.
www.natron.fr
GNU General Public License v2.0
1.49k stars 164 forks source link

Write node Manual frame range not being updated #1757

Closed unfa closed 6 years ago

unfa commented 6 years ago

Problem

I've stumbled upon another strange problem while fighting with https://github.com/MrKepzie/Natron/issues/1756 .

The issue was that when I changed the "manual" frame range in my Write node to resume rendering I had a few times when the restarted rendering used an old frame range - even though I saved my Natron project under a different file name! It looked like Natron GUI didn't update the Write node's frame range at times and saved the project with old values (many times in a row). I wonder if anyone ever had this problem.

Expected behavior: New frame range values should be stored in a saved Natron project file.

Actual behavior:

Old values remained in the file and were used for rendering.

Steps to Reproduce

I never had this happen before I don't know if it's specific to my project, I can submit it but it depends on a lot of external data.

Versions

Multiple versions of Natron before the 2.3.10 release.

Linux Mint 18.3 KDE5, linux-lowlatency-hwe kernel. Ryzen 7 1700 CPU.

devernay commented 6 years ago

Can you figure out a series of operations to demonstrate this bug? ("how to reproduce") Whet about if you save the project, quit Natron, and reopen the project?

devernay commented 6 years ago

This issue was moved to NatronGitHub/Natron#249