azslow3
rogeriodec
But we are currently "hostage" to CAL Script, annoyingly limited and outdated.
Band Labs, meet this request: invest in a more advanced scripting interface for the user!
You and all users will benefit from this!
Some time ago I have seen that... And one of the users has suggested Lua as an alternative (I guess based on REAPER success in Lua scripting). I have decided to have a look at that language and even "invested time" into a possibility to use Lua MIDI processing in Sonar.
Result? NO ONE, not even the user which has asked for that, have ever tried to use the possibility.
So sorry man, I seriously doubt someone will benefit "from this".
I can't see this happening either.
As I mentioned in another post, I've got a rough design for a LUA implementation using the ControlSurface API, however in order to do per-event MIDI processing it would mean programmatically writing CAL scripts on the fly and running them in the background.
In the end, I decided (a) It would be a horrible hack, and (b) I've not got the time to do it any way.
Unless BandLab extend the API to included access to the track data, only BandLab can implement this sort of thing in any reasonably clean way.... and extending the API in a "safe" way is not a trivial task, so I don't see that happening either seeing they've got a small team.
Given that Reaper is pretty cheap and already has scripting capabilities, it might make more sense to do your MIDI processing in Reaper and import the MIDI back into Cakewalk.
There's no rule that says that everything must be done within Cakewalk.... I mean plenty of us would quite happily use SoundForge as an external editor for audio, so I don't see why MIDI should be any different.