Missing Libraries on Ubuntu in release.

[Brogan Ross]

Hey guys,

   I'm trying to get Tuttle up and running on Ubuntu 12,04, but the release build seems to be missing some libraries.

libtiff.s0.3 

libpng14.so.14 

libwebp.so.0

libicuuc.so.46

libicui18n.so.46

Just curious if they were supposed to come with the release or if I need to manually install them?

[Fabien Castan]

Hi!

They should be included in the archive. It's an error.

We have to upload a new archive...

--
You received this message because you are subscribed to the Google Groups "tuttleofx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tuttleofx-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Brogan Ross]

Ok.  Cool.  Hopefully it's not a major issue.  Thanks a lot.

 

[Marie Fétiveau]

Hi !

You can download here a package with all dependencies. 

It's a version a little bit newer than the one you already downloaded (updated libraries).

We're currently preparing a new release including some improvements on how we generate those bundles.

Stay tuned !

Marie

On Tue, May 6, 2014 at 10:34 PM, Brogan Ross <broga...@gmail.com> wrote:

Ok.  Cool.  Hopefully it's not a major issue.  Thanks a lot.

 

--

You received this message because you are subscribed to the Google Groups "tuttleofx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tuttleofx-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Marie Fétiveau Color and D-cinema R&D Engineer +33 1 55 63 11 00 m...@mikrosimage.eu Mikros Image / Digital Post-Production for Video and Film  www.mikrosimage.eu

[Brogan Ross]

Thanks, Marie.  Looks like there's still some issues though.  libjpeg.so.62 was missing so I copied it in from the production build.  Then it was erroring when looking for libwebp.so.0, but libwebp.so.5 is in the build you sent, and libwebp.so.2 is in the production build.

Also I took a look in the lib folder and didn't see these:

libtiff

libpng

libicuuc

libicui18n

But, just for fun, I renamed libwebp.so.5 to libwebp.so.0 and didn't get any errors right away.  I'll check messing with it and see if anything goes wrong.

Let me know if there's anything I can do to help.

[Marie Fétiveau]

Arrrg, I uploaded the wrong file -__-

Should be ok, here.

Sorry for that !

[Brogan Ross]

Looks like the libs are all there now, though there might be a python issue.  When I just run sam, I get:

/usr/bin/python: /opt/tuttle-v0.8-1/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/python)

/usr/bin/python: /opt/tuttle-v0.8-1/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/python)

this shows up for ll, lls, lss, and viewer commands.  I don't think it will get in the way of what I'm working on, but I thought you should know.

Thanks again for the quick turnaround.

[Brogan Ross]

you can ignore the no version info warnings.  I was still in a virtualenv and deactivating it got rid of that.  But, I did run into a different error when trying to do a resize:

sam do reader sit003_bg_v2_hd.####.jpg // resize width=640 // writer some_new.####.jpg // -V 0

[sam do] Error on node: "tuttle.resize".

Syntaxe error for expression: "640"

 * Advanced message: No diagnostic information available.

----------

 * Full exception information:

libraries/tuttle/src/tuttle/host/attribute/expression.hpp(68): Throw in function Type tuttle::host::attribute::extractValueFromExpression(const string&) [with Type = int, std::string = std::basic_string<char>]

Dynamic exception type: N5boost16exception_detail10clone_implIN6tuttle9exception5ValueEEE

std::exception::what: std::exception

kOfxStatErrValue[PN6tuttle9exception14tag_devMessageE] = No diagnostic information available.

[PN6tuttle9exception15tag_userMessageE] = Syntaxe error for expression: "640"

----------

    Sorry, I feel like I come with nothing but bad news.  If I get a chance I'll see if I can find anything blatant in the repository, but it's been a while since I've done anything in C. 

Thanks

[Marie Fétiveau]

Indeed, this seems related to your python environment.

What "no version info" warning are you talking about ?

I'm using pyenv + its virtual env plugin to set my various python workspace.

I can launch Tuttle in them without warning.

Don't worry about the bad news, these kind of feedbacks are precious for us :)

[Brogan Ross]

Sorry, forgot to respond to the mail list:

The "no version info warnings" I mentioned were:

/usr/bin/python: /opt/tuttle-v0.8-1/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/python)

/usr/bin/python: /opt/tuttle-v0.8-1/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/python)

when I ran sam do.  But they can be ignored as I was in a virtual env.

However, the "syntaxe error" I'm getting (mentioned previously) when trying to run sam do commands is still an issue.

I tried building from the repository to debug the issue myself, but I ran into another issue that I haven't been able to resolve.  When building I get:

plugins/image/process/color/CTL/src/CTLProcess.cpp:83:83: error: within this context

3rdParty/ctl/IlmCtl/CtlInterpreter.h:182:12: error: 'Ctl::Interpreter::Data* Ctl::Interpreter::_data' is private

I saw that you guys are using your own fork of ctl, and from what I can tell that's what i'm using as I just ran the init.py script in 3rdParty, and build in that directory.  Any ideas on figuring this one out?

[Marie Fétiveau]

Hello !

For the warning, try to remove libcrypto and libssl from the lib directory.

We're currently doing a lot of tests to make a portable version of Tuttle and it appears that embedding system libraries provokes more troubles than it helps.

So you should also remove : 

ld-linux-x86-64.so.2  libc.so.6   libexpat.so.1  libGL.so.1    libm.so.6                   libnvidia-tls.so.304.51  librt.so.1      libutil.so.1  libXau.so.6  libXext.so.6  libxvidcore.so.4

libcrypto.so.1.0.0    libdl.so.2  libgcc_s.so.1  libltdl.so.7  libnvidia-glcore.so.304.51  libpthread.so.0          libstdc++.so.6  libX11.so.6   libxcb.so.1  libXt.so.6

Your python "syntaxe error" is really weird, I wasn't able to reproduce it despite some tests in various python configurations.

As libpython2.6.so.1.0 depends on sys libs, it's worth giving a try without the libs above-mentioned.

It's becoming pretty clear to us, that a solution may be to bundle a python with Tuttle.

About CTL, I'm sorry init.py isn't very updated so you have to use our forked CTL.

Be careful, though, if you are building master branch you have to use https://github.com/tuttleofx/CTL/tree/tuttle_master branch.

Improving and cleaning all of this is one of our goal for the next release.

Again, thanks you for your feedbacks.

Marie

[Brogan Ross]

I noticed that I was getting some python errors just before the syntax error.

Could not find platform independent libraries <prefix>

Could not find platform dependent libraries <exec_prefix>

Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]

'import site' failed; use -v for traceback

This was happening cause tuttle was built with python2.6 but Ubuntu requires 2.7.  After installing python2.6 the above disappeared, but I still get the syntax error, even after removing the above libraries.

I've switched my ctl to the fork you mentioned, and it looks like everything is building now.  Is there a particular changeset id you'd recommend I work with?  Maybe the one you generated my build from?

[Marie Fétiveau]

As a lot of improvements have been made since the last release, I would suggest to go for the develop branch even if there must be some fixes and clean to do on it.

For develop branch, you'll need CTL 1.5.

I made you a bundle with an embedded python 2.6.2, here.

Please note that it's an experimental bundle that needs some clean.

Try this and tell me if it resolves your syntax error.

[Brogan Ross]

Awesome!  Thank you, Marie.  The embedded python did get rid of my expression syntax issue.  Thank you for all your help.

I have run into a couple other issues though.  Mostly it seems to be an exr thing, which I know can be a pain.

If I run sam info on a sequence of exrs rendered from Nuke, the only info it finds the file name and frame range.  I'd be really helpful if I could get the colorspace at least as well.

if I try to apply a 3dl lut to an exr using the plugin I get the following error:

Error in graph components propagation.

Connection "TuttleExrReader_1.Output" (OfxImageComponentAlpha) => "TuttleOcioLut_1.Source" (OfxImageComponentNone).

 * Plugin identifier: tuttle.ocio.lut

 * Plugin name: TuttleOcioLut_1

----------

 * Full exception information:

libraries/tuttle/src/tuttle/host/ImageEffectNode.cpp(664): Throw in function void tuttle::host::ImageEffectNode::validInputClipsConnections() const

Dynamic exception type: N5boost16exception_detail10clone_implIN6tuttle9exception5LogicEEE

std::exception::what: std::exception

kOfxStatErrValue[PN6tuttle9exception14tag_devMessageE] = Error in graph components propagation.

Connection "TuttleExrReader_1.Output" (OfxImageComponentAlpha) => "TuttleOcioLut_1.Source" (OfxImageComponentNone).

[PN6tuttle9exception14tag_pluginNameE] = TuttleOcioLut_1

[PN6tuttle9exception20tag_pluginIdentifierE] = tuttle.ocio.lut

----------

Looks like the lut plugin if having issues reading the alpha of the exr, maybe?

Also, and this one is quite weird, it seems like the mathoperator plugin is converting all the double inputs to ints.  So if I run:

sam do reader in.####.exr // mathoperator operation=plus alpha=-0.10 // writer out.####.exr

The image output has increased the alpha channel by 1.  not decreased it by .1

I'll see if I can get the development branch up and running on my machine.

Thanks again for all your help!