Then create an insert in the master bus pre-fader and connect jamin’s ins and outs to it. This will make ardour run without much CPU and most of the DSP processing will be jamin’s. The idea is that since the songs are mixed down, you should not apply ANY effects to the tracks. Once you songs are mixed down, create a new ardour session, and import each wav files (one song per track for example).
Mixing down means that when you’re happy about your mix for a song, export it to a single stereo wav file. A good mix for all your songs is independent of the mastering process. There is no point to forcing one on people with a DAW.
The reasoning is the same as the one why Ardour doesn’t have a default EQ in its tracks, everyone will like a different sound, and might like different processors(As evidenced in part above). Jamin just provides a nice packaged interface that works pretty well.Īnd personally I don’t believe it is within the scope of Ardour to provide a mastering interface. There is other work I am doing, but it isn’t to improve it but rather to port it to OS X, however my work isn’t ready for public release yet until I fix at least one more rather annoying issue that I can’t find the cause of.Īll this being said, there is nothing saying you can’t use other things in your work. And while development of it is not speeding ahead, glancing through CVS some commits were done 5 months ago for example. You are correct in that the last tarball on their website was 0.95. The catch is that it is very difficult to get these ‘versions’ and you really have to do a CVS checkout and compile from there. I have release announcements for various versions of 0.97 in my mail, but I seem to recall 0.98 somewhere. For the record, Jamin has proceeded past the 0.95 tarball a LONG time ago.
0 kommentar(er)
