… but let’s please avoid that everyone’s branching a new tool from an existing tool, just to add a single new feature to it.
If you have made some improvement for a tool, contact the author of the tool and work with him together and let’s update the original tool. Lets collaborate on this. You both are already in contact, but just wanted to have that said again …
Yeah. If someone makes some new features in scripts, they can send patches to the original author. No point in creating multiple forks of tools under tools.renoise.com, unless it is ideologically different, merging the features is impossible and the new fork offers some benefit over the original.
yeah well it’s nowhere near “finished”… well, actually it nearly could be I figure, but besides that I’m not sure if it’s okay to insert all those individual conditionals, I’m kinda puzzled by one thing:
how do I (in the function generate()) detect if the sample length changed (so I can skip the creation of a new sample in that case)?
I tried “buffer_new.number_of_frames == real_cycles*int_frames” but that never triggers scratches head
Try math.floor(real_cycles*int_frames)
Theres just one number in Lua and thats a double precision floating point number. Can be quite confusing if you’re new to Lua…
who I said I even dreamed about doing this? I specifically asked about forking, pm’s and diffs, way near the top… and most importantly, if there is a place that gets called when any notifiers change GUI buttons/sliders get changed. that kinda should tell you I’m really trying to actually produce something that can be used and reintegrated, instead of just something that does what I wanna do and upload that.
but since I’m really poking around in the dark alot, I either am chatty and a bit of pest (it’s not like you have to answer my questions, but I need surely to ask them, be it just to answer them myself later on), or I just fumble around with something that will eventually benefit nobody (or would take more work to patch in than for someone know already knows what they’re doing to do it themselves).
YAY! that did it. it’s a bit clicky when updating, but otherwise it seems to work perfectly! unless I forgot a notifier for some GUI element of course. I will review it later today, make a note of the changes and send that to it-alien.
and yes, I really need to read some basic LUA tuts before I progress further, I don’t know anything.
I vote for github.
Git is way better than SVN for such a thing (note: not EVERYthing!), as it is highly community driven. The distributed nature of git works like a charm for such projects, as you don’t have to manage commit rights. It takes a little time to get used to the distributed, fork-driven development, but it’s worth it. I tend to manage all of my private coding using git, whether public or not.
Just my 2cents. Back to topic 
well, the latest news is that somewhere between cleaning it up, adding stuffs I broke it haha… the thing I sent it-alien stops auto-updating as soon as you change operator tabs, and I swear it didn’t do that earlier 
I am really clueless as to why that’s happening now, and to be honest there’s only so much staring at code I hardly know I can take in one day, so I’ll have another go tomorrow I think…
fixed! I think.
I don’t know if Johann is referring to the fix I have sent him some minutes ago, anyway I have also fixed it 
this auto-generation system works very well and it is very comfortable to use; I actually think the “Generate” button is superfluous now and should be removed, leaving auto-generation always enabled, what do you think?
edit: if you want to try out the automatic generation in order to decide if Generate button should be removed, use the attached version
I’m gonna FUBAR that waveform generator once I get beta 
This really works great for very small waves! At base note C-0 this is very noticeable though. I’d keep it as option. Maybe simply turn it on by default?
And here’s a patch (well, file) to make the GUI pretty again: 
yeah, it “breaks” (the continuous playback) quickly with longer samples, and
I was referring to the two emails I sent you after that and the attachment, which got lost in transit (I got the failure notice two hours ago uhhh?), and I just now resent:
so yeah, even though I didn’t know WHY, I found the fix already 
^^
unless you made other changes in the meantime, please take the file I just resent.
I also started to add sliders, that is for “number of real cycles” and the “frequency multiplier” of operators, and that’s kinda neat as well, but the slider shows also up for wavetypes where it shouldn’t (e.g.) noise, so I’ll keep that to myself for now harrrr.
you know what, I’ll just download that and do the two little changes of mine that got lost to that, and upload it here?
for some reason I’m not getting mails from you anymore. please check the errors you received
“I’m not going to try again; this message has been in the queue too long.”
sounds like a love song, but that’s the failure notice 
Okay. I downloaded what It-Alien uploaded, overwrote gui.lua with the one taktik posted and then I applied my two changes to it.
I also added a slider for “number of cycles”, though that may not be everybodies cup of tea… well it can be easily removed, consider it a suggestion ^^
I tried adding a slider to frequency multiplicators of operators, too, because there it’s actually useful, but it shows up even for wavetypes where it shouldn’t (e.g. noise), so I left that out for now.
(note that manifest isn’t updated and still at version 0.4)
well I wasn’t so sure about that, since it overwrites samples as soon as you touch a slider?
about number of cycles as a slider:
I’m not sure this is the best option: you usually need a precise, integer value of cycles, that’s why I think that the textbox is a better choice
Spinbox maybe?
you still have that, they’re just linked. (which by the way couldn’t hurt for the amplitude slider/text field combo?)
but yeah, for the cycles thing it’s really not that useful, if not to say useless, just a random thing to try haha…
for the frequency multiplier of individual operators it would rock though, because you can change that one without the sample length changing => without playback stopping (unless the sample is too long), though maybe one of those thin sliders would be better (?)