Option "Re-analyse beats" hard to understand

Bug #1082734 reported by Daniel Schürmann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Low
Daniel Schürmann

Bug Description

Current string is this:

Re-analyse beats when settings change or beats already present
(e.g. from 3rd-party programs or older Mixxx versions)

Proposed string:

Re-analyse beats when settings change or beats are outdated
e.g. from 3rd-party programs or older Mixxx versions.
(Not checked: Analyse only, if no beats exist.)

Can one native speaker review this?

Candidate for 1.11 with the risk of staying untranslated?

Related branches

Revision history for this message
Daniel Schürmann (daschuer) wrote :

I would like also to commit the attached patch. It reorders the according code removes outdated comments and gives a clean debug log. I hope I did not get confused and the code logic is still unchanged.

The string change is not included.

Revision history for this message
jus (jus) wrote :

Indeed, this needs some wording from a native speaker. Can a beat get outdated, or are we talking about beat detection data?

The specific menu point is already too long imo. Explanatory notes should go into tooltips. I propose a menu point similar to:
* Re-analyse beats when settings change or beat detection data is outdated

The rest -> tooltips.

Changed in mixxx:
status: New → Confirmed
importance: Undecided → Low
milestone: none → 1.11.0
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

If a version of Mixxx generated the beat data from before 1.11 then we consider that "outdated".

I think making it less long would be good though I wanted to stress that if you had this checked it would overwrite your old data from Mixxx 1.10.

Changed in mixxx:
assignee: nobody → Daniel Schürmann (daschuer)
Revision history for this message
Daniel Schürmann (daschuer) wrote :

I will prepare the following:

Re-analyse beats when settings change or beat detection data is outdated

Tooltip:
e.g. from 3rd-party programs or Mixxx versions before 1.11.
(Not checked: Analyse only, if no beats exist.)

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Commited to lp:mixxx/1.11 #3562

Changed in mixxx:
status: Confirmed → Fix Committed
Revision history for this message
jus (jus) wrote :

At the risk of being a nitpicker, i dont think the tooltip text from #4 is good.
We should not forget that a translator does not have a context, he does not know what "e.g. ..." refers to. Same for "Not checked:.." since he does not know we are talking about a checkbox. The ""Not checked: ..." is redundant since we dont have tooltips in other menu points talking about what happens when something not happens.

Also it is not clear what kind of "settings change" qualifies for renewed beat analysis.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Hey Jus, never mind! we need nitpickers to make mixxx almost perfect! :-)

Do you have a proposal?

---

Although I do not like those tooltips at all. I think most of the new users who should read those tool tips will not find them. Because at least you need to reckon that there is a tooltip, to to rest with the mouse waiting for it.

What about (for 1.12) to introduce an static info area right of the preferences pain where we could display much more prose then in a single tooltip.
Eclipse for instance has such a field.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Last part becomes Bug #1090892

Revision history for this message
jus (jus) wrote :

I would like to submit a proposal to fix this string before 1.11 final.

What is the context of the current tooltip "Re-analyse beats when settings change..."?
What kind of "settings change" is meant, changing any setting in the Beat detection preferences or a specific setting?

RJ Skerry-Ryan (rryan)
Changed in mixxx:
status: Fix Committed → Fix Released
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/6717

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.