You should add this too.
i am now violently smashing my head into the tabletop trying to figure out where my mind was when i forgot to add that. damn. thanks. will get right to it.
edit: done.
was looking for a reggae tutorial tonight, remembered using a really good one before but sadly i could not find that again. then i stumbled across one i did not know and which is equally good. so, to not forget it again, i added the link to the cheatsheet, in the ‘Links’ tab and added its own category ‘Styles’. check it out here: http://www.roaldblijleven.net/renoise/cheatsheet/links.php
edit: if anyone has any other good tutorials for beats/rhythms/melodies in any kind of style (except trance, please, the cheatsheet is still personal enough for me to steer away from a type of music i cannot stand), feel free to suggest it here and i will add it if i agree on the quality/usefulness of it.
Only just dived into this for the first time, nice effort here rhowaldt! However, one suggestion: I’m finding the near white on the really dark background a bit hard on my old eyes. Is it easy for you to soften that contrast for old codgers like me? 
Otherwise well done, feel free to link in there the other In:Depth articles I’ve done just in case you haven’t yet. Sheesh, I’ve still got to make time to write more of those… 
thanks man, good to hear even someone i regard as ‘loads more experienced than me’ still has use for my cheatsheet.
the colors are literally white on black (#fff on #000). i will look into it. i noticed that (at least in FF4) the top navbar line is shifted so i’ll have to check out the GUI again anyway. maybe do a bit of an update. my goal was to make it look like the Renoise (default) interface, but that turned out to be too much effort at the time so i settled for pure white on black. i bet if the background were a bit more grayish (lighter) it would be easier on the eyes, right?
i need to check out those In:Depth articles again, as i don’t remember each one, and might find some use for adding it to the cheatsheet.
as i may have said before, the cheatsheet is simply a collection of links and forum-posts and stuff that are nice to have in 1 organized place, so you don’t have to whip out Google or the Forum Search to find that cool native synth or that tip on phaser-techniques. got a PM from esaruoho asking if he could use some of it for something (still waiting for the explanation), asking if that was ok. for anyone reading this: that is perfectly ok, for the simple reason stated above, it is not my work, it is simply a collection. all i ask is some credit somewhere somehow, be it in a script comment or a forum post or a mention on your blog or whatever.
(everytime i smoke weed i have a tendency to talk too much. i am shutting myself up now, back to my first electronic-reggae-attempt)
ok, per the request from MMD above i have changed the GUI a bit. should be a lot easier on the eyes now, i think. i’ve traced some images to get them as transparent background .png, and they look pretty good if i say so myself. the pattern effects was a bit of a problem so i left that as it is for now. it does have the dashed border like the other images to make it stand out more, or something. and, i made the default view the effects + midi, instead of just the non-midi effects.
let me know what you think. (you might have to do a Ctrl+F5 (reload from server) to see the changes).
edit: went back in and changed some more, including the pattern effects image which i redrew completely. also removed some little mistakes from there, and improved the readability a bit. made the XML for the DSP Devices easier to select. gave the links and tips/tricks sections some columns and some changes in fonts etc. to optimize readability and give it a cleaner look.
re-read some of MMD’s In:Depth articles that i hadn’t linked to yet, and placed them in the links and tips/tricks section (thanks again, MMD!).
Awesome. ++
added my own Renoise Top-Right (instrument list) Customization thread to the cheatsheet tips&tricks list. because it’s awesome.
forgot to add this one a long time ago: the MASSIVE (not the software, but massive as in, huge) adventure kid waveform collection, for all your single-cycle needs. seriously, i rarely use anything else. http://www.roaldblijleven.net/renoise/cheatsheet/links.php
I’ve got a request to add to your cheat sheet.
Equation needed to tune a single cycle waveform to A-4
Afraid I’m too tired for my brain to work today so was hoping it’s on there and thus can’t instantly provide it for adding 
Or is it not even possible with basic calculations and trial and error against a tuned (eg vst) source a better idea?
well, i have no idea myself how i’d got about doing such a thing. i suck at mathematics so even the word ‘equation’ is scary to me. if you would want me to put something like that up on the Cheatsheet you’d have to provide me with the details yourself i’m afraid.
well sample rate divided by length of sample gives frequency at base note.
Then once I’ve done that I go to this Wiki page and see what note it closest
But no idea how to then work out what amount of fine tune I would need!
damn that sounds like tedious work. there’s gotta be a simpler way, right?
I always wonder: should I adjust the basenote in the Sample Keyzones, or should I use Transpose in the Instrument Settings?
There are no steadfast rules but personally I always use Instrument Settings for anything sample based (IE tuning an individual sample) and Basenotes only for multisampled instrument assignment.
this makes sense to me.
cheatsheet tips&tricks section updated with my own Sorta Auto-Pan thingy (with xrns) and my own Alternative Native Delay trick > http://www.roaldblijleven.net/renoise/cheatsheet/tipstricks.php
The formula for frequency to midi note is: midi value= 69+ 12*log[sub]2/sub.
Fine tuning is 1/128 division of a semitone, so just multiply the decimal part of the midi value above by 128 to get the fine tuning required, which in this case will always be positive.
I wrote a script that does this calculation, which began because I had no idea how to find the frame length of a sample from inside Renoise. Anyway, it also converts to scientific pitch notation, saving any need to look up wikipedia, since I couldn’t find midi values in Renoise.
--calculation functions
function log2(x)
return math.log(x) / math.log(2)
end
function round(num)
if num >= 0 then return math.floor(num+.5)
else return math.ceil(num-.5) end
end
local samp_ind = renoise.song().selected_sample_index
local inst_ind = renoise.song().selected_instrument_index
local chosen_sample = renoise.song().instruments[inst_ind].samples[samp_ind]
local frames_selected = 1+(chosen_sample.sample_buffer.selection_end - chosen_sample.sample_buffer.selection_start)
--print(("Frames Selected: %s"):format(frames_selected))
local sample_rate = chosen_sample.sample_buffer.sample_rate
local freq = sample_rate/frame_total
--Converts to decimal MIDI value
local conversion = 69+(12*log2(freq / 440))
--print(("MIDI value: %s"):format(conversion)) --not needed
--Converts from MIDI to Letter name
function letter_name(x)
local midi_pitch = round(x)
local octave = math.floor((midi_pitch-12)/12)
local letter_table = { "C","C#","D","D#","E","F","F#","G","G#","A","A#","B" }
local letter = letter_table[(midi_pitch%12)+1]
print(("Note: %s%s"):format(letter,octave)) --prints A4 etc.
return letter
end
letter_name(conversion)
--Displays the fine tuning (negative or positive)
local finetuning = (round(conversion)-conversion)*128
print(("Finetuning: %s"):format(finetuning))
OK changed so that it calculates selected frames in the sample editor. If none are selected it calculates for all the frames.
@JupiterXLI: well, since i only half understand what you guys are talking about, i hope kazakore is very happy with your post! not sure if i should put this on the Cheat Sheet though, as only kazakore started about this, and now that he has the code he could just use that… or am i wrong? only thing i could do is place the code online or something as i don’t know what to do with it