Closed ramellij closed 8 years ago
Hi. What is CGRU version? Or may be it is compiled from its latest sources?
2.1.0
Hm. This version is still, in progress. And i did not tested Natron with 2.1.0. It seems that something was broken in this version, that affects Natron. I will check. I definitely will check all soft types before create 2.1.0 a release. But right now i have no Natron by hand.
same issue with 2.0.8
Hm This is strange. If you have time, you can try it with 2.0.7, when Natron integration just started.
Did Natron RC5 work? Could be related to changes made to integrate our new crash reporter, you could also send in the crash report and let us take a look (remember to add a comment that you used afanasy). Also note that RC6 on Windows has an issue with EXR due to wrong OpenImageIO version, I'm a bit unsure if that has been fixed, try a snapshot build if possible.
Yes I send the report using NatronIssueReporter and I'm using RC6 "latest" snapshot. I'm doing more tests right now. It seems to work correctly using previous versions of Afanasy.
Did you comment on the crash? Else it's impossible to find your report.
Yes I did with the same message posted in natron issue github. I'll do more tests later and try to reproduce it. But with Afanasy version 2.0.8 it works finally.
The latest crash reports on Windows is without comments, maybe your report has not been processed, will check.
On 6 February 2016 16:45:50 CET, jonathan Ramelli notifications@github.com wrote:
Yes I did with the same message posted in natron issue github. I'll do more tests later and try to reproduce it. But with Afanasy version 2.0.8 it works finally.
Reply to this email directly or view it on GitHub: https://github.com/CGRU/cgru/issues/175#issuecomment-180795541
I can't reproduce the bug, and now it works fine with all afanasy latests versions (2.0.7, 2.0.8, 2.1.0). I don't understand what happened. Maybe the bug was related to my other Natron versions installed. I removed them to let just the RC6 snapshot and set the path to the good exe. I'll do more tests and report bug if there is.
One other thing When I launch a job from afstarter I get the correct working directory, wich is my network drive so all clients can see it (//WORKSTATION-PC/...). And when I use Afanasy node in Natron it sets my local drive as working directory (C:\USER...) and so they can't reach it and fail to render. My project settings in Natron are good but somehow it changes it.
Also using afstarter thumbnails aren't created.
Hi. Checked RC6 and 2.1.0 - works fine.
May be when you took 2.1.0 sources, it was broken exactly that time. Working on a new version i can commit some half of changes, just to store.
ps Better to use releases. And sources for tests/develop only.
Hi Timur,
Sorry to bother you with this but I still can't use Afanasy with Natron. My tasks are rendering in loop and all I get from Output is (at the very end, after all frames are done):
Spawned process crashed, exiting.
It's certainly related to Natron but can we "force" Afanasy to continue to the next task ?
Also "afanasy" node doesn't work in Natron (Windows 7). The only way for me to actually see it was by launching your example scene from keeper but that's all.
I use Natron 2.3.9 and Afanasy 2.2.3, the officials releases. And I use afStarter to launch my jobs.
Thanks for your help JR
Hi.
Hello,
I just report that issue to Natron guys : https://github.com/MrKepzie/Natron/issues/1176 From Afanasy I get this : "AFERROR: Service::parse: parser="natron" returned value is not a tuple" And from Natron : "Spawned process crashed, exiting."
Natron renders the frames but crashes at every end tasks. Do you know what it is ? Thanks for your help JR