ardour3

I wasn’t sure where to put this quick note, so i’ll start here.

After some small adventures, i got ardour3 compiled and working from svn.
Seems to work ok, with the odd crash (to be expected at the bleeding edge)
and, to my delight, the midi is really taking shape. I’m impressed with the design and layout, and to have inline editing is a wonderful bonus. Congratulations to all concerned with getting this done. Inline editing has always been a bit of a holy grail for midi users, and it’s a large irony that you chaps at Ardour are starting with this, where other programme developers have been noticeably reluctant to even consider this at any stage (Something that continues to mystify me).
It’s important for extensive midi input, and you chaps get a big thumbs up from me for implementing this.
Next, the layout is simple and easy to follow, and now i have my head around the Ardour routing paradigm, the midi is consistent with the Ardour paradigm.

Some observations, and i keep in mind this is a bleeding edge scenario:

By default, the midi track seems to treat middle C as C5. Is this intentional? Can we change this at user level?
From my perspective, the design is just about spot on. I put in my two roubles worth, and ask you don’t change it, however, is it feasible to introduce one more step in the track size parameters? We have up to largest, but i’m wondering if a ‘megalarge’ setting might be useful, particularly when editing or building up complex chords in midi.

Is there some sort of snap to grid setting for the midi? I quickly drew a few notes in, but couldn’t find a setting to snap them to grid.

I get this error message in the ardour3 log:

[ERROR]: JACK: jack_set_sample_rate_callback: deprecated
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_in
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_in
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_out
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_in
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_out
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_in
[ERROR]: JACK: JackActivationCount::Signal value = 0 ref = 4
[ERROR]: JACK: JackActivationCount::Signal value = 0 ref = 4
[ERROR]: JACK: JackActivationCount::Signal value = 0 ref = 4
[ERROR]: JACK: JackActivationCount::Signal value = 0 ref = 4
[ERROR]: JACK: JackActivationCount::Signal value = 0 ref = 4
[ERROR]: JACK: JackActivationCount::Signal value = 0 ref = 4
[ERROR]: JACK: JackActivationCount::Signal value = 0 ref = 4
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_out
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_in
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_out
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_in
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_out
[ERROR]: AudioEngine: cannot connect system:midi_capture_2 (system:midi_capture_2) to Midi 1/midi_in (ardour:Midi 1/midi_in)
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_in
[ERROR]: AudioEngine: cannot connect Midi 1/midi_out (ardour:Midi 1/midi_out) to system:midi_playback_1 (system:midi_playback_1)
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_out
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_in
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_out
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_in
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_out
[ERROR]: JACK: Unknown destination port port_name = Midi 1/midi_in

As a reasonably new linux user, i’m not sure if this is jack settings (I’m using jackdmp 0.70 and qjackctl), or a failure of recognition in ardour3 somewhere. I’ve posted this log readout for you chaps in case it’s the latter.

There are some squashed up letters in the edit boxes for a midi track, but i gather this is some sort of drawing challenge by my computer.

So far so good, and i’m impressed with the work you fellas are doing.
The midi setup is excellent (imho) for a speedy workflow, and that’s my chief concern in all this.

Thanks!

Alex.

Ok, further testing. (I’m using Fons’s Aeolus organ for this)
In the midi track meter, there is a sign of activity. Good so far. But when a particular region has played, and i’ve stopped Ardour, the meter continues to show activity for a short time afterwards, and sometimes in short bursts, when nothing is happening. (Between 2-3 seconds.)
Is this ok, or some sort of residual notes off, or sysex data function?

I got this as well, in command line:
WARNING: MidiModel::end_write: Channel 0 has 1 stuck notes
SMF Source path: /home/alex/midi test 2/interchange/midi test 2/midifiles/Midi 1-3.mid
Adding 1 to region list
Adding 1 to region list

Alex.