Posts made by ustk

@d-healey Good idea

@christoph-hart then using a reg should resolve the issue right? For a better world?

@mypetrobot Thanks! that is interesting

@d-healey probably not, but I'll try with a shoehorn

@d-healey That's what I was afraid of because I don't have the space to write such a long string...

This is a question for the US people, or whoever knows the answer of course
I'm working on a project that necessitates a distance value and is intended for live sound engineers
I know how to convert meters to yards, but the question is:
Is it ok to write yard with decimals, or should it always be converted to yard/feet/inches?
What is more natural for you guys?

@d-healey

@d-healey @Christoph-Hart

inline function onbtnQueryControl(component, value)
{
	if (value)
	{
		local state = "";
		
		for (i = 0; i < buttons.length; i++)
			state += Math.round(buttons[i].getValue());
		
		Console.clear();
		
		switch (state)
		{
			case "0001": Console.print("Do this"); 		break;
			case "0010": Console.print("Do that"); 		break;
			case "1011": Console.print("Do whatever"); 	break;
			default:		Console.print("Do nothing");
		}
	}
}

@christoph-hart Yep that works! I understand the allocation issue though... This is where using a string would be better

@d-healey Note that it can also be replaced by the string representation of the same binary number.
I'm not sure to agree with the fact that it can become unpleasant, because it's always easier to debug or maintain a visual representation rather than a state you don't "see", but it's a matter of taste of course...

@d-healey You can also switch over an array, it has the advantage of giving easy readable code, but it might not be compatible with what you want to achieve...

inline function onbtnQueryControl(component, value)
{
	if (value)
	{
		local state = [];
		
		for (i = 0; i < buttons.length; i++)
			state.push(buttons[i].getValue());
		
		Console.clear();
		
		switch (state)
		{
			case [0,0,0,1]: Console.print("Do this"); 		break;
			case [0,0,1,0]: Console.print("Do that"); 		break;
			case [1,0,1,1]: Console.print("Do whatever"); 	break;
			default:		Console.print("Do nothing");
		}
	}
}

@d-healey So if I understand well, you need a single number representation of the state of all buttons at a time?
In this case, effectively this is the best solution I can see...

@d-healey Well, as for just displaying, yes it can be much simpler but I know you already know what I will show you below, so if you do it your way, I'm sure there is a good reason behind it, like for filtering your list

HiseSnippet 1065.3ocsV0uaaaCDmxNZqx6CzBrG.B+OSFNy0Nwsa.YCKKNICFqI0aNKX.EEEzRzwDghTijJqFaAnOJ6QqOB6MX6n9vlI0oHwK0vvV22+zc7tiiTxHpVKUHufSlmRQdep+34ByrAyHLAZ39VFSYbCUcBUaP6MOkn0zXjmW8ezpgWvFn7O+y2uGgSDQzkrPnSkrH5yXILyRti18mXb9gjX5IrDGs6u6vHoXfjKy.zT2uKJkDcN4L5wDqZ07QdezAwLiTM1PLTMxai8jwyGOS9GhB8OkoYS3TKQOzXvQErOTxisH1xEMXFiGOp5sVi.uLZYNndQN3K7OhEyVveYt3g4BvKsvMe3U6pvq9UfWOW300Adq.RdNPZiBH8H+wQJVpYoDKd9D+gBnzLk.ocWnTnKp1Cq6OPBZHLcRHmSOTADKrH7oc6tIF9o0NMZ.odsAOIyXfGveG9EuDXNUpvgLfp6NXF9aw8g+Z2tUi+rQPolcRyzyBqhwYTy.YRpT.DgM2KWkl31VezF2qUKHPUF9B1K6nspKLJIe.gym.U6PonPdIevfKaz3wOFOwH94LpZdENKIAns5XWoPSvCUOeCwqT5xH1fI3LAEOMSDYXRA9cTJLpJRahufvyn4oD1TbXIU.PFvkQDNdBfwlM2ACuDlYLMNRlwiwSnXh.STJxbrVhYluTioDMipvFINkplQR03hFOl3LLAyYZSmNc.+BeudgopZvohyLyJqRAA4PxIgC4nSs.LrUtzfI31.3bqSs60B9uIF.pISInwvK+l3l6TDV30WK4zNQbJQEZqlKXkBvzDNwx6xFW5j5NVZnOWDlmgfhI95hlNckxJyzbpZkhsiNTuOCCEYISnJ25iUQne5pMo92bSp6LjnhSYNJJECELyySohaZxBp7nocFSIp.UM4syedY6bQtGwft1.+BhdnbH6NYEcGLeqqadIPtklu8+Oy6uBv+qC2mXH1wZkIDHIAmvMLa92ae5EvNhhgbA96S0majoPcYQyL77sHm8Z2EIyWP7FxtTAAJn141OCN0JriGQ2Imukiyea78ry21w4+s9d148cQ9ecmb9CtQm2vuZZni2eShi2e6uuqg9ZvIeregdqHVL8QxDHRDPrmWMM4B5PwHEElQmCk2cCHr6UFmwIlqtP1dKjRAv.fqrEztoSnYl4tGGu21Reag3i7GwLQyVMFqsBLBcJeHvX4ca9L+ClNkFYVBvM7O729vbQFzuHyLv5qiHFECNr3ebVxX35cQTH5BAkaG.6UyNhoftqk1lAFSEw4D+K7oTXOKsWovdUBQIjHk7UQEynr2d5A4b.LIxu3Xf+QVZ7h4p99c6zEk.mFeUTj80+qfo2q1lsVCa1dMro+ZXySVCad5ZXyWuF17MuWarCB9gLiLonc.XL5f7UDddGjOoH+TH5+.OiUWF

@d-healey It is indeed interesting programmatically, but isn't that a bit convoluted for such a simple task?
Or do you intend to use it something else, maybe?

@Christoph-Hart I tried myself with no luck. Could you have a look, please?

@crd yeah that’s how I understood it but I just noticed this aside the main issue

@christoph-hart said in Scriptnode Midi CC Node Bug:

Yeah, that's me basically not liking #0

Feeling the same... demons from school I guess

@christoph-hart Speaking of offset issues, there's another one (not that problematic though)
the display buffer starts at 1 but the script index starts at 0...

@crd is it intended that your max is 130?
Shouldn't be 127? I don't think it is related to the issue though …

@Christoph-Hart Would it be conceivable to have a display buffer for filter development, or even a dedicated SNEX filter node?