Today:
- more filter tweaking, still not totally happy with it – but will leave it for the time being
- implemented saturate, replacing the algorithm I was using with a better one too
- implemented EQ too… although it’s more of a lo+hi filters combined, but it’s useful for building certain sounds (e.g. giving a metallic twist to a hi-hat generated entirely with rand() noise and a quickly decaying volume envelope)
- plus fixed and polished more bugs/things!
I was going to add an audio sample but I’ll wait for when I have something more musically interesting…
I have also decided to stop porting/adding more features to the synth and begin working in the mixing, export and sequencer side. I will probably add something else (I was thinking of LFO’s) later, when/if I need them for the song I build.
Besides, building the interface between the VSTi and the actual synth is boring to death! I need a break from this side.
This is going to be an strange process: usually, when I start a demo I already have the song ready and finished, and now I only have a general idea of what I want, but I do not have music or graphics or anything yet. I don’t even know if I’ll manage to build the Windows binary on my own! haha!
But hey, we’ll see! :D
dp
But then one question pops out, you’re making a synth without any size limit right?
sole
Of course I’m not bothered about size limit! I don’t know why all of you are insisting on this being a 64k intro :D
I just want to concentrate on the audio quality, and forget about size limitations. This is going to be a proof of concept demo :)
dp
I guess we insist because we’re more used to it. Neverthless do how you feel. Btw: are you thinking of leaving vsti appart? what I like of working with raw data is easiness of development. Make it quick, make it better. :) that should be my motto.
sole
I see!
The VSTi part is just a wrapper/helper for sequencing the song and specially finetuning the synth’s parameters.
When I made the first version of Sorollet I had no way of playing with the values of the parametes “real time” and if I had done so I would have spotted lots of errors that I have found these past days, since some values (for example, the resonance and cut frequency in the filter) interact between them and their ranges need to be adjusted properly so that the output doesn’t go saturating all over the place :)
Back to the technicalities, the VSTi contains an instance of SorolletVoice. That’s all! And Renoise (or any other host) is the one performing the sending of events to the VSTi and mixing all channels. For the final demo, two nice classes called SorolletPlayer and SorolletMixer will be used, and in a way they act as a “lighter” Renoise.
So this way everything can be sequenced way more comfortably than writing your song in a .h file, because Renoise is a PROPER sequencer, much better than whatever I can build in two months.
And the good part is that things get synchronized “for free”, thanks to having access to the song itself, instead of having to extract interesting stuff manually once we got an MP3 (which is a horrible process).
I think of this as a mix of traditional tracker synchronization and sound technology for intros :)