Old 01-10-2020, 03:04 PM   #1
synkrotron
Human being with feelings
 
synkrotron's Avatar
 
Join Date: May 2015
Location: Warrington, UK
Posts: 1,122
Default tcp_heights (small) driving me nuts!

I've not really questioned this until now.

I'm talking about the global setting tcp_heights.

From the WALTER themer's guide:-

Quote:
The tcp_heights gives you control over the height your TCP track takes in various circumstances.

tcp_heights a b c d

The four values are:

a : Supercollapsed - the height of any track that is inside a folder, when the foldercomp button has been pressed twice.

b : Collapsed - the height of any track that is inside a folder, when the foldercomp button has been pressed once.

c : Small - one size above minimum size when doing cntrl+shift+up.

d : Recarm - height of a record armed track.

Okay, I am okay with "a," "b" and "d."

But "c : small" has got me totally flummoxed.

I could just ignore it but I'm a dog and this has become my bone.

Woof!

First, here is the line from the default V6 theme:-

tcp_heights 4 25 50 64

And from the default V5 theme:-

tcp_heights 4 24 35 58

I'll work with the V5 theme...

So, to reiterate, C = one size above minimum size when doing ctrl + shift + up

what is "one size?"

Well, it ain't "b."

From the smallest size, as set by "b" (not supercollapsed, which can only be achieved with a folder) my track is 24px high.

With 1 x ctrl + shift + up the track height increases to 29px

With 2 x ctrl + shift + up the track height increases to 35px

With 3 x ctrl + shift + up the track height increases to 46px

With 4 x ctrl + shift + up the track height increases to 58px

With 5 x ctrl + shift + up the track height increases to 73px


It takes 2 x ctrl + shift + up to get to 35px, which is set by "b."

Let's change "b" to 36.

With 1 x ctrl + shift + up the track height increases to 30px

With 2 x ctrl + shift + up the track height increases to 36px

With 3 x ctrl + shift + up the track height increases to 47px

With 4 x ctrl + shift + up the track height increases to 58px

With 5 x ctrl + shift + up the track height increases to 73px

Now let's change "b" to 37.

With 1 x ctrl + shift + up the track height increases to 30px

With 2 x ctrl + shift + up the track height increases to 37px

With 3 x ctrl + shift + up the track height increases to 47px

With 4 x ctrl + shift + up the track height increases to 58px

With 5 x ctrl + shift + up the track height increases to 73px


Well, there is a pattern there, I suppose, but not what I expected.

The 4th ctrl + shift + up seems to match the "recarm size."

And regardless of the "small" size, the 5th ctrl + shift + up = 73px


If we set "b" back to 35 and increase the "recarm size" to 60, the 4th ctrl + shift + up makes the track height = 60px and the 5th ctrl + shift + up = 75px. So at some point the "recarm size" plays a part.


Anyway, if you got this far then you're as mad as me

Good night
__________________
Bandcamp // YouTube // SoundCloud
synkrotron is offline   Reply With Quote
Old 01-11-2020, 04:09 PM   #2
xpander
Human being with feelings
 
xpander's Avatar
 
Join Date: Jun 2007
Location: Terra incognita
Posts: 5,323
Default

Quote:
Originally Posted by synkrotron View Post
I've not really questioned this until now.
I'm talking about the global setting tcp_heights.

From the WALTER themer's guide:-
Quote:
The tcp_heights gives you control over the height your TCP track takes in various circumstances.

tcp_heights a b c d
The four values are:
a : Supercollapsed - the height of any track that is inside a folder, when the foldercomp button has been pressed twice.
b : Collapsed - the height of any track that is inside a folder, when the foldercomp button has been pressed once.
c : Small - one size above minimum size when doing cntrl+shift+up.
d : Recarm - height of a record armed track.

Okay, I am okay with "a," "b" and "d."
But "c : small" has got me totally flummoxed.

...

And from the default V5 theme:-
tcp_heights 4 24 35 58
I'll work with the V5 theme...

So in this case it's 4 for the supercollapsed (a), the smallest when collapsed in folder.
Then 24 for the collapsed (b). This is the second smallest inside a folder, smallest outside a folder.
Then 35 for the small (norecarm)(c), meaning regular track not record armed.
And finally 58 for the record armed tracks (d).


Quote:
Originally Posted by synkrotron View Post
So, to reiterate, C = one size above minimum size when doing ctrl + shift + up

what is "one size?"
Well, it ain't "b."

From the smallest size, as set by "b" (not supercollapsed, which can only be achieved with a folder) my track is 24px high.

With 1 x ctrl + shift + up the track height increases to 29px
As we get to the next defined size, you will notice that this 29 pixels is about half way between the two defined sizes.

Quote:
With 2 x ctrl + shift + up the track height increases to 35px
And this is your small norecarm size (c), meaning regular track not record armed. Now we can do a bit of calculating, 35 (this size)-24 (collapsed size)=11. Divide that by 2 and we'll get 5.5. So we could say that the previous step was about half way between the two sizes defined in the theme.

Quote:
With 3 x ctrl + shift + up the track height increases to 46px
Ok, we are again about half way between two defined sizes as you'll see next.

Quote:
With 4 x ctrl + shift + up the track height increases to 58px
And here we arrive at the size for the record armed tracks (d). Calculating again, 58 (this rec arm size)-35 (small norecarm size)=23. Divided by 2 gets us 11.5. Add that to 35 and we get 46.5, the previous half way point.

But your earlier question about "one size"? Well, small (c) is "one size" bigger than collapsed (b) which was the smallest you can get a regular not record armed track. It's not really about size in pixels or zooming steps, but rather the difference between sizes defined in the theme. As we could see, this "one size" also has a half way point when zooming.

TCP minimum height?

Quote:
Originally Posted by synkrotron View Post
Anyway, if you got this far then you're as mad as me
I'm not quite sure if I should be relieved or concerned?
xpander is online now   Reply With Quote
Old 01-12-2020, 03:52 AM   #3
synkrotron
Human being with feelings
 
synkrotron's Avatar
 
Join Date: May 2015
Location: Warrington, UK
Posts: 1,122
Default

Quote:
Originally Posted by xpander View Post
I'm not quite sure if I should be relieved or concerned?
I would say "concerned."


__________________
Bandcamp // YouTube // SoundCloud
synkrotron is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 12:39 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, vBulletin Solutions Inc.