|
|
|
02-26-2023, 10:50 AM
|
#1
|
Human being with feelings
Join Date: Feb 2022
Posts: 95
|
height value of the mixer
good afternoon
I am looking at how I can find out the height of the mixer using Walter, but from what I have read, we can define at what height to locate, the buttons, the meter, etc... But it does not allow us to obtain the height value of the mixer.
Am I wrong, or is there a way.?
Sorry my English is very bad.
All the best
|
|
|
02-27-2023, 12:47 AM
|
#2
|
Pixel Pusher
Join Date: Mar 2007
Location: Blighty
Posts: 4,984
|
'h' in WALTER is the height of the panel. That might not be the height of the total mixer because it doesn't include the extended mixer area (if present) or the track icon area (if present).
|
|
|
02-27-2023, 05:55 AM
|
#3
|
Human being with feelings
Join Date: Feb 2022
Posts: 95
|
Quote:
Originally Posted by White Tie
'h' in WALTER is the height of the panel. That might not be the height of the total mixer because it doesn't include the extended mixer area (if present) or the track icon area (if present).
|
Thanks for the reply.
The only option that I have seen, has been to define small ranges to adjust the meter. having two options, when the track is selected and when it is not selected.
This way of doing it is quite precarious, and complicated to try to balance with the other elements of the skin.
I give an example:
set mcp.meter ?track_selected [52 648 76 375 0 1 0 1] h>441 h<600 [4 30 37 59 0 0 0 0] h>600 h<650 [4 30 37 72 0 0 0 0] h>650 h<670 [4 30 37 92 0 0 0 0]
However, I have put the same question in the script forum, in case it could be done that way.
All the best
|
|
|
02-27-2023, 06:02 AM
|
#4
|
Pixel Pusher
Join Date: Mar 2007
Location: Blighty
Posts: 4,984
|
What is it you are trying to do?
|
|
|
02-27-2023, 11:13 AM
|
#5
|
Human being with feelings
Join Date: Feb 2022
Posts: 95
|
Quote:
Originally Posted by ArmTazar
Thanks for the reply.
The only option that I have seen, has been to define small ranges to adjust the meter. having two options, when the track is selected and when it is not selected.
This way of doing it is quite precarious, and complicated to try to balance with the other elements of the skin.
I give an example:
set mcp.meter ?track_selected [52 648 76 375 0 1 0 1] h>441 h<600 [4 30 37 59 0 0 0 0] h>600 h<650 [4 30 37 72 0 0 0 0] h>650 h<670 [4 30 37 92 0 0 0 0]
However, I have put the same question in the script forum, in case it could be done that way.
All the best
|
I have attached two screenshots. the first is with the full size mixer. The second has been reduced manually and is where you can see that the meter are not correctly. Therefore, knowing the height of the mixer or how to obtain it. And in what way have I done it to go, as is usually deir pulling.
All the best
Last edited by ArmTazar; 04-12-2023 at 10:07 AM.
|
|
|
02-27-2023, 11:34 AM
|
#6
|
Pixel Pusher
Join Date: Mar 2007
Location: Blighty
Posts: 4,984
|
In that case yes, the height of the mixer is h.
Do you want to learn how themes work, or do you just want that one thing fixing? Because that looks like the kind of easy fix that a lot people here would have no trouble doing for you if you asked nicely. If you'd rather do it yourself, see the stickies at the top of this forum.
|
|
|
02-27-2023, 01:03 PM
|
#7
|
Human being with feelings
Join Date: Jan 2006
Posts: 1,994
|
Quote:
Originally Posted by ArmTazar
I have attached two screenshots. the first is with the full size mixer. The second has been reduced manually and is where you can see that the meter are not correctly. Therefore, knowing the height of the mixer or how to obtain it. And in what way have I done it to go, as is usually deir pulling.
All the best
|
In your 2nd image I'm seeing when you reduced the height, that your pan,width and their associate labels have been hidden along with a couple other mcp controls that were present in your full height image. You really don't need to know the actual height value of the MCP to fix this.
Likely within your rtconfig there are some parameters which have something along the lines of
*When your Pan hides example
set mcp.pan h<(some h value or variable) [0]
You would need to include that h<(some h value or variable) within your set mcp.meter command and then adjust your meter h parameter value size.
You essentially just need to just refer to the sections of code in your rtconfig for those other items that are creating the space and apply the same h adjustment to your set mcp.meter command so when the spaces appear due to items going away, the meter resizes and fills those spaces that are created in their place at the same time.
If you're unable to follow my explanation which may have some incorrect terminology and is more along the lines of the thought process, then see stickies at top of page and dig further into the theming guide.
|
|
|
02-27-2023, 02:56 PM
|
#8
|
Pixel Pusher
Join Date: Mar 2007
Location: Blighty
Posts: 4,984
|
Youd probably best post your theme because this...
set mcp.meter ?track_selected [52 648 76 375 0 1 0 1] h>441 h<600 [4 30 37 59 0 0 0 0] h>600 h<650 [4 30 37 72 0 0 0 0] h>650 h<670 [4 30 37 92 0 0 0 0]
..is some really confused WALTER that you're probably not going to find easy to understand, it doesn't make sense already.
|
|
|
02-28-2023, 08:01 AM
|
#9
|
Human being with feelings
Join Date: Feb 2022
Posts: 95
|
Quote:
Originally Posted by White Tie
Youd probably best post your theme because this...
set mcp.meter ?track_selected [52 648 76 375 0 1 0 1] h>441 h<600 [4 30 37 59 0 0 0 0] h>600 h<650 [4 30 37 72 0 0 0 0] h>650 h<670 [4 30 37 92 0 0 0 0]
..is some really confused WALTER that you're probably not going to find easy to understand, it doesn't make sense already.
|
Good afternoon. According to the photos that I attached. In the first the mixer occupies the entire screen, and in the second the mixer "has another size that is not full screen".
In this case, as I have indicated the meter, it does not fit well with the size of the skin. And that is why I have generated the WALTER programming that I indicated. Which is nothing more than depending on the size of the mixer, the meter will have its size.
In this way, I roughly control the size of the meter.
The reason is because at home I have a 32" screen and then I have a laptop, which has a 19" screen. The theme does not fit well on the laptop.
Apart from that I also have defined different screenshots
All the best
|
|
|
02-28-2023, 08:03 AM
|
#10
|
Human being with feelings
Join Date: Feb 2022
Posts: 95
|
Quote:
Originally Posted by Rednroll
In your 2nd image I'm seeing when you reduced the height, that your pan,width and their associate labels have been hidden along with a couple other mcp controls that were present in your full height image. You really don't need to know the actual height value of the MCP to fix this.
Likely within your rtconfig there are some parameters which have something along the lines of
*When your Pan hides example
set mcp.pan h<(some h value or variable) [0]
You would need to include that h<(some h value or variable) within your set mcp.meter command and then adjust your meter h parameter value size.
You essentially just need to just refer to the sections of code in your rtconfig for those other items that are creating the space and apply the same h adjustment to your set mcp.meter command so when the spaces appear due to items going away, the meter resizes and fills those spaces that are created in their place at the same time.
If you're unable to follow my explanation which may have some incorrect terminology and is more along the lines of the thought process, then see stickies at top of page and dig further into the theming guide.
|
Thanks for the reply.
In this case, I have WALTER programmed for what is observed in capture 2. I prefer to see the meter than to have the PAN.
Although, to be honest. I'm thinking about it.
All the best
|
|
|
02-28-2023, 08:28 AM
|
#11
|
Pixel Pusher
Join Date: Mar 2007
Location: Blighty
Posts: 4,984
|
You're not going to get far until you've understood the basics. In this:
Quote:
Originally Posted by White Tie
set mcp.meter ?track_selected [52 648 76 375 0 1 0 1] h>441 h<600 [4 30 37 59 0 0 0 0] h>600 h<650 [4 30 37 72 0 0 0 0] h>650 h<670 [4 30 37 92 0 0 0 0]
|
Polish Notation goes Question YesAnswer NoAnswer, so that h>600 makes no sense. The opposite of h<600 is already h>=600. Same with h>650. At the end, h<670 doesn't have a NoAnswer.
When selected you are using edge attachment [. . . . 0 1 0 1] but not when unselected [. . . . 0 0 0 0].
It sucks that the WALTER guide is only in English, sorry about that, I can only suggest you try to translate it.
|
|
|
02-28-2023, 11:53 AM
|
#12
|
Human being with feelings
Join Date: Jan 2006
Posts: 1,994
|
Quote:
set mcp.meter ?track_selected [52 648 76 375 0 1 0 1] h>441 h<600 [4 30 37 59 0 0 0 0] h>600 h<650 [4 30 37 72 0 0 0 0] h>650 h<670 [4 30 37 92 0 0 0 0]
|
Yep, like WT mentioned this is some pretty confused Polish Notation you have going on.
What are you trying to accomplish with the ?track_selected scaler value?
My recommendation would be to avoid the Polish Notation if you're just getting into WALTER. Polish notation is nice in that it puts everything in 1 line of code for each MCP element but is completely unnecessary and often leads to more confusion if it's not your code you're starting with.
I've found it's much simpler to write individual lines for each "h" step value and then when you adjust the height of the MCP, you can focus on each of those individual single lines and make value adjustments from what you see on-screen. Then once you have everything resizing how you want, you can then always go back and make a single line of Polish Notation code from the individual lines of code to tidy everything back into a single consolidated line of Polish Notation code.
You should also be able to take that single line of Polish notation code you have and break it up into separate lines of code. If you're not able to do that, then you'll likely never be able to fix the issues you're currently trying to solve and like WT already mentioned you have multiple questions going unanswered in that mess of Polish notation single line code going on and if you broke that single line into separate lines, the problems you're having would become much easier to understand. Go visit the Polish Notation section in the theming guide if you're unable to break that line into separate lines of code.
Last edited by Rednroll; 02-28-2023 at 12:03 PM.
|
|
|
02-28-2023, 03:27 PM
|
#13
|
Human being with feelings
Join Date: Feb 2022
Posts: 95
|
Quote:
Originally Posted by Rednroll
Yep, like WT mentioned this is some pretty confused Polish Notation you have going on.
What are you trying to accomplish with the ?track_selected scaler value?
My recommendation would be to avoid the Polish Notation if you're just getting into WALTER. Polish notation is nice in that it puts everything in 1 line of code for each MCP element but is completely unnecessary and often leads to more confusion if it's not your code you're starting with.
I've found it's much simpler to write individual lines for each "h" step value and then when you adjust the height of the MCP, you can focus on each of those individual single lines and make value adjustments from what you see on-screen. Then once you have everything resizing how you want, you can then always go back and make a single line of Polish Notation code from the individual lines of code to tidy everything back into a single consolidated line of Polish Notation code.
You should also be able to take that single line of Polish notation code you have and break it up into separate lines of code. If you're not able to do that, then you'll likely never be able to fix the issues you're currently trying to solve and like WT already mentioned you have multiple questions going unanswered in that mess of Polish notation single line code going on and if you broke that single line into separate lines, the problems you're having would become much easier to understand. Go visit the Polish Notation section in the theming guide if you're unable to break that line into separate lines of code.
|
Good night.
I have tried the polish notation. And the difference between what I have written, with respect to what they indicate. It is that in my form, the scale of the meter is ascending. In other words, the code will ask about the height of the growing mixer. and with the Polish notation you have to write it asking in a decreasing way.
Although already knowing this. The code is easier with the Polish notation.
I attach the code without polish notation and with polish notation. In the end the result is the same.
This is my way. The question is asked in ascending order. They are with a semicolon, because I have carried out different tests. Finally leaving it in Polish notation, which as I said is easier to understand.
;set mcp.meter h>441 h<600 [4 30 37 78 0 0 0 0] h>600 h<650 [4 30 37 72 0 0 0 0] h>650 h<700 [4 30 37 112 0 0 0 0] h>700 h<750 [4 30 37 160 0 0 0 0] \
; h>750 h<800 [4 30 37 210 0 0 0 0] h>800 h<850 [4 30 37 290 0 0 0 0] h>850 h<900 [4 30 37 323 0 0 0 0] h>900 h<950 [4 30 37 295 0 0 0 0] \
; h>950 h<1048 [4 30 37 301 0 0 0 0]
With Polish notation. Here it will always result in the first question. It will always be greater than 441:
;set mcp.meter h>441 [4 30 37 78 0 0 0 0] h>600 [4 30 37 72 0 0 0 0] h>650 [4 30 37 112 0 0 0 0] h>700 [4 30 37 160 0 0 0 0] \
; h>750 [4 30 37 210 0 0 0 0] h>800 [4 30 37 290 0 0 0 0] h>850 [4 30 37 323 0 0 0 0] h>900 [4 30 37 295 0 0 0 0] \
; h>950 [4 30 37 301 0 0 0 0]
And this is with Polish notation with descending questions.
set mcp.meter h>950 [4 30 37 301 0 0 0 0] h>900 [4 30 37 295 0 0 0 0] h>850 [4 30 37 323 0 0 0 0] h>800 [4 30 37 290 0 0 0 0] \
h>750 [4 30 37 210 0 0 0 0] h>700 [4 30 37 160 0 0 0 0] h>650 [4 30 37 112 0 0 0 0] h>600 [4 30 37 72 0 0 0 0] \
h>441 [4 30 37 78 0 0 0 0]
All the best
|
|
|
02-28-2023, 07:47 PM
|
#14
|
Human being with feelings
Join Date: Dec 2015
Posts: 2,102
|
Quote:
set mcp.meter h>441 h<600 [4 30 37 78 0 0 0 0] h>600 h<650 [4 30 37 72 0 0 0 0] h>650 h<700 [4 30 37 112 0 0 0 0] h>700 h<750 [4 30 37 160 0 0 0 0] \
; h>750 h<800 [4 30 37 210 0 0 0 0] h>800 h<850 [4 30 37 290 0 0 0 0] h>850 h<900 [4 30 37 323 0 0 0 0] h>900 h<950 [4 30 37 295 0 0 0 0] \
; h>950 h<1048 [4 30 37 301 0 0 0 0]
|
double stacking the height seems like an error to me.
h>800 h<850
If it does work, you'll need to add an answer for each of the 2 questions asked, plus a third for when the answer to both questions is false.
EXAMPLES:
The code in simple form is:
set mcp_meter [4 30 37 295 0 0 0 0]
The code with changes at a specified height is:
set mcp_meter h>850 [4 30 37 295 0 0 0 0] [4 30 37 195 0 0 0 0]
The second example says if the height of the mixer is more than 850, make the meter height 295.
If the mixer height below 850, make the meter height 195.
h>850 = the question
[4 30 37 295 0 0 0 0] = answer if question is true
[4 30 37 195 0 0 0 0] = answer if question is false
When using "h>" and there are more height changes below 850, the height questions and answers need to be added from the highest to the lowest height.
If using the "h<" and there are more changes, the height questions and answers need to be added from the lowest to the highest height.
To clarify "h>800 h<850" probably does nothing, but is also unnecessary.
::
Last edited by lucas_LCS; 02-28-2023 at 07:58 PM.
|
|
|
02-28-2023, 10:39 PM
|
#15
|
Human being with feelings
Join Date: Jan 2006
Posts: 1,994
|
Quote:
Originally Posted by lucas_LCS
double stacking the height seems like an error to me.
h>800 h<850
<snip>
To clarify "h>800 h<850" probably does nothing, but is also unnecessary.
::
|
I'm going to speculate what's he's attempting to do.....although likely incorrectly.
Just taking that snippet....
Code:
set mcp.meter h>800 h<850 [4 30 37 290 0 0 0 0]
I think what he's trying accomplish is asking the question as "is h>800 AND is h<850?" ,If "Yes" THEN set mcp.meter to Answer=[4 30 37 290 0 0 0 0]
I could be wrong but based on the code he posted, it seems he's trying to bracket in sections of the height value, at least that's what it seems like he's attempting to do with that type of double stacking logic.
Quote:
Originally Posted by ArmTazar
Good night.
set mcp.meter h>950 [4 30 37 301 0 0 0 0] h>900 [4 30 37 295 0 0 0 0] h>850 [4 30 37 323 0 0 0 0] h>800 [4 30 37 290 0 0 0 0] \
h>750 [4 30 37 210 0 0 0 0] h>700 [4 30 37 160 0 0 0 0] h>650 [4 30 37 112 0 0 0 0] h>600 [4 30 37 72 0 0 0 0] \
h>441 [4 30 37 78 0 0 0 0]
|
Based off of above line, here's how I would write the Walter code
Non-Polish Notation separate line version
Code:
set mcp.meter [4 30 37 301 0 0 0 0]
set mcp.meter h<900 [4 30 37 295 0 0 0 0]
set mcp.meter h<850 [4 30 37 323 0 0 0 0]
set mcp.meter h<750 [4 30 37 210 0 0 0 0]
set mcp.meter h<700 [4 30 37 160 0 0 0 0]
set mcp.meter h<650 [4 30 37 112 0 0 0 0]
set mcp.meter h<600 [4 30 37 72 0 0 0 0]
set mcp.meter h<441 [4 30 37 78 0 0 0 0]
Now above in Polish Notation form
Code:
set mcp.meter h<441 [4 30 37 78 0 0 0 0] h<600 [4 30 37 72 0 0 0 0] h<650 [4 30 37 112 0 0 0 0] h<700 [4 30 37 160 0 0 0 0] h<750 [4 30 37 210 0 0 0 0] h<850 [4 30 37 323 0 0 0 0] h<900 [4 30 37 295 0 0 0 0] [4 30 37 301 0 0 0 0]
I would further be asking the question, what are the set mcp.size parameters? A >900 pixel height seems pretty tall to me for the mixer section.
Last edited by Rednroll; 02-28-2023 at 11:46 PM.
|
|
|
03-01-2023, 12:26 AM
|
#16
|
Human being with feelings
Join Date: Feb 2022
Posts: 95
|
Quote:
Originally Posted by Rednroll
Just taking that snippet....
Code:
set mcp.meter h>800 h<850 [4 30 37 290 0 0 0 0]
I think what he's trying accomplish is asking the question as "is h>800 AND is h<850?" ,If "Yes" THEN set mcp.meter to Answer=[4 30 37 290 0 0 0 0]
|
Right that was the idea.
However, thank you all, because now I have more clarity on how to do it.
Sorry if this post has generated controversy. But thanks to her you learn.
Thanks also to the translator that my English is disastrous.
Greetings to all.
|
|
|
03-01-2023, 06:59 AM
|
#17
|
Human being with feelings
Join Date: Jan 2006
Posts: 1,994
|
Glad you got it figured out.
Do you still think the Polish notation is simpler to understand?
Personally, although many more lines, I find when trouble shooting and things are not working as intended, I prefer the separate individual resize height adjustment steps in separate lines of code. It makes my head hurt less having to walk my brain through all the Q&A logic in a single line. Throw some variables into that single line and it's just too much book keeping for my head to keep track. With the separate lines, I can also temporarily comment out each line for trouble shooting purposes to isolate a particular adjustment step.
When starting with someone else's code, then trying to figure out the logic they had going on at the time can be a struggle. Heck, even with my own code when I've written something in a long Polish notation code line I find myself going back and trying to modify it to make some changes. Then find myself asking "what was I thinking when I was writing this before?"
Last edited by Rednroll; 03-01-2023 at 07:14 AM.
|
|
|
03-01-2023, 05:05 PM
|
#18
|
Human being with feelings
Join Date: Feb 2022
Posts: 95
|
Quote:
Originally Posted by Rednroll
Glad you got it figured out.
Do you still think the Polish notation is simpler to understand?
Personally, although many more lines, I find when trouble shooting and things are not working as intended, I prefer the separate individual resize height adjustment steps in separate lines of code. It makes my head hurt less having to walk my brain through all the Q&A logic in a single line. Throw some variables into that single line and it's just too much book keeping for my head to keep track. With the separate lines, I can also temporarily comment out each line for trouble shooting purposes to isolate a particular adjustment step.
When starting with someone else's code, then trying to figure out the logic they had going on at the time can be a struggle. Heck, even with my own code when I've written something in a long Polish notation code line I find myself going back and trying to modify it to make some changes. Then find myself asking "what was I thinking when I was writing this before?"
|
all the reason
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 12:32 PM.
|