Good evening! I’m happy to announce some progress: I’ve fixed a few minor issues and ModScript is now compatible with Windows! Thanks to @Steve_Russell for reporting the issue
While doing so I went ahead and prepared plugin packages for Linux and Windows, I’m offering these in an almost beta stage for curious users and developers to test it! The following explains why I’m cautious about that.
Please read: By offering to run scripts from unknown and/or unverified sources, this plugin has a few security implications, much like VCV-Prototype had too. I give you my word that I will do my best to protect against that and that I won’t attempt to run cryptocurrency stuff remotely on your computer or anything harmful. The best security is still your understanding and alterness about this!
Download links, the file are hosted on my website (links and files updated to latest post) :
- ModScript-2.0.0-win.vcvplugin Windows x64, tested on Windows 10 and Windows 11
- ModScript-2.0.0-lin.vcvplugin Linux 64, tested on Debian Testing and Ubuntu 22.04. Doesn’t work on Debian Unstable because of incompatible libc versions.
The source code of these builds is up-to-date, find it here.
Because it is such an early release, I don’t recommend at all to start serious work using ModScript although most of the API shouldn’t change too much. I also do not recommend trying to run complex Lua scripts including existing libraries etc., as I have found out myself that this is a bug/limitation in the build system currently. That being said, I would be very happy to know that is does work for the basic stuff demonstrated below! And if it doesn’t… well, sorry!
Instructions
Once you have installed the plugin, click File > New to get the default Rack patch, add Pleine Lune, select keyboard.lua
in the right-click menu, select the Keyboard input as MIDI driver, check the script and see what happens! That script has a lot of comments to help writing your own, don’t hesitate to ask here and suggest additional help! Thanks.
During the development of scripts I find myself heavily relying on the display()
function to print info and debug things. On Linux you can view it by running: tail -f ~/.Rack2/log.txt
. The equivalent for Windows is to run this in Powershell: Get-Content log.txt -Wait
(you have to cd to Documents/Rack2 first, this is where this log file is located)
Future
Things that are expected to change:
- Module size and layout, 4 in/out isn’t enough, I’d like to make it a little wider and maybe a little screen. Also leds for midi device and script status.
- Script files locations: for now they are in the plugins folder (
Documents/Rack2/plugins/ModScript/scripts
on Windows), I would like to have them directly in the Rack2 folder in a ModScript folder.