Dragging waveform is too sensitive

Bug #605353 reported by hiend
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Medium
RJ Skerry-Ryan

Bug Description

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.

Related branches

Revision history for this message
hiend (hippako) wrote :

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

hiend (hippako)
summary: - 1.8.0. beta 2 >> forward and rewind to sensitive<<
+ 1.8.0. beta 2 >> forward and rewind too sensitive<<
Revision history for this message
Sean M. Pappalardo (pegasus-renegadetech) wrote : Re: 1.8.0. beta 2 >> forward and rewind too sensitive<<

How does it compare with v1.7.2?

Revision history for this message
hiend (hippako) wrote :

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

Revision history for this message
Albert Santoni (gamegod) wrote :

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?

Revision history for this message
hiend (hippako) wrote :

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.

Revision history for this message
jus (jus) wrote :

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.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

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.

Changed in mixxx:
status: New → Confirmed
milestone: none → 1.8.0
importance: Undecided → Medium
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

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.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

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.

RJ Skerry-Ryan (rryan)
summary: - 1.8.0. beta 2 >> forward and rewind too sensitive<<
+ Dragging waveform is too sensitive
RJ Skerry-Ryan (rryan)
Changed in mixxx:
assignee: nobody → RJ Ryan (rryan)
status: Confirmed → Fix Committed
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

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.

RJ Skerry-Ryan (rryan)
Changed in mixxx:
status: Fix Committed → Fix Released
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/5457

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.