I have run into what seems like a *horrible* bug which is really impacting my workflow...
- When 'remote pad play' is set to 'beats' the Tempest switches beat even when in '16 Sounds' mode. I've tried restarting and the same thing happens. Switch 'remote pad play' mode back to 'sounds' and the problem doesn't occur. This could well make this beta unuseable for me.
Yes, that's how it is supposed to operate and how it's operated from the start. If you set Pad To Note Mode to Beats, incoming MIDI Note On messages will select Beats. I think you may be intending to set Pad To Note Mode to Follow Pad Func, which
follows the Pad Function. Hopefully this will be less horrible for you.
Also sync when switching beats via 'remote pad play' seems to be intermittently awful if 'pad hold' is switched on. It's like the whole beat starts a beat late or something. I can work round this but it never used to be a problem on the last official firmware.
When you say the beat starts late, which of the following are you saying?:
1) Tempest is not playing, then you remotely press a key on your external MIDI keyboard to start a beat. Tempest starts playing the beat about one 1/4 note after you press the key.
2) Tempest
is playing, then you remotely press a key on your external MIDI keyboard to change to a different beat. Tempest changes to the new beat late, perhaps by one 1/4 note.
If you are saying #2 above, is it possible that you had Beat Quantize set to 1/4 note? If so, this would result is the beat only changing on 1/4 note boundaries. If this is the problem, set Beat Quantize to Off and perhaps it will be less awful for you.
On a positive note, you have found a bug: In the System > MIDI Remote Pad Play screen, set Pad To Note Mode to Beats. Then in the 16 Beats / Pads screen, set Pad Hold (soft key) to On. Now press keys on the remote MIDI keyboard. Notice that pressing the key starts the beat, but releasing the key
does not stop the beat. Thank you for finding this bug.
Trying to stay positive with this machine because I love so much about it but this really seems like one step forward two steps back.
Thank you for trying to stay positive.
* edit *
OK - on further investigation this problem is intermittent. I'm not sure exactly what causes it but I seem to be able to get the Tempest to enter this buggy state reliably by switching beats remotely with 'pad hold' on. If I do this and then stop the sequencer the T enters this buggy state whereby hitting a pad in '16 sounds' mode also changes the beat. If I switch 'pad hold' off and restart the sequencer everything goes back to working as it should.
I was unable to reproduce the problem you're describing. If you are able to find a list of actions that if repeated will reproduce the problem, please post them here.
Also I notice that 'pad hold' seems to turn itself off if you switch from '16 beats' mode to '16 sounds' and back which I'm pretty sure shouldn't happen and didn't happen in v.1.4.
Yes, that is correct. Pad Hold mode is only available while in the 16 Beats / Pads screen. It has always been that way.