When using CinemaDNG frame sequences in the Windows version of Natron it consistently stops reading frames some where between 140-180 frames. The resolution of the frames (HD & 4.6k tested) does not seem to impact the point at which Natron stops reading the frames. If a project is rendered as a separate rendering process the frame range can be changed after the render fails and continued from that point forward as long as it is rendering to an image sequence; however, this problem makes tracking footage next to impossible, and rendering very long sequences very tedious. The Linux version does not have this problem. So I am currently dual booting to Linux for my Natron work and Windows for everything else. This is still a problem for me however, because I need to be able to pass the files off to other people who may not have Linux for running Natron. I can provide HD sample footage if needed.