There are a couple methods of speeding up the computation time of the "rpmTrack" function:
- Divide the signal into various segments. Then, estimate the rpm over each segment, and concatenate those rpm estimates.
- Coarsen the frequency resolution to reduce FFT length, and then compensate the ridge estimation accuracy by specifying enough ridge points and penalty values. This can be done using the name-value pairs for this function such as "FrequencyResolution" and "FrequencyPenalty", as pointed out in the function's documentation page.
