No, it’s not a bug. I probably misunderstood what you were trying to do.
The parameter in my script wasn’t really meant to be used on macro page or connected to a knob. Only thing it does is mirror the value of quick control 1 and then renames it.
If you wanted a knob on macro page with that behaviour then you could use your original script with some modification.
local QC3String = { [0]="Digital", "1", "2", "3", "4", "5", "6", "7", "8", "9", "10", "11", "12", "13", "14", "15", "16", "17", "18", "19", "20", "21", "22", "23", "24", "25", "26", "27", "28", "29", "30", "31", "32", "33", "34", "35", "36", "37", "38", "39", "40", "41", "42", "43", "44", "45", "46", "47", "48", "49", "Analog", "51", "52", "53", "54", "55", "56", "57", "58", "59", "60", "61", "62", "63", "64", "65", "66", "67", "68", "69", "70", "71", "72", "73", "74", "75", "76", "77", "78", "79", "80", "81", "82", "83", "84", "85", "86", "87", "88", "89", "90", "91", "92", "93", "94", "95", "96", "97", "98", "99", "Bionic" }
defineParameter("QUALITY", nil, 50, QC3String)
Or the same thing using loop to save some typing
local QC3String={}
QC3String[0]="Digital"
for i=1,100 do
QC3String[i]=tostring(i)
end
QC3String[50]="Analog"
QC3String[100]="Bionic"
defineParameter("QUALITY",nil,50,QC3String)
This parameter doesn’t do anything except for displaying the values you wanted.