No, using an external recorder is just as valid.
If it's more convenient for you, it's also a way to achieve it.
The advantages I find to how I do it:
1 You don't leave the Qtractor workflow.
2 The file is saved directly in your project folder with the name of the project and the postfix "MasterFinal" of the track. For example: myproyect-MasterFinal.flac
3 You can use Qtractor's in-range recording to ensure that the final master recording starts and ends exactly where you want it.
4 Since the final Master track and the connections to the PipeWire monitor output are saved in my start template, it works just as integrated as an internal Qtractor feature. It's as if I had programmed an alternative export functionality, without programming anything. This ability of Qtractor to allow the user to create their own workflows and have them integrated with the application is one of its strong points. For me, its greatest charm.
No, using an external recorder is just as valid.
If it's more convenient for you, it's also a way to achieve it.
The advantages I find to how I do it:
1 You don't leave the Qtractor workflow.
2 The file is saved directly in your project folder with the name of the project and the postfix "MasterFinal" of the track. For example: myproyect-MasterFinal.flac
3 You can use Qtractor's in-range recording to ensure that the final master recording starts and ends exactly where you want it.
4 Since the final Master track and the connections to the PipeWire monitor output are saved in my start template, it works just as integrated as an internal Qtractor feature. It's as if I had programmed an alternative export functionality, without programming anything. This ability of Qtractor to allow the user to create their own workflows and have them integrated with the application is one of its strong points. For me, its greatest charm.