It’s a lot of work. I slightly enjoy it but boooooy is getting into audio and music pretty challenging. It’ll be good if I ever need to know what I’m talking about when working with others… in the future where I can dedicate myself full time to game dev… One day one day…
I don’t really have a point here. If anyone has any resources, tips, or recommendations on this subject let me know.
Edit: Congrats on the new 9.0 release!
Pablo Casals famously replied when asked why he was still practicing in his 70s that he "felt like we was making progress", so don't let yourself feel inadequate.
And he was like "people say 'even the music?' The music was the easiest part!!!'
It does make me feel like once you get into the right headspace and figure out how most of the tooling works all of this becomes quite smooth.
which I think is a lack of cast check in port_data_type? (from IOSelector::setup_ports -> PortMatrix::setup_global_ports )
I also got an assert in; #5 0x00000000011fa927 in StartupFSM::check_session_parameters (this=0x3dcf00a0, must_be_new=true) at ../gtk2_ardour/startup_fsm.cc:740 #6 0x00000000011f80d2 in StartupFSM::dialog_response_handler (this=0x3dcf00a0, response=-3, dialog_id=StartupFSM::NewSessionDialog) at ../gtk2_ardour/startup_fsm.cc:267
I think this was opening an existing ardour project that I'd copied onto this machine and was the first run of ardour on this machine.
However, following the tempo map is a very different challenge than following user-directed edits between warp markers, and neither RubberBand nor Staffpad really offer a good API for this.
In addition, the GUI side of this poses a lot of questions: do you regenerate waveforms on the fly to be accurate, or just use a GUI-only scaling of an existing waveform, to display things during the editing operation.
We would certainly like to do this, and have a pretty good idea of how to do it. The devil, as usual, is in the details, and there are rather a lot of them.
There's also the detail that having clips be bpm-synced addresses somewhere between 50% and 90% of user needs for audio warping, which reduces the priority for doing the human-edited workflow.
just use GUI scaling, and only IF the prior is too challenging
Zero crossings were an early myth in digital audio promulgated by people who didn't know enough.
Fades are always the best solution in terms of limiting distortion (though even then, they can fail in pathological situations).
I'm most excited to try the perceptual analizer, which was something I found always had disappointing performance in plugins.
Which of the new features would you say posed the most interesting engineering challenge?
I didn't want to replicate the code we already had for the Editor, and figuring out to refactor this took a lot of time and experimentation and failures. Although there are still some rough spots, in general I'm very happy with how things turned out.
Clip recording was also a bit of a challenge. It uses an entirely different mechanism than timeline recording, and as usual I got the basics working in a couple of days, followed by months of polishing (and likely, quite a few more to go as we get feedback from users).
analyzer. I think analizer has a different meaning.
(Cyclictest gives me between a 3x and 5x worst-case latency improvement depending on the background load, but I'm not nearly musically skilled enough to try a real-world test.)
We haven't really tested this sort of thing for quite a few years.
You can already load Cardinal as a plugin and get the full scope of is power(s) (or VCV Rack if you paid for the "pro" version). You just don't get the GUI "integrated" into Ardour, and its tied to a specific track.
We might do this via I/O plugins (an existing Ardour feature), which would make the inputs & outputs of Cardinal be just like your hardware. Lots of details to that sort of design, however.
There is also PlugData which could theoretically be handled in a similar way.
What we will not try to do is to implement Yet Another Software Modular Environment ourselves. Cardinal/Rack (or even PD) are approximately infinitely better than anything we could or would do.
document.querySelector("#content .section-header + p").className = "date"
document.querySelector("#content .date + p").outerHTML = (`
<p>
We are pleased to announce the release of Ardour 9.0.
</p>
<p style="font-style:italic; font-size:smaller; margin:2em
4em">Ardour is a free and open-source digital audio workstation
app that works cross-platform on Linux desktops, Mac OS, and
Windows. Get Ardour or get involved with the community at <a
href="https://ardour.org/">Ardour.org</a>.</p>
<p>
Ardour 9.0 is a major release for the project, seeing several
substantive new features that users have asked for over a long
period of time. Region FX, clip recording, a touch-sensitive
GUI, pianoroll windows, clip editing and more, not to mention
dozens of bug fixes, new MIDI binding maps, improved GUI
performance on macOS (for most)...
</p>
`)A couple friends and I started a band a couple months ago and we've started to use Ardour + a Behringer UMC1820 for some basic recording work; it's wild how quick we've been able to get up and running with it (to the point where our only limitation right now is scrounging up enough cables to hook up all our instruments to the UMC1820). Create tracks, pick each track's input, arm tracks for recording, hit record, hit play, and make noises. Our lead guitarist is more familiar with Cubase, but I had him try out Ardour and he's already putting together recordings; just had to point him to a couple manual pages and he was off to the races with it.
Curious to see how quick 9.0 will hit Ubuntu Studio (which is what we're using in our practice room). Cool to see Ardour finally get a dedicated piano roll window (presumably ported over from MixBus?); even though it's neat to be able to do MIDI editing directly from the main editor window, having the option to focus on a specific snippet will be handy. And the continued improvements with the new cue-based flow will be cool to play around with (and maybe work into live performances once we've got enough material down solid for shows?).
Things aren't often "ported over from Mixbus", though there are a few features that do start life there (the new perceptual analyzer is one good example).
The pianoroll stuff was started so that we could do clip editing. It appeared in Mixbus first because ... well, let's just say that there was some disagreement about when it was appropriate for that stuff to go public, and the release of Ardour 9.0 represents the ardour team's judgement on that :)
However, in recent years, we've added a lot of the stuff you need for "in the box composition" and many people do use it that way. There's (always) more to do, but it's fairly capable in this sort of workflow now too and will continue to improve over time.
Ardour has been around for more than 25 years.
Please be aware that almost any fully-capable DAW (everything named here except lmms) has a steep, challenging learning curve. Don't jump in thinking it will be easy.
But I’ve used Ardour a long time ago and I don’t see why you couldn’t release music with it. Another alternative is Reaper.
or you use a VST host like Kushview's Element and load up on all the free VST instruments and effects that are out there. you would just need a midi keyboard hooked to it then or use Cardinal to generate note patterns
or something like Orca if you want to go off the deep end!
[1] https://github.com/Ardour/ardour/tree/9.0/libs/tk/ytk
[2] https://mail.gnome.org/archives/gtk-list/2002-March/msg00136...
Implemented like any custom GTK+ 2 widget?
Off topic but is there a linux DAW which focuses on live loop recording? Something like what the LoopyPro app does on iOS ?
It's just an inline pianoroll, which is cool for ProTools and award winners like Olafur Arnalds, but apparently not good enough for everyone else.