Comment 6 for bug 1457746

Revision history for this message
joe (joseph-chilcott) wrote : Re: [Bug 1457746] Re: Withdraw stored analysis if the track sample count changes

Hi Ferran,

Have you been able to replicate this issue, I am still having problems.
When I restart Mixxx, it never remembers what I have cued up on either
deck. Therefore I do not see this problem as I am forced to reload the
track each time. This could be a newbie thing (I have looked through the
mixxx documentation and config but could not see anything that would help.

If you were able to to replicate this issue can you tell me what the Git
commit ID was that you are building against when you see this issue? (
*Daniel- can you tell me the Git commit ID that you are also building
against when you see this issue?)*
I cannot comment in much depth on the solution you have proposed, however
it seems reasonable. Would this solution work if the user loaded a track
in mixxx, minimized Mixxx, edited the track and then maximized Mixxx again?

Many thanks,
Joe

On Thu, Jul 30, 2015 at 7:06 PM, Ferran Pujol <email address hidden>
wrote:

> Would this work?
>
> 1-Store in the database the last time when Mixxx modified a track file.
> 2-When the track is loaded, compare the database last modified time with
> the OS last modified time. If Mixxx is not the last app to modify the
> track, re-analyze it.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1457746
>
> Title:
> Withdraw stored analysis if the track sample count changes
>
> Status in Mixxx:
> New
>
> Bug description:
> This may happen if the track was cut or in case of seek decoding issues
> (still in 1.12 alpha).
> Currently the waveform does not fit to the samples and the sync feature
> will fail is such a case.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1457746/+subscriptions
>