Re: Bad visual feedback for KORG nanoKONTROL 2

Len Ovens <[email protected]> writes:

> On Sat, 26 Aug 2017, David Kastrup wrote:
>
>> So it would seem that the uri-style controls echo their state back
>> into the nanoKONTROL2 while the function/action style controls don't.
>
> Menu action commands will never give feedback. In general they tell
> the GUI to do something.

For me as a user, that's gobbledygook in the first approximation.  It is
not clear what makes the uri-style declarations different from the
function/action style declarations here.

But then I am not on the user list, and we are talking about things that
a user is not expected to be changing routinely even though there is
some basic-level documentation (without bothering about such
explanations as you give) there.

So let's skip over how to make the documentation relay this kind of
information better for now.

Instead let's focus on the task.  It seems to work on the uri-style
declarations for some reason (including when their state is changed
using the mouse rather than the controller itself), so either we want
uri-style equivalents for the GUI commands.

_Or_ we want separate ways to declare how changes of Ardour's state
(affected by the GUI commands or other means) might get relayed back to
a controller.  That would require us to add additional lines to the Midi
maps, for output from Ardour to the controller.

>> In a nutshell:
>>
>> a) advice at the top of the midimap file(s) is bad.  The only change
>> that's actually warranted over the default is switching LED control
>> to external instead of internal
>
> Feel free to create a better map and submit it as a pr on github.

This is just a change in the comment.  I assume that I can submit
patches to the list when not having a Github account.

> I do not know if it is better to leave the current map alone and
> create a new one, or fix the one that is there. I would test it well
> though.

As long as we are only talking about fixing the comments, I don't see
the point in creating a new map.

>> b) channel controls S/M/R are not lit initially when a session with
>> set controls is loaded
>
> Do you know if they light when banked?

First I'd need to know what it means to have the channel controls
banked.

>> Now for having the computer (and its rotating disk and fan) in a
>> different room and just taking the nanoKONTROL2 in the recording
>> room, not getting visual feedback for the "PLAY" and "REC" buttons is
>> awkward.
>>
>> Any chance someone will change this given suitable feedback/info, or at
>> least good pointers at what would need changing here?  I can submit a
>> patch for a) but am somewhat without a clue for the rest.
>
> There is already a bug filed for c):
> http://tracker.ardour.org/view.php?id=7288

Ah, ok.  I was not aware that this was a general shortcoming.  I thought
I remembered that this was different with some Mackie Surface emulation
mode of the Korg nanoKONTROL2, but it's been some time since I tried
that and it might just have been a toggle with LED control independent
of Ardour.

> But I am not aware of one for B) at this time. If you are filing one,
> please see if banking has the same problem.

What would banking look like?

Thanks

-- 
David Kastrup