All analysers execute concurrently (the analyser queue decodes the song in
chunks and runs every analyzer on each chunk) so the ordering of
AnalyserGain and AnalyserWaveform doesn't matter.
I think it may be best to re-enable the progress bar behavior and tie it to
an 'analysis progress' stored in the TrackPointer.
On Wed, Jul 4, 2012 at 4:08 PM, Daniel Schürmann <<email address hidden>
> wrote:
> ** Changed in: mixxx
> Assignee: (unassigned) => Daniel Schürmann (daschuer)
>
> ** Changed in: mixxx
> Status: New => In Progress
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https://bugs.launchpad.net/bugs/1008721
>
> Title:
> AnalyserGain before AnalyserWaveform
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1008721/+subscriptions
>
Hi Daniel,
All analysers execute concurrently (the analyser queue decodes the song in
chunks and runs every analyzer on each chunk) so the ordering of
AnalyserGain and AnalyserWaveform doesn't matter.
I think it may be best to re-enable the progress bar behavior and tie it to
an 'analysis progress' stored in the TrackPointer.
On Wed, Jul 4, 2012 at 4:08 PM, Daniel Schürmann <<email address hidden>
> wrote:
> ** Changed in: mixxx /bugs.launchpad .net/bugs/ 1008721 /bugs.launchpad .net/mixxx/ +bug/1008721/ +subscriptions
> Assignee: (unassigned) => Daniel Schürmann (daschuer)
>
> ** Changed in: mixxx
> Status: New => In Progress
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https:/
>
> Title:
> AnalyserGain before AnalyserWaveform
>
> To manage notifications about this bug go to:
> https:/
>