re. How complex would it be...
Hi again, Rui:
As I indicated, Qtractor can do the job, but it's not very intuitive to find the way. Qtractor is like that in some ways, but the rest more than makes up for it. I don't plan on changing DAWs. :)
Thanks for the reply.
re. Switch velocity off in your software instrument
Hi Bluebell:
The point here is being able to process/generate the signal before recording without relying on external tools so that everything is configured in the session/template.
There are many reasons: filtering, arpeggiators, pattern sequencers, virtual keyboards. In these cases, I want to be able to take advantage of the automation of these plugins, but also be able to edit and customize the recorded result.
In other DAWs, the way to do this is to put a plugin on the input bus. In Qtractor, you can do it too, but the way is to create additional buses specifically for that purpose and redirect the signal from them to the bus responsible for recording.
If you're going to need it frequently, you can include it in the default template without any major problems. Connect the MIDI Controller to the filter bus. If filters, arpeggiators, etc. are active, they will be processed. If they're disabled, the original signal will be received.
With the configuration I've specified, I don't think there's any latency, at least I haven't noticed it.
re. How complex would it be...
Hi again, Rui:
As I indicated, Qtractor can do the job, but it's not very intuitive to find the way. Qtractor is like that in some ways, but the rest more than makes up for it. I don't plan on changing DAWs. :)
Thanks for the reply.
re. Switch velocity off in your software instrument
Hi Bluebell:
The point here is being able to process/generate the signal before recording without relying on external tools so that everything is configured in the session/template.
There are many reasons: filtering, arpeggiators, pattern sequencers, virtual keyboards. In these cases, I want to be able to take advantage of the automation of these plugins, but also be able to edit and customize the recorded result.
In other DAWs, the way to do this is to put a plugin on the input bus. In Qtractor, you can do it too, but the way is to create additional buses specifically for that purpose and redirect the signal from them to the bus responsible for recording.
If you're going to need it frequently, you can include it in the default template without any major problems. Connect the MIDI Controller to the filter bus. If filters, arpeggiators, etc. are active, they will be processed. If they're disabled, the original signal will be received.
With the configuration I've specified, I don't think there's any latency, at least I haven't noticed it.