For me to be able to customize the UI, because it is part of the creative experience. Especially on a music show. (I also personalize my physical musical instruments).
In an image program, you create images, and therefore you want a visual environment with symbolic icons that is as neutral as possible, that does not contaminate the image you are creating.
In a text program you create concepts, so even icons are unnecessary there.
But music is emotional, and having a visual style that matches what you're trying to convey emotionally is helpful. It is no coincidence that the most elaborate, different, disruptive and innovative interfaces are found in musical software, (DAWs, synths, plugins...)
Sometimes calling on the tactile and physical world, visually emulating analog instruments and tools. Others building symbolic interfaces.
Thus one feels immersed in different environments, a recording studio, or in a band's garage, in a concert hall, on a conceptual plane with waves and pure colors of electronic music, etc.
Going back to Qtractor and QSS.
There are things that we cannot modify, and others that, although we can touch with QSS, it is not recommended because we lose functionalities.
For example, it is possible to change the backgrounds on the mixer tracks (create other gradients etc). However if you do this, you lose the functionality of highlighting if you select the track in the sequencer. If the mixer tracks had a "selected" state, it could be done, but I don't know if that state can be created for that specific Widget.
"TrackList" could be customizable if the list items were independent Widgets.
I don't know the complexity of making this possible.
Something similar happens with the track "color list" selector. It is a QComboBox type element. If you customize the generic properties of the QComboBox, it will also affect this one, and it may stop working as expected.
Do we have limitations? Yeah. It is logical, programs are not created to be customizable, but functional and efficient.
And all of us who use Qtractor as a DAW do so because both in terms of performance and ease of creating and applying workflows, it is a masterpiece.
Summarizing all the spiel I've given:
Within the limits there is much that can be done. :)
Welcome to customization :).
For me to be able to customize the UI, because it is part of the creative experience. Especially on a music show. (I also personalize my physical musical instruments).
In an image program, you create images, and therefore you want a visual environment with symbolic icons that is as neutral as possible, that does not contaminate the image you are creating.
In a text program you create concepts, so even icons are unnecessary there.
But music is emotional, and having a visual style that matches what you're trying to convey emotionally is helpful. It is no coincidence that the most elaborate, different, disruptive and innovative interfaces are found in musical software, (DAWs, synths, plugins...)
Sometimes calling on the tactile and physical world, visually emulating analog instruments and tools. Others building symbolic interfaces.
Thus one feels immersed in different environments, a recording studio, or in a band's garage, in a concert hall, on a conceptual plane with waves and pure colors of electronic music, etc.
Going back to Qtractor and QSS.
There are things that we cannot modify, and others that, although we can touch with QSS, it is not recommended because we lose functionalities.
For example, it is possible to change the backgrounds on the mixer tracks (create other gradients etc). However if you do this, you lose the functionality of highlighting if you select the track in the sequencer. If the mixer tracks had a "selected" state, it could be done, but I don't know if that state can be created for that specific Widget.
"TrackList" could be customizable if the list items were independent Widgets.
I don't know the complexity of making this possible.
Something similar happens with the track "color list" selector. It is a QComboBox type element. If you customize the generic properties of the QComboBox, it will also affect this one, and it may stop working as expected.
Do we have limitations? Yeah. It is logical, programs are not created to be customizable, but functional and efficient.
And all of us who use Qtractor as a DAW do so because both in terms of performance and ease of creating and applying workflows, it is a masterpiece.
Summarizing all the spiel I've given:
Within the limits there is much that can be done. :)