Brake effect initial speed and factor
Bug #1571442 reported by
elmarikon
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Fix Released
|
Undecided
|
ronso0 |
Bug Description
1. In the controller's scripts.js the "[float factor]" for the brake effect seems to be ignored. I tried several values.
2. The effect seems to start with the original speed of the track, rather then the actual playing speed.
So when I have the track pitched down and use the effect, the speed jumps up before slowing down to brake,
although the initial rate is set to 1.
Changed in mixxx: | |
assignee: | nobody → Ronny Sandig (medontknow) |
Changed in mixxx: | |
status: | In Progress → Fix Committed |
Changed in mixxx: | |
milestone: | none → 2.1.0 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
whoopsy, just noticed that I worked around this without considering it a bug.
Below is my controller function, that calculates speed factor and passes it to brake().
You can adapt decay rate to your liking.
TerminalMix.brake = function (channel, control, value, status, group) { group.substring (8,9)); getValue( group," file_bpm" ); getValue( group," bpm");
engine. brake(deck, 1, 10, currentSpeed);
if (value) {
var deck = parseInt(
// enable when button is pressed, release is irrelevant. usage:
// engine.brake(deck, enable/disbale, decay rate, initial playback speed);
var origBPM = engine.
var currentBPM = engine.
var currentSpeed = currentBPM / origBPM;
}
}