PS: please don't file the same problem three times (here, email to cloudsupport@b.o, and Stack Exchange). Give us some time to actually respond and handle it.

This is resolved in version 1.7.1, which I released yesterday :)

When logging in, you get an authentication token that gets stored on your harddisk, which is valid for a year. The statement "you're logged in" actually means "we have an authentication token stored".

Thanks, that worked, but does that mean the session is somehow active even when I close Blender?

Try logging out and back in again, that'll reset your session.

@Sybren A. Stüvel (sybren), that one seems to be for you. :)

Implemented in version 1.6.4 of the Blender Cloud add-on (which requires a recent master build of Blender, doesn't work with 2.78)

Fo reference: in the context of a production (for example the current one) we use only 1-2 types of video (.mov and .mkv). I'm not sure I understand the "unlink videos used by the image editor". The videos I'm talking about are used in the sequencer for example.

Interesting. This would be something that can change on a file-by-file basis, I think. Tthere are too many video extensions to ignore, and there are cases when they shouldn't be ignored, so there is no good default value.
Maybe we can be a bit smarter about this, and temporarily unlink videos that are only used by the image editor, before bam-packing?

Hi Peter,

Hi Francesco and thank you for pointing that out. I revised the code and checked to make sure that all buttons function properly. This should function correctly in any HTML5 browser. Let me know if you have any other questions.

Hi Pete. Thanks for providing this code. In the example that you provide on http://peterrobie.com/blenderCloud/ I noticed that the pause button does not pause the video anymore, but it causes it to restart playback from the stored location. Do you have any fix for that?

The end code I put together as an example seemed to work ok outside of the current code base. Should be able to be modified to fit in an external script.

Solved in master and production!

Issue should be fixed now (some months ago) by @Pablo Vazquez (venomgfx).

Can confirm the issue on Chrome and MacOS 10.11.

Here an screenshot:

To close this, I'm fine with an env var PILLAR_DIR as fallback/override, as long as the virtualenv also keeps working.

For example, someone might be running everything in Docker (in dev mode). So he has no local dev env configured installed. In that case I think a fallback option would be nice.

I can wholeheartedly recommend any Python developer to work from a virtualenv. In which case don't we use one?

Thanks for the clarification!

Seems to be a duplicate of T49258. Deploy of Blender Cloud needs a properly set up virtualenv, and needs to be able to import pillar.

That's not a version, that's a package name. Try dpkg -l | grep python3-requests and/or apt-cache policy python3-requests.

python3-requests