Do you remember what type of widget you used?
It’s a round green knob. I tend to use the Yellow ones for note limits and the green one for transpose. These are just so I have widgets, I don actually interact with them.
Sometimes (most of the time) I’ll just select the 3 that are already in use and duplicate them and assign them to a different Midi in block (I always use Omni). If it’s in a rack space that hasn’t already got them ill drag them over to it from the list on the left in edit mode.
I can post a screen shot tonight but I can’t force it to happen until it does if that makes sense.
This just happened again.
I have a backspace with widgets that aren’t assigned to anything. I have two soft synths in it.
I decided i needed a split and transpose on one of the existing synths so selected 3 knob widgets and assigned them to this midi in block. The result was a -1276 transpose and high and low note limit’s were set to C1.
I tried again and it works fine. I can’t reproduce it purposely. It’s not the order or how im doing it, it’s random.
I don’t know if this answers your question (at all), but when I first tried to transpose using a widget connected to the midi in block, I had a tough time.
I then switched to just created a 2nd MIDI In block. That worked fine, but was a bit unwieldy.
With the newest version of GP use MIDI Transposer. So easy, even I can to it!
Jeff
What version of GP?
We are about to release a new update but if this is something that can be easily addressed, it would be good to know how to reproduce.
That said, I’m not sure why nobody else has ever encountered this issue.
Can you write detailed step by step instructions when this is likely to happen according to your observations?
I’d like to see if I can reproduce the issue.
I’m on 5.0.9. Mac Sonoma 14.6.1
I can’t write a step by step guide as I went back and tried to do it and I couldn’t get it to happen. If I can reproduce it intentionally I will of course make a note of the steps, but it seems random, other than it only happens when I first assign a Widget to each of the functions listed above, and the mini in block will already have a transpose or key limit in place.
In fact all 3 happen together, even if one or two dont have a limit set beforehand.its never just one on its own.
As I think ive said above, it’s not a big deal, I know what to look for if a sound stops working, but wanted to share my experience. Ive got most of my Rackspaces sorted so Im not making new ones each day.
Ok. It just happened again and I have a screen recording of it.
I think the issue might be to do with changing variations.
The video shows me being a bit incisive as I couldn’t remember what I was going to do, so apologies but if you skip to near the end, and keep an eye on Strings 1.
I said before it was chaining to C1 but its C-2.
Not sure if that video link is working on here. Its playing ok from Dropbox.
“Dropbox”
Well, it kind of is — you might know how to deal with it but if this is happening to other people, there might be significant confusion.
Can you export the rackspace where this is happening and upload it?
I notice from that video that they are all MIDI In OMNI blocks. Not saying it has anything to do with the issue, but that’s probably not a good idea.
I can reproduce a version of this simply.
-
Add a dial widget
-
Assign the dial widget to the Transpose, Min Note, or Max note parameter (though it can be any parameter) of the MIDI In Omni Block
The dial should on be on 5 (Transpose = 0)
- Exit Edit mode
- Double click on the dial widget
The dial turns to 0 (Transpose = -127)
EDIT: this only has to do with double clicking a dial widget when in non-Edit mode. Even when its assigned to nothing, double clicking sets the widget to 0.
Of course it does - that’s working as designed. The default value for double-click is set to 0.
If you set it to 50 then double-clicking will set the transpose to 0
What am I missing?
Right, I see that now.’
@Dave_bass5 I’m seeing in the video that just before the Transpose goes to -127, .you switched variations. Are those dial widgets set up to go to 0 in that variation?
This is the rackspace from the video. I only started this today so my earlier reports weren’t based on this one. I’ve added a few things since the video. There are a few things that need tidying up so it’s one I’ll be using as is. It’s a work in progress.
I was not double clicking on any of the widgets.
Mercy.rackspace (1.1 MB)
Can I ask why its not a good idea to use Omni?
Im only using one keyboard at a time, there is no other controller other than my Boss BT footswtich.
With my set up I can’t see me running in to any issues, but happy to be educated.
It’s fine if you only have one controller — and there wouldn’t be any interference.
Is your Boss BT connected to keyboard or is it on its own port? If the latter, then in fact you should actually use individual devices so you can control the flow better although if you always use those two together, you may not care.
Ah yes, you might be on to something. I haven’t changed any of the default settings for the widgets, although i assumed they would just follow whatever was set in the midi in block.
1 Like
Thanks. the footswitch is connected to the MacBook using Bluetooth.
Ive only been using GP for a couple of months, and I appreciate im not using it as a more seasoned user would, still very much learning, but as I progress im not going back to older backspaces to tidy them up at the moment. one day ill go and unify thing, but at the moment the priority is getting all the songs up and running.
1 Like