Force new waveform creation on analyze all

[djphaidon]

I have run into several waveforms in the "entire track" waveform that have been completely off. Could you please force the recreation of every waveform on analyze all.

Also, there is a distinct difference between the the overall track waveform and the track head waveform. Could you possibly make a way that we can choose which type of waveform we want to display on both, cause the overall track waveform seems to be generated on the mids or highs volume, rather than the tracks bass.

[sylMV]

I have run into several waveforms in the "entire track" waveform that have been completely off.

i.e.?

Could you please force the recreation of every waveform on analyze all.

No we can't force the user to re-analyze his tracks. But, on your side, you can reanalyze them (right click on the track -> analyze).

Also, there is a distinct difference between the the overall track waveform and the track head waveform. Could you possibly make a way that we can choose which type of waveform we want to display on both, cause the overall track waveform seems to be generated on the mids or highs volume, rather than the tracks bass.

Sorry, but both displays are using the same data (created during analysis.

[djphaidon]

I have run into several waveforms in the "entire track" waveform that have been completely off.

i.e.?

From W&W's Liftoff below, I can show several spots that are incorrectly rendered and will not change when re-analyzed

Could you please force the recreation of every waveform on analyze all.

No we can't force the user to re-analyze his tracks. But, on your side, you can reanalyze them (right click on the track -> analyze).

I was unclear on this. Not force users to re-analyze, but force the recreation of new waveforms for the track that you are analyzing. Currently, it seems that the waveforms do not update when analyzing a track other than the first time it is imported.

Also, there is a distinct difference between the the overall track waveform and the track head waveform. Could you possibly make a way that we can choose which type of waveform we want to display on both, cause the overall track waveform seems to be generated on the mids or highs volume, rather than the tracks bass.

Sorry, but both displays are using the same data (created during analysis.

https://www.dropbox.com/s/n3kam0oeoajyu70/Audacity.png
This screen capture shows audacity's wave render of W&W's Lift off for reference. I will be using the inner, lighter blue waveform from this waveform because it is the most similar to what Cross renders.

https://www.dropbox.com/s/q5m7xy8ujnativk/cross1.png
This screen capture shows two spikes in audio that are not present in the waveform. One is halfway from the beginning to the first new phrase, and the second is right above the left border of "seek 16". The spikes don't go away with a re-analyze. This is just an example, but I have and have had in the past several waveforms that come up completely wrong when looked at in any other editor or DJ program.

Which leads me to my last point

https://www.dropbox.com/s/cc47wigjk58p8ej/cross2.png

The waveform for the whole track, just in this track, goes from filling 100% of the waveform, to nearly 0% of the waveform at the purple marker. The track head waveform never hits 100% on any track that I've ever played. In fact, it is always maxed at 75% or so of the entire waveform area, on any track. The track head waveform will also have audio displayed when there is little to no audio displaying in the whole track waveform. When comparing the audacity waveform to the whole track waveform, in the first phrase, the Cross waveform seems to decrease in energy from the beginning to the first phrase drop, however, the energy is mostly constant in the song and in audacity. This leads me to believe that the two waveforms are different.

I will go through and find more specific examples of this.

[djphaidon]

https://www.dropbox.com/s/ii1s4i5x83ptnzi/Cross%20waveform%20issue.mov

From Deadmau5's HR8938 Cephei, you can see that the quietest spot of the song, between locator 2 and 3 is rendered in the whole track waveform graphically as the loudest part of the song, however, in the trackhead waveform, it is rendered correctly.

[sylMV]

Ok, I guess I was misunderstood.
For what's shown in the overview, indeed there are peaks in this example. But they won't disappear even after re-analysing as it's the analysis result! I don't know why on this track (and maybe other ones) the analysis creates peaks but it does.
I first thought you were talking about waveform not displaying as they used to.

For the second point, once again misunderstood. With "track head waveform" I understood "the one showed in the beatmatcher".
But the player waveform is completely different from the overview and even not coming from the analysis. Moreover, unlike the overview, it's not filtered nor processed.
In any case, we know the overview waveform is neither consistent, nor efficient, nor beautiful and it should change. But that's not the time to...

Could you maybe send us the track used for the screenshots so that I can have an idea of what kind of sound gets the analysis crazy