Seriously, I’ll say this again:
CHANGE THE RESOLUTION IN THE EFFECTS COLUMN TO FFF!!!
That way we can have 4096 points of resolution AND the ratios remain the same, which will make transferring current renoise projects over to a new version much easier (you just have to multiply all columns by F!).
Case in point:
A break that is chopped well will usually be 1 or two bars in 4/4.
That means there are 16 well defined points in the break already, so you just need to break the offset up into 16 pieces in order to get to these spots, and work with the in between points to get finer grains.
If you have FF, your first hit is at 00, second at 10, third at 20, etc.
so 00,10,20,30,40,50,60,70,80,90,A0,B0,C0,D0,E0,F0 are all the “important”
parts of the break, with the kicks generally on the even numbers and the snares or off hits on the odds.
If you have a resolution of FFF, then your “important parts” become -
000,100,200,300,400,500,600,700,800,900,A00,B00,C00,D00,E00,F00.
Exaclty the same idea, because it’s just division of numbers with a base of 16.
Adding things like user-definable breakpoints is, imho, just lazy because, what if I want to use all of the possible points in the break? There are definitely times where I iterate through an entire break over the course of a bar or several bars in order to get that drawn out “blur,” or, even, tap the break at the beginning of the measure to make sure it stays in time. If I had user-defined breakpoints, I wouldn’t be able to do this. I’d have to load up an entirely different copy of the sample; and what if this was a REALLY high quality break and was about 2-3 megs? That’s 2-3 megs in my RNS file that I don’t need!
And don’t talk to me about aliasing the sample, because that’s just a kludge.
A better solution would be to:
a) Allow the wave editor to be manipulated with the keyboard.
Allow the user to go to a point in the break and hit a keypress that copies the current position to the clipboard.
THEN they can paste this into the offset column.
As people become accustomed to this it will become extremely fast (a matter of 3 keypresses) and, of course, once you paste once, you can refer back to that point as to the value of the offset. Unless you suck at cutting breaks, you’ll notice that it will be, or will be close to, a whole number.
I am really opposed to these sorts of “advancements” in the tracker paradigm. I track because I want to be able to have a tool that lets me get my ideas across effectively; I don’t care if I have to learn a new way of doing things, so long as that new way is faster and compatible with the previous concepts I’ve learned.
Fruityloops completely lost me when they introduced shit like the “scratcher” and started adding “generators” and charging people for them.
A tracker is a tool that can function as a DAW.
It’s an Emacs, or a VI. It’s not for the faint of heart, but once you learn it, you’re much better off than someone using Pico or Visual Studio.
VI does not want to be Visual Studio and visa versa.
I sound angry! But I promise I’m not.