I have Alesis v25 midi and I am trying to set up som shortcuts for make my life easier but it seems that it does not works properly. I did make it work once but now it does not working and I can not understand why.So,
I connect the midi to my laptop and I start ardour. I create a new session wit this settings:
I read that to create a shortcut I have to press Ctrl+middle mouse click then a Operete controller now is showing up and then I press the knob or the button that I want to control.
In my case it seems that there is not any input.
I checked the MIDI tracer to see if ardour get the signal and it seems that does not get anything.
(But If I create a track and connect it to MIDI throw MIDI input it works fine)
Thank you for your help my friend!
I went to the new session window -> clicked to the MIDI system and selected the ALSA sequencer
and then I clicked to the MIDI device Setup and I saw my MIDI keyboard.
For some reason I have 2 midi interfaces but only the first one is working. I do not know the use of the other.
And then I had to set up the connections like this:
^Select âMusic Dataâ for the first row, âControl Dataâ for the second.
Uncheck âV25 MIDI 1(In)â and select the one just below it.
^ Go to Preferences/âControl Surfacesâ â try the âGeneric MIDIâ surface definition, and choose the âV25 MIDI 2(In)â in the âShow Protocols Settingsâ.
(the following is a screenshot of how this looks like on another system)
When you do "ctrl+middle-mouse-buttonâ on a bindable/Midi-learn control on the daw, such as the âplayâ or âstopâ button, you can set things⌠by turning a âcontrolâ from the Midi controller (your hardware keyboard). If Midi-learning does not work with the chosen âcontrol surfaceâ protocol, then try the âMackie Controlâ control surface controller instead. (from the Preferences/âControl Surfacesâ window)
Youâre using âV25 MIDI 1(In)â for sending midi notes â and this midi input always goes to the track⌠so avoid binding it as a âcontrol surfaceâ.( if youâve got âV25 MIDI 1(In)â set as a âcontrol surfaceâ then you will no longer be able to send notes from it.)
âŚ
Those two things that show up as Hardware devices, those are referred to as âhardware midi portsâ.
From what I understand the âGeneric MIDI Control inâ pertains to the Ardour program as a whole â and relates to the âcontrol surfaceâ << this is a fancy name that translates easily to âMidi Controllerâ⌠just consider the two equivalent for now, itâs easier to understand it as an âexternalâ piece of midi equipment.
The problem here with âcontrol surfaceâ settings, is that the âMidi Connectionsâ window defines the settings better in a particular fashion that should be noted since it was opened â if you happen to âchangeâ the âcontrol surfaceâ from there â for example set all hardware midi ports, and then go to âPreferences/Surface Controlâ, choose protocol, then choose âShow protocol settingsâ ⌠the âpulldownâ of one option(from the Preferences window) is not âresettingâ and âunselectingâ options that have been set from the âMidi connectionsâ window.
^ So if you did this, then verify everything looks correctly from the âMidi connectionsâ window and make sure there is only one âcontrol surfaceâ hardware midi port selected. I always wondered where I can set more than one âsurface controlâ midi port, and apparently I didnât know the two places of Preferences and âMidi connectionsâ window here are related.
hope this helps (and see the later notes)
perhaps this area of Ardour can be enhanced
@x42 I think I also spotted a bug in the Midi connections â Iâm not 100% sure it is a bug,
âMIDI Control inâ becomes âGeneral MIDI Control inâ after another âsurface controllerâ is added from the Preferences/âControl surfacesâ⌠this makes it a bit difficult to keep track of where settings are related.
The other, as described previously, is there is not a full reset of âcontrol surfaceâ selections when using Preferences/âControl surfacesâ. The Preferences/âControl surfacesâ+âShow protocol settingsâ pulldown is not intuitive because it does not âunselectâ other possible things from the âMidi connectionsâ window.
⌠I just tested Ardour 6.0.pre0.2488 here with Linux 64-bit, and the I think it is a bug, because
I can select these two items in the âMidi connectionsâ window.
(selected both âKeystation 88 Midi 1â and âKeystation 88 Midi 2â in this window)
If I now choose either âKeystation 88 Midi 1â or âKeystation 88 Midi 2â from the Preferences/âcontrol surfaceâ+âShow protocol settingsâ, the âMidi Connectionsâ window whether it is closed or open, never reveals an update from the selection from the Preferences window.
However if I choose âdisconnectedâ from the Preferences window, the âMidi connectionsâ window gets updated showing no selection hardware midi input devices, as shown in the following screenshot.
^ So I suppose it is a bug â if my release of Ardour6 is out-dated and this has been fixed or improved in some way then I guess thereâs nothing more to report.
Iâm too new to Ardour to know if this is a bug, it is also difficult to explain these things without pictures, so I think it might be easier that I post about it here.
^ also it helps to illustrate that if this is a feature, then it is rather pretty confusing.
Essentially the user can lose the ability to send Midi notes to a midi track, because the âpulldownâ menu is not updating things correctly imho.
If this is a bug, then I suppose the solution here is that as a workaround the user needs to choose âDisconnectedâ first, then choose a hardware midi input device.
))
thanks. I think I am learning something in the process here, discourse provides the ability to enhance paragraphing things, so Iâll try out one its nice features of summarization.
Further notes â separated because I do not want it to sound too confusing above^, expand the following summary notation for extra tips which should solve the problem I think @joynstar is going after. I never tested the following because I do not have âthat hardwareâ but I am pretty sure it is the solution that is being sought because it looks like a simple Midi Controller, and so it shouldnât be too difficult to resolve the MIDI-Learn/binding issue. (âMIDI shortcutsâ is a misnomer â actually the request pertains as âMIDI Learningâ because âcontrolsâ from the âMidi controllerâ get binded to âcontrols inside the dawâ << easy vocabulary â if someone knows a better to phrase it, let me know⌠I think I got this right.)
Mapping CC-* numbers for the Alesis v25 "PADS"
Tracks also have their own âMidi port I/Oâ portsâŚ
eg: the Midi port I/O for MyMidiTrack, is named âMyMidiTrack inâ and âMyMidiTrack outâ â as these are like âslotsâ but theyâre really just called âtrack midi portsâ as they belong to the track.
( see also about âtrackâs outputsâ â Ardour just says âtrackâs output portsâ as the ports can be either âaudioâ or âmidiâ types. I call it track midi ports here just to make it easier to explain how midi ports actually exist for a midi track. The midi ports are either âinputâ or âoutputâ and belong to a âtrackâ. )
(these screenshots are not from your setup, and are just demonstration purposes)
^ Notice that you can select/bind a MIDI input source from the pull-down above the plugin list. I am not able to select the hardware midi port that is binded as a âcontrol surfaceâ.
Here, even though the âMyMidiTrack inâ is âbindedâ to listen to MIDI notes from âKeystation 88 MIDI 1â, I donât think messages from the âcontrol surfaceâ can reach into MIDI-Learning for plugins. << if I am wrong on this, someone can correct me⌠Here I can send CC- messages from the note-sending hardware midi port.
The Alesis V25âs documentation mentions that the âPADSâ generate CC-* messages. With the MIDI Tracer window from Window/Midi_Tracer menu (details about in manual here), it should show the CC- number right after the channel number â note: if it shows it in hex, then you probably just want to use something like kmidimon or gmidimon to see it in human decimal.
With Note-sending hardware midi input port âV25 MIDI 1(In)â connected to a track, and having test what the CC-* number is for each PAD button, you can then use the following plugin to grab the specific CC-* number message and transform that into a âMidi noteâ message that the sitting âsynth pluginâ only understands. The name of this plugin is called "MIDI CC to Note", and it comes with Ardour.
^ It looks pretty intuitive, and I suppose the setting to use is
âAll keys, key = parameter, velocity= CC-valueâ for the Operation mode,
CC Parameter to intercept: use the human âdecimalâ value of the traced MIDI CC-* message over here.
Key (midi-note) to use with fixed-key mode: â this one is pretty obvious, and represents 128 possible notes from 0 to 127. C-4 is the âmiddle C keyââŚ
note: The lowest keys are âLETTER-1â, so it is âC-1â (represents MIDI note-on value â0â), one octave up becomes âC0â(value â12â), then âC1â(value â24â), âŚG9 as the highest note which is MIDI note-on value â127â.
The lowest MIDI note value is numerically always â0â to â127â, representing 128 notes.
Some synth plugins exhibit a âvirtual keyboardâ and represent the âlowestâ numerical MIDI note not the same as Ardourâs pianoroll of âC-1â but something as âC0â. This makes the highest C- key become âC10â to represent the value 120. The highest note is never altered and always is Note-on value â127â, but it is symbolically represented as G10 by the pluginâs virtual keyboard which in turn plays G9 on the pianoroll â both G10(in plugin) and G9(piano-roll) symbolic labels here play the same âMIDI valueâ of â127â for the note-on message. There can never be a note-on value beyond 127, or below 0, so just to be clear on that.
⌠if ever in doubt, the user just has to look at the piano-roll on the track and see which piano key is lighting up. This is not difficult or a âbig dealâ to keep a reminder on, just something to be aware of as this is not very well explained. The minimum/maximum for the âMIDIâ note values is always â0â and â127â, so whatever the âsymbolicâ starting/ending labels a plugin can display its virtual keyboard, the user just has to look at the piano-roll and see if the âlowestâ possible play-note is matching to the same as the pianoroll.
^ Why is this being mentioned. Itâs because the âMIDI CC to Noteâ is using the symbolic-convention used as Ardourâs pianoroll. If you expect âC0â in the synth plugin to represent value â12â but you find out it isnât, youâll understand why thereâs a difference in the mismatch of âMIDI note-onâ values being passed. This is not obvious for starters, and this took me a little while to realize after trying out dozens of plugins⌠Thereâs at least a couple that provide virtual keyboards that do not share the same symbolic labels as Ardourâs pianoroll. At first it seems confusing, so if ever in doubt, one just has to look at the âpianorollâ to see if âC0â in the synth pluginâs virtual keyboard is âlighting upâ the C0 play-key on the pianoroll and it is easy to determine later what âsymbolic valueâ needs to be set in the âMIDI CC to Noteâ plugin.
When placing the âMIDI CC to Noteâ, it should be placed above(âpriorâ), the synth plugin that is receiving the incoming MIDI notes. The order of plugins is important as the signal-routing starts from the top as âearlierâ passing the signal down as âlaterâ.
If you havenât yet picked up, the âred linesâ represent âMIDIâ input, and the âgreen linesâ represent âaudioâ. You can read up about this color coding scheme from over here,
The processor box is where the effects are added. By default, one effect is always present: the Fader (see below). The effects can be added pre -fader and appear in brown, or post -fader, where they will appear in dark green. The signal flow is represented by lines, red for the MIDI and green for the audio.
))
@x42 , the reason why I add commentaries that are lengthy is so that other users can correct me as I am learning things. I am pretty sure thereâs something very weird going on between the Midi connections even into the Ardour6-prealpha â and we are not yet able to send bugtracking reports about it yet â however this issue is also found in Ardour 5.xx â I donât think itâs a âdesignâ, I think itâs somewhere between feature and bug, Iâm too new to Ardour to know really what the âintentionâ is. However when I choose âdisconnectedâ as I illustrated, then the Midi connections gets fully updated as expected. < Design or bug? Iâm wondering if I can make a feature request for this into Ardour6 prealpha â if this is already resolved in the upcoming release then I suppose I would be eager to try it out.
hope this is helps someone who is wondering how to map similar hardware devices that send the CC-*
@joynstar, also if you check the manual of the Alesis v25, it mentions it sends CC-* things. I suppose that means it sends it with "V25 MIDI 1(In)â. Midi is very versatile, I think you would want to use the âMidi Input follows Midi Track selectionâ as I mentioned I think on your other topic for the same hardware Problem with midi sound
â your hardware is connected via usb, and there is more than 1 midi port from it. 1 is for note-on data(with some CC-* messages), the other is for the âcontrol surfaceâ. From memory, you cannot service a hardware midi port as both a âcontrol surfaceâ and as a midi note-on port. â afaict this is not possible.
â I hope the illustration of the âMIDI CC to Noteâ helps solve the issue of not requiring an advanced MIDI-Learning plugin, instead you can use any digital synth along with it.
Easier said than done, but I also think thereâs a possibility that there might even be a bug here â and I think @joynstar youâre attempting things caught within this potential bug/feature that wonât resolve on its own::: the workaround for now afaict is to select âDisconnectedâ, and then choose a hardware midi input source in Preferences/'Control surfaces'+protocol+"Show protocol settings" (see above pictures)