I am trying to integrate three programs, each of them with a different purpose:
MuseScore -> Score writing, exports to *.mid (could also be something like SuperCollider which generates music algorithmically)
Qtractor -> Renders *.mid with LV2 plugins and automation to *.wav
Ardour -> Arrangement, mixing and mastering of *.wav files
That's the *NIX philosophy for ya! But I have a problem setting up this workflow because Qtractor does not have a CLI to easily render a single MIDI track to a .wav file.
This would be my ideal workflow (suggestions and critiques welcome, of course).
Let's say I made a .mid file with MuseScore (or SuperCollider, or hardware, or really any program capable of generating MIDI). I run:
qtractor -i bass.mid -o bass
And it automatically creates a Qtractor session bass.qtr with a single MIDI track called bass which imports the clip bass.mid.
I can then edit the session, put synths and automation in it, then run:
qtractor bass.qtr --render 1 bass.wav
Here 1 can be optional and refers to the first track, and if omitted Qtractor renders the whole track.
I can then use the exported .wav elsewhere (e.g. in Audacity or Ardour).
I think this kind of workflow goes well with @rncbc statements that Qtractor is first and foremost a MIDI sequencer more than it is a DAW, and instead of just improving Qtractor it improves free software music production as a whole, since it gives more flexibility.
Hello,
I am trying to integrate three programs, each of them with a different purpose:
*.mid(could also be something like SuperCollider which generates music algorithmically)*.midwith LV2 plugins and automation to*.wav*.wavfilesThat's the *NIX philosophy for ya! But I have a problem setting up this workflow because Qtractor does not have a CLI to easily render a single MIDI track to a .wav file.
This would be my ideal workflow (suggestions and critiques welcome, of course).
Let's say I made a .mid file with MuseScore (or SuperCollider, or hardware, or really any program capable of generating MIDI). I run:
qtractor -i bass.mid -o bassAnd it automatically creates a Qtractor session
bass.qtrwith a single MIDI track calledbasswhich imports the clipbass.mid.I can then edit the session, put synths and automation in it, then run:
qtractor bass.qtr --render 1 bass.wavHere
1can be optional and refers to the first track, and if omitted Qtractor renders the whole track.I can then use the exported
.wavelsewhere (e.g. in Audacity or Ardour).I think this kind of workflow goes well with @rncbc statements that Qtractor is first and foremost a MIDI sequencer more than it is a DAW, and instead of just improving Qtractor it improves free software music production as a whole, since it gives more flexibility.