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!
a few sites i’ve found lately, during searches for ways to brain-storm, optimize, streamline, expand, … the low-level parts of axonlib and other code:
haven’t completely consumed all knowledge and ideas in there yet, as there’s a lot of info and hints….
Chris Lomont’s Publications page
Toshi’s Project Page
be nice to your cache
bit twiddling hacks
A Whirlwind Tutorial on Creating Really Teensy ELF Executables for Linux
creating small win32 executables
techniques for reducing executable size
references on coding for optimization on x86 architectures
the impossibly fast c++ delegates
member function pointers and the fastest possible c++ delegates
const illustration in c++
rant on c++’s operator new
optimizing c++ (pdf)
c++ and the linker
hidden features of c++
source code for data structures and algorithm analysis in c
c++ for c programmers
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…
some more smaller updates to axonlib:
later today (or tomorrow) i will pack the current revision to a zip file, put that up on google code hosting for download, completely erase the files currently in there, and upload this newer version, even if it is broken and uncomplete at the moment (that’s why i’ll put the zip file there as a backup if needed), and possibly bumping the version number up to 0.0.99. when everything is in place again, there will be a 0.1.0 official ‘release’.
the two main (bigger) missing pieces is the win32 and vst audio/midi stuff. but this ought to be just a few copy/paste actions to get working… i have concentrated on getting the event/message passing right first, focusing on the class (inheritance) hierarchy, and having a smaller code-base to concentrate on during that, makes things easier… then i just fill in the blanks, copy/paste’ing from the previous version…
i’m very excited about this new version, and am already looking forward to making proper plugins and applications with it!
just wanted to inform you, in case you wondered where i’ve been hiding…
i’ve been disconnected from almost everything for a few weeks now… it’s been a good, quiet period, very productive.
been recoding axonlib from scratch.
i started to notice some problems in the original code design, and some other things i became more and more dis-satisfied with. things that hindered natural progression, that made it difficult to add new features without breaking everything..
something needed to be done…
i initially wanted to do the changes slowly, one by one, in the current project, but i soon discovered that the low level changes made everything on top of it incompatible, so i would need to go over everything anyway, to clean it up, and tie up the loose ends…
so, i started from scratch, re-designed the class hierarchy, and started to fill in the blanks from there, a lot of copy/paste from the earlier version. now it will compile correctly again, and i have enough of the basic parts in there, working properly, that i can make simple debug/test plugins and applications.
the main low-level changes:
a few days [or worst case: week(s)] and it will be ready for a v0.1.0 i think. the missing bits and pieces is more or less just copy/paste into the new class hierarchy…
i also need to consider how the ‘upgrade’ will be done in the google code repository. should i make a new, separate project, or a separate sub directory in the existing project, or delete everything currently in there, and upload this new version over it?
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… 🙂