the gui-less version is up’n’running, fully functional, but give me a few days, and you’ll be able to play around with it.. and no, i’m certainly not a graphic designer!
cernobyl audiogenics, and its alias, ccernn.audio, has just invested in a new machine, a laptop, and, in almost all regards, it’s different from the box, it’s got an intel processor, an avi graphics card, and running win7 64-bit… an interesting challenge!
an opportunity to try the axonlib plugins in their ‘real world’, a very different (and alien) world than i has been used to… so, quickly, with lots of helpful hints from neolit123, a quite suitable development environment for axonlib were set up. mingw, codeblocks, rapidsvn, .. and it almost felt like ‘home’ 🙂
and i’m proud (?) to tell you that i just compiled the first ‘working as expected’ exe file for windows, in windows.. quite a feat…
there’s some serious problems with the win32 support in axonlib at the moment, but with both os’es now available, and neolit123 helping, i hope it will be fixed quickly..
so, hopefully there will be plugins and binaries arriving soon…
i fokkin’ hate unstable and resource-swallowing synthedit/synthmaker stuff, so i often use this simple script (linux) to check if a plugin .dll is made with synthedit: (in addition to looking for a subdirectory with a bunch of sem/sep files):
strings $1 | grep SynthEdit
if it prints out anything, it’s a SE plug, and into the trash it goes. not interested…
now if i could make something similar for synthmaker, things would be very good…
i could of course just ignore them, not download them, but plugin authors often don’t mention that their creations are made with these tools, and, if you start playing around wtth it, and have some inspirational moments, kaboom!! your daw crashes, and you lose everything, all those hours wasted.. so, i would rather not take the chances.. and you can even risk not being able to open previous project files if you forget to render to audio and delete the plugins before saving… additionally most of it is generic sound-the-same crap anyway…
i’m setting up a new page with various audio related code projects i’m working on
that will eventually replace other temporary stuff i’ve put out, like:
i have 4 or 5 plugins ready now, and will package them properly with source code and everything, make some example projects, some tutorials, how-to’s, some presets, and then upload them in a few days.
expect something else than your boring, typical eq and dynamics stuff. not for hifi freaks, but for the experimental people, fort those that have an open and explorative mind… 🙂
even more jesusonic plugins! i can’t stand still!
a simple plugin i made to test the performance of various jesusonic internal commands and structures. useful for benchmarking, learning, … among other things, you can test it on multiple tracks to see how reaper and/or your os (of choice, or by force) balances the workload. i saw quite nice things here, on linux, with four tracks, this one in each of them, some cpu heavy tests…
another test-plugin. this time for testing various methods of communication between plugins, tracks and items.. have multiple of these, in various items and tracks, and start moving the set sliders. it takes a while to get the feeling of what’s happening, but i think i’ve got a pretty good idea of how local and global memory, plugin execution order, etc, works, but, the more i experiment, the more unsure i get at times… threads seems to be jumping back and forth between the cpu cores (some load balancing going on i think, by reaper or linux, i don’t know), and that seems to sometime change the order of execution of plugins in tracks or items.. more experimentation needed, as always, and it could be nice to have midi in there too.
an experimental in brainwave synchronization and binaural beats. it generates one sine wave, frequency controlled by playing midi-notes, in the left ear, and another sine wave in the right ear, with a defined, constant difference in the frequencies. most of the stuff i’ve been reading about binaural beats, involves boring stuff like hours of an almost static sine wave. and then this idea about making it midi-controllable, and play the main frequency, might call it the carrier, as a melody.. have no idea if the binaural beats effect will (still) work. more experimentation to do.
a very simple kick-drum synthesizer, inspired by the similar plugins in fruity loops, and lmms. and i got the main inspiration from an idea to make a remix of the included demo tune in reaper (a version of brad sucks – making me nervous), using only my own plugins. this song have only a kick drum, so it was/is a good excuse to test this.
karplus-strong, plucked string, waveguides. lots of fancy names for a simple delay line, a bit of noise, and some filtering… play with midi, it’s only monophonic. just wanted to test the principles. maybe later a monster synth thing to incorporate all synth ideas and tests.. ?
my ‘favourite’, a phoneme synthesizer, or speech synthesizer, but simplified down to the audio-generative black-box. i have made several versions of this now, and get a better understanding of everything each time i do… my plan now, is to make separate plugins for controlling this. one plugin for holding a phoneme table (reatalker settings + crossfading info), another plugin for selecting, and crossfading between these phonemes (A->I) , and a third one for a list of phonemes (‘Tis is ey testh+’, but with sliders/numbers), and even some more, for making words triggable via midi-note (n-n-n-nineteen).. also, it’s a kind of emulator of the computalker ct-1, hence the name reatalker, heh..
now i really have to sort and finalize everything into a plugin pack, or some plugin archive… i have been planning to upload these, or proper versions, to stash.reaper.fm soon too. i’m on my way, but i’m so much more motivated to experiment with audio than writing documentation and uploading and stuff… and it’s hard to decide when (or if) a plugin is finished, as i constantly do small modifications, tests, some copy/paste, etc…
but, currently you can find the plugins here:
i will set up that site properly to be the main place for my plugins, and will start updating documentation, previews, screenshots, etc, soon.
btw, jesusonic is a (dsp) programming language built into reaper, where you can do almost whatever you want with audio, midi, graphics, mouse, etc, … an amazing experimentation platform! download the plugins somewhere, and move them into <your reaper installation directory>/Effects/ccernn. and, to learn more, have a look at the sources
…and, doing kkoagulaa mixing inbetween, and sometimes at the same time as this makes my head twist and turn in lots of unknown directions…
ok, more updates.. found some interesting formant tables via the almighty google, and was really surprised. now i need to work more on the plosives and non-wovel sounds… oh, how i enjoy this!
this one is only using one saw/noise oscillator, and two formant filters. tried with 3 and 4 filters, but decided to use only two, because of performance (as if i really care about that, hah), and because i don’t have any good/better formant-frequency list… takes ages to find a decent set of frequencies/phonemes from scratch, that sound even reasonably convincing.
a new mp3, spent 15 minutes trying to make it say “reaper can speak, reaper can sing”.. well, don’t know what to say about the result…
and, until i can get myself together to finish the jesu.ccernn page update, download and play around with the jesusonic source. note that this is not finished, its pre-alpha/beta, might crash. additionally, import this into your reaper midi editor, to have the midi-notes show their phonemes.
not much documentation yet, so you have to experiment. just ask if there’s anything…