16 levels pad light feature request

[SxnnyB]

Observed:

1. While in 16 levels
2. Pad light only lights up for source pad regardless of what pads were hit or recorded

Suggestion:
2. I think it would be helpful to show pad lights (velocity) for each pad/ note hit or recorded in 16 levels while in 16 levels for that sample/source pad.

While not in 16 levels the source pad could behave as it does currently to indicate all notes that were recorded for 16 levels on that pad.

[izzyreal]

Hi @SxnnyB, sorry for getting back so late about this feature. Let's refine it a bit more.

I think it would be helpful to show pad lights (velocity) for each pad/ note hit or recorded in 16 levels while in 16 levels for that sample/source pad.

Let's first describe what the current behaviour is in v0.4.4.

1. Start VMPC2000XL.
2. Enable 16 LEVELS with Note: 35/A01-(No sound) and Param:VELOCITY.
3. Any pad triggered via the computer keyboard results in PAD 1 lighting up.
4. The intensity of the light is derived from the pad number that was originally hit, pad 1 being lowest and pad 16 being highest intensity.
5. Disable 16 LEVELS.
6. Record some arbitrary pad hits between pad 2 and 16.
7. While the recorded sequence is playing we see the pads that were hit light up, all at max intensity.
8. What occurs in 7. occurs regardless of whether 16 LEVELS is enabled or not.
9. Enable 16 LEVELS and go to an empty sequence.
10. Record some pad hits.
11. When playing back the sequence, we see the same as what we see while recording it, which is the same as what we see when manually hitting those pads (see 3. and 4.).

At which point do you have some alternative behaviour in mind?

[SxnnyB]

It's been a while But I believe my intention was for 16 levels in pitch mode I use this on my hardware quite often. The velocity in pitch mode would not be locked to the same levels as in velocity mode, but instead is free unless full levels is also applied. It's been so long but I assume I was seeing the lights at locked velocity intervals on pitch mode for 16 levels and thought it should have the light response match user input. As in if they are clicking corner of pad it is soft and center of pad is full velocity.

…

On Wed, Sep 7, 2022, 3:14 PM Izmar Verhage ***@***.***> wrote: Hi @SxnnyB <https://github.com/SxnnyB>, sorry for getting back so late about this feature. Let's refine it a bit more. I think it would be helpful to show pad lights (velocity) for each pad/ note hit or recorded in 16 levels while in 16 levels for that sample/source pad. Let's first describe what the current behaviour is in v0.4.4. 1. Start VMPC2000XL. 2. Enable 16 LEVELS with Note: 35/A01-(No sound) and Param:VELOCITY. 3. Any pad triggered via the computer keyboard results in PAD 1 lighting up. 4. The intensity of the light is derived from the pad number, pad 1 being lowest and pad 16 being highest intensity. 5. Disable 16 LEVELS. 6. Record some arbitrary pad hits between pad 2 and 16. 7. While the recorded sequence is playing we see the pads that were hit light up, all at max intensity. 8. What occurs in 7. occurs regardless of whether 16 LEVELS is enabled or not. 9. Enable 16 LEVELS and go to an empty sequence. 10. Record some pad hits. 11. When playing back the sequence, we see the same as what we see while recording it, which is the same as what we see when manually hitting those pads (see 3. and 4.). At which point do you have some alternative behaviour in mind? — Reply to this email directly, view it on GitHub <#79 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASV5JBS56WAKCJ3BPJ4CWFDV5DSPZANCNFSM4XBQWNQQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[izzyreal]

By "pitch mode" do you mean Param:NOTE VAR with Type:TUNING? If yes, let's look at the current behaviour:

1. Start VMPC2000XL.
2. Enable 16 LEVELS with Note: 35/A01-(No sound), Param:NOTE VAR, Type:TUNING and Original key pad:4.
3. Any pad triggered via the computer keyboard results in PAD 1 lighting up.
4. The intensity of the light is constant.

When you say the below:

The velocity in pitch mode would not be locked to the same levels as in
velocity mode, but instead is free unless full levels is also applied.

do you mean that in 4. the light intensity should vary, with lower pad numbers resulting in lower light intensity and higher pad numbers in higher light intensity?

Or do you mean that different pads light up, matching the final pitch of the note number produced after 16 LEVELS processing has happened?

[SxnnyB]

Yes I mean in tuning mode with 16 pitched notes of the sample set across the 16 pads. Iirc the previous behavior was that pads lit up the same amount regardless of the input velocity. E.g. the velocity mapping you employ with mouse clicks of pads, from center of pad = most velcity to outer of pad = least velocity I'm specifically talking in terms of mouse presses on pads as opposed to key presses. This may have changed in later revisions of your app as I have not updated in some time.

…

On Thu, Sep 8, 2022, 2:32 AM Izmar Verhage ***@***.***> wrote: By "pitch mode" do you mean Param:NOTE VAR with Type:TUNING? If yes, let's look at the current behaviour: 1. Start VMPC2000XL. 2. Enable 16 LEVELS with Note: 35/A01-(No sound), Param:NOTE VAR, Type:TUNING and Original key pad:4. 3. Any pad triggered via the computer keyboard results in PAD 1 lighting up. 4. The intensity of the light is constant. When you say the below: The velocity in pitch mode would not be locked to the same levels as in velocity mode, but instead is free unless full levels is also applied. do you mean that in 4. the light intensity should vary, with lower pad numbers resulting in lower light intensity and higher pad numbers in higher light intensity? Or do you mean that different pads light up, matching the final pitch of the note number produced after 16 LEVELS processing has happened? — Reply to this email directly, view it on GitHub <#79 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASV5JBRGPADUJWP2RIXDMD3V5GB65ANCNFSM4XBQWNQQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[SxnnyB]

To further clarify, in note var: tuning Behavior I see as helpful would be the pad you hit regardless of its pad number, should light up matching the velocity level of the input velocity as in 16 levels note var: tuning allows you to input velocity per pad the light level per individual pad should reflect this velocity in that mode. And on playback the velocity light strength of notes could be played back on the single note when outside of 16 levels mode.

…

On Thu, Sep 8, 2022, 2:39 AM Carl Burns ***@***.***> wrote: Yes I mean in tuning mode with 16 pitched notes of the sample set across the 16 pads. Iirc the previous behavior was that pads lit up the same amount regardless of the input velocity. E.g. the velocity mapping you employ with mouse clicks of pads, from center of pad = most velcity to outer of pad = least velocity I'm specifically talking in terms of mouse presses on pads as opposed to key presses. This may have changed in later revisions of your app as I have not updated in some time. On Thu, Sep 8, 2022, 2:32 AM Izmar Verhage ***@***.***> wrote: > By "pitch mode" do you mean Param:NOTE VAR with Type:TUNING? If yes, > let's look at the current behaviour: > > 1. Start VMPC2000XL. > 2. Enable 16 LEVELS with Note: 35/A01-(No sound), Param:NOTE VAR, > Type:TUNING and Original key pad:4. > 3. Any pad triggered via the computer keyboard results in PAD 1 > lighting up. > 4. The intensity of the light is constant. > > When you say the below: > > The velocity in pitch mode would not be locked to the same levels as in > velocity mode, but instead is free unless full levels is also applied. > > do you mean that in 4. the light intensity should vary, with lower pad > numbers resulting in lower light intensity and higher pad numbers in higher > light intensity? > > Or do you mean that different pads light up, matching the final pitch of > the note number produced after 16 LEVELS processing has happened? > > — > Reply to this email directly, view it on GitHub > <#79 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/ASV5JBRGPADUJWP2RIXDMD3V5GB65ANCNFSM4XBQWNQQ> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[izzyreal]

I'm having trouble understanding what feature you have in mind.

It would be helpful if you use the numbered steps from #79 (comment) as a template and describe what you have in mind those terms.

Please start the latest version of VMPC2000XL (v0.4.4) and create a step-by-step description of what is currently happening in the process where your feature suggestion would come into play. Once you have that list of steps of current behaviour, tell me what improvement you have in mind by saying for example "In step 8 I actually want this and that to happen".

[SxnnyB]

2. While in 16 levels tuning mode specifically. 7. Visual reference (light strength) should match input velocity for individual 16 levels pads while in 16 levels tuning mode, as the audio would play at different velocity input levels when using mouse input on pads. Irl In 16 levels tuning, regardless of the pad number you hit, you still have velocity control by how much pressure is applied to pad. I would expect this pressure to be represented for the note/pad that is input while in this mode. So imagine c#3 was pressed at 50% pressure/velocity it would light up 50% 16 levels Velocity mode splits velocity between 16 pads but with 16 levels tuning mode, input velocity is still user input, so this should be reflected In the playback visually while in this mode instead of just a solid visual light level.

…

On Thu, Sep 8, 2022, 3:16 AM Izmar Verhage ***@***.***> wrote: I'm having trouble understanding what feature you have in mind. It would be helpful if you use the numbered steps from #79 (comment) <#79 (comment)> as a template and describe what you have in mind those terms. Please start the latest version of VMPC2000XL and create a step-by-step description of what is currently happening in the process where your feature suggestion would come into play. Once you have that list of steps of current behaviour, tell me what improvement you have in mind by saying for example "In step 8 I actually want this and that to happen". — Reply to this email directly, view it on GitHub <#79 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASV5JBQRK5Q2LMRXQVM46V3V5GHFJANCNFSM4XBQWNQQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[izzyreal]

Which version of VMPC2000XL are you using?

I've replaced 2. and 7. and added some questions to 4. and 7. The rest is the same.

1. Start VMPC2000XL.
2. Enable 16 LEVELS with Note: 35/A01-(No sound), Param: NOTE VAR and Type: TUNING.
3. Any pad triggered via the computer keyboard results in PAD 1 lighting up.
4. The intensity of the light is derived from the pad number that was originally hit, pad 1 being lowest and pad 16 being highest intensity. Where should the intensity of the light be derived from?
5. Disable 16 LEVELS.
6. Record some arbitrary pad hits between pad 2 and 16.

Visual reference (light strength) should match input velocity for individual 16 levels pads while in 16 levels tuning mode, as the audio would play at different velocity input levels when using mouse input on pads.
I don't understand what you mean by "should match input velocity for individual 16 levels pads while in 16 levels tuning mode".

Currently:
a. The pad that is associated with the note number that is assigned in the sixteen levels screen lights up according to velocity. No other pads light up, and that is by design.
b. If you play it with the computer keyboard it's max intensity because velocity is 127.
c. If you play it with the mouse it varies the velocity and therefor the light intensity.
d. If a note event that was recorded is played back, it lights up according to the velocity of the note event.

Which of these aspects would you like to see differently?

8. What occurs in 7. occurs regardless of whether 16 LEVELS is enabled or not.
9. Enable 16 LEVELS and go to an empty sequence.
10. Record some pad hits.
11. When playing back the sequence, we see the same as what we see while recording it, which is the same as what we see when manually hitting those pads (see 3. and 4.).

Irl In 16 levels tuning, regardless of the pad number you hit, you still
have velocity control by how much pressure is applied to pad.

Yes, VMPC2000XL has that as well (if I understand what you mean correctly).

I would expect this pressure to be represented for the note/pad that is input while in this mode. So imagine c#3 was pressed at 50% pressure/velocity it would light up 50%

Ok, so it's aspect 7a from above that you would like to see differently? If that's the case, I'm not sure yet. The original idea behind the pad lighting up is not that you can see which pad you pressed, but which sound is being played. The user typically already knows which pad he/she pressed.

16 levels Velocity mode splits velocity between 16 pads but with 16 levels tuning mode, input velocity is still user input, so this should be reflected In the playback visually while in this mode instead of just a solid visual light level.

I don't know what you mean by this. It sounds like you're saying that when you're in 16 levels tuning mode you get no visual feedback regarding velocity, but I am not able to confirm that. In v0.4.4 the behaviour is like I've described above in 7. So at least with mouse, keyboard and playing back the light intensity represents velocity. I'm not aware of a "solid visual light level", if by that you mean that the light intensity is always maxed out.

[izzyreal]

I just realise there's a small chance that if you're running v0.4.4, it may not be the latest version. I released another v0.4.4 like the next day, and it may contain changes related to this feature, so just to be sure you could download and reinstall v0.4.4.

[izzyreal]

Please check functionality in https://izmar.nl/release-candidates. Will close this issue for now, please open a new ticket if any pad light behaviour still needs to be addressed. Thanks!