Hello everyone, I'm new here! :)
I recently purchased the Pro Infinity license. I don't own a hardware controller yet, so I'm currently using my mouse and keyboard, but I hope to get a proper controller in the future.
I've noticed a few bugs while using this skin (and/or the software itself) and wanted to report them:
Bug #1: Pitch Reset Behavior
When two decks are playing simultaneously, the Pitch Reset button does not function correctly. Clicking it once only changes the BPM by 0.01 (up or down). If I double-click it, the BPM suddenly jumps sharply, which ruins the transition.
Bug #2: Automatic PFL on Track Load
Every time I load a new track into any deck, the PFL (Pre-Fader Listen / Cue) button activates automatically by itself, as if I clicked it manually.
Bug #3: Beatlock & Microphone Conflict
When Beatlock is enabled on a deck, engaging my USB microphone and speaking causes the BPM of the playing track to glitch out and suddenly jump to random values like 60 BPM or 140 BPM.
Has anyone else experienced these issues, or is there a known fix/script update for this skin?
Thanks in advance for the help!
I recently purchased the Pro Infinity license. I don't own a hardware controller yet, so I'm currently using my mouse and keyboard, but I hope to get a proper controller in the future.
I've noticed a few bugs while using this skin (and/or the software itself) and wanted to report them:
Bug #1: Pitch Reset Behavior
When two decks are playing simultaneously, the Pitch Reset button does not function correctly. Clicking it once only changes the BPM by 0.01 (up or down). If I double-click it, the BPM suddenly jumps sharply, which ruins the transition.
Bug #2: Automatic PFL on Track Load
Every time I load a new track into any deck, the PFL (Pre-Fader Listen / Cue) button activates automatically by itself, as if I clicked it manually.
Bug #3: Beatlock & Microphone Conflict
When Beatlock is enabled on a deck, engaging my USB microphone and speaking causes the BPM of the playing track to glitch out and suddenly jump to random values like 60 BPM or 140 BPM.
Has anyone else experienced these issues, or is there a known fix/script update for this skin?
Thanks in advance for the help!
Posted 7 hours ago





