I can’t launch Natron - I have tried versions 2.3.11 up to 2.3.14. This is the error message I get consistently, something to do with Python. How do I fix this, can’t find anything Natron related on the web that refers to this error.
Dyld Error Message:
Symbol not found: __ZNSt12length_errorD1Ev
Referenced from: /Applications/Natron.app/Contents/MacOS/../Frameworks/libshiboken-python2.7.1.2.dylib
Expected in: /usr/lib/libc++abi.dylib
in /Applications/Natron.app/Contents/MacOS/../Frameworks/libshiboken-python2.7.1.2.dylib
The last version I’m able to run on OSX 10.7 is 2.2.7. Newer builds has the same issue as above (or other issues related to Qt). That’s as much I can test with the OSX version I have (The graphics card don’t even support OpenGL2, I know it’s crap, I just use it to build stuff).
ok thank you, downloading 2.2.7 to try - if it works I’ll work upwards from that as I’m not on OSX 10.7.
I just double checked my system with the installation requirements for Natron. Everything according to that list checks out, I’m on OpenGL 2.1, all the extensions are installed etc. There must be something else that’s required.
Did you try with the latest 2.3.15RC binaries? Releases · NatronGitHub/Natron · GitHub
Please try the Universal (10.6+) as well as the 64bit (10.9+) binaries.
Good to hear it will be fixed. I got it working on a newer OS but have since (very reluctantly) migrated to another node-based editing solution. This was because of the lack of sound in Natron and no real reasonable way to edit to sound which was a deal-breaker for me. I hope Natron will continue to be developed and at some point consider sound - if it does I’ll be back.
Sound is not an priority, Natron is not a NLE. You can however use the AudioCurve node (will be available in a future Natron release) to generate curve data for use in Natron. I will also look into JACK integration at some point, but there are more important things to work on the moment.
Natron is a community project with very limited resources, so feature requests has a low priority. You are more or less depending on that one of the developers want the feature, else it will probably not be worked on.