3.10.0.5 beta / 3.11 alpha

Exposing the coordinates in the icon positioning control was ridiculously complex. The control has some bugs (especially during resizing) that I had to work around and a weird coordinate system, which was a nightmare to convert to something understandable.

But now it's done.

Version 3.10.0.578 Please use link in later post,

A somewhat larger update.

There are now script actions to set state icon size and position for scripted faders.
{iconsize:10}
{iconuppersize:10}
{iconposition:x,y}
{iconupperposition:x,y}

Position actions have x/y coordinates for the upper left corner of the icon. The top left corner of the button is 0,0, and the bottom right corner is 144,144.

In addition, the {icon} and {iconupper} actions are extended to allow optional size and position properties. Available options for both actions:

{icon:path}
{icon:path, size}
{icon:path, size, x, y}

There are also some new math commands:

{text:#HHMMSS(value)#} displays the value (ms) as time HH:MM:SS
{text:#HHMM(value)#} displays the value (ms) as time HH:MM
{text:#MMSS(value)#} displays the value (ms) as time MM:SS

Version 3.10.0.599

Version 3.10.0.599 still has the issue of scripted v-pot after doing these steps:

- Set the scripted v-pot to Single
- Set rotation to "both ways"
- Set the scripted v-pot to "lower" or "upper"
- The checkbox options of "both ways" are visible

Except the minor issue described in my previous post, everything seems to work perfectly. The new additions are great.

This is an update with most of the changes under the hood.

• The script engine has been restructured to allow for easier maintenance and extensions. A couple of bugs were fixed in the process.
  
• Changes are made to enhance performance a bit.
  
• Changes are made to have scripted faders and vpots act as expected when configured as horizontal pairs.
  

These changes should be pretty unnoticeable, but please let me know if you see any negative side effects.

In addition, a couple of new math functions for padding have been added.

LPAD(value, count, pad_character)
RPAD(value, count, pad_character)

LPAD will add pad characters to the left until the total number of characters is "count". RPAD will add characters to the right. Example:

LPAD(25,4,"0") will create the text "0025".
RPAD("Hell",7,"o") will create the text "Hellooo".

Version 3.10.0.672

Everything seems to work fine in version 3.10.0.672 

OK, a significant rewrite is done. I decided to implement searchable dropdown boxes instead of numeric fields in many places. This caused pretty extensive changes to the UI, which in turn required property migration from text boxes to dropdowns.

Please backup your profiles before installing this update. If values are not appropriately migrated, please let me know so I can fix that. If a few buttons are affected, perhaps you can live with that, but if many buttons are affected, it's better that I fix the migration, and you can re-run the update from the backed-up profiles.

During this update, I found several bugs. I realized, e.g., that the dual-byte CCs have never fully worked. When used, the wrong commands were sent, and the plugin never handled commands sent from the host. This is fixed.

I also realized that using NRPN with Cubase isn't very successful. NRPN from the Generic Remote does not work according to the recommendations in the MIDI spec. Technically, it isn't wrong, but the way they do it can't be handled by the MIDI driver I use. NRPN from the MIDI Remote in Cubase doesn't work at all. I haven't tested with other daws.

In addition, I've fixed several minor bugs and UI issues. And probably a bunch of other things I have forgotten about now.

I also implemented a new feature where faders and Vpots can have variable speed based on a script variable, even if the fader/vpot itself isn't scripted.

Version 3.10.0.809

Admin wrote:I also implemented a new feature where faders and Vpots can have variable speed based on a script variable, even if the fader/vpot itself isn't scripted.

I don't know what you mean. Could you explain this new feature with some example? Thanks!

I've had requests for a feature where you can have a shift button to control the speed of faders and vpots. The idea is (I believe) to have the fader/vpot function at "normal" speed, but if you need more detailed control, you could press a shift button to make the fader/vpot go slower.

I have implemented this with a text field for faders and vpots where you can reference a script variable for speed control. You can create a separate script button that sets this variable. Assume you reference the variable "faderspeed" from a fader button. You can configure a script button as a Hold button that sets the  "faderspeed" variable to 10 while the button is held and to 50 when it is released.

You can operate the fader at normal speed (50) but can get a slower speed (and higher precision) by holding down the script button while using the fader button.

I can't see the last midi values of the dropdown menu.
Scroll down stops at 126 in the "On" menu and at 124 in the "Off" menu.
I can select the higher values with the keyboard (arrow down), but not with the mouse.
It looks like this in my mac:

It seems that Generic Midi>Program Change is only sending value 127. It doesn't matter what value do I select, it always sends 127.

As example, here are two buttons with the same configuration: send a program change 80 MSB 0 LSB 0.

The legacy option works fine, but generic midi>program change is always sending 127:

jordikt wrote:I can't see the last midi values of the dropdown menu.

Yes, I can see the same on Windows if the Stream Deck window is "too small". The dropdown seems to have a fixed height, and if the bottom part is outside the window, it is clipped without being redrawn.

I've had some css clashes between the Strean Deck css and the dropdown css, and this is probably another one. I'll see if I can find it.

jordikt wrote:It seems that Generic Midi>Program Change is only sending value 127. It doesn't matter what value do I select, it always sends 127.

Why haven't I seen that!? You're correct; it doesn't send the configured value.

Admin wrote:Yes, I can see the same on Windows if the Stream Deck window is "too small".

I usually have the stream deck window at the maximum height in my macbook pro 16'. So I am experiencing this issue in a stream deck window that has a height of about 1100 pixels.

• Fixed the problem with the Program Change number.
  
• Updated the MIDI driver.
  
• Fixed some other minor UI bugs.
  

I haven't yet had time to look at the dropdown css problem.

Version 3.10.0.816

This is a new version after some code cleaning and additional bug fixes.

I consider this version to be "final" in the sense that I have no more planned job to do with it. On the other hand, when I start to record videos and write documentation explaining how it works, I often find that it doesn't work as I expected, so I wouldn't be surprised if that happens this time too.  

Version 3.10.0.894

Could you post the release notes of this update?

It would be useful to test all the additions.

The only functional change is that Latch buttons now work across Generic Midi/Note OnOff actions. Previously, it was two separate latch systems.

There were some minor situations where fields were displayed when they shouldn't have been.

The fader button had a bug where images for the handle background and VU front weren't handled correctly  (or rather, they weren't handled at all).

Besides that, there are internal changes that shouldn't affect what you see.

Sorry, I meant the release notes of the release update, the changes regarding the previous release version. 

As you say this is the release candidate and you have wrote the documentation, I suppose you have the release notes explaining the timers, the generic midi, etc.

I'm about to write the documentation and the release notes...

As "expected", I have found some issues while looking at the documentation.

There are some UI issues where the wrong fields are shown for scrub wheel buttons.

And I need to rework the latch button functionality a bit. I forgot it needs to work across pages, which the current version doesn't.

Or rather...I see that the documentation for the previous latch system says it works across pages, but in reality, it doesn't. I think I take the easy way out and change the doc instead of the solution.

Joerg wrote:I have discovered an issue. When changing pages the Fader Script Button values reset while the Mackie Control Button values don't

Fader Script Button values still reset when changing pages.

The plugin doesn't save the state for script buttons, so it can't restore anything when switching pages. You need to use the (init) command for that.

Version 3.10.0.894

It seems there is a bug when printing text of a variable that contains "\n". The button prints it instead of changing to the next line.

This is what the button shows with the following script:




[(init)(@PRO_G_Style:0){text:STYLE\nBUTTON}{state:0}]

[(@PRO_G_Style:*){@l_1:CLASSIC\n\nMODE}]
[(@PRO_G_Style:*){@l_2:CLEAN\n\nMODE}]
[(@PRO_G_Style:*){@l_3:VOCAL\n\nMODE}]
[(@PRO_G_Style:*){@l_4:GUITAR\n\nMODE}]
[(@PRO_G_Style:*){@l_5:UPWARD\n\nMODE}]
[(@PRO_G_Style:*){@l_6:DUCKING\n\nMODE}]

[(init)(@PRO_G_Style:1){text:#@l_1#}{state:0}]
[(init)(@PRO_G_Style:2){text:#@l_2#}{state:0}]
[(init)(@PRO_G_Style:3){text:#@l_3#}{state:0}]
[(init)(@PRO_G_Style:4){text:#@l_4#}{state:0}]
[(init)(@PRO_G_Style:5){text:#@l_5#}{state:1}]
[(init)(@PRO_G_Style:6){text:#@l_6#}{state:0}]

[(cc:12,4,0){@PRO_G_Style:1}{text:#@l_1#}{state:0}]
[(cc:12,4,31){@PRO_G_Style:2}{text:#@l_2#}{state:0}]
[(cc:12,4,63){@PRO_G_Style:3}{text:#@l_3#}{state:0}]
[(cc:12,4,95){@PRO_G_Style:4}{text:#@l_4#}{state:0}]
[(cc:12,4,127){@PRO_G_Style:5}{text:#@l_5#}{state:1}]
[(cc:12,5,127){@PRO_G_Style:6}{text:#@l_6#}{state:0}]

[(press)(@PRO_G_Style:0){cc:12,4,0}{cc:12,5,0}]
[(press)(@PRO_G_Style:1){cc:12,4,32}{cc:12,5,0}]
[(press)(@PRO_G_Style:2){cc:12,4,64}{cc:12,5,0}]
[(press)(@PRO_G_Style:3){cc:12,4,96}{cc:12,5,0}]
[(press)(@PRO_G_Style:4){cc:12,4,127}{cc:12,5,0}]
[(press)(@PRO_G_Style:5){cc:12,5,127}]
[(press)(@PRO_G_Style:6){cc:12,4,0}{cc:12,5,0}]

The "\n" script problem is fixed.
The script problem where setting a blank string in a script variable caused it to have the value 0 is fixed.
Several editor UI problems are fixed.

Version 3.10.0.905

If anyone wants to review the documentation, the new pages are accessible using the links below. The pages are not available in the menu yet, so the only way to see them is through these links.

Generic Midi button
Custom button fader images V2
Script timers
Script events
Script actions