Closed gabeduke closed 7 years ago
Thanks for the report! However the log file is only showing the current session, not the crash. If you send the log again via Time-lapse Clips->(menu button)->Send log for review, I should get the relevant log. Thanks!
Oops! I sent a couple logs from test clips earlier today. I think they had around ~4 frames each. Let me know if there's any repro issues.
On Sat, Feb 4, 2017 at 10:41 PM Elijah Parker notifications@github.com wrote:
Thanks for the report! However the log file is only showing the current session, not the crash. If you send the log again via Time-lapse Clips->(menu button)->Send log for review, I should get the relevant log. Thanks!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/timelapseplus/VIEW/issues/4#issuecomment-277495363, or mute the thread https://github.com/notifications/unsubscribe-auth/AD69Hgk35FrHAU3HdjH1wvHvi6eGP2knks5rZUTygaJpZM4L3XbL .
Thanks! I'v got what I need now -- it's related to an empty keyframe set. I put a fix in to avoid the crash (not committed yet), but I'll also dig a little deeper into the core issue yet. I'll make sure it's fixed for the official 1.6.0 release. Thanks for the help!
I sent the log with 4 images from a Canon 6D
Connecting to the TL+VIEW App seems to reliably crash the module on v1.6.0 Beta12 Thanks!