Midi Mapping doesn´t work with Akai LPK 25

[Jan09]

I tried to map a key of my LPK25 to a scene of Daslight. At the Midi Trigger Window it shows channel 1 number 72. At Daslight 3 & 2 it shows 0#72. With this versions it works. I tried to change the channel to 0 but i can not change it. I use Beta9. Midi mapping with the Behringer BCF200 is no problem.

[Jp]

Hi

Normally you shouldn't have to change the channel number as it's automatically detected.
Can you send a screenshot of the configuration ?
Do you know how your console works ? Like if it sends Note On 0/127, Note On/Off with velocity 127, if it sends data when press release or if it's more of a toggle ?
A screenshot of the midi watcher input would also be nice

Sorry we don't have this console at the office, only a BCF2000...

[Jan09]

I don´t know how the controller works. Here is an Screenshot of the Midi Watcher and the Midi learn Window. At the Midi Watcher i pressed the key only onces, but there are two commands.

[Jp]

Can you try by changing the Midi In Off value to 0 ? It's currently set to 127

[Jan09]

Like this ?

Midi learn.JPG (23.44 KiB) Viewed 28030 times

But it does not work. Or do I have to change something at the midi controller ?

[Jp]

My bad, wrong advice :/ ...
I'll double check tomorrow but if you specify "Note On" in midi in and use the other default settings (Trigger 127 and release 127) it should work

[Jan09]

This does not work. I think the fault is that it is channel 1. The Midi Watcher shows channel 0.
Tomorrow i will try with the new Beta.

[PolDavril]

Hi,

The MIDI channels are usually numbered from 1 to 16 in sequencers and keyboards. Inside the MIDI file, their corresponding numbering is 0 to 15. The Daslight4 MIDI watcher just displays the internal value 0 and it actually means channel 1 for the keyboard.

When a keyboard key is pressed, the keyboard sends a MIDI message "NOTE ON" with the channel, the key number and the velocity. MIDI keys are numbered from 0 to 255. The key number 0 is the first C note, usually the C0 (octave 0). Be aware that the "middle C" octave number may vary from one keyboard brand to another. It may be C4 (note number 48) or C5 (note number 60).

To trigger a scene, Daslight4 needs the exact velocity, to play a scene and to stop it. For example, if the scene is meant to be triggered with the note at velocity 100, the scene won't start with a velocity other than 100. Some keyboards have an option to disable the notes velocity. In that case, the keyboard always sends a velocity 127, whatever the speed the key is pressed.

This is the screen copy of a working example with a MIDI sequencer and a virtual MIDI cable.
Hope this helps.

MidiTrigger.jpg (226.44 KiB) Viewed 28015 times

[Jan09]

I understand the problem. But i find no option at the midi keyboard.
But why does it work with the old Daslight Versions and not with the new?

Edit:
Daslight always crahs when i mapped the midi keyboard to a scene. I couldn´t send the bug report (Error 301).

[Jp]

Can you send me your show by PM ? I'll see what I can do

Do you have files in the "crash" folder of your daslight install ? i'd like them as well...

[Jan09]

The crash file gets deleted when the crash reporter closes, but i saved the file But i can not send it because it says file size too large.

[Jan09]

Does still not work with the new Beta.

[Jan09]

Is there any possibility to get this Keyboard work with Daslight 4 ? I tried it with the official Version. But still the sam I can learn the Midi function, but in Live it does not work.

This Keyboard is very important for me. If it does not work with the Software i will have to look for a other software.

[Merkal]

Does everyone benefit from Proextender or it still not work with the new Beta.

Does it work now Jan?

[Jan09]

Yes it works with this settings. The red ones you have to change.

Daslight 4 LPK25 Midi.JPG (33.11 KiB) Viewed 27760 times