1
It's necessary to be able to document and comment on project processes.
Qtractor has so far lacked tools in this regard.
Other DAWs allow you to comment on any work element with text and images (tracks, clips, plugins...).
This is functional, but it's not easy (it involves a lot of development and unnecessarily complicating the interface). So it's outside the Qtractor philosophy.
Things should be functional and simple :).
2
I've always done what Rui says. It's the trick to be able to leave comments and clarifications. But it has several drawbacks. The name will be transferred to the recorded clips, and we end up with folders with files with biblical names. It's not nice to look at, and the available field of view is small.
3
I think what you were saying about adding a "Comments" field to the track properties is the best solution.
That text would be displayed below the track name in the sequencer in a smaller font size.
If the text exceeds X characters (tests would have to be done to know how many) ellipses appear, implying that there is more information and can be read in properties.
That would allow for an acceptable, easy-to-use documentation capability. Qtractor style.
I don't know if you also think it could be helpful.
I think we're getting there.
1
It's necessary to be able to document and comment on project processes.
Qtractor has so far lacked tools in this regard.
Other DAWs allow you to comment on any work element with text and images (tracks, clips, plugins...).
This is functional, but it's not easy (it involves a lot of development and unnecessarily complicating the interface). So it's outside the Qtractor philosophy.
Things should be functional and simple :).
2
I've always done what Rui says. It's the trick to be able to leave comments and clarifications. But it has several drawbacks. The name will be transferred to the recorded clips, and we end up with folders with files with biblical names. It's not nice to look at, and the available field of view is small.
3
I think what you were saying about adding a "Comments" field to the track properties is the best solution.
That text would be displayed below the track name in the sequencer in a smaller font size.
If the text exceeds X characters (tests would have to be done to know how many) ellipses appear, implying that there is more information and can be read in properties.
That would allow for an acceptable, easy-to-use documentation capability. Qtractor style.
I don't know if you also think it could be helpful.