Closed cgvirus closed 2 years ago
cgvirus
commented
2 years ago Needs more investigation. Closing for future ref. Edit: After doing some more experiment, seems it was a wrong assumption. The problem might be involved with NVIDIA GPU drawing in Linux.
devernay
commented
2 years ago Read node infers the frame rate from the file itself, but in the end video files are always read frame by frame, and no retiming will ever occur (which would cause flickering) unless you explicitly use a retime node.
cgvirus
commented
2 years ago Do still frames also require project frame rate match? Not sure enough but seems like the flicker is possibly happening for nvidia repainting glitch. It's subtle, so I will check it in Windows as well to compare. Probably it's not a Natron problem.
cgvirus
commented
2 years ago After close observation I have found the silly side. VLC for some reason sometimes fail to buffer prores file. That is why it flickers. Also sometimes GPU fails to buffer 4K in h264 as well. In windows and Linux both.
Now it makes sense. Natron is outputting perfectly. Checked with after effects and some other apps.
[INVALID ISSUE]
DRI-UK75
commented
2 years ago Don't bother with VLC it sucks. Use Anydesk, it's as good as Teradici and for the moment still free.
On Sun, 3 Apr 2022 at 00:55, Fahad Hasan Pathik @.***> wrote:
After close observation I have found the silly side. VLC for some reason sometimes fail to buffer prores file. That is why it flickers. Also sometimes GPU fails to buffer 4K in h264 as well.
Now it makes sense. Natron is outputting perfectly. Checked with after effects and some other apps.
[INVALID ISSUE]
— Reply to this email directly, view it on GitHub https://github.com/NatronGitHub/Natron/issues/775#issuecomment-1086744029, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHNBWQOKHCP76S2GBGILSCTVDDM6PANCNFSM5Q5QEQXA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- David Robinson
Director David Robinson Imaging Ltd The Lodge Stovolds Hill Cranleigh Surrey, GU6 8LE
@. w @.>ww.dr-imaging.co.uk
Make sure to follow our issue report guidelines
Provide a description of your feature request
Natron read node frame rate uses default 24 fps.
This creates a severe error if not cautious enough while working on a 60/30/25/29.9 fps. A flicker will occur due to mismatch. And will output that flicker as well.
Instead of 24 fps default, Read node should look at the project settings for fps query before loading. Or at least throw a warning.
Today I realized the read node actually uses 24 fps instead 30 although the project is set to 30 fps. Thanks to a smooth animation for catching this error I am working on right now.
Is this a realistically implementable feature?
Can you contribute in creating this feature?
Additional details
No response