What I do not understand on the waveform display is the that the waveform between a slow BPM song and a fast BPM song do not match in size, even when they are beatmatched...

The wave display of the lower BPM song will move faster over the screen, so it matches the correct beat in the middle with the other song, but that's about it...

Wouldn't it be much more usefull that the wave forms are streched/shrinked compared to their pitch? That way, beatmatched songs will have the same (beat)size on both wave displays?

the very small beatmatch window does that already, why not program the big wavedisplay with the same functionality?

i've noticed that too and that can really throw you off when you're beat matching. even in scratch live the waves match up evenly regardless or original pitch. i do hope they fix this it would really help a lot.

+1

I would also like to have the display tuned like this.

Gotta agree. It should stretch/zoom accordingly just like the beatmatch display in SSL does.

I would second this. To be honest the whole SSL display is better than the Itch display. In SSL you can see exactly at which particular time a cue point is set and not just its place on the waveform without a time specification. The Track Time Display in SSL is also better. Why is it not possible to show the elapsed and remaining time in Itch simultaneously?

I really would appreciate if Itch could offer the same display options like SSL.

+1 to exactly what Baum said

In SSL, I think some of the cpu load is in the actual audio box, but with Itch 100% off the cpu load is on the computer, so to keep a lower load on the computer, the software app is written with less than SSL. I agree SSL has a much better GUI, but Itch is quite young, & SSL is a few years old.
I hope Itch can get the same attention like SSL.

No please do not make the waveform stretch and shrink. Torq does this and it can get very confusing, because there is a delay in what you are actually doing and when the waveform actually stretches/shrinks to the actual size it is supposed to be.

It just happens occasionally after the software is sure to "hear" a constant pitch. It already does this on the beatmatching displays and I don't think it is annoying. Just check it out.

I have noticed that it does do it there. However, one of the things I like about Itch that I hate about Torq is that it does not stretch the main waveform. In Torq when you quickly bringing a track back to a certain location it is difficult to do visually, because as you do so the wave form is compressed and as you quickly attempt to stop it where you need to, the waveform expands again. Visually this is decieving and a nightmare. This just does not happen in Itch (which is good in my opinion.)

Now if this was to be implemented, and as you say it will wait to find the constant pitch where do you find the happy medium, (there really may never be one) because if the delay in the waveform recalibration is too large, when you make small movements or bends (there will be a visual delay to see this information updated, where as you may over adjust because the recalibration of the waveform is not happening fast enough, basically what you hear will not be what you see), but if you eliminate this delay, then when you quickly cue back or scratch the waveform will move erratically (attempting to recalibrate constantly to follow all of the sudden changes in tempo).

Hm, good points you brought up.

However after giving this more thought, this may not be as much of an issue as I may believe it to be.. Because I am comparing timecode (torq) to midi (itch).
But since itch is midi and scratch and jog are separate functions, if a scratch was to be made then the waveform could remain untouched until the "found constant pitch" was achieved. But at the same time since the jog or pitch bend is a separate control via midi, this could be made tighter and more responsive to more accurately represent what is actually is happening.

This I feel may be a viable option which would satisfy both...
Recalibration of the waveform from Scratching and quick back cuing would not happen until a predefined delay period was over.
And slight jog and bends would recalibrate instantly so what we see matches what we hear...
This may ultimately be a good thing...