Nice!
 
I was not aware about Lua till wst3 has mentioned it about a week ago. And I have to create easy to use binding for DX API (not one to one, I want it simpler), sandbox and control execution to prevent sonar crashes / real time engine disturbing from endless loops in musicians code and distributing viruses as plug-in presets by "smart" hackers   
 
And so once initial prototype is ready (in days, may be 1-2 weeks), I need help from 2 categories of users:
* Lua experts, to check that I have no horrible design mistakes (I see many Lua fans in Internet which are quite aggressive once spotting bad Lua code) 
* unexperienced in plug-ins programing "beta testers" to check the result/documentation/tutorials make sense (for me it make sense by definition, so I can not judge myself)
 
Just to mention: the project well be freeware but with closed source (at least for now I have no plans to publish it, everything I use is "clean" for almost any kind of license). Current plug-in size is 300 kB (single DLL, Lua interpreter build-in) and it is not going to grow much. The interface is from XX century, but unlike any other DX I have seen it can be resized (well... maximize button is grayed by Sonar, but border resizing is working).

azslow3
* unexperienced in plug-ins programing "beta testers" to check the result/documentation/tutorials make sense (for me it make sense by definition, so I can not judge myself)

I am not sure that I will have time to check everything, but I would be happy to try write some plugins for myself. I haven't done it before, and only heard about Lua few days ago. So totally unexperienced. But I have some programming experience, mostly on Delphi and years ago. Anyway I am not afraid to learn something new. =)

Delphi was good... Lua is not a problem for you then, I think is is more Delphi then CPP (if such comparison is possible at all). My MfxEvent class has "properties"

azslow3
Delphi was good... Lua is not a problem for you then, I think is is more Delphi then CPP (if such comparison is possible at all). My MfxEvent class has "properties"

Nice!
So please let me know when it is ready and I'll try! Thanks!!

Isn't VST Module Architecture how VST MIDI plugins are done?  Different from the VST we're most familiar with ...

BobF
Isn't VST Module Architecture how VST MIDI plugins are done?  Different from the VST we're most familiar with ...

Can you point me on some information which confirm it is supported in Sonar? The only information I have found so far:
a) it is pretty "old"
b) some plug-in in this format was not recognized by Sonar 4
c) the question "what should I use?" in forums is normally answered "VST 2.x/VST 3.x".
 
One post from KVR (mbncp, 2008) more or less summarize the spirit:

That stuff is pretty buggy and totally abandonware. Woulddn't be suprised to see it gone in the next cubase version.

 
But in case there is any evidence it can work better then normal VST in Sonar, I can give it a try.

I have nothing for you Az other than having seen it a few eons ago while grabbing the VST SDK.
 
The only DAWs I spend any real time in are Sonar and Reaper.  I've never seen MA mentioned in either forum, despite having read that MA was the MIDI side of VST.  But agin, that was a while back.
 
OK ... I just downloaded the MA SDK to have a look.  It appears that V1.0 in '04 is the last update.  Please disregard all mentions of VST MA above.   
 

 

I just downloaded and checked the current VST SDK.  It appears that MA has been folded into the VST3.6 SDK.  I did some poking around in the docs and found zero references to MIDI
 

If there are some example, may be you can test either Sonar recognize them. May be I will look later. At the moment I want finish at least simplest working version of my AZ Loa and I have already delayed WebDAW feature in AZCtrl and some other fancy staff...
 
My last attempts was with VST2.4. Simplest "MIDI repeater". I have got the whole set of problems with it: delay in forwarded MIDI (also DIFFERENT for live and recorded material, in the last case Sonar compensate it, in the first not), random loosing assignments for MIDI tracks connected to the plug-in outputs, especially if I try to "record" the input from another track (input is reset to omni, triggering "MIDI loopback" with logical consequences) and random hanging notes, at lease on X2 (I remember there was some fix in future Sonar versions). Many people use VST MIDI more or less successfully, but I do not like such flickery environment.

It seems that VST midi outputs don't work really well in Sonar, at least for me. I use some VSTs to control my hardware synths, Ctrlr staff and other, and I never couldn't make it work through Sonar internal midi path. I always use midi loop drivers for it. So if I set VST's midi out to the midi loop driver (in plug-in settings), and use this driver as midi track input in Sonar, it works fine. If I set plug-in to output midi to host, and route its output inside Sonar to other midi track, it always cause some troubles, some data are lost or corrupted in this way.
Also I made my own VST3 plug-ins with midi output, and tried to test Sonar midi with them, and it seems there is something not good with it, but I couldn't say what exactly the problem is.