Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No scratching on touching jog wheel for the first time #9489

Closed
mixxxbot opened this issue Aug 23, 2022 · 9 comments
Closed

No scratching on touching jog wheel for the first time #9489

mixxxbot opened this issue Aug 23, 2022 · 9 comments
Labels
Milestone

Comments

@mixxxbot
Copy link
Collaborator

Reported by: max-beiersdorfer
Date: 2018-10-28T11:51:44Z
Status: Fix Released
Importance: Medium
Launchpad Issue: lp1800343


Mixxx: 2.3.0-alpha-pre (build master r6617)
OS: Apple macOS High Sierra 10.13.6
CPU: 1,6 GHz Intel Core i5
Video: Intel HD Graphics 6000 1536 MB
Sound: Apple Core driver -> Pioneer DDJ-SX

After a fresh boot of MacOS, a fresh start of Mixxx (I can pick any version, for example Mixxx 2.1.4 or Mixxx 2.2.0 or the master build) and after reconfiguring the sound output settings from internal sound to the controller's sound card...I wasn't able to do scratching on touching a jog wheel of a playing deck for the first time. The track only stops/pauses at the touched position. After releasing and touching the jog wheel again I can scratch normally.
It's annoying when you forget to touch the jog wheel once before you want to do some scratching.

I could reproduce this behavior with four different controllers using the Mixxx-Included mappings:
Pioneer DDJ-SX
Pioneer DDJ-SB
Hercules DJ Console RMX2
Hercules DJ Console 4-MX

Starting MixxX from Terminal using controller debug information gives no special output concerning this problem.

@mixxxbot mixxxbot added the bug label Aug 23, 2022
@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2018-10-28T15:24:26Z


I am surprised we have not had reports about this from other macOS users. Can you reproduce this on other Macs?

@mixxxbot
Copy link
Collaborator Author

Commented by: Pegasus-RPG
Date: 2018-10-28T16:27:17Z


I can confirm this on Linux (Debian) as well.

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2018-10-28T17:41:18Z


I just tried master and the latest 2.1 buildserver build on macOS 10.13.6 with a Hercules 4-Mx and can't reproduce. I'm using the built-in Hercules 4-Mx preset.

  • Start Mixxx (built-in interface and Hercules 4-Mx enabled at boot)
  • Load track to deck 1, hit play.
  • Enable "Scratch" button on Hercules 4-Mx deck 1.
  • Pref -> Interface -> Change primary output to Hercules 4-Mx Channel 1/2, no headphone output.
  • Turn jog wheel.

Result: Audio pitch bends like normal on first touch.

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2018-10-28T17:58:30Z


Sean -- what controller are you able to repro with?

@mixxxbot
Copy link
Collaborator Author

Commented by: ronso0
Date: 2018-10-28T23:22:16Z


I can reproduce with Reloop TerminalMix2 & TerminalMix4.
I can see the touch signals are sent to the script, but I need to cycle through
 engine.scratchEnable(deck, 800, 33+1/3, alpha, beta);
 engine.scratchDisable(deck);
once until the scratch ticks are registered by the engine.

@mixxxbot
Copy link
Collaborator Author

Commented by: ronso0
Date: 2018-10-28T23:22:49Z


2.2 ubuntu studio 18.04

@mixxxbot
Copy link
Collaborator Author

Commented by: ronso0
Date: 2022-05-18T12:32:47Z


Got it:
I added some qWarnigns to trace the scratch functions and scratchEnable and scratchTick functions are called correctly. It's just that each deck's booleans m_brakeActive, m_spinbackActive & m_softStartActive are not initialized, thus decks are stopped in scratchProcess.

Before #4708 I experienced that any wheel touch would 'freeze' the deck even though scratch ticks were sent, or interpret wheel turn as jog move.

I'll open a PR asap

@mixxxbot
Copy link
Collaborator Author

Commented by: ronso0
Date: 2022-05-18T20:19:03Z


#4761

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Fix Released.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@mixxxbot mixxxbot added this to the 2.3.3 milestone Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant