| 2016-05-12 23:18:51 |
RAWRR |
bug |
|
|
added bug |
| 2016-05-12 23:21:08 |
RAWRR |
description |
I had one or two tracks manually added to the analyze pane and decided to try out the new feature, "Analyze entire Playlist". It clearly was working because BPMs started appearing in the BPM column.
However, I went to the Analyze pane to watch the progress and there was nothing there but the few tracks I had manually added earlier. I had expected that the Analyze option in the Playlist menu would shunt the tracks over to the Analyze pane.
I wonder if this is an undecided workflow?
Obviously I feel it intuitive to dump the list of whatever is being analyzed - regardless of what pane or menu the command originates from - to the Analyze pane as a visual progress readout.
However, absent lasso select (bug #1093598) it does get a bit unwieldy to select from huge quantities of files in the Analyze pane, so I could see a case for deliberately isolating tracks at their visual point of origin.
A logical alternative option would be to change "Analyze entire Playlist" to "Add Playlist to Analyze" where the tracks would be simply added but not automatically analyzed and could be manually selected at the Analyze pane. This requires more clicks by the user however, and might seem less powerful.
Ultimately I think visually dumping anything that is being analyzed to the Analyze pane is the most straightforward visually and intuitively, regardless of whether bug #1093598 is addressed (though especially if it is). |
I had one or two tracks manually added to the analyze pane and decided to try out the new feature, "Analyze entire Playlist". It clearly was working because BPMs started appearing in the BPM column.
However, I went to the Analyze pane to watch the progress and there was nothing there but the few tracks I had manually added earlier. I had expected that the Analyze option in the Playlist menu would shunt the tracks over to the Analyze pane.
I wonder if this is an undecided workflow?
Obviously I feel it intuitive to dump the list of whatever is being analyzed - regardless of what pane or menu the command originates from - to the Analyze pane as a visual progress readout.
However, absent lasso select (bug #1093598) it does get a bit unwieldy to select from huge quantities of files in the Analyze pane, so I could see a case for deliberately isolating tracks at their visual point of origin.
A logical alternative option would be to change "Analyze entire Playlist" to "Add Playlist to Analyze" where the tracks would be simply added but not automatically analyzed and could be manually selected at the Analyze pane. This requires more clicks by the user however, and might seem less powerful.
Ultimately I think automatically starting the analysis while visually dumping anything that is being analyzed to the Analyze pane is the most straightforward visually and intuitively, regardless of whether bug #1093598 is addressed (though especially if it is). |
|
| 2016-05-12 23:23:22 |
RAWRR |
description |
I had one or two tracks manually added to the analyze pane and decided to try out the new feature, "Analyze entire Playlist". It clearly was working because BPMs started appearing in the BPM column.
However, I went to the Analyze pane to watch the progress and there was nothing there but the few tracks I had manually added earlier. I had expected that the Analyze option in the Playlist menu would shunt the tracks over to the Analyze pane.
I wonder if this is an undecided workflow?
Obviously I feel it intuitive to dump the list of whatever is being analyzed - regardless of what pane or menu the command originates from - to the Analyze pane as a visual progress readout.
However, absent lasso select (bug #1093598) it does get a bit unwieldy to select from huge quantities of files in the Analyze pane, so I could see a case for deliberately isolating tracks at their visual point of origin.
A logical alternative option would be to change "Analyze entire Playlist" to "Add Playlist to Analyze" where the tracks would be simply added but not automatically analyzed and could be manually selected at the Analyze pane. This requires more clicks by the user however, and might seem less powerful.
Ultimately I think automatically starting the analysis while visually dumping anything that is being analyzed to the Analyze pane is the most straightforward visually and intuitively, regardless of whether bug #1093598 is addressed (though especially if it is). |
I had one or two tracks manually added to the analyze pane and decided to try out the new feature, "Analyze entire Playlist". It clearly was working because BPMs started appearing in the BPM column.
However, I went to the Analyze pane to watch the progress and there was nothing there but the few tracks I had manually added earlier. I had expected that the Analyze option in the Playlist menu would shunt all the tracks from that playlist over to the Analyze pane.
I wonder if this is an undecided workflow?
Obviously I feel it intuitive to dump the list of whatever is being analyzed - regardless of what pane or menu the command originates from - to the Analyze pane as a visual progress readout.
However, absent lasso select (bug #1093598) it does get a bit unwieldy to select from huge quantities of files in the Analyze pane, so I could see a case for deliberately isolating tracks at their visual point of origin.
A logical alternative option would be to change "Analyze entire Playlist" to "Add Playlist to Analyze" where the tracks would be simply added but not automatically analyzed and could be manually selected at the Analyze pane. This requires more clicks by the user however, and might seem less powerful.
Ultimately I think automatically starting the analysis while visually dumping anything that is being analyzed to the Analyze pane is the most straightforward visually and intuitively, regardless of whether bug #1093598 is addressed (though especially if it is). |
|
| 2016-05-12 23:25:37 |
RAWRR |
description |
I had one or two tracks manually added to the analyze pane and decided to try out the new feature, "Analyze entire Playlist". It clearly was working because BPMs started appearing in the BPM column.
However, I went to the Analyze pane to watch the progress and there was nothing there but the few tracks I had manually added earlier. I had expected that the Analyze option in the Playlist menu would shunt all the tracks from that playlist over to the Analyze pane.
I wonder if this is an undecided workflow?
Obviously I feel it intuitive to dump the list of whatever is being analyzed - regardless of what pane or menu the command originates from - to the Analyze pane as a visual progress readout.
However, absent lasso select (bug #1093598) it does get a bit unwieldy to select from huge quantities of files in the Analyze pane, so I could see a case for deliberately isolating tracks at their visual point of origin.
A logical alternative option would be to change "Analyze entire Playlist" to "Add Playlist to Analyze" where the tracks would be simply added but not automatically analyzed and could be manually selected at the Analyze pane. This requires more clicks by the user however, and might seem less powerful.
Ultimately I think automatically starting the analysis while visually dumping anything that is being analyzed to the Analyze pane is the most straightforward visually and intuitively, regardless of whether bug #1093598 is addressed (though especially if it is). |
I had one or two tracks manually added to the analyze pane and decided to try out the new feature, "Analyze entire Playlist". It clearly was working because BPMs started appearing in the BPM column.
However, I went to the Analyze pane to watch the progress and there was nothing there but the few tracks I had manually added earlier. I had expected that the Analyze option in the Playlist menu would shunt all the tracks from that playlist over to the Analyze pane.
I wonder if this is an undecided workflow?
Obviously I feel it intuitive to dump the list of whatever is being analyzed - regardless of what pane or menu the command originates from - to the Analyze pane as a visual progress readout.
However, absent lasso select (bug #1093598) it does get a bit unwieldy to select from huge quantities of files in the Analyze pane, so I could see a case for deliberately isolating tracks at their visual point of origin.
A logical alternative option would be to change "Analyze entire Playlist" to "Add Playlist to Analyze" where the tracks would be simply added to the Analyze pane but not automatically analyzed, and would be have to be manually selected. This requires more clicks by the user however, and might seem less powerful.
Ultimately I think automatically starting the analysis while visually dumping anything that is being analyzed to the Analyze pane is the most straightforward visually and intuitively, regardless of whether bug #1093598 is addressed (though especially if it is). |
|
| 2016-05-12 23:39:37 |
RJ Skerry-Ryan |
bug task added |
|
mixxx |
|
| 2016-05-13 05:38:16 |
RAWRR |
summary |
Analyze menu option for Playlists and Crates does not visually add tracks to Analyze pane |
Analyze menu option for Playlists and Crates does not add tracks to Analyze pane |
|
| 2016-05-13 05:38:16 |
RAWRR |
description |
I had one or two tracks manually added to the analyze pane and decided to try out the new feature, "Analyze entire Playlist". It clearly was working because BPMs started appearing in the BPM column.
However, I went to the Analyze pane to watch the progress and there was nothing there but the few tracks I had manually added earlier. I had expected that the Analyze option in the Playlist menu would shunt all the tracks from that playlist over to the Analyze pane.
I wonder if this is an undecided workflow?
Obviously I feel it intuitive to dump the list of whatever is being analyzed - regardless of what pane or menu the command originates from - to the Analyze pane as a visual progress readout.
However, absent lasso select (bug #1093598) it does get a bit unwieldy to select from huge quantities of files in the Analyze pane, so I could see a case for deliberately isolating tracks at their visual point of origin.
A logical alternative option would be to change "Analyze entire Playlist" to "Add Playlist to Analyze" where the tracks would be simply added to the Analyze pane but not automatically analyzed, and would be have to be manually selected. This requires more clicks by the user however, and might seem less powerful.
Ultimately I think automatically starting the analysis while visually dumping anything that is being analyzed to the Analyze pane is the most straightforward visually and intuitively, regardless of whether bug #1093598 is addressed (though especially if it is). |
I had one or two tracks manually added to the analyze pane and decided to try out the new feature, "Analyze entire Playlist". It clearly was working because BPMs started appearing in the BPM column.
However, I went to the Analyze pane to watch the progress and there was nothing there but the few tracks I had manually added earlier. I had expected that the Analyze option in the Playlist menu would shunt all the tracks from that playlist over to the Analyze pane.
I wonder if this is an undecided workflow?
Obviously I feel it intuitive to dump the list of whatever is being analyzed - regardless of what pane or menu the command originates from - to the Analyze pane as a visual progress readout.
However, absent lasso select (bug #1093598) it does get a bit unwieldy to select from huge quantities of files in the Analyze pane, so I could see a case for deliberately isolating tracks at their visual point of origin. Still, if analysis is started automatically on all of the tracks and exclusively those added through the menu command, there isn't really anything to select, so it should be fine.
A logical alternative option would be to change "Analyze entire Playlist" to "Add Playlist to Analyze" where the tracks would be simply added to the Analyze pane but not automatically analyzed, and would have to be manually selected. This requires more clicks by the user however, and might seem less powerful.
Ultimately I think automatically starting the analysis while visually dumping anything that is being analyzed to the Analyze pane is the most straightforward visually and intuitively, regardless of whether bug #1093598 is addressed. |
|
| 2016-05-13 05:39:42 |
RAWRR |
description |
I had one or two tracks manually added to the analyze pane and decided to try out the new feature, "Analyze entire Playlist". It clearly was working because BPMs started appearing in the BPM column.
However, I went to the Analyze pane to watch the progress and there was nothing there but the few tracks I had manually added earlier. I had expected that the Analyze option in the Playlist menu would shunt all the tracks from that playlist over to the Analyze pane.
I wonder if this is an undecided workflow?
Obviously I feel it intuitive to dump the list of whatever is being analyzed - regardless of what pane or menu the command originates from - to the Analyze pane as a visual progress readout.
However, absent lasso select (bug #1093598) it does get a bit unwieldy to select from huge quantities of files in the Analyze pane, so I could see a case for deliberately isolating tracks at their visual point of origin. Still, if analysis is started automatically on all of the tracks and exclusively those added through the menu command, there isn't really anything to select, so it should be fine.
A logical alternative option would be to change "Analyze entire Playlist" to "Add Playlist to Analyze" where the tracks would be simply added to the Analyze pane but not automatically analyzed, and would have to be manually selected. This requires more clicks by the user however, and might seem less powerful.
Ultimately I think automatically starting the analysis while visually dumping anything that is being analyzed to the Analyze pane is the most straightforward visually and intuitively, regardless of whether bug #1093598 is addressed. |
I had one or two tracks manually added to the analyze pane and decided to try out the new feature, "Analyze entire Playlist". It clearly was working because BPMs started appearing in the BPM column.
However, I went to the Analyze pane to watch the progress and there was nothing there but the few tracks I had manually added earlier. I had expected that the Analyze option in the Playlist menu would shunt all the tracks from that playlist over to the Analyze pane.
I wonder if this is an undecided workflow?
Obviously I feel it intuitive to dump the list of whatever is being analyzed - regardless of what pane or menu the command originates from - to the Analyze pane as a visual progress readout.
However, absent lasso select (bug #1093598) it does get a bit unwieldy to select from huge quantities of files in the Analyze pane, so I could see a case for deliberately isolating tracks at their visual point of origin. Still, if analysis is started automatically and exclusively on all of the tracks added through the menu command, there isn't really anything to select, so it should be fine.
A logical alternative option would be to change "Analyze entire Playlist" to "Add Playlist to Analyze" where the tracks would be simply added to the Analyze pane but not automatically analyzed, and would have to be manually selected. This requires more clicks by the user however, and might seem less powerful.
Ultimately I think automatically starting the analysis while visually dumping anything that is being analyzed to the Analyze pane is the most straightforward visually and intuitively, regardless of whether bug #1093598 is addressed. |
|
| 2016-09-26 07:18:13 |
Daniel Schürmann |
tags |
analysis analyze gui library menu menus |
analyzer library usability |
|
| 2020-05-08 21:21:12 |
Daniel Schürmann |
mixxx: status |
New |
Confirmed |
|
| 2020-05-08 21:21:15 |
Daniel Schürmann |
mixxx (Ubuntu): status |
New |
Confirmed |
|
| 2022-10-08 20:32:51 |
Swiftb0y |
bug watch added |
|
https://github.com/mixxxdj/mixxx/issues/8550 |
|
| 2022-10-08 20:32:52 |
Swiftb0y |
lock status |
Unlocked |
Comment-only |
|
