In my search for VST plugins that could produce a real-time record scratch effect, I came across and gladly bought your product (Effectrix).
While it's other features are uniquely beneficial, the ScratchLoop effect is what I'm most interested in making regular use of.
After experimenting with ScratchLoop for a few days, I feel the need to provide some suggestions for it's improvement so as to better it's functionality and over-all ease of use.
My primary request is for the ability to program scratch solos and fills that are exact in their rhythmic accuracy.
Basically, I'd like to be able to set the scratch size boundaries to and EXACT note duration which corresponds and reacts to the host sync. Namely, a 16th is a 16th, a 16th triplet is a 16th triplet, without any "in-betweens" on the size knob. The "in-betweens" will be left for the "flavor" produced by the other knobs.
Assuming this is now an option and a given note value is selected, my next adjustment (FWD speed) is set to a percentage of the notes size, so ...
If the FWD speed percentage + the BWD speed percentage is greater than 100 (100%) then whichever knob is NOT being adjusted must compensate / readjust so that the math never goes over 100%. Basically, if the size is set to 16th, don't ever let FWD or BWD speeds add up to more than that note's millisecond value via percentage. Instead, simply shift the apex as to where one stops and the next begins.
Then, to compensate for slope, we do the same thing as above ... only within the individually allotted percentage for the FWD / BWD speeds.
The slope of the FWD speed can only be a percentage (up to 100%) of the total FWD speed (a limited percentage of the total time of the fwd motion). Because the FWD and BWD speeds are now calculated to compliment each-other within the given note size, this same calculation will work in conjunction with the BWD speed.
Assuming all of this can happen, I'll be able to program just about any funky scratch concept I want with much greater ease.
Now, I'm probably off on some of this simply due to the fact that I'm unfamiliar with how you've shaped this feature. However, I think my request is not only reasonable but easily accessible from a programming standpoint.
Thanks for your time
