We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.

New [3.5.2 284] Analyze - process order & writing speed

Discussion in 'Bug Reports' started by alec.tron, Oct 1, 2021.

  1. alec.tron

    alec.tron Well-Known Member

    I recently analyzed a large batch of files (2145) with [3.5.2 284].
    One thing that seemed odd:
    - analyzing itself took under an hour, roughly (with parallel processing, on a i7 7700HQ). Not super speedy, but all good there.
    - after each analyze step (Traktor seems to process these in 499 file batches [?] ) there was an extra step where Traktor seemingly was writing the metadata (as per the readout...) of each batch only after the analyze step of the same batch was finished.
    - what felt off is: the writing step, following the analyze process, took longer than the analyze itself... all in all the above batch took around 2.5 hrs. So writing the data adds another 1.5 hrs on top seems weird, especially when I can rewrite the metadata of the same batch of 2145 files via python (on the same external magnetic HDD / not SSD) in 34.6 seconds... [so it's not the drive either...]

    - Traktor is taking over 90 minutes to write the metadata of 2145 files, whereas this can be done in less than a minute.
    - in the past I've occasionally had unexplained metadata loss on files that were recently analyzed, and I have a hunch, having analyze & tag writing as 2 processes might have been a large factor in this, that Traktor was shut down while still [silently ? in past versions maybe, as in [3.5.2 284] I can now see a readout for each file written...]. Just a thought that writing the analyze results should be more closely tied to the analyze step.

    Not a high prio [for me], just an oddity I noticed.

    Last edited: Oct 1, 2021
    • Informative Informative x 1
  2. alec.tron

    alec.tron Well-Known Member

    Had another batch - and tried what happens when you shutdown Traktor in the writing phase now, and there's a 'Flushing Background Tasks' pop up now printing each file metadata write - each of which took between 2-8 seconds... so ended up with the pop up shown for a good 20 minutes (for around 300 files...) before actually exiting the program.
    Anyone noticed this in the past and knows when this was introduced ?

  3. re5etuk

    re5etuk New Member

    ive had some quirky issues with analysing but this was on mac.
    most of the tempos were half/double (fixable using the options to limit tempo, even though these tracks had been previously done)
    stripe files missing, so they needed to be done again.even though they'd previously been fine .
    when i reboot, there are usually a small amount of tracks that need to be done again.
    sometimes it doesnt always analyse new tracks within the folders specified in 'music folders' so i have to drag things in myself.