Fantastic! Thank you very much… Can’t wait to try it out later…
Wow, what a great release! And ghost note editing has arrived in Ardour too! Considering that when I started using Ardour it didn’t support MIDI at all, it’s truly astonishing how recent work has turned it into the most MIDI feature-rich DAW in the open source world (at least in my opinion).
I’d like to thank all the developers for their enormous amount of work, but my special thanks go to @jean-emmanuel for fixing the grid/note drawing issue, and especially for 208769d78b. Until then, zooming the pianoroll with the mouse wheel was really difficult – now it works precisely as I would expect. Thanks!
If only 0010247 could be addressed in the near future, MIDI support in Ardour would be almost perfect…
I haven’t had chance to try it out yet, but does it support moving controller data with the selected MIDI notes?
Nope. That would be almost all the way to MPE, and I’d rather do MPE properly than half-assed. That requires a deeper architectural change in how Ardour thinks about notes.
#102047 has just been fixed.
Thanks!
Is the fix included in 9.5.11? Just did some quick tests and it doesn’t seem to work.
I think the fix was pushed after the nightly build was made.
According to the bug tracker it was fixed in commit 2f3a6f069d
And git describe --tags calls that commit “9.5-9-g2f3a6f069d”, so if the nightlies are using the same versioning it should supposedly have been in 9.5.11, aka 9.5-11-g7fad21d517.
Some aspects of MIDI chase are fixed by that commit. And in some scenarios, it will work 100%.
However @jean-emmanuel has pointed out to me some examples where it would not. I’m working on redesigning how this all works for MIDI CC and parameters to deal with those sorts of examples.
Thanks a lot for the updates! I’m a subscriber since 2023 (aprox) and this is getting better and better, I’m slowly drifting from Protools to Ardour, and hope to one day stop using/needing Protools.
![]()
Bottom panel is great addition also (i didn’t notice it in earlier versions).
That’s one thing i don’t use in other apps but in Ardour i definitely will. It’s handy.
Also, the fact that plugin parameters are presented as knobs/pots speaks to my old school mixer loving heart
. One wish - make the double-click return the knob to zero/neutral?
@paul , @x42
Also, i read somewhere online yesterday (youtube comment or description) that vertical scroll bar is coming up soon? Not a big deal, but it does make orientation in projects a little easier, at least to me, and sliding verticaly thru tracks just seems more elegant. Somehow, not sure why, i’m not a big fan of jumpy vertical movement we can do with mouse scroll wheel at the present moment.
Takes a while to break the Reaper muscle-memory but you do get used to Shift+Click in Ardour (and Ctrl+Shift+Click for individual channels in a group) ![]()
The vertical summary / scrollbar is already available in nightly builds if you want to give it a try (disabled by default, can be shown from the Display menu). No work has been done (yet ?) to add a smooth scrolling option.
Aaah, so we do have the shortcut for that…
…it’s just that i don’t know it
.
Hey, i just read the whole topic.
Good points there, i completely agree with you.
The thing i’d like to add is that i often actualy use half-tracks (if i understood correctly what bothers Robin @x42 ) in other apps …Here’s how - sometimes i just search for a quick waveform transient (loud kick hit, some blast sfx etc) and implement some automation or move regions on other tracks around, based on that info. In those cases i don’t have to see that whole track, just s tiny bit of it, basicaly, just a waveform peak. When doing that kind of intervention, especialy when using laptop (this again
) , seeing just a desired protion of a track is very useful to me.
So, it’s basicaly when i’m creating “manual” ducking or sidechaining using automation.
So… what’s that:
- [new branch] smooth_scroll → origin/smooth_scroll
???
It’s me having some time to kill before a concert ![]()
I suggest to find a better way to spend your time in between concerts then ![]()
The main reason is that halt track views don’t work well with control surfaces . The smallest banking increment is one track.