I realise this isn’t a bug, just a ‘feature’, but this keeps catching me out.
If I have a rack space that I add the above widget’s to, as an after thought when I realise I need them, they set the assigned midi in block to a transpose of -127, and note on and off to C-1. This then means I get no sound. I was just wondering if im doing something wrong and there is a way to keep the existing settings.
I tend to use small knobs, should I maybe use a different style of widget?
I am lost, what widget are you using?
How is it mapped?
Im mapping widgets to a midi omin in block. There are set up for Transpose, lowest note and highest note. Mapped to the corresponding command.
Im adding these widgets so I can use Variations with different key ranges. I dont use the Widgets as such, I just believe I need them to allow the Midi in blocks to change when I change variations.
I normally do this as an after thought if I find I need to have certain sounds split etc.
keep in mind that this way you could get hanging notes.
Better user predefined midi in block with different note ranges and use widgets to block NOTE ON messages.
You could scale the values of the widgets to get a proper working range for your low/high keys?!
I haven’t had any note hanging issues so far. I do use the block note on feature with a button widget.
1 Like
The widgets work fine once set up. It’s just the way they behave when i first connect them to the Midi in block I’m talking about. I never need to touch them.
I think that is normal behavior when the widget value is 0 and you map it to a MIDI IN block.
Are you talking about the initial value literally after mapping the widget?
Yes, just the one time when they are first assigned.
I assume because the knobs go in turned far left it’s changing the settings.
I wonder if i should put faders in instead?
In just tried and after mapping the widget value was set to the value of the assigned parameter and not the opposite.
I do not understand this — as you can see in this gif, if I drag a new widget into a rackspace and map it to the transpose parameter of a MIDI In block, the widget is set to 0.5 (which is half way up) and represents a transpose amount of 0.
Ok. 2 things i might be doing different.
I have the widgets resized (if I’m duplicating them), if not i make them really small. This is before they are mapped to anything, and possibly already have settings changed in the midi in block before i do it.
Could you try that? As far as i can see this is happening every time i do it so it’s not a 1 off.
I’ll make a video tonight to show you.
I included a widget, resized it to very small, mapped => not issue.
Let’s address the base case first. Create a new MIDI In block and map a new widget to the transpose. What happens?
Thanks for the replies.
I’m at work at the moment so can’t try anything until later this evening. I’ll report back then and do a video if needed.
I’ll take note of all the steps etc.
i know i have successfully done this in the past, which i know i said it happens all the time in my previous post but that’s not true, but its at least once in each Rackspace, so there must be something in how im doing it that is triggering it.
Ive not be able to reproduce this in a way I can get a screen recording. I had the Transpose jump to -127 last night when adding a Transpose widget, but after deleting it and trying again with screen recording on it worked as expected.
Ill live with it, I know what to look out for if I find I suddenly have no sound after adding widgets.
What is a Transpose widget?
You mapped a widget to the transpose parameter of of MIDI in block?
Please re read the other posts to see what im doing. We went over this already.