X-Raym's - Avoid Using Native/SWS Action

[ceanganb]

I wonder if every action can be replaced by scripting. I want to make a script that cycles through toolbars, but I did not find any API to open toolbar x.

Is every action replaceable by scripting? Apparently not, but I want to be sure from you, scripting gurus.

Thanks

[Lokasenna]

There are a number of things that we don't have API commands for (yet). However, using Main_OnCommand to do things is perfectly fine - you aren't going to kill your performance or anything.

[ceanganb]

Thanks Lokasenna. I suspected, but is better to hear from a scripting-savvy.

[X-Raym]

In fact this "guideline" was to outline the fact that if you use SWS actions like "Save current itme selection to Slot 1", "save current cursor position", you may erase a precious selection for the user.
And writing this kind of action with dedicated function is as simple as a simple code snippet.

But feel free to use native actions,
sometimes it is both more efficient and more simpler to code !

Just don't forget to place undo blcoks at the right place to not create 50 undo points if the action call is inside a loop.

[X-Raym]

Actually for performance, creating items with scripts functions was approx 10 times faster than using native actions to set track as last touched, set a time a selection, insert item into time selection, move time selection and repeat.


So yes, native actions can be really bad for performance in some case.

[ceanganb]

Originally Posted by X-Raym

Actually for performance, creating items with scripts functions was approx 10 times faster than using native actions to set track as last touched, set a time a selection, insert item into time selection, move time selection and repeat.


So yes, native actions can be really bad for performance in some case.

I understand, it's that the statement in your blog made me consider there was always a substitute. Now I see it's only preferable when it's available.

[Lokasenna]

Originally Posted by X-Raym

So yes, native actions can be really bad for performance in some case.

Only if you're doing a) a lot of stuff at once or b) stuff while the audio is playing. If the project is stopped and you're just running a series of actions, you're never going to notice.

10x faster than "a few ms" isn't a difference worth caring about, to me. As long as the programmer knows what sort of situation their script is being used in, it should never be an issue.

[X-Raym]

@Lokasenna
I don't have the benchmark, but the action was use to create items for subtitling,
the first version used native action to insert empty items,
the second use custom functions,
and the difference was something around 10 times faster (it took 10 seconds with v1, only 1 in v2). 10 seconds for an action without REAPER responding is enough to make the user worried about what is going on.
Audio was not playing.

Sure, in most case, you should not notice a difference in performance, but in some case, you will :P

[Lokasenna]

Ah, fair enough.