a layer count
- Peter Wassink
- Posts: 4437
- Joined: 17 Feb 2006, 15:38
- Location: Amsterdam
- Contact:
a layer count
a layer count.
anything that lets me see the number of layers in a project / the selected number of layers.
don't mind where you put it, in the project info or in the top of the layer bar.
anything that lets me see the number of layers in a project / the selected number of layers.
don't mind where you put it, in the project info or in the top of the layer bar.
Peter Wassink - 2D animator
• PC: Win11/64 Pro - AMD Ryzen 9 5900X 12-Core - 64Gb RAM
• laptop: Win10/64 Pro - i7-4600@2.1 GHz - 16Gb RAM
• PC: Win11/64 Pro - AMD Ryzen 9 5900X 12-Core - 64Gb RAM
• laptop: Win10/64 Pro - i7-4600@2.1 GHz - 16Gb RAM
- Paul Fierlinger
- Posts: 8100
- Joined: 03 May 2008, 12:05
- Location: Pennsylvania USA
- Contact:
Re: a layer count
I would go a step further; I'd like to see the layers numbered in consecutive order which would make for easier communications as in:"It's layer number 26!" instead of having to yell: "It's layer Boyinueat!"
Paul
http://www.slocumfilm.com
Desktop PC Win10-Pro -64 bit OS; 32.0 GB RAM
Processor: i7-2600 CPU@3.40GHz
AMD FirePro V7900; Intuos4 Wacom tablet
http://www.slocumfilm.com
Desktop PC Win10-Pro -64 bit OS; 32.0 GB RAM
Processor: i7-2600 CPU@3.40GHz
AMD FirePro V7900; Intuos4 Wacom tablet
Re: a layer count
+1anything that lets me see the number of layers in a project / the selected number of layers.
Mac OS 13.4.1 , Mac Studio 2023, 32GB RAM, Wacom Cintiq 27 QHD (no touch), Wacom Driver 6.4.2-4.
TVP Pro 11.7.1
TVP Pro 11.7.1
Re: a layer count
I second that, and ask for an additional change:
instead of naming layers as "Untitled 1" and so on, just assign them a number. That "Untitled" may be reasonable for files, but not inside a file.
instead of naming layers as "Untitled 1" and so on, just assign them a number. That "Untitled" may be reasonable for files, but not inside a file.
TVP 10.0.18 and 11.0 MacPro Quadcore 3GHz 16GB OS 10.6.8 Quicktime 7.6.6
TVP 11.0 and 11.7 MacPro 12core 3GHz 32GB OS 10.11 Quicktime 10.7.3
TVP 11.7 Mac Mini M2pro 32GB OS 13.5
TVP 11.0 and 11.7 MacPro 12core 3GHz 32GB OS 10.11 Quicktime 10.7.3
TVP 11.7 Mac Mini M2pro 32GB OS 13.5
Re: a layer count
But the aim here is to have a layer count in addition of the name, isn't it ?
Peter, IYO, how would the layer count work ? Would each layer have a unique name ? What if you change their order ? What if you copy past a layer from a different project ?
Peter, IYO, how would the layer count work ? Would each layer have a unique name ? What if you change their order ? What if you copy past a layer from a different project ?
Re: a layer count
for the time being, such a tool could be scripted with no big trouble I think,Peter Wassink wrote:a layer count.
anything that lets me see the number of layers in a project / the selected number of layers.
...
- if no selection, the script counting all existing (or onlly "visible" as option) layers of the clip, and return the total number,
- if a selection of layers, counting only the selected layers and return the number.
... script assignable to a hotkey, naturlich.
Re: a layer count
Most users don't know that each layer, as it is created for a specific project, is assigned a unique identifier number (not visible, but accessible with the George command: tv_LayerGetID position explained in the TVPaintWiki, HERE or the tv_LayerCurrentID explained HERE.
So, a layer's position (which can change within a project) is different from its identifier (which remains the same within the project).
Even when the layer's position is moved up or down the stack of layers, the unique identifier can be used to reference, find or select that layer, wherever it goes.
When a layer is killed, the identifier is permanently retired for that project. When a new layer is created, a new, unique identifier is generated and stays with that new layer for the life of that layer in that project.
These numbers are totally accessible via George commands plus much more layer parameter-status information as well, for each layer.
What's needed is some kind of popup spreadsheet "abstract" which could give the user various statistical views of the layers states and that could assist in assigning and organizing associations and identities like the color groups, naming of layers, tracking numbers, various states of the layers (visible, selected, locked, etc.) and which would let you coordinate linkage between the timeline info and the actual stack of image layers. (Thanks to paul for this insight and some scripting ideas!)
Right now, all that info is there, but the user more or less has to keep it in his head since most of it is off-screen, in hidden parts above or below the visible strip of layers in the timeline or encoded in the tiny icon check boxes of the heading of each layer.
Sven
So, a layer's position (which can change within a project) is different from its identifier (which remains the same within the project).
Even when the layer's position is moved up or down the stack of layers, the unique identifier can be used to reference, find or select that layer, wherever it goes.
When a layer is killed, the identifier is permanently retired for that project. When a new layer is created, a new, unique identifier is generated and stays with that new layer for the life of that layer in that project.
These numbers are totally accessible via George commands plus much more layer parameter-status information as well, for each layer.
What's needed is some kind of popup spreadsheet "abstract" which could give the user various statistical views of the layers states and that could assist in assigning and organizing associations and identities like the color groups, naming of layers, tracking numbers, various states of the layers (visible, selected, locked, etc.) and which would let you coordinate linkage between the timeline info and the actual stack of image layers. (Thanks to paul for this insight and some scripting ideas!)
Right now, all that info is there, but the user more or less has to keep it in his head since most of it is off-screen, in hidden parts above or below the visible strip of layers in the timeline or encoded in the tiny icon check boxes of the heading of each layer.
Sven
TVP Pro 11.0.10-64bit Win10 - 64GB ram -2TB HHD - 256GB SSD - Wacom Cintiq 16, driver 6.3.41-1
Android Tablet: rel. 11, Samsung Galaxy Note10.1 - 32GB with microSD 32GB
Android Tablet: rel. 11.5, Samsung Galaxy Tab S7plus - 128GB with microSD 64GB
Android Tablet: rel. 11, Samsung Galaxy Note10.1 - 32GB with microSD 32GB
Android Tablet: rel. 11.5, Samsung Galaxy Tab S7plus - 128GB with microSD 64GB
Re: a layer count
I'm not sure if layer identifier numbers are really an issue for any other users, but after looking at the nature of identifier numbers again, I felt I should clarify my comments to say that the identifier for each layer is permanently assigned to that layer ONLY for the current session with the project.Svengali wrote:So, a layer's position (which can change within a project) is different from its identifier (which remains the same within the project).
Even when the layer's position is moved up or down the stack of layers, the unique identifier can be used to reference, find or select that layer, wherever it goes.
When a layer is killed, the identifier is permanently retired for that project. When a new layer is created, a new, unique identifier is generated and stays with that new layer for the life of that layer in that project.
These numbers are totally accessible via George commands plus much more layer parameter-status information as well, for each layer.
Once the project is closed and reopened at a later time, a new set of identifiers are assigned to the layers (which are usually different from the original identifiers) and those remain permanent with the layer (even if the layer is moved up or down in the stack order) but only as long as the project is being worked on for that session. Next time the project is opened, another new set of identifiers is created.
I think the whole purpose for layer identifiers is to let the program keep track of each layer for each project currently in memory for for various operations... like when the track in one project is used as a source for some FX in another, or cut and paste operations between projects (and I guess clips) and so on.
Hope someone finds this helpful.
Sven
TVP Pro 11.0.10-64bit Win10 - 64GB ram -2TB HHD - 256GB SSD - Wacom Cintiq 16, driver 6.3.41-1
Android Tablet: rel. 11, Samsung Galaxy Note10.1 - 32GB with microSD 32GB
Android Tablet: rel. 11.5, Samsung Galaxy Tab S7plus - 128GB with microSD 64GB
Android Tablet: rel. 11, Samsung Galaxy Note10.1 - 32GB with microSD 32GB
Android Tablet: rel. 11.5, Samsung Galaxy Tab S7plus - 128GB with microSD 64GB
- Paul Fierlinger
- Posts: 8100
- Joined: 03 May 2008, 12:05
- Location: Pennsylvania USA
- Contact:
Re: a layer count
I never thought of layer numbering as anything else than an identifier of the layer stack regardless of which layer sits on that number at any time of any session. When you have so many layers to work with and you can orient yourself by a glance at the numbers and see that you are somewhere in the middle of the stack, that is a lot of practical information.
It's like being plopped down by a taxi, or up from a subway,in the middle of Manhattan, all you need is a peek at the number of the street you are on to become oriented, no matter which buildings stood there the last time you were in that local and have been replaced by newer ones. The consistently numbered layers together with the numbered frames would form a dependable visual navigation grill and that would mean a lot for the two of us here.
On the other hand, names of layers are disorienting anyway so let those change. In Philadelphia, you have about ten parallel lanes named after trees, which is hopeless because it takes years before you can remember which tree comes after Pine street when you are walking west.
It's like being plopped down by a taxi, or up from a subway,in the middle of Manhattan, all you need is a peek at the number of the street you are on to become oriented, no matter which buildings stood there the last time you were in that local and have been replaced by newer ones. The consistently numbered layers together with the numbered frames would form a dependable visual navigation grill and that would mean a lot for the two of us here.
On the other hand, names of layers are disorienting anyway so let those change. In Philadelphia, you have about ten parallel lanes named after trees, which is hopeless because it takes years before you can remember which tree comes after Pine street when you are walking west.
Paul
http://www.slocumfilm.com
Desktop PC Win10-Pro -64 bit OS; 32.0 GB RAM
Processor: i7-2600 CPU@3.40GHz
AMD FirePro V7900; Intuos4 Wacom tablet
http://www.slocumfilm.com
Desktop PC Win10-Pro -64 bit OS; 32.0 GB RAM
Processor: i7-2600 CPU@3.40GHz
AMD FirePro V7900; Intuos4 Wacom tablet
Re: a layer count
Hi paul,
Have a look HERE to see what I've come up with that might prove useful.
Actually, I see now what you are wanting, you want the actual layers themselves to have ordinal numbering. It should be easy to add...
I could also see a little script being able to non-destructively introduce (and then update) prefix numbers to the layer titles with the click of a button. Hmm.
Sven
Have a look HERE to see what I've come up with that might prove useful.
Actually, I see now what you are wanting, you want the actual layers themselves to have ordinal numbering. It should be easy to add...
I could also see a little script being able to non-destructively introduce (and then update) prefix numbers to the layer titles with the click of a button. Hmm.
Sven
TVP Pro 11.0.10-64bit Win10 - 64GB ram -2TB HHD - 256GB SSD - Wacom Cintiq 16, driver 6.3.41-1
Android Tablet: rel. 11, Samsung Galaxy Note10.1 - 32GB with microSD 32GB
Android Tablet: rel. 11.5, Samsung Galaxy Tab S7plus - 128GB with microSD 64GB
Android Tablet: rel. 11, Samsung Galaxy Note10.1 - 32GB with microSD 32GB
Android Tablet: rel. 11.5, Samsung Galaxy Tab S7plus - 128GB with microSD 64GB
- Peter Wassink
- Posts: 4437
- Joined: 17 Feb 2006, 15:38
- Location: Amsterdam
- Contact:
Re: a layer count
i'm afraid you misunderstood my request.Elodie wrote:But the aim here is to have a layer count in addition of the name, isn't it ?
Peter, IYO, how would the layer count work ? Would each layer have a unique name ? What if you change their order ? What if you copy past a layer from a different project ?
i was only asking for a way to know the total number of layers, the ammount of flayers in the project.
just like we already have the information on the ammount of frames in the project
and to have this information visible somewhere.
thats all.
maybe a numbering of the layers would be usefull too, but as you see from this discusion it could be tricky to implement
Peter Wassink - 2D animator
• PC: Win11/64 Pro - AMD Ryzen 9 5900X 12-Core - 64Gb RAM
• laptop: Win10/64 Pro - i7-4600@2.1 GHz - 16Gb RAM
• PC: Win11/64 Pro - AMD Ryzen 9 5900X 12-Core - 64Gb RAM
• laptop: Win10/64 Pro - i7-4600@2.1 GHz - 16Gb RAM
Re: a layer count
In fact, I did understand your need, but as other persons were thinking about something more complicated...
So, ok, just a total amount of layers, ok !
So, ok, just a total amount of layers, ok !
Re: a layer count
What about the infobar? There is plenty of room there for another permanent segment that might always show current-layer/total-layercount for the active project?
Sven
Sven
TVP Pro 11.0.10-64bit Win10 - 64GB ram -2TB HHD - 256GB SSD - Wacom Cintiq 16, driver 6.3.41-1
Android Tablet: rel. 11, Samsung Galaxy Note10.1 - 32GB with microSD 32GB
Android Tablet: rel. 11.5, Samsung Galaxy Tab S7plus - 128GB with microSD 64GB
Android Tablet: rel. 11, Samsung Galaxy Note10.1 - 32GB with microSD 32GB
Android Tablet: rel. 11.5, Samsung Galaxy Tab S7plus - 128GB with microSD 64GB