That way, only the missing frames will be rendered. If Natron hangs or crashes when rendering an image sequence (this does not work when rendering to a video), check that the rendered frames are OK, relaunch Natron and in the parameters of the Write node uncheck “Overwrite”.See the tutorial on how to convert videos to image sequences. This is the standard compositing workflow and the preferred method of running Natron. FFmpeg, MEncoder, or VirtualDub (windows-only). To compress frames to a video, there are also many tools available, e.g. To extract frames, you may use a simple Natron project or any other tool (e.g. Extract individual frames, do your compositing, then compress the frames (and optionally mux the audio) with an external tool. The video writer may also be a source of bugs, and should be avoided for long sequences: if Natron crashes in the middle, then the whole sequence has to be rendered. The video reader is here for convenience, but it may have difficulties decoding some videos. Individual frames are best (DPX, EXR, TIFF, PNG, JPEG, whatever suits your input video quality and bit depth). ProRes is OK but slow, especially for writing. This includes H.264 (eg AVCHD) and H.265 (HEVC) video. Avoid using videos with inter-frame compression as inputs and outputs.Here are a few one worth trying, but of course your mileage may vary or you may find another workaround (which you should describe in the proper Natron issue). Luckily, there are workarounds for most Natron crashes or hangs. The sharp+number is the number of the issue on github to help keep track of bugfixes. This document is an very incomplete stage. You can then either attach your project as a zip file to the github issue, or post a link to a file sharing service. Make the project as small as possible: remove extra assets or replace them by small JPEG sequences, checkerboards or colorwheels, etc. If possible, also post a project that exhibits the issue. The issue title should be as precise as possible (“Natron crash” is not a correct title, see existing issues for title examples). If this bug does not seem to be a known issue, then post a new issue on the Natron github, and follow strictly the guidelines to report the bug. If yes, then read about it, and try some workarounds given in these bug reports (see below for more workarounds). The best way to have your bug considered for fixing is to first search on the Natron forum and in the Natron issues if this is a known bug. Bugs may come from OpenFX plugins that were not bundled with Natron, so before reporting anything, if you have any extra OpenFX plugins installed, uncheck “Enable default OpenFX plugins location” in “Preferences/Plug-ins”, save preferences, relaunch Natron, and check that the bug is still here.
0 kommentar(er)
