Public bug reported:
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).
** Affects: mixxx (Ubuntu)
Importance: Undecided
Status: New
** Tags: analysis analyze gui library menu menus
** Description changed:
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).
+ 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).
** Description changed:
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.
+ 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).
** Description changed:
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.
+ 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).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581251
Title:
Analyze menu option for Playlists and Crates does not visually add
tracks to Analyze pane
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mixxx/+bug/1581251/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
