I would like to use a LFO-device that’s synced to the speed of the song, and when stop playing the device is also stopped.
Hard for me to explain but I hope you understand what i mean?
Agree. To be able to sync it to x number of lines or x number of ticks would be great.
While on the subject I would like see a few more wave types as well: reverse saw, triangle and random which slides between the values.
as far i know LFO is synced to the speed. 100% frequency is one full LFO’s cycle per frame (6 ticks), 50% is half LFO’s cycle per frame, and etc. just use LFO reset in the start of patterns and you’ll get full sync.
Thanks Zed, I didn’t know of this… Still a simpler, more intuitive solution would be preferrable. A sync which follows the tempo changes so you don’t have to worry about reseting the LFO.
you’re welcome… actually, tracker is tracker, you have to program the music(not draw by mouse), that’s the tracker philosophy, it’s the basis which always should be in. and that’s quite important because your brain becomes more effective in general while you’re programming. i mean you always should think how to make sound the way you need, your brain work in “problem>solution” mode all the time. that’s what makes you actual human. imho, the tracker should not be too much comfortable, it should be fast, and bugless.
Well I don’t agree with you at all here. First of all I think it is a difference between programming music and creating, but I do see your point.
Secondly, addin a sync button would still keep the old way of working. And thirdly I think it’s faster to press a button once instead of adding several reset commands on different locations you’d have to keep track of.
well… i was talking in general… i didn’t say creating music equal programming… i meant there are a lot of programming element in there…
honestly, i don’t need sync button, i don’t need pianoroll, i don’t need skin support, and i don’t like renoise developers waste time for that, that’s my imho…
Well if features like this will result in more registered users you will gain from it as well in the long run… 
well, as beta-tester i can say that my ass costs more than you think
Hmm, to some degree I agree. What really feels lika a overkill is the skinsupport.
Because I don´t think there will be lots of skins made, if any? After all this is not a player like winamp, nor is it a synth like rebirth.
On the other hand its important that the developers who has put their soul in this product also gets to do some features that they enjoy doing. Otherwise they might grow tired of developing it…
And it will make the product look better, and small things like that gives the product a soul…
I agree too regarding skins, and I’ve never hidden my disappointment about them, but seems like a lot of people asked for them, so ok, let them be…
the same goes for pianoroll, though in this case there are two differences:
- a lot (which is different from a simple italic lot
) of people asked for them and would be interested by ReNoise with this new feature - it is a composition-related feature
so I “surrended” to it.
About the synch button: I’ve requested it about one month ago, and I don’t think that having it would turn ReNoise into a babytoy nor let me feel less a programmer; it will just give a more coherent design to the LFO.
…and I’ve tracked for years having an hex calculator on my left…
but now I have much less spare time, and having the chance to choose to save some time by pressing a button is not a crime, according to me.
We know for a fact that many users never even try using Renoise after downloading it, because they think it’s too ugly and just shut it down almost at once. You may call it stupid if you wish, but people are different
oh come on, give this shit a break. I want to make music, not program. I do not care shit “how” you made you music, if its good its good.
and sorry to bug you it-alien, but calculating hex with a calculator is l4m3, back in my c64 days I calced hex in my head (atleast plus and minus).
no, jokes aside, this is the second time something like this starts to pop up (if I remember right), people who are fearing their cute little elite-status gets lost because the tracker they use gets user-friendlier.
For me, I want every single option anyone comes up with to be implemented if it makes it easier for me to make my music.
and come on, if you are really arguing about a sync-button for the lfo to be “too much comfortable” then you should go back to protracker on amiga or whatever.
taktik, maybe you should do some “hardcore version” for renoise aswell, deleting everything which might be “too userfriendly”. good thing would be that this version would be finished right at this moment because as I see everything which will be added to renoise now just makes it “userfriendlier” or adds features offering solutions for things which can already be done going an insanely stupid hard way.
looza,
I use hex calculator for BPM/speed changes, when for example I have to change speed from 15 to 6 and then change the BPM accordingly.
Most of times I convert the current BPM value to dec, make the multiplication, then convert it back to hex all in mind, but next time I’ll give you a call and you’ll help me on this, ok? 
About the rest of your post,
yes, this “oldskewl” discussion died years ago; I still look at myself as a “music programmer” because I actually program each event in the song and that’s why I’m a proud tracker user, but if you all need a skin for your inspiration to be born… well ok… I will second you
How about deleting the UI and make a console version based on hex values?? 
kinda like povray for music … with its own un-understandable script-language.
Welcome to audiogeek’s paradise
The problem is, the LFO starts differently every time, so it’s difficult to
predict how it’s going to sound and it seems even impossible to get a grip
on it.
You can reset the LFO device with a command : X600 (with X = number of the effect in the chain). You also see what you have to type in by pressing the LFO`s “Reset” button.
If I’ve got what you mean, your solution should be LFO reset command:
x600 to reset the LFO, where x is the LFOdevice position in the DSP chain
edit: argh… this time taktik preceded me by a whole pair of minutes… 
damned editing care 