Here's the start of a ReaScript wish list. What have I missed? What shouldn't be on the list? What should and shouldn't be in red? (No matter what anyone says I'm not taking the Wiki items off the list.) There aren't many Python items. (can't think why...)

These are the top ten things in the Wish List. Positions are set by +1 or -1 votes, so make sure you vote for what you need and un-vote for what you don't...

Get/SetMidiItemInfo_Value() - perhaps not this API exactly, but something a more ReaScripter friendly than chunks. (Some aspects of friendlier could be user-contributed if we could call RPR_* functions from a module)

GetFuncAddress() call. Not needed now include() is implemented.

Jeffos would like to be able to say GetSetObjectState(ReaProject*), personally I would prefer to see a GetSetProjectState() to allow access to project-wide parameters using chunkish editing.

Oh, and just to be clear. I'm not complaining, I think ReaScript (yes, yes & the C++ API) is the best thing since sliced bread.

Mike

(* Some items may stretch the capabilities of the development team, but we shouldn't let that stop us asking. Remember - hard work is good for them. )

- something to get a valid reaper_plugin_info_t *rec (or any alternative other way to register to Reaper's notif)

- LICE_IBitmap * b = GetPNGFromCurrentTheme("mcp_volthumb.png", NULL);
getting the user's current theme in a cross-plateform way would be cool for VSTs extension plugins
==> EDIT: no API update needed for that

- something to work within FX chains in a FX type independent way (VST, JS, Dx): main first needs: trigering REAPER's preset (then, FX's one) but also pin connection processing==> EDIT July 2010: trigering REAPER's preset is doable

I stop here. I really think the two 1st ones would open many doors. I'd be happy only with them.

Other devs wishes I really agree with (ordered too):
- same as SWS: plugin_register("hookcommandex", hookCommandProcEx);
FR: http://forum.cockos.com/project.php?issueid=1465
- same as padre_pc, klinke, yves: enhanced csurf notif, see http://forum.cockos.com/showthread.php?t=44152 (but forget what I said there: now, I know how to do almost everything I asked there)
- same as geoff: a way to enumerate the action list (I promise I won't do a parallèle learn system.. ;-)

I could really do with .
RPR_GetMidiItemInfo_Value( ) Retries all position pitches and velocities of notes in an item by index.
and
RPR_SetMidiItemInfo_Value( ) Sets all position pitches and velocities of notes in an item by index.

Chunk editing is just two tricksy for your average Rescripter it needs to be transformed into something far more friendly .

Chunk editing is just two tricksy for your average Rescripter it needs to be transformed into something far more friendly.

I agree.

Jedstar, would your proposed API call be able to, for example, take all notes of certain pitch in the item (or all notes from current note selection), and then, for example, select every other note in each pitch? Visually:

Code:

C5
B4
A#4 e e
A4
G#4 e e
G4
F#4 e e e e e e e e e e e e
F4
E4

Let's say this is a hi-hat rhythm you'd want to transfer to closed hats only, and then select every other note to edit velocity further manually. After setting:

+1 for #13 this is a problem when you start loading vst effects on media items or tracks. The size quickly gets out of hand.

My request is for a mechanism similar to the way you write c++ dlls, but for reascript. I would like to have a function RPR_GetFunc which given the function name would return a function pointer. That way I can write modules in python which can access reaper plugin functions without having a huge callback class in the main script. Ideally, all I'd have to pass is a reference to RPR_GetFunc and the modules can get the plugin functions themselves, by calling 'DeleteTrack = RPR_GetFunc("DeleteTrack")' for example.

Jedstar, would your proposed API call be able to, for example, take all notes of certain pitch in the item (or all notes from current note selection), and then, for example, select every other note in each pitch? Visually:

Sure You would be able to do all that and a lot more.
you would just have to write the appropriate script.

We would also need .
RPR_CountSelectedMediaItems(0); but for counting how many notes inside an item
somthing like.
RPR_CountMidiNotesInMediaItems(0);

This would allow you to step threw every note in an item and manipulate it however you felt fit.

My request is for a mechanism similar to the way you write c++ dlls, but for reascript. I would like to have a function RPR_GetFunc which given the function name would return a function pointer. That way I can write modules in python which can access reaper plugin functions without having a huge callback class in the main script. Ideally, all I'd have to pass is a reference to RPR_GetFunc and the modules can get the plugin functions themselves, by calling 'DeleteTrack = RPR_GetFunc("DeleteTrack")' etc.

This sounds tempting. Given the address of a REAPER function, from GetFunc(), you could wrap it in an FFI call and have a much more Python-ish or Perl-ish version of ReaScript, probably The implementation of ReaScript would then be in Perl or Python modules. You'd be able to write things like this:

PHP Code:

use RPR; # the standard RPR_* API calls, wrapped using FFI
use MyRPRLib; # a set of amazingly cool library objects & routines.

The functions GetSetEnv/Item/TrackState return bool (amongst other things), is the bool return value not reliable?

Hi Mike! sorry for this late anwser. no, I meant that sometimes you have to fight to validate chunk updates (to avoid what you called "a temporary update" in another thread) while the fuction had returned "true". Sometimes it also return true but nothing is applied at all and there're other worst issues (e.g. right now I'm facing some deadlocks when setting, I'm trying to clarify that..)

Quote:

Originally Posted by MikeLacey

So that we can update project global parameters in a chunkish way? (In the style of GetSetProjectState()?)

yes, it's the idea: master enveloppes, tempo, etc...

Last edited by Jeffos; 01-06-2010 at 04:44 AM.
Reason: none, see post bellow

1. APIs to control individual FX parameters. This includes manipulating FX params, but also getting information back from them , eg which plugin and plugin FX knob they control, so you could open the plugin window if you'd like

2. The before mentioned extensions to the [url=http://forum.cockos.com/showthread.php?t=44152]notifications/callbacks.[]/url

[*]Support for Tk (GUI used by Python & Perl) (long shot) Or... Drop down lists, text boxes and such in windows that can be called from ReaScript functions. (less of a long shot maybe)

Just spotted this one. I had no trouble running tkinter in Reaper, except of course not having the ability to make API calls without some kind of a callback mechanism (which I still have to figure out!). But it certainly is possible to have a GUI.

Just spotted this one. I had no trouble running tkinter in Reaper, except of course not having the ability to make API calls without some kind of a callback mechanism (which I still have to figure out!). But it certainly is possible to have a GUI.

Would you mind to post a little (python) demo snippet, because i didn't get this to work either?

However, all I needed to do was change the import statements from "import Tkinter" to "import tkinter" in the 2 .py files it generates, and the code seemed to work fine with Python 3.1. But I've only tried it briefly. Anyway, have fun!

Thanks a lot. Works fine.
Also thanks for the link to the GUIbuilder thingy. Makes things a lot easier.

Right, just be careful with the root.destroy() function. I've removed it from the example since closing the GUI with the X button calls that function anyway. If you were to say, put root.destroy() as a function call for one of the buttons, it will do the same thing.

However putting it in the wrong place can sometimes create an infinite loop spawning a few dozen windows, and you have to crash Reaper via the task manager to get rid of them. But it only happens if you don't know what you're doing (I got burned on that one myself )

Edit: Looks like tkinter seems to be a bit buggy, or I'm doing it wrong. For the life of me I can't figure out why sometimes a button activates itself on it's own. And I'm getting infinite loops, windows popping out everywhere. Argh!

It looks like the maximum number of envelope points I can retrieve with an extension is 629 points. Trying to extract more crashes reaper, with a "Memory could not be 'written' at address 0x********"

It seems Reaper has no problem having more than 629 envelope points. So it's probably a limitation of the size of the chunk RPR_GetSetEnvelopeState can return. At 629 points the string/chunk returned is 15742 characters long.

I'm not saying the limit should be changed. 629 is more than enough for anyone I guess.

On the good side of news, my envelope extraction function (which performs some regular expressions on the chunk) stores all the envelope data and points data in separate dictionaries pretty fast. Around ~20 milliseconds for 629 points, if cProfiler is to be trusted.

When a (python) script is running, none of the other shortcut keys work until that script exits (although running other scripts via the Actions window work).

A script with a GUI is usually executing an infinite loop until the user hits a close button of some sorts (or the script exits by itself). I've just tried running two GUI scripts at once. After I've ran the first script, the shortcut keys were not responding (as in ctrl-c, escape, F1-F12 buttons etc). I've opened the Actions window and tried executing other scripts. This will work, unless the other script is a GUI script as well. In that case, trying to run that second GUI script will leave Reaper completely frozen.

I think this is worth investigating if we're hoping to some day have GUI scripts running side-by-side. I've tested this with tkinter, and a commercial GUI library, with the same results on Reaper 3.2 and 3.21 beta.