Micron Editor (Micronizer) - need ideas for update

I did a fair bit of work on the micronizer editor a little while ago (over a year, maybe 2 years ago).

My version of it is in the files section of the Yahoo group....

Anyway, I've been thinking about working on that some more: the code is not in good shape at all - it's an MVC type of architecture and very sloppy, plus it's in C++ which I haven't really used in over 10 years (so I'm pretty rusty).

Anyway, what I'd really like would be to find an easy way to create a sound-diver style interface, with adsr displays and associated sliders, that kind of thing. The project currently uses WxWidgets, and was meant to be portable to the Mac.

I'm looking to fork it to the PC platform, so WxWidgets can go...

Do any of you cats know of any freeware (even source code is fine) that can allow me to relatively quickly develop ADSR and LFO waveform displays?

I don't really care what language it's in as long as it's not Python or Smalltalk...

Thanks

I would really like to be able to be of some assistance with this. Unfortunately, I know nothing, so all I can offer you is thanks for the work you've put in on it.

It looks fine to me.

Cool, I didn't know the author of Ionizer was a forumite here.

I'm still stuck in VB6, so there's not much I can do to help......

open frameworks is pretty sweet if you want to stick in C++, is completely cross platform (windows/osx/linux), ridiculously simple, and LGPL.

Well, to give credit where it is due, the program was written by Hector Urtubia, but abandoned some time ago.

Myself and another individual fixed a lot of bugs, making it capable of real-time editing on the PC platform, and brought it up to version 1.7.5.2.

I'm going to rename my effort to Micronizer+, to avoid confusion with the older BETA 3 version, and hopefully secure some webspace to host the project.

The Micron firmware is interesting to say the least - it took a lot of looking at sysex dumps and head scratching to figure out some of the quirks in how parameters are mapped from the editor to the sysex: first on my list now is trying to find a way to get the micron to dump it's edit buffer without activating the "Send Sysex" function from the front panel.

Very cool !! As a Micron owner, and software engineer, I really appreciate the effort !! Do you have a website ?

Very cool !! As a Micron owner, and software engineer, I really appreciate the effort !! Do you have a website ?

No, not yet.

Currently I'm using the yahoo micron/ion list to host my efforts. (look in wades_files)

Getting a stand-alone webspace is on my list though.

I am currently working on fixing the sysex import/export functions.

I spent several hours on it last night and now have the header information properly encoded.

Hopefully tonight I can write some diagnostics which will allow me to dump the decoded body of the sysex - I'm using a hacked version of the Micron Perl Decoder as a reference and will go through the sysex byte by byte until I can be sure that the Micronizer is correctly placing all values in the sysex dump.

I also came across a cool set of wxWidgets components that may help me in my quest to add waveform displays for the LFO's and ENV's.

But I plan on getting the core sysex and NRPN handling working perfectly before undertaking that.

One last thing - there's a lot of confusion because the original maintainer stopped his work at beta version 3; many functions that do not work properly in that version have been fixed in mine.

So what I plan to do is update the name to avoid confusion: I'm thinking "Micronizer Plus"

Alesis did a real good job of making all the parameters available in a small amount of space without having to resort to a computer to edit it.

But a lot of people say the problem they have with the Micron is editing it. I think a lot of people are also coming to expect a manufacturer to provide a software editing program for their hardware.

I don't have a problem editing it from the hardware, but I can see where it'd be difficult for someone not familiar with it.

I have mixed thoughts about this, because while a strange little beast like the Micron cries out for an editing program, that same program can become sort of a planned obsolescence. It's something that has to be (or should be), thought about years after a synth has been discontinued. And if a manufacturer releases an editor, it'll generate some bad press if they don't continue to update it.

Leaving it up to interested users is good for while the interest lasts, but there's also no guarantee that a synth will generate enough interest from people with the required programming skills for an attempt to be made at making an editor. The Alesis Fusion comes to mind here. I don't thnk anyone's attempted an editor for it - it's pretty complex with all the different things going on with it.

The Micron generated enough interest that at least 3 different editors (that I know of), have been started for it.

Just rambling.

the real trick would be to make some sort of open source universal editor that could read each synth's sysex implementation from xml files. xml patch files would be tasty too.