Quote:
Originally Posted by deseipel
update: I had to put it in the correct scripts folder, in my case 'C:\Users\User\AppData\Roaming\REAPER\Scripts'
I've put this in my Scripts folder and renamed it "__startup.lua" but how do I verify its working? it didn't do anything when I shut off one of my midi controllers.
|
hmm I'm not sure if I got you right, but it sounds like you renamed
neutronic_MIDI plug and play.lua to
__startup.lua and then put the file in the REAPER Scripts folder. If so, then it's not how it should be installed and that's why it doesn't work.
Here's a step-by-step setup guide:
1. Install the plug and play script by either
- (recommended) importing my repository into ReaPack, searching for the script there and installing it. This way the script will automatically appear in the Actions list.
- download the script through the direct link in my original post, put it in your REAPER Scripts folder and add it to the REAPER Actions list (New Action --> Load ReaScript...)
After you successfully did any of the above and you can find
Script: neutronic_MIDI plug and play.lua among REAPER actions, go ahead and run it to see how it works.
You can check if it's running by expanding the Actions file menu entry and see if it's there:
If it is, you can now plug your MIDI controllers and they should be automatically initialized.
2. If you wish the script to run automatically every time you open REAPER you can either
- use the SWS global startup action functionality
- create __startup.lua file right in the root of the REAPER Scripts folder and then put in the file an API call that will inform REAPER to run the plug and play script automatically.
Example:
Code:
local plug_play_script_id = reaper.NamedCommandLookup("_RS3b3b25e3431ec478e2b0f38af56ad3828a8730f5")
reaper.Main_OnCommand(plug_play_script_id, 0)
If you installed the plug and play script through ReaPack, the above code should work as is, otherwise you might need to replace
_RS3b3b25e3431ec478e2b0f38af56ad3828a8730f5 (keep the quotes) with the relevant command ID that you can retrieve by right-clicking the script name in the Action list and selecting the "Copy selected action command ID" option.