ax incremental update

some more smaller updates to axonlib:

  • linux: separate event thread & display connection, now it works in Jost too (partially)
  • improved mouse event handling vs container widgets (hovering, doEnter/Leave messages, etc)
  • modular audio graph preparations

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…

– ccernn

i’m very excited about this new version, and am already looking forward to making proper plugins and applications with it!

been hiding…

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:

  • cleaner, more uniform class hierarchy, better handling of platform dependent classes
  • removed the necessity of most (or all) flags/defines
  • no more global variables
  • changed handling of canvas/gfx resources (color,pen,brush,font)
  • skins
  • low-level vst, using the AEffect struct directly
  • standalone executables from unmodified source code (axPluginExe wrapper)
  • better exe/plugin main/entrypoint handling

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?

– ccernn


experimenting with a logo for based on an ancient viking symbol, valknut, also sometimes called triquetra (i think). work in progress, this will probably change quite a bit…


what do you think?

– ccernn

kkoagulaa reviews…

the reviews are starting to appear:


v0.0.0, preview

things are happening…

…end all…

fåfengt, fåfengt, kryp der nede..
døy? eg er udøydeleg!!

“…but, but, i read it on the internet… it must be true…”

you fools!

– manes[ss]
being all/ending all

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…