v4: SWS/S&M Extension

[musicbynumbers]

Originally Posted by Reno.thestraws

Auto color for region and markers! Ooooohhhh yeah!!!!!!!

indeed!

Thanks guys!

[gofer]

Lots of awesomeness in there. I'll have to wait for the weekend to get to try some of the ReaScipt stuff, I'm afraid (or I just do some nightshifts, sure is tempting ).

These immediately caught my eye:
+SWS/BR: Move edit cursor to next/previous envelope point and select it

Man, that's going to be cool! I might finally be able to edit envelopes using my li'l control surface... Breeder (I guess it is?) if I may ask, would you like to add

- Move edit cursor to next/previous point, add to selection
- Move edit cursor to next/previous point (just move)

to make envelope point navigation complete?

[Breeder]

Originally Posted by gofer

Man, that's going to be cool! I might finally be able to edit envelopes using my li'l control surface... Breeder (I guess it is?) if I may ask, would you like to add

- Move edit cursor to next/previous point, add to selection
- Move edit cursor to next/previous point (just move)

to make envelope point navigation complete?

Sure...I'll do it for the next release (if it doesn't happen in the next few days, lol)

[TonE]

Originally Posted by whatsnew.txt

+Updated action "SWS/S&M: Remove all envelopes for selected tracks":
This action removes all track/plugin envelopes. Now it also removes parameter modulations.

Now, if there would be a "parameter lock" function, you could protect certain parameter automations from this action. Whatever you liked and do not want to reset.

The workflow would be then always:
record, lock, reset
record, lock, reset
record, lock, reset
...

Or is there a workaround for this? Can envelope invisibility protect from this action? That would equal to parameter locking then.

[Viente]

Thx for ReaScrip additions! Going to try it tomorrow.

[timlloyd]

Originally Posted by Veto

Jeffos is waiting for feedback for his new work on OSX for about 10 days, that makes me a bit sad.

Sorry Jeffos!

I just set it up (OSX 10.6.8), the install script works fine, only tried Get/SetIntConfigVar so far, but they're working I will try to spend some more time with it.

[ThrashJazzAssassin]

EDIT: False alarm

I may have found a bug.

I have selected "play to next project marker..." from within seek settings and I am using the "goto /select next marker/region" SWS action to select the region to play after the last one has finished.

Sometimes when the selected region starts playing it cuts short the first note.

Could someone please try to reproduce this. I have included an example project. Play it from the beginning, and before region 1 finishes run the goto/select next marker/region SWS action. Is the first note of region 2 cut short?

Reaper v4.261
SWS v2.3.0 b4

https://dl.dropbox.com/u/325655/sws%20bug.RPP

[inspired]

please, an action request:
Paste within time selection

meaning the paste normally starts at the edit cursor, but any parts of the pasted items that are not inside the time selection get deleted/trimmed

or if not an action like this, actions for handling items and time selection (there is already an action "unselect items that do not start in time selection".
so similar actions like "delete items that do not start..", "delete items/trim outside parts of time selection")

[semiquaver]

hey Breeder thanks for these automation actions - I've been waiting for years for this.

wonder - is there any way for an action to focus 1st/next envelope on selected track?

It would be great to do automation editing via keyboard without having to click to focus the damned envelope...

[Breeder]

Originally Posted by semiquaver

Is there any way for an action to focus 1st/next envelope on selected track?

As far as I know, something like that is currently not possible with the API, and I haven't stumbled on a possible workaround.

[daxliniere]

Originally Posted by semiquaver

wonder - is there any way for an action to focus 1st/next envelope on selected track?

Oh wow. Yes! This would be a great action to have!

[semiquaver]

@Breedar: FR! I think your actions do not work on take envelopes - possible to add ? tia

[Breeder]

Originally Posted by semiquaver

@Breedar: FR! I think your actions do not work on take envelopes - possible to add ? tia

I didn't forget about takes, but it seems it's not possible to find the active take envelope - Jeffos confirmed it too on developer's forum
Envelope's API is rather simple at the moment :/

[Anton9]

Here is a python script I wrote that will select every n'th MIDI note. Special thanks goes to Veto for his help with explaining how to use the new SWS/S&M ReaScript functions and of course the SWS/S&M team for making working with "chunks" a thing of the past!!!

Requires at least sws_2.3.0.6.exe

I've posted some LICEcaps to illustrate how this thing works, all the caps use the same settings.(Start Note=0, n'th Note=2)

Cap #1: If you have a single row of notes and use the default settings you will see that every 2nd note is selected.



Cap #2: IF you have two rows of notes and run the script you end up with this and may think to yourself
"WTF.., this does'nt seem right" The reason for this is because the FNG_GetMidiNote() function appears to return notes starting from bottom left and working towards top right from a MIDI grid point of view.



Cap #3: Shows what happens with three rows of notes and better illustrates the bottom left to top right functioning.




Cap #4: Shows how it works on a single column of notes.



Oh and by the way it does'nt have to be used on a contiguous row/collumn of notes you could run it and receive something like this.



Thoughts and future imporvements:
1: Regarding the way in which the notes are selected when multiple column/rows of notes are present.., I'm sure this could be fixed using some type of sorting function.

2: Thought about adding a field on the dialog that would allow selection of a single specific pitch or pitch class. This way the user for example could run the script once and enter the pitch C3 with a setting of every 2nd note then run the script again with pitch G3 and every 3rd note to get something like this.



3: Maybe some sort of "add to/subtract from" current selection function?

4: Option for selection CC events.

5: Maybe add a function to insert or delete notes at every n'th grid divison. (This might be better implemented as a separate script?)

Unfortunately I don't have so much time to work on this right now and some of my ideas are a little beyond my current python skills.., so if anyone would like to add stuff or make imporvements then feel free to have a go at it. enjoy The script can also be downloaded from the stash here..,
https://stash.reaper.fm/14426/Select%...9;th%20note.py

# Select every n'th note.py  v0.5
# --------------------------------------------------------------------------
# Selects every n'th note in the current open MIDI editor.
# --------------------------------------------------------------------------
# If you come up with any interesting modifications of this code please post 
# on the REAPER board.
# --------------------------------------------------------------------------
# Code written by Anton9 with special thanks to Veto for getting me started with
# using the SWS/S&M export functions. Also extra special :) thanks to 
# Tim, Jeffos, and Fingers of SWS/S&M fame!!!
# --------------------------------------------------------------------------


from sws_python import *

# user input dialog
dialog_name = "Select every n'th note"
howmanyfields = 2
field_names = "Start Note,n'th Note"
default_values = "0,2"  # If you want default values enter them between the "" examp: "0,2"
maxreturnlength = 10    # have this at least one more than you expect as return length. I just choose arbitrary.
User_Input = RPR_GetUserInputs(dialog_name,howmanyfields, field_names, default_values, maxreturnlength) # Dialog setup
	
	
takeInMe = RPR_MIDIEditor_GetTake(RPR_MIDIEditor_GetActive())   # the pointer of the currently active take in the midieditor

midiTake=FNG_AllocMidiTake(takeInMe)	# allocates memory for a midi take

notesCount=FNG_CountMidiNotes(midiTake)	# counts all notes of "midiTake"

if User_Input[0] == 1:  # first item in the list it returns is 1 (true) for "user clicked ok", 0 (false) for "cancel"
	UserValues = User_Input[4].split(',')
	Start_Note = int(UserValues[0]) # Dialog input field 1
	nth_Note = int(UserValues[1])   # Dialog input filed 2

for i in range(Start_Note,notesCount,nth_Note): # iterates through all notes
	currNote=FNG_GetMidiNote(midiTake, i)   # gets a pointer of the current note with index i
	FNG_SetMidiNoteIntProperty(currNote, "SELECTED",1)      # set note property to selected state


FNG_FreeMidiTake(midiTake)      # "Commit changes to MIDI take and free allocated memory"

Update: Corrected a comment line.., no changes functional wise.

[Anton9]

Regarding the above Select every n'th script.., while testing I came across this bug. I did'nt want to post at the beta site until it can be determined if it is comming from REAPER or the extension.

It seems as though it only happens when there are MIDI CC events present.., if you guys need a project file I can post.., just let me know.

The attached LICEcaps illustrate what is happening:

In cap #1 execution is fine.


In cap #2 some notes are shrinking to zero length. The bug only appears when there are MIDI CC events present.

[musicbynumbers]

Anton9 this looks great! Will try it out at some point. Need to get into using scripts at some point and this looks like a good place to start!

[Sexan]

OMG Anton thank you very much!!!!!! This is life savior!!!!!!!!!!!!!!!

[fingers]

Hey Anton9,

Can you create an issue here with a small one item project attached.

Thanks.

[Anton9]

Originally Posted by fingers

Hey Anton9,

Can you create an issue here with a small one item project attached.

Thanks.

Done.., "Issue 531:Shrinking Notes Bug"

Thank you for looking into this.

[fingers]

Thanks. Fixed, will be in the next build.

[Jeffos]

Originally Posted by Veto

By running f.e. SNM_GetMediaItemTakeByGUID(0,"71C11FD4-BF92-49E5-A603-8F92740C6C1D")
i get an "WindowsError: exception: access violation reading 0x00000000"

Thanks for the reprot Veto, fixed for the next build.
Rmk: you have to enclose GUIDs with { } for SNM_GetMediaItemTakeByGUID to work!

[TonE]

Originally Posted by fingers

Thanks. Fixed, will be in the next build.

What was the reason for that behaviour? Were some velocities set to zero, unwantedly?

[TonE]

Ok, thanks, nothing with velocities set to zero.

[TonE]

Which Reascript functions for example? Also smooth seek we have now for a longer period, did there anything change also? If yes, what?

[dr_After]

Something is wrong with "select all folders (parents only) command (_SWS_SELALLPARENTS).
Problem:
I made cycle action that should cycle between compact and uncollapsed states of all folders:

_SWS_SAVESEL
_SWS_SELALLPARENTS
_SWS_FOLDSMALL
_SWS_RESTORESEL
!
_SWS_SAVESEL
_SWS_SELALLPARENTS
_SWS_UNCOLLAPSE
_SWS_RESTORESEL

but it doesn't work well - depending of it which track is selected, sometimes it doesn't compact all folders, sometimes it does.

EDIT: action works well with _SWS_SELFOLDSTARTS instead of _SWS_SELALLPARENTS command. Strange (or I don't understand something...)

[sws]

Looks like you figured it out -
SWS_SELALLPARENTS selects just the lowest level of the folder hierarchy, SWS_SELFOLDSTARTS selects all tracks which have children regardless of their "level". It's a subtle difference, I know, but important!

[dr_After]

Thank You for explanation. Yes, this is subtle difference, but now I get the idea

Another thing is that naming of actions is inconsistent.

In Reaper actions track can be compact, collapsed or uncollapsed. In SWS there is no action for "compact", instead it is for "small" tracks. If I wouldn't knew that it HAS to be somewhere on list I would never find it

[Anton9]

Hey Tim,

I've been playin' around with the SNM_SetDoubleConfigVar() and SNM_SetIntConfigVar() functions and noticed the following issue.

For example:

from sws_python import *

SNM_SetDoubleConfigVar("projbpm", 60.00000000)
SNM_SetIntConfigVar("projmeaslen", 5)
SNM_SetIntConfigVar("projsdenom", 4)

When executing this script if you then open the "Project Settings" dialog you'll notice that the settings where changed however the transport does'nt reflect these changes unless you manually edit one of the settings in the dialog and then click 'Ok'. Can anything be done about this?

There was one other thing I was wondering.., do you guys have access to REAPER's toolbars code? If so could you maybe see if you can create some kind of refresh action. The problem is when importing a custom toolbar that is docked and which has a custom tab title the title is not refreshed unless you close the tab and reopen it. It continues to read for example "Toolbar 3".

Thank you,

Anton9

[Jeffos]

Anton, try this:

from sws_python import *
SNM_SetIntConfigVar("projmeaslen", 5)
SNM_SetIntConfigVar("projsdenom", 4)
RPR_SetCurrentBPM(0, 60.00000000, False)

__

Originally Posted by TonE

Which Reascript functions for example? Also smooth seek we have now for a longer period, did there anything change also? If yes, what?

since v2.3.0 #5, we deliver a whatsnew (dedicated action or Main menu > Extensions > About SWS > button What's new?) => you will find all the info your are after (+screenshots, +link to BRs/FRs, etc..)

[musicbynumbers]

Was just working on some orchestral stuff and was getting to the point where I needed to slightly change a group of items relative brightness just so I could see they were slightly differentfrom the parts before and after .

It would be a amazing to have two new actions. One for increasing brightness (or perhaps contrast) and one for decreasing it on the selected items or even tracks.

Would be useful!

[gofer]

I have some ReaScripts that do the trick. What they basically do is get the color number, convert to hsv values, change either hue, saturation or brightness (got scripts for all of these), convert back and hand the new color number over to Reaper. In practice I had to struggle with some corner cases, though (particularly increase brightness made me scratch my head for some reason I still don't get).

The scripts takes quite a long detour to convert between Reaper's color number and HSV values (and back), relating on some functions I found on the net. I just wasn't able to pull it off myself, so I used what I could find, ending up with a conversion from Reaper color through RGB and then finally to HSV - the way back is even a step longer - but what the heck, it works . Someone with more brain than me can likely come up with a much more elegant solution than mine in no time... I'd be thankful if that someone would let me know of his solution .

I wanted to pack and upload them since ages, but forgot... so I do that right now. I'd be glad if some of the ideas (not so much my crude code) would become part of SWS extensions or stock Reaper. I use most of the track color scripts pretty often (the item versions not so much, but that's me).

If interested, grab them at the stash: https://stash.reaper.fm/v/14535/gofer...%20scripts.zip

[musicbynumbers]

Thanks Gofer! will check them out!

This also lets Tim/Jeffos and the gang know that more than one person finds this useful and t hey may consider putting it in SWS

[gofer]

Originally Posted by musicbynumbers

Thanks Gofer! will check them out!

This also lets Tim/Jeffos and the gang know that more than one person finds this useful and t hey may consider putting it in SWS

Yeah, that was my thinking as well . Really useful functions if you're like me.

hinthint: there are also functions to copy the first selected track's color to a "clipboard" and to paste that color to all selected tracks (I quickly threw together versions of these for items) and maybe go from there dialing in the color with the other functions. These I especially dig .

[Anton9]

[QUOTE=Jeffos;1065235]Anton, try this:

from sws_python import *
SNM_SetIntConfigVar("projmeaslen", 5)
SNM_SetIntConfigVar("projsdenom", 4)
RPR_SetCurrentBPM(0, 60.00000000, False)

Thank you Jeffos, that worked real well.

[TonE]

Is it possible in sws extension action naming, NOT to use the character "&", as for example in S&M? It could be replaced by "SandM" for example?

Why?
Those "&" seem to cause problems in AutoHotkey, but I might try to find a solution for it. My quick tests showed AutoHotkey does not like "&" and a very quick solution I could not find. So I used the digit number for that action, which is not recommended in the sws extension manual, but at least it was working for now, via AutoHotkey. See my ReaSamplomatic5000 workaround.

[mabian]

Originally Posted by TonE

Is it possible in sws extension action naming, NOT to use the character "&", as for example in S&M? It could be replaced by "SandM" for example?

Why?
Those "&" seem to cause problems in AutoHotkey, but I might try to find a solution for it. My quick tests showed AutoHotkey does not like "&" and a very quick solution I could not find. So I used the digit number for that action, which is not recommended in the sws extension manual, but at least it was working for now, via AutoHotkey. See my ReaSamplomatic5000 workaround.

Have you tried using a double ampersand in these cases? It seems the literal value for ampersand in AutoHotKey is a double ampersand...

- Mario

[TonE]

No, did not know about this, I will try it as soon as possible, thanks a lot!

[Reaktor:[Dave]]

Just noticed that "SWS/S&M: Paste sends to selected tracks" works only for the first selected track instead for all selected tracks. Does it work for anyone else?

[Jeffos]

Originally Posted by Reaktor:[Dave]

Just noticed that "SWS/S&M: Paste sends to selected tracks" works only for the first selected track instead for all selected tracks. Does it work for anyone else?

I don't think you have the latest sws version (v2.3.0 #8) because this has been improved recently has explained here..

[musicbynumbers]

Hi Gofer, Finally got round to trying these with python 2.7 and no matter what colour the items are they always turn black regardless of the parameter I choose to increase or decrease. any ideas? need python 3?

Thanks!

Originally Posted by gofer

I have some ReaScripts that do the trick. What they basically do is get the color number, convert to hsv values, change either hue, saturation or brightness (got scripts for all of these), convert back and hand the new color number over to Reaper. In practice I had to struggle with some corner cases, though (particularly increase brightness made me scratch my head for some reason I still don't get).

The scripts takes quite a long detour to convert between Reaper's color number and HSV values (and back), relating on some functions I found on the net. I just wasn't able to pull it off myself, so I used what I could find, ending up with a conversion from Reaper color through RGB and then finally to HSV - the way back is even a step longer - but what the heck, it works . Someone with more brain than me can likely come up with a much more elegant solution than mine in no time... I'd be thankful if that someone would let me know of his solution .

I wanted to pack and upload them since ages, but forgot... so I do that right now. I'd be glad if some of the ideas (not so much my crude code) would become part of SWS extensions or stock Reaper. I use most of the track color scripts pretty often (the item versions not so much, but that's me).

If interested, grab them at the stash: https://stash.reaper.fm/v/14535/gofer...%20scripts.zip