We have to consider, that the beatgrid and waveforms took a significant HD space.
So I am in doubt that analyzing by default is a good choice.
The other issue is that analyzing it took sooooo long. We may introduce a strategy to make that unnotable for the user. Something like a maintenance thread that runs only when no other cachingreader is active.
We have to consider, that the beatgrid and waveforms took a significant HD space.
So I am in doubt that analyzing by default is a good choice.
The other issue is that analyzing it took sooooo long. We may introduce a strategy to make that unnotable for the user. Something like a maintenance thread that runs only when no other cachingreader is active.