Impulse tracker supported A-Z characters, its also a relic from the past. And IT wasn’t the only tracker supporting 36 pattern effect commando’s.
I never said that every solution that was used in the past is wrong, just that some cases they can be and that people can be persistent when it needs to change. This is why I vote for decimal numbers, just so the product can be more intuitive for regular human beings and not everyone I try to teach the program to gets all confused about how to think in base 16. Also, I think it makes more sense if letters are used for things that doesn’t have a numerical connection. If there are more effects than the number of letters in the alphabet, then go for two letters.
I’m leaning towards agreeing to some kind of painful optimization.
Maybe use a pulldown menu here and there. Imagine if the FX column works as an pulldown menu, where when you type P it jumps to [P]itchbend down and if you like to pitchbend up you just scroll it down once.
These days most ppl use widescreen monitors or high resolutions, so it doesn’t make much sense to cramp it all together anymore.
I’m all for getting rid of hex. I was used to that 15 years ago but I’d prefer some more intuitive scale like 000-127 (or 255) these days…
(or at least a global option switch that gives you a choice)
+1 for global switch option
As much as I would prefer and think a decimal system is more intuitive, I know some old school guys are probably quite used to it and get good results from it, thusly I think a complete ditching of the system may not be fair.
Blasphemes!
0-FFh IS 0-255dec.
The easy halving/doubling by one having to change one number is very useful.
C-4 80
c-4 40
C-4 20
C-4 10
Compared to:
C-4 128
C-4 64
C-4 32
C-4 16
Although I wouldn’t actually oppose an option but Hex really does make sense in more than just reducing used screen real estate. I prefer to have my Lines numbered in Hex, over Decimal, which is already a user option. Although when working at 12/24 LPB sometimes decimal can be a little easier…
And how do you want to translate these symbols to the keyboard?
I’m all for this to change, It’s easy to adapt by excising users.
they will get used to other things that do the same.
For new users it might get less intimidating to see more defined stuff on their screen.
To try to make things tens times more complicated because it’s cool.
I hate the FF or what ever for velocity.
Ridiculous and stone age.
I’m making music here not reinventing the theory of relativity FFS.
Why do DAWS speak in their own language instead of ours?
Waiting for all DAWS to step out of the mathematicians lab and embrace the year 2011 not the 90s.
Time for DAWS to be simple and speak to us like humans instead of being as hard as C+ programming.
The first company or person that makes a DAW with every feature but speaks to us in a language we understand,will be a trillionaire.
Garf´s quicksearchable puuldown menu would do the trick, but then keys reflect the symbols description ofcourse.
+1
Get rid of the hex as default.
It might fit some old trackers and some coders but for the rest of the world its just yet another weird obstacle to get into the program and it limits the nr of effect.
A dropdown with symbols or letters (each symbols having a letter connected to it?) would make it easier to use,
easier to read (better overview) and give it more possible effect comands.
Come on guys hex is really wonderful and easy!
Yes that’s right, but put yourself into the position of a new user.
It could lower the threshold for those who don’t say 0E14= re trigger where 1 is volume slide down and 4 is tick count so easily.
Anything is easy for someone who knows how to do it, but it’s kind of obvious that it’ll be tricky for a beginner to figure out why 37 should be written as 25.
If you weren’t at least vaguely technically minded you wouldn’t of chosen a composing software than looks like the Matrix over something fluffy like Music2000 
Every body has instant access to something that will very quickly change between decimal and hexadecimal at their fingertips. All OSes come with a calculator built in with this function!
So, do you want to mess around with calculators to make music?
And We have a hex<>dec converter tool 
That’s actually quite convenient.
I doubt that. I’ve had no problem teaching Renoise to people, apart from the one single thing with the hexadecimal numbers. These were users who basically knows how to operate a web browser and a word processor, and I could easily teach them to input notes and add samples and VST instruments. They do not think it’s convenient to use a converter or a calculator, they just wonder why it just isn’t normal numbers. I’m making conclusions from experience.
Well it would be best if there was some internal renoise converter. If some one want to put values in decimal i think he should have such choice. I mean its just a view.
It’s not just about converting the numbers from hexa decimal to decimal (which isn’t quite difficult to be honest) in my opinion.
If we have decimal numbers it would expand the possibilites for the effect column which would be a great improvement imo.
i think that inputting numeric values in hex is quite fine (since i’ve gotten used to it i guess lol)
when it comes to the names of the commands then i think hex values works but imo: mnemonics > 00 to 0E.
would be easier to remember AR or AP for arpeggio, PS for pitch slide and CV for channel volume etc and the commands doesn’t really, to my knowledge, have any logical “order” so assigning them to hex numbers doesn’t really help.