Library features.

[daninski]

Hi,

A couple of thoughts that I miss when I'm using the library.

Firstly it would be good to be able to export a library so that it could be used across many projects. Either that or have a universal and an embedded library; much like custom panels work. I find myself spending a lot of time duplicating libraries; and as we all know every second counts when you're animating to deadlines!

The other thing is it would be good if you could just drag images out of the library and they automatically become a guideline support image. This one isn't so important as my first suggestion.

Thanks!

[Peter Wassink]

+1

3 year old request.

Http://www.tvpaint.com/forum/viewtopic. ... ary#p95000

Related to that I'd really like to be able to add directly the current custom brush as an image guide instead of having to add it in the library and then as an image guide

I'd also like to have the image library global for the whole project, and could be nice to be able to embed those images in the project cause it's a hug issue when working in a team (or i missed something)

i dont use the library because...:
it is limited to a single project. That it is not a global library makes it unsuitable for palettes or modelsheets in larger productions.
Not ideal but to have a save/export option could function as a workaround for this, and is
.

[NathanOtano]

Yes, would still love this :'(
If you have some technical developers at your studio however, I think you should be able to import an entire library with a one button script.
Still much easier for me to put model sheets on animated custom brushs per character, on embedded custom panels included in your production templates

Right now the workaround regarding embedding image guidelines in a project is for me to import an image as a brush, put the brush in the library, and add as a guideline. Seems that then the image is "embedded" but I need further testing, cause I recall that sometimes it didn't work?

[daninski]

You can copy and paste folders from the library btw, but it should be easier than that to make the library live up to it's true potential.

[daninski]

Yes, would still love this :'(
If you have some technical developers at your studio however, I think you should be able to import an entire library with a one button script.
Still much easier for me to put model sheets on animated custom brushs per character, on embedded custom panels included in your production templates

Right now the workaround regarding embedding image guidelines in a project is for me to import an image as a brush, put the brush in the library, and add as a guideline. Seems that then the image is "embedded" but I need further testing, cause I recall that sometimes it didn't work?

A handy thing for using the support image is to put a keyboard shortcut for "Guidelines: Edit". I have it set to G. This way its very quick to move and scale the support image around your desk space within TVPaint.

[NathanOtano]

AH copy pasting seems interesting yes

Yep I have a shortcut for editing guides, and also have one to toggle the global visibility to flip model sheets directly on my drawings without bothering with layers

[Thierry]

A few words about the Library.

The Library was designed -and implemented- to be per project, not a global one, to store images that would be used for the Image guides for example.
There are two main reasons it was not made global:
- The first, and major one is that the current engine has lots, lots of trouble managing different sizes of images in the same project. This is why, when you use the Texturizer, your texture needs to have the same dimensions as your project. This is also why you can't have clips with differents dimensions.
- With a global library, by having more and more images in it, it takes more and more space on your disk. Should the Library contain only references to the files, which would be stored elsewhere on your disk (and if you move them or delete them, not being able to use them), or should they be a copy of the original images? And if that's the case, where should those images be stored? We didn't have the answers to these question at the time.

So:

it would be good to be able to export a library so that it could be used across many projects. Either that or have a universal and an embedded library; much like custom panels work

This is not possible in the current engine.

The other thing is it would be good if you could just drag images out of the library and they automatically become a guideline support image.

On the other hand, this, while complex, might be doable.

[NathanOtano]

Should the Library contain only references to the files, which would be stored elsewhere on your disk (and if you move them or delete them, not being able to use them)

Could it be possible in the current engine? Because this + being able to export the library path to get those references on another project of somebody else on another computer could be nice, and often we don't want to have an heavier project by importing, say, the backgrounds of model sheets (and we want it to be updated with the file on the network when there is changes).

[Svengali]

As discussed in another thread, I think it would be VERY useful if GEORGE were to include a command which enabled the exporting of existing library image(s) via Cutbrushes... and from there into other project libraries or stored temporarily in project layers or exported/saved to image files using tv_savebrush command.

Sven