bcr2000 get value from d110

Pour tester un peu le concept, je me suis amusé à faire un profil pour le Nord Lead 2, c'est assez facile, pas trop de paramêtres.
Une fois programmé les CC sur les potars et boutons, il ne reste plus qu'à lui apprendre le sysex "all controlers request" du nl2, et l'associer à la fonction "learn".
Et là c'est magique.
Quand on selectionne le preset "nord lead 2" sur le BCR, il demande automatiquement les valeurs des CC au clavier, et immédiatement, l'ensemble des valeurs s'affichent sur les couronnes de led. On se retrouve avec l'interface du NL3
Si on change de patch sur le nl2, il suffit d'appuyer sur "Edit/learn" et hop on récupère le nouveau setup sur la BCR2000

[12] What do the Request checkbox and the ‘LEARN output’ tab in BC Manager’s Preset dialog box refer to?
If the current preset on the BC has its Request parameter set to on, the BC automatically sends the preset’s ‘LEARN output’ whenever you select that preset. If Request is off, the BC only sends this ‘LEARN output’ when you press EDIT + LEARN on the BC itself.
On the ‘LEARN output’ tab you can define a sequence of MIDI messages for each individual preset. You’re completely free as to the nature of these MIDI messages (although the total length is restricted to something like 125 bytes).
Probably Behringer’s original idea was that this LEARN data sent from the BC should be a request for settings getting sent back from the other device to the BC: hence the name ‘LEARN’, i.e. learned by the BC. However, that doesn’t have to happen: you can of course have the BC send anything, not necessarily triggering a MIDI response from the other device back to the BC. One obvious idea is to have the BC simply send a MIDI Program Change message indicating that the BC has indeed selected that preset. So e.g. for preset 1 you could define ‘$C0 $00’, for preset 2 ‘$C0 $01’, etc. Another application is the initialization of a receiving synthesizer or so.

this is the 'big ask' for the BC.
Unless the synth will output all its values in CC messages, the BC can't understand the data.

Usually the patch data is output as System Exclusive (sysex), and the definition of what is in the sysex message is up to the manufacturers of the synth, so there is no way Behringer could allow this for every synth out there.

The only way to do it is write a PC program that sits between the BC and the synth.