Dragging waveform is too sensitive

[mixxxbot]

Reported by: hippako
Date: 2010-07-14T10:32:06Z
Status: Fix Released
Importance: Medium
Launchpad Issue: lp605353

---

Forward and rewind are to sensitive while I drag the waveform with mouse, one step forward it speed up the song almost twice, so is very difficult to fine tune the dragging while mixing the songs.

[mixxxbot]

Commented by: hippako
Date: 2010-07-14T10:41:33Z

---

Three steps ahead, the song is too fast making impossible to hear the beat.

[mixxxbot]

Commented by: Pegasus-RPG
Date: 2010-07-14T10:55:22Z

---

How does it compare with v1.7.2?

[mixxxbot]

Commented by: hippako
Date: 2010-07-14T11:04:35Z

---

It's more tolerant and smooth in 1.7.2 and the all previous versions.

[mixxxbot]

Commented by: asantoni
Date: 2010-07-14T16:09:52Z

---

What's your latency set at?

I don't think we changed anything related to the waveform dragging rate control in 1.8 (which is what, "scatch"?). Does anyone know?

[mixxxbot]

Commented by: hippako
Date: 2010-07-14T16:33:41Z

---

The latency is set to default 46ms. The only doubtful message I've get from terminal is: 
lappy@lappy-laptop:~$ mixxx
Debug: [Main]: Mixxx 1.8.0~beta2 "" is starting... 
Warning: [Main]: Configuration file is at version "1.7.2" and I don't know how to upgrade it to the current 1.8.0~beta2 
   (That means a function to do this needs to be added to upgrade.cpp.) 
-> Leaving the configuration file version as-is. 

[mixxxbot]

Commented by: esbrandt
Date: 2010-08-10T07:00:50Z

---

Would be total ace if we could use the same configurable behaviour like for the ramping pitchbend function.
Depending on how long you press the ffw/frw button the speed changes.

[mixxxbot]

Commented by: rryan
Date: 2010-09-11T05:59:38Z

---

I just looked into it. We totally changed the way the 'wheel' control (what dragging the waveform uses) works in 1.7.2 versus 1.8.0.

In 1.7.2, while the track is playing we add the wheel value directly to the rate. In 1.8.0, we add 400x that value to the rate.

In 1.7.2 when the track is stopped, we use the wheel value * 40. In 1.8.0, we add 10x that value to the rate.

[mixxxbot]

Commented by: rryan
Date: 2010-09-11T06:25:09Z

---

I think that in 1.8 we should keep the 40x factor when paused (makes it easier to seek through the file) and add only a 10x factor on the wheel factor when playing. Without any factor at all it isn't possible to drag to the left and stop or reverse the file.

[mixxxbot]

Commented by: rryan
Date: 2010-09-11T06:31:05Z

---

I take it back, with no factor you can make the song go in reverse, but you have to move Mixxx all the way to the right of the screen and drag from the deck all the way to the left. Adding a 10x factor makes it much easier.

[mixxxbot]

Commented by: rryan
Date: 2010-09-21T03:49:12Z

---

I've just removed the change between 17.2 and 1.8.0. Now the wheel control has no adjustment whatsoever -- its value is added directly to the rate.

There are two MIDI devices in the repo that use the wheel control so the scope of this change is almost purely waveform-related, though it helps to not change behavior with respect to 1.7.0 if possible. Everyone who wants a more sensitive wheel can just use script to adjust the sensitivity.

[mixxxbot]

Issue closed with status Fix Released.