Comment 15 for bug 733376

I can do some extensive testing of trunk starting tomorrow. I'll also try my hand at merging the changes with features_xwax2 if Owen doesn't beat me to it...

--
Joseph Colosimo
http://jwcxz.com
(Mobile)

----- Reply message -----
From: "RJ Ryan" <email address hidden>
To: <email address hidden>
Subject: [Bug 733376] Re: Track Cache does not Save to Database
Date: Thu, Mar 24, 2011 01:49

Ok, just pushed my stuff to the 1.9.x branch. To summarize:

- Tracks save now. (Woo?)
- The cache size is much smaller, around 5. I'm scheming to fully remove it.
- The track table updates correctly when tracks are saved and does NOT reset or cause any massive queries to happen when tracks are marked clean
- Sorting and searching shows their up-to-date data (Bug #700802)

Sean : I never saw your cue point bug. I tried it with both fresh and
dirty libraries. Shrug.. could you try again w/ the 1.9.x branch?

Marking this committed. I want to get it in the hands of the dev-team
and trunk/1.9.x from-source testers ASAP since it wasn't a simple fix.

--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs.launchpad.net/bugs/733376

Title:
  Track Cache does not Save to Database

Status in Mixxx:
  Fix Committed
Status in Mixxx 1.9 series:
  Fix Committed

Bug description:
  Running 1.9 on Linux. The problem continues to appear in trunk.

  Steps to reproduce:
  1. Open Mixxx.
  2. Start anywhere on your playlist and load a track. It doesn't matter how you load the track. It doesn't matter whether you actually play the track or not.
  3. Now load another track. For the sake of convenience, load the next one on your playlist.
  4. Continue to load tracks for a while. In fact, load 20 tracks total.
  5. Now, load the 21st. Examine the "played" checkbox column. You should see that the checkboxes for your previous tracks have become unchecked!

  But there's more. This problem is *NOT* limited to just the played
  checkboxes -- it is related to *ANY* modification of the database. An
  important example is cues. If you had set cues for each of those 20
  tracks above and then loaded a 21st track, all of your cues that you
  had set before in those 20 tracks are now lost.

  The cache also fails in another interesting way too. Sometimes, I was
  able to load successive tracks and watch individual checkboxes from
  previous tracks get unchecked one-by-one (like the game Snake) or
  perhaps in small grops of 2 or 3.

  There is no useful debug information in mixxx.log. It only shows
  lines saying tracks were played.

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/mixxx/+bug/733376/+subscribe