is anyone able to get SWS extension to function with 5pre16? I'm not getting the incompatibility error, just simply doesn't load. using v2.6.0 x64, also verified the location of the dll in the portable reaper install I am using, also verified version with the "whats new" txt

is anyone able to get SWS extension to function with 5pre16? I'm not getting the incompatibility error, just simply doesn't load. using v2.6.0 x64, also verified the location of the dll in the portable reaper install I am using, also verified version with the "whats new" txt

edit: rolling back to version 5pre10, sws extension works.

I just checked and I have SWS 2.6.1 x64 in the latest 5pre16. It works as expected so far. You might want to give SWS 2.6.1 a try.

Out of curiousity I checked for an SWS update and it said there was a beta 2.6.2 version out. I clicked on the link and it went to the SWS home page and there wasnt a 2.6.2 beta build to be found.

- SWS/BR: Play from mouse cursor position (perform until shortcut released)
- SWS/BR: Play from mouse cursor position and solo track under mouse for the duration (perform until shortcut released)
- SWS/BR: Play from mouse cursor position and solo item and track under mouse for the duration (perform until shortcut released)

Yup, that was the idea to go with my new Logitech G602 mouse (I know you don't use mouse, but others may like the idea )
I have programed these 6 buttons on the side as follows:
2 for contextual toolbars (one primary, one secondary)
2 for these play actions to preview things while editing (whole project and active track only)
2 for undo/redo (I do that a lot when editing MIDI, lol)

Feels really smooth once you get used to position of all the buttons (and invest time to set up MIDI toolbars, lol)

Quote:

Originally Posted by musicbynumbers

I like how if you start it whilst the mouse is just before the item it will actually allow all items on that track to play as known were selected. don't change that!

Do you mean if mouse is over item edge or simply not over any item?

In case you mean mouse is over item edge - I would maybe consider this a bug (because mouse doesn't have to be over item, but very close to it's edge so REAPER changes mouse cursor (to make it easier to grab item edge) - but I still haven't fixed mouse detection code to take item edges into account so that's why it's like that)

In case you mean mouse is simply not over any item - that's by design.

Very cool breeder! I can't do a mouse anymore for fear of rsi but good setup!

I meant if you are over no items at all. That's really nice "smart" behaviour that it does.

It would be cool if when over the item's left edge/start that it would always play exactly from the start and not miss a slight bit of the starting transient etc.

I'm not sure if it does miss anything as I didn't try with drums but that would be a bit of intelligent design too that would be useful.

Also, I forgot to try but does it do that great thing that if the project is already playing, then it remembers where it was before you used the action and then jumps back there on release of the action and continues playing still? That's awesome in the older ones.

__________________subproject FRs click herenote: don't search for my pseudonym on the web. The "musicbynumbers" you find is not me or the name I use for my own music.

To be able to have more control about positionning with the recent "play until shortcut is released" action, maybe we can imagine the same actions, but not from mouse, but from edit cursor ?
It will allow us to make it sure it start from an item start, or a measure start or anything else.

are not usable in sessions that includes more than just a bit of automation by all appearances.

They take an ungodly amount of time to zoom back out. I've had to switch to the zoom tool of the extension, using CTRL+middle mouse button in this case. The simple edit focus type of action toggle is screwed.

are not usable in sessions that includes more than just a bit of automation by all appearances.

They take an ungodly amount of time to zoom back out.

Can't reproduce Just tried with a session that has over 80 000 envelope points and the things was instantaneous (my PC is over 4 years old)
Please share OS info, example project (together with repro steps) and your REAPER.ini

By this I mean, if I was to grab an items left edge and move it, I wonder if I can trigger this whilst holding the left edge so I can very quickly hear the item's start point.

Yep, but editing while the shortcut is pressed in case you're using versions that solo item/track can be sketchy. Because these actions don't create undo points (it would be redundant and spam undo list) since they restore solo/mute state after shortcut release.
So editing something would make it possible for edit's undo point to take into account temporary solo/mute state - it really depends on which kind of undo point the edit does create (as long as it doesn't include track state it should be fine with track only versions...but if items are muted too then it could become a problem when editing items)
It seems that changing item edge works ok when soloing track only

If GetProjectStateChangeCount() API was working, I could use it to create undo points if something is edited for the duration of the playback - but unfortunately it's not working.

are not usable in sessions that includes more than just a bit of automation by all appearances.

They take an ungodly amount of time to zoom back out. I've had to switch to the zoom tool of the extension, using CTRL+middle mouse button in this case. The simple edit focus type of action toggle is screwed.

But at least the extension works in pre17 . Thanks for that fix.

Quote:

Originally Posted by Breeder

Can't reproduce Just tried with a session that has over 80 000 envelope points and the things was instantaneous (my PC is over 4 years old)
Please share OS info, example project (together with repro steps) and your REAPER.ini

I was going to bump it up to 32, same with the mute/solo state. That was just my initial thought, being used to some other actions where I could go into the ini. and add my own.

though I also assumed though that 32 might not even be enough eventually, though I'm not there yet. If it is possible to add that option to the ini, I think it would be valuable to some people, depending on how much effort it takes, as then it allows the user to change it if they need be.

Could we get it so resource bookmarks automatically order alphabetically?

I like to use a number to categorize types of track template, the unfortunate thing is that if I add anything new, it throw my whole system out of whack. Though if I just keep adding bookmarks, eventually I end up with a whole mash of bookmarks that are completely unorganized and are really hard to navigate/manage.

As you can see, now if I want to add anything, it's going to be pushed to the bottom of the list

Btw, I also found that if I delete a bookmark, it is actually deleting any track templates within the folder that the bookmark is set to autofill/save to. I was pretty bummed out when I went to re-organize my bookmarks, only to realize all my actual template had been deleted. Luckily I have them backed up, bit still, just thought you should know.

But you can also use REAPER 5 API to change MIDI events position without changing their indexes. (same thing that applies to BR_Env functions applies here...FNG_MIDI stuff is using chunks so may be slower than native functions so choose wisely (in short, use BR_Env and FNG_MIDI only when you can't do it without native API (chunk API not included since doing chunks from ReaScript will be slower than doing them from C++ )

Code:

reaper.MIDI_SetNote(MediaItem_Take take ... boolean noSortInOptional)

So if you pass noSortInOptional as true, indexes won't change. Once done, you just have to call MIDI_Sort()

Code:

reaper.MIDI_Sort(MediaItem_Take take)

Regarding chunks vs separate functions - while I always recommend not using chunks if possible, please take into account that I love to micro optimize prematurely (that's a bad thing, lol) - so don't listen to me, instead profile stuff before optimization. For example, if you use some of FNG/SWS midi actions that change CC lanes or MIDI notes you will notice that you have to have a HUUUUUUUUUUGE number of MIDI events before you actually notice a slowdown inherent in chunks. Not to mention Jeffos' chunk parser which we use throughout the extension for a lot of stuff, and we're yet to hear from someone about how slow it is

When opening a project into a new tab from the Resources window, it will open the default template into the new tab, just to close it and open the project requested. This is slow if your default template uses many tracks or plugins. It should just open the project into a new tab directly.
This also happens in the Project Management - Open projects from list, when opening a list of projects from a file. It would be great also if we could open multiple projects at the same time from the Resources window. We can select multiple rows, but if you open them will open one project only.

The action SWS: Select tracks with active routing to selected track(s) _SWS_SELROUTED
does not select if the tracks are routed but muted. I understand this behaviour, but could we have another action that selects all the tracks with routing to selected track(s) independently of the mute state of the tracks?. It would be useful.
Thanks!

- SWS/BR: Move active floating window to mouse cursor (9 version with different horizontal and vertical positions in regards to mouse cursor)

This is very useful. Would you consider providing a version that only affects FX windows?

I'm using it in a macro to 'toggle float FX xx for selected tracks", so this new action works great in placing the floated fx under the mouse cursor, but when I re-execute my macro to close the fx window it moves the main Reaper window.

Great release! So many great functions and API.
I think at the end REAPER install will include SWS, maybe with a checkbox to not install it if you don't want. But I can't imagine anyone doing that.
Thank you!

Can you guys please fix the "master channel send on/off" when importing snapshots? Right now if doesnt work. All imported channels have master send on. Thats not so useful when wanting to transfer buss settings

"
Quote:
- SWS/BR: Move active floating window to mouse cursor (9 version with different horizontal and vertical positions in regards to mouse cursor)
This is very useful. Would you consider providing a version that only affects FX windows?

I'm using it in a macro to 'toggle float FX xx for selected tracks", so this new action works great in placing the floated fx under the mouse cursor, but when I re-execute my macro to close the fx window it moves the main Reaper window.
"

I was thinking of the same use. Great!
I guess a script could be used to determine if you are closing the fx window and do not want the new action to be executed. Mayble will try this weekend...