MSF et al: a Scripting module
-
- KVRAF
- 10366 posts since 2 Sep, 2003 from Surrey, UK
Here's a radical idea.
How about having a Scripting module?
This would allow the dedicated users to write their own scripts for processing audio or MIDI. So for all those cases where the modules and other features do not do what you want, just write your own. Keyboard splits with cross-fading to name but one idea. Or a different filter implementation.
Think of the lua and JS FX scripts in Reaper. There are hundreds of each now available to users. And. I'm sure, they boost the take-up of Reaper.
User-scripting in MSF would match, or overtake, Kontakt and Falcon in that area.
https://www.uvi.net/uviscript/
https://www.uvi.net/uviscript/_tutorial.html
How about having a Scripting module?
This would allow the dedicated users to write their own scripts for processing audio or MIDI. So for all those cases where the modules and other features do not do what you want, just write your own. Keyboard splits with cross-fading to name but one idea. Or a different filter implementation.
Think of the lua and JS FX scripts in Reaper. There are hundreds of each now available to users. And. I'm sure, they boost the take-up of Reaper.
User-scripting in MSF would match, or overtake, Kontakt and Falcon in that area.
https://www.uvi.net/uviscript/
https://www.uvi.net/uviscript/_tutorial.html
- KVRist
- 428 posts since 23 Jun, 2012
But I can already see the answer:
"The existing structure of the plugins is too complex and cannot simply be converted to a scripting language. There would also be far too many ways to outwit and crash the plugins. Imagine what everyone would try to write about possible things that are, in the worst case, hearing-impairing.
There is also far too little development time."
Or something like XD
-
- KVRAF
- 1758 posts since 11 Nov, 2009 from Northern CA
And then, maybe 48 hours later: "Never mind, I figured it out and it will be in the next beta available in a couple of days."Faiky wrote: Mon Mar 02, 2020 3:20 pm
But I can already see the answer:
"The existing structure of the plugins is too complex and cannot simply be converted to a scripting language. There would also be far too many ways to outwit and crash the plugins. Imagine what everyone would try to write about possible things that are, in the worst case, hearing-impairing.
There is also far too little development time."
Or something like XD
-
- KVRAF
- 2508 posts since 24 Jul, 2017
There are sandboxing mechanisms available to make it more stable. I would be happy to have a scripting language available as it would make MSF the perfect prototyping environment. Sort of application server for sound… strange idea.
It could be remotely controlled, react to input data in complex ways…
It could be remotely controlled, react to input data in complex ways…
-
- KVRAF
- Topic Starter
- 10366 posts since 2 Sep, 2003 from Surrey, UK
Perhaps I should not have included the "No, I do not need them" choice as scripts will only apply to Device creators who are looking for some special processing requirement.
Most users will not create them but may well use them if they are in published Devices.
And, yes, there would need to be some method of including the script module(s) in the published devices, but conceptually that is the same as some vast chunk of data in a module.
Also, of course, this could take some workload off Vojtech - instead of us making suggestions for new features we could do them ourselves (probably).
Oh Device designers, just think of the power and flexibility you would have. But "With great power comes great responsibility" (Voltaire?)
And, yes, there would need to be some method of including the script module(s) in the published devices, but conceptually that is the same as some vast chunk of data in a module.
Also, of course, this could take some workload off Vojtech - instead of us making suggestions for new features we could do them ourselves (probably).
Oh Device designers, just think of the power and flexibility you would have. But "With great power comes great responsibility" (Voltaire?)
-
- KVRist
- 460 posts since 25 Jan, 2016
Spiderman!DarkStar wrote: Tue Mar 03, 2020 10:15 am Oh Device designers, just think of the power and flexibility you would have. But "With great power comes great responsibility" (Voltaire?)
- KVRian
- 1059 posts since 28 Jun, 2006 from Germany
I like the idea, IF it won't produce more headaches for Vojtech and if it doesn't make the overall Melda framework unstable in any way. But yes, I like the idea to let user and device designers "help" themself, hehe.

Offtopic by the way: I just recently saw that you are a Reaper user as well and I was very happy to see your nick in the Reaper forums as well, nice! I recently switched to Reaper and I am kind of sad that I did not discovered all the great things in Reaper much earlier (like some years ago already or so!) - it's an unbelievable DAW !!DarkStar wrote: Mon Mar 02, 2020 1:23 pm Think of the lua and JS FX scripts in Reaper. There are hundreds of each now available to users. And. I'm sure, they boost the take-up of Reaper.
You both are hilarious, haha, like it!
System: Win 10 64 bit / i9 9900K (8x 3.6 GHz) / 16 GB DDR4-3200 RAM / 1TB M.2 SSD + 2x 500 GB SSD / RME Babyface / Reaper
Tagirijus.de
Tagirijus.de
- KVRian
- 1093 posts since 23 Sep, 2006
This is an interesting idea, but is really dependent on how easy to use it is and how powerful it potentially is. Personally, I'm really only interested in spectral stuff as my other needs are covered... and there's no easy way to make spectral effects scripting friendly (I'd imagine).
So I'm kind of a 'yes, but only if it's worth it'.
I'm also a big time Reaper fan too
So I'm kind of a 'yes, but only if it's worth it'.
I'm also a big time Reaper fan too
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14325 posts since 15 Mar, 2008 from Czech republic
WHo knows in the future... probably more like a far future though 
-
- KVRAF
- Topic Starter
- 10366 posts since 2 Sep, 2003 from Surrey, UK
