-----

[Veto]

-----

[gofer]

I totally missed this thread .

May your awesome examples pave the way for people to come and dare enter the dungeons of scripting for Reaper's MIDI.

Hopefully the devs see them as well and understand that there are many useful ideas for actions and it'd be worth it to make it much easier to create them (plus maybe be inspired for some new stock actions ).

[caseyjames]

I'm going to dig into these in a few days once I get my current score done.

So are these working bug free?

If Cockos isn't planning midi functions for the API in the near term, it would be great to hear a final word approach to the safest most reliable way of altering the midi chunk data. I am in no way a regex or string processing wiz... I'm up to the point of displaying the midi chunk in the console with all the e's and E's. It would be great to see an example that is the sure fire method for getting the offset, status, channel, note and vel from and to the chunk in python.

It seems that there is a fear that the cockos folks are going to alter the chunk structure in some way. Are they aware this is the fear? It seems if they were they could give a nice big red warning when they do change something that is going to break the code... or at least toss and turn in their sleep.

I'm very excited to get some ideas going with the midi editor and no one has acknowledged that midi functions for the api are even planned.

Would it be possible to make a set of classes that use a safe method for patching the chunk that allows for some simple utilities? Things like getting the length between two events, poly count or the current notes start position in the whole song could make this task much easier if the underlying framework isn't what is broken.

I'm still very new to reascript, I'm still giddy about using it on everything, but the time that I'm saving in editing items makes the midi editing feel like a long, dark carpal tunnel.

[pipelineaudio]

Thank you so so much!!!!!

Keep em going!

[andysarchus]

How the hell did I miss this thread???

These are awesome Veto. Thanks for all your hard work.

[kailuamusicschool]

The deselect script seems to span octaves, can anyone think of how to turn that off?

[gofer]

I read a similar question in another thread, but don't understand what is meant. You're talking about "Unselect every second note of the same pitch"? It doesn't affect any notes which aren't previously selected here.

One of these actions, "Select every note of the same pitch class", is supposed to select every note on any octave based on the current selection. EG if you have one note C3 selected this action will select all notes C on any octave. Maybe the question has to do with that action instead?

[pipelineaudio]

Ill see if I can make an rpp repro. In my case I am editing drums.

I right click a note row to select all notes in it.

I then run the deselect every other note script

At this point I see every other note on my desired note row deselected, but I also see the notes an octave above selected.

Note: KMS is usually me as well, its the account I set up for the teachers at the school. I will make a repro of this and if I can't, and it works as it should, I'll post back up here

[pipelineaudio]

ugh I cant make it repro on this pc...might have been just pilot error

Is it just me or do tyou have to click outside of the midi editor in order to run a script?

[gofer]

Never happened here, it only ever unselects. Yep, a problem rpp hopefully helps to find the condition needed to trigger that behavior. For actually fixing code we're going to need Veto, though. My Code-Fu isn't great enough for that



Cross posted. Dang. I have set up the actions I use as buttons in the MIDI editor. Did you import the action into the MIDI editor action list or into the Main list?




Sorry, gotta run to work for some hours now....

[pipelineaudio]

Its in the main list, I couldnt find an action for scripts in the midi editor

[gofer]

In the action window you just switch to the MIDI Editor section and then import the same way (via the ReaScript New/Load button). Then the script will be part of the MIDI editor action list.

You can still keep them in the main section as well, or delete these instances. Doesn't matter, but they don't make too much sense there anyway.




Hmm, aside, where they would make sense would be in the inline editor section, but I just tried and they won't work there. I guess they need further tweakage for this. Back to the drawing board to make this possible it seems...



Did someone already mention that handling MIDI with ReaScript is a pain in the backside ?

[Viente]

Thanks for this great scripts!

Now i can make inverse chord actions

[Viente]

Thanks for warning

Maybe a little donation will help you to find some time?

[Viente]

Ouch Yeah i imagine what are you talking about...

Anyway i hope you will come back when you pass it

[beyond]

Originally Posted by Viente

Thanks for this great scripts!

Now i can make inverse chord actions

Very cool!