SWS Extension pre-release builds

[Yanick]

It seems there is such a bug when using the function of finding the track under the mouse cursor

If you open the master track at least once, then the first normal track gets confused with the master

[cfillion]

Thanks, fixing! (This issue happens in REAPER v6 and newer)
EDIT: You can try the fix using the builds posted here: https://github.com/reaper-oss/sws/pu...ment-749205596.

For future reference, SWS bugs are best reported in the SWS issue tracker.

[Yanick]

Thanks for the fix

[mozart999uk]

Sorry if I've missed this info elsewhere.

Just out of curiosity.....

How close are you guys to a public release?

I noticed the thread is called "pre-release" . How does that position in your release schedule? Is that like a release candidate?

[vitalker]

Originally Posted by mozart999uk

I noticed the thread is called "pre-release" . How does that position in your release schedule? Is that like a release candidate?

Don't look at it, SWS can be used at any stage.

[mozart999uk]

Originally Posted by vitalker

Don't look at it, SWS can be used at any stage.

Sure. But there are some upcoming features that I'm looking forward to and I'd rather not use a beta....

Wondered when the next public release is

[vitalker]

Originally Posted by mozart999uk

Sure. But there are some upcoming features that I'm looking forward to and I'd rather not use a beta....

Sure, it's your decision to choose. It just works, so I don't see any reason to not use pre-releases.

[mozart999uk]

Originally Posted by vitalker

Sure, it's your decision to choose. It just works, so I don't see any reason to not use pre-releases.

Good point :-)

[Meo-Ada Mespotine]

Originally Posted by mozart999uk

Sorry if I've missed this info elsewhere.

Just out of curiosity.....

How close are you guys to a public release?

I noticed the thread is called "pre-release" . How does that position in your release schedule? Is that like a release candidate?

The latest pre-release is considered a stable one, so you can use it.
It's SWS 2.12.1.1

[mozart999uk]

Originally Posted by Meo-Ada Mespotine

The latest pre-release is considered a stable one, so you can use it.
It's SWS 2.12.1.1

Cool. Thanks for letting me know :-)

[nofish]

There'll probably be a SWS 2.12.1.2 pre-release with a few more fixes shortly which will then hopefully turn into an official release soon(ish).

[mozart999uk]

Originally Posted by nofish

There'll probably be a SWS 2.12.1.2 pre-release with a few more fixes shortly which will then hopefully turn into an official release soon(ish).

Thanks for the update. 👍👍👍👍

[javiramallo]

Originally Posted by nofish

There'll probably be a SWS 2.12.1.2 pre-release with a few more fixes shortly which will then hopefully turn into an official release soon(ish).

Great!

Thank you for you enormous work!

[musicbynumbers]

Indeed! Thanks!

[daniellumertz]

thanks for all working in SWS !!

[Edgemeal]

What changed in Dec 27 SWS release? The Whatsnew.html only shows previous info (December 23, 2020) on https://www.sws-extension.org/download/pre-release/

[nofish]

That's only the two Dec 27 commits. Related to building SWS so no change for the end user.
(When committing to master new builds are generated automatically on the pre-release site.)
https://github.com/reaper-oss/sws/commits/master

edit:
In general, if the version number doesn't change (as in this case) it's internal changes only.

[cfillion]

The toolchain (Xcode SDK and compiler version) used to produce the macOS i386 and x86_64 builds was reverted to what was used before v2.12.1.1.

[Stroudy]

Not sure if this is the correct place...

These commands not longer work AFAIK

SWS/NF: Eraser tool (marquee sel. items and time ignoring snap, cut on shortcut release)

AND

SWS/NF: Eraser tool (marquee sel. items and time, cut on shortcut release)

Thanks

[Meo-Ada Mespotine]

What does no longer work mean exactly? Does it do something wrong or nothing at all anymore?

BTW, for bugreports, it's best to post them over here:
github.com/reaper-oss/sws/issues

It's easier for the SWS-team to keep track of it on GitHub.

[nofish]

Originally Posted by Stroudy

Not sure if this is the correct place...

These commands not longer work AFAIK

SWS/NF: Eraser tool (marquee sel. items and time ignoring snap, cut on shortcut release)

AND

SWS/NF: Eraser tool (marquee sel. items and time, cut on shortcut release)

Thanks

The usage of it has changed at some point (originally it erased directly on mouse movement but that didn't go well with ripple editing).
Tried it not that long ago and still worked for me though:
https://forum.cockos.com/showpost.ph...&postcount=589

[Stroudy]

Originally Posted by nofish

The usage of it has changed at some point (originally it erased directly on mouse movement but that didn't go well with ripple editing).
Tried it not that long ago and still worked for me though:
https://forum.cockos.com/showpost.ph...&postcount=589

Amazing - I honestly remembered it working without a left mouse press. Oops

[nofish]

Originally Posted by Stroudy

Amazing - I honestly remembered it working without a left mouse press. Oops

Actually I wanted it to work without left mouse press originally but haven't figured out how how to do it properly. Maybe one day...

[rstockm]

SWS ARM v2.12.1.2 ca9c3899 runs flawless on my Apple Silicon M1 - great job!
Is there a chance to get it as an Universal Build - working both on x86 and ARM Macs?

[cfillion]

Originally Posted by rstockm

SWS ARM v2.12.1.2 ca9c3899 runs flawless on my Apple Silicon M1 - great job!

Glad to hear that!

Originally Posted by rstockm

Is there a chance to get it as an Universal Build - working both on x86 and ARM Macs?

A universal build would double the file size with half always unused. I don't see a good reason for doing that (especially when REAPER provides split builds too). You can have the x86_64 and arm64 versions of SWS installed at the same time if you need both.

[BPBaker]

Hello and apologies if this isn't the best place to ask this SWS question. I'm teaching a series of online Zoom tutorials training radio/podcast producers how to use REAPER (and generally evangelizing for REAPER) and installing SWS is a critical part of the system I'm teaching.

I'm getting hundreds of people per Zoom lesson (using Mac and PC, with a wide range of tech skills/comfort), and installing SWS on the Mac side is one of the real pain points in my class.

On the PC side, everything goes smoothly with the .exe-based installers. But I run into SO many issues with SWS installation on the Mac side--particularly with people who have less tech experience. And even though I walk users through the whole process step by step, these issues really, truly, derail the class and prevent me from getting people on board with REAPER--making the whole DAW seem more daunting than it really is.

Even though I explain this all in my class, sometimes the issue is just confusion about finding the UserPlugins folder. Sometimes it's about the broken link on the SWS .dmg. And sometimes it's the issue of notarization on Catalina/Big Sur, having to go into System Preferences and manually allowing something from an unidentified developer. Sometimes it's an issue of *experienced* users moving too fast rather than listening to me! ;-)

I'm sure there is a reason the current Mac SWS installation is the way it is, but I'm writing it ask: is there a way to simplify installation process on the Mac either with creating an automated .pkg and/or fixing the link to "UserPlugins" on the SWS .dmg (which seems to have been broken for several years now)?

Thanks for your work maintaining SWS and let me know if there's any info I can provide that might be helpful in helping address this issue!

[daniellumertz]

noob question related to the latest release:

all the things updated in the pre-release up to v2.12.1.2 pre-release build is now in the stable release?

Also thank you all for the SWS great tool! Use a lot in some scripts

[cfillion]

Yes. It has everything from the pre-releases of the last two years.

[PigeonTheorist]

How do I uninstall the SWS extension package? After installing, Reaper on my Windows 10 machine has become very sluggish. No uninstall instructions could be found in the manual. Please advise how to.

[cfillion]

1. From REAPER: Options > Show REAPER resource path in explorer/finder
2. Go in the UserPlugins directory
3. Remove reaper_sws-x64.dll or reaper_sws-x86.dll (REAPER must be closed first)

[PigeonTheorist]

Originally Posted by cfillion

1. From REAPER: Options > Show REAPER resource path in explorer/finder
2. Go in the UserPlugins directory
3. Remove reaper_sws-x64.dll or reaper_sws-x86.dll (REAPER must be closed first)

Thank you, that did it! Sluggish behavior was very pronounced, as much as 15 second delay in certain operations. The one that the most pronounced, was adding FX through a portion of a track, through the Item Properties-->Take FX setting. That caused no playback to occur for that track and rendering of the mixdown (of three vocal tracks) was delayed about 15 seconds. Just FYI.

[Daodan]

Hi. Is it right place for little request?
I modified me2beats transpose script so now I can convert midi item's pitch to transposed notes in this items.
e.g. Item pitched by n semitones->notes in this item transposed by n and item's pitch id 0.


But there is a problem with pooled midi. if you select 2 polled midi items pitched by 2 semitones and run script notes will be transposed by 4 semitones, not by 2 (pitch*number of pooled items)
Original script have problem with pooled midi as other scripts for transposing. or just ignore pooled midi.
Only SWS/FNG: Transpose selected MIDI items... actions do it right.
So it'll be great to have an action SWS/FNG: Transpose selected MIDI items by item's pitch or something like this.
Of course pooled midi items can be pitched by different amount and I think that put items with different pitch to different pool is good suggestion.

Another is use only one vale of pitch and then transpose and pitch items by this value. It's hard to explain for me, english is not my native, so example will help I guess:
A) 4 pooled midi items in one pool. Items 1 and 2 pitched by +2 semitones, 3,4 - by +14. Result is 1,2 and 3,4 in different pools, items pitch is 0. 1,2 transposed +2, 3,4 transposed +14.

B) 4 pooled midi items in one pool. Items 1 and 2 pitched by +2 semitones, 3,4 - by +14. Result is midi notes transposed +2, pitch of items 1 and 2 is 0, and pitch of 3,4 - +12. Items still in one pool.

I hope at least something is clear😊
If it's impossible to add such an action, then can you give some advice on how to modify my script to make it work with pooled midi as written above? I'll attach script. Thanks.
https://stash.reaper.fm/41547/MIDI%2...ed%20Notes.lua

[Aulicon]

Not sure this is the right place for a new action request...
I noticed that the actions:

SWS/S&M: Copy selected tracks routings
SWS/S&M: Paste routings to selected tracks

Don't carry over the "Master Send" settings (on/off)
I was wondering if it was possible to have a pair of new actions:

SWS/S&M: Copy selected tracks routings (include master send settings)
SWS/S&M: Paste routings to selected tracks (include master send settings)

Cheers!

[Swi]

I feel like I must have done something here so apologies in advance, but I can no longer type in ReaConsole commands in the cycle action editor. I was doing this a couple weeks ago without fail and I have gone back a few versions in Reaper to make sure a dev didn't muck things up.

I can add steps and actions from the action list per usual but when I try to type in a ReaConsole command I am not allowed to type any info into the list. This is the only time I tend to type into the cycle action editor so there may be other reasons to type into the editor that I do not use and thus don't know.

I have made a practice of using this method for adding fx and quite like it.

I can still create these by editing the S&M_Cyclactions.ini file and it all works as expected.

Using
v2.13.2.0 a3693ad5

[nofish]

This doesn't work for you?
What OS are you on?

[Swi]

Nevermind. I got the columns mixed up somehow.... Oy

[javiramallo]

Hi.

I hope you are well.

I noticed that the following actions don't work anymore with points inside "Automation Items".

SWS/BR: Set selected envelope points to first selected point's value
SWS/BR: Set selected envelope points to last selected point's value
SWS/BR: Set selected envelope points to next point's value
SWS/BR: Set selected envelope points to previous point's value


Is there any chance to address it for future releases?

Thanks in advanced!

Javier.

[nofish]

Originally Posted by javiramallo

I noticed that the following actions don't work anymore with points inside "Automation Items".

It's a known issue.
Honestly (and sadly) I wouldn't put too much hope that it gets fixed anytime soon as there are currently very few active SWS contributers (it's open since 2018...).

[Suzuki]

Actions related to floating fx windows do not work for fxs inside container, e.g. SWS/S&M: Close all floating FX windows do not close floating fx inside container.