>
>
> If you don't need/use those settings, they can be removed
> by editing the Controllers for the Device:
>
This sounds exactly what I need. Excellent!
>There are definitely bugs WRT rewinding CCs. We just don't do that
> at all. The only way to reliably get what was in the sequence is
On 2/18/19 7:04 AM, Sami Jumppanen wrote:
2. Program change and CC (most notably pan and volume) are sent
sometimes even though not programmed into segments.
The Pan and Volume settings in the "Instrument Parameters" panel in
the left column will be sent at sequence load. They also may be
On 2/19/19 2:14 AM, Will Godfrey wrote:
To make this change would actually break known and accepted MIDI behaviour. I
would prefer it to stay as it is. Indeed with Yoshimi we actually make use of
a variation of this effect - initially after I realised you could make use of
it to set up drones
On Mon, 18 Feb 2019 22:21:37 -0500
"D. Michael McIntyre" wrote:
>On 02/18/2019 06:48 PM, Ted Felix wrote:
>
>> This is an interesting case. I've confirmed this. It's likely that
>> no one ever expected a user to do this. So, there's no extra code in rg
>> to send NOTE OFF events when the
On 02/18/2019 06:48 PM, Ted Felix wrote:
This is an interesting case. I've confirmed this. It's likely that
no one ever expected a user to do this. So, there's no extra code in rg
to send NOTE OFF events when the current track is switched.
I'm going off memory here, but I'm pretty sure
On 2/18/19 7:04 AM, Sami Jumppanen wrote:
1. Play MIDI keyboard through rg track and switch to another track - the
NOTE OFFs are lost (notes on the MIDI channel of the first track are
stuck ON).
This is an interesting case. I've confirmed this. It's likely that
no one ever expected a
Hello, everyone!
It's hard to form a user friendly subject, but the first word is the key:
I'm introducing myself to this list. Also joined the other lists (bugs,
dev).
Note: this post became quite long. At first there is a lot of background
info, not requesting feedback for those chapters. And
