View Single Post
Old 04-15-2012, 06:23 AM   #38
diversgens
Human being with feelings
 
Join Date: Oct 2010
Location: France
Posts: 125
Default

Quote:
Originally Posted by gofer View Post
Just caught this by coincidence and am not sure whether it's resolved in this thread.

Action numbers (in any action list context) are only reliable identifiers across different installs for inbuilt stock Reaper actions. For both, custom actions and extension actions, you need to use the Custom Id string instead of the Cmd Id number, as the Cmd Id's are dynamically applied to them at Reaper startup.

Use the function NamedCommandLookup to translate Custom Id to the current Cmd Id.
In Reascript it would look like

Code:
Create_CClane =  RPR_NamedCommandLookup('_S&M_MECREATECCLANE')
RPR_Main_OnCommand(Create_CClane, 0)

BTW, that ^^ looks real cool
I'm not sure i understand the point here ... anyway you can change every action (and had yours), locate the switchs, pads or whatever look in the project window:

- if it's a single button the action id is in the 'act()' script, in the reaper action list search for the same action and change the number in the script.
- if it's a multiple actions switch or pad, locate the arr={id,id,...} and change the ids to feet your need.

In the 'Mixer' interface under the 'Actions' tab the is a set of red pads with two empty pads, if you select the pads in the Lemur Editor project window 'actions1' is select, click on the grey little arrow, click on the arr={id,id,....} and add one or two actions id you want to insert, add a text field under the pad. Next time you touch the pad it launch the action you insert.

Much easier to do than to write ...
diversgens is offline   Reply With Quote