Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Analyze doesn't show new tracks #5874

Closed
mixxxbot opened this issue Aug 22, 2022 · 7 comments
Closed

Analyze doesn't show new tracks #5874

mixxxbot opened this issue Aug 22, 2022 · 7 comments

Comments

@mixxxbot
Copy link
Collaborator

Reported by: morxa
Date: 2011-04-22T18:44:37Z
Status: Fix Released
Importance: Medium
Launchpad Issue: lp769138
Tags: analyze, library
Attachments: analyze_new_track.patch


Steps:

  1. Add a track to the library (e.g. by rescanning)
  2. Go to the Analyze view
    The new tracks are not shown.
    If you change the view to "All Songs" from "Recently Added" or vice versa, the new track appears.

Mixxx trunk Revision #⁠2758

@mixxxbot
Copy link
Collaborator Author

Commented by: alex-marin89
Date: 2011-04-22T22:22:55Z


If you run on windows 7 and add tracks to the library (step1) and then go to analyze view (step2) the new tracks are not shown, even if you change the view to "All Songs" from "Recently Added" or vice versa. The only way you are able to see them is by restarting Mixxx. On Ubuntu 10.10, the behavior is as in the description ( the new tracks appear if you change the view, no need for restarting).

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2011-10-01T02:59:19Z


We should check that this is fixed.

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2011-10-12T05:25:49Z


It's not fixed yet.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2011-11-06T09:22:58Z


With the current trunk lp:mixxx #⁠2950 new songs are displayed when you switch between "all" and "recent" tracks or if you resort via header click.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2011-11-06T23:05:55Z
Attachments: analyze_new_track.patch


All changed and new tracks where signalled by BaseTrackCache.
One solution would be to do select, if a new track is signalled. This is a good Idea for currently not displayed tables, but not for the current table, because the user likely is disturbed by such a select.
An other solution would be, to add all new songs to the end of the table. This is seems to be a major work for a minor problem.

In the attached patch I have prepared the following solution:

  • select onShow
  • select after library scan
  • select after drop a track ?field.comment=All changed and new tracks where signalled by BaseTrackCache.
    One solution would be to do select, if a new track is signalled. This is a good Idea for currently not displayed tables, but not for the current table, because the user likely is disturbed by such a select.
    An other solution would be, to add all new songs to the end of the table. This is seems to be a major work for a minor problem.

In the attached patch I have prepared the following solution:

  • select onShow
  • select after library scan
  • select after drop a track

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2012-07-10T20:05:30Z


commited to lp:mixxx/1.11 #⁠3311.

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Fix Released.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant