SWS Extension Updates

[cfillion]

Originally Posted by Buy One

Not critical, just to double check whether this is worth attention

Fixing! The glitch happens when the new color's green channel is higher than 127.

(It's easier to keep track of pending bug reports on the SWS issue tracker than here on the forum.)

[Buy One]

Originally Posted by cfillion

Fixing! The glitch happens when the new color's green channel is higher than 127.

(It's easier to keep track of pending bug reports on the SWS issue tracker than here on the forum.)

Alright, noted.

[cfillion]

Originally Posted by mlprod

Old issue that I am finally reporting.

- Run the SWS loudness analyser on an item/file.
- Delete the file from the project and save.
- Run the project directory cleanup, it will not find the deleted file.
- Quit + restart reaper, open project and run the cleaner again. Now it will find the deleted file.

Confirmed. (EDIT: Posted it to the SWS issue tracker for safekeeping: https://github.com/reaper-oss/sws/issues/1300)

As a workaround you can either leave the Loudness window open while deleting the media item from the project or reopen it before cleaning the project directory.

[dangguidan]

Please fix the bug in groove tool.
If CC is used in MIDI, run the script, select the notes, get user groove, select other notes, apply groove, the Bezier curve attribute in CC will be lost, and extend item, and some data will be copied later.

[chumbo]

In SWS Zoom Preferences, I have the first three check boxes ticked...
- Zoom with middle-mouse...
- No-drag click zooms to item...
- No-drag click to undo zoom

If I middle-mouse click an item to zoom, I can easily exit by middle-mouse clicking outside of the item as there always is an empty space somewhere outside the item.

But if i make a marquee selection using the middle-mouse, then there is no 'outside' area to click to exit the zooming.
So I enabled the option in SWS Zoom Preferences 'Undo SWS zooms only ' but it doesn't work?
It just undoes the normal Reaper Undo list ignoring the SWS zoom...any ideas what could be wrong?
Thanks!

[nofish]

Originally Posted by chumbo

But if i make a marquee selection using the middle-mouse, then there is no 'outside' area to click to exit the zooming.

Middle-click in ruler area works here to undo zoom.

So I enabled the option in SWS Zoom Preferences 'Undo SWS zooms only ' but it doesn't work?
It just undoes the normal Reaper Undo list ignoring the SWS zoom...any ideas what could be wrong?

That's maybe a bit misleadingly worded.
Afaik SWS zoom history doesn't appear in Reaper's undo history at all, no matter what settings you have set in SWS Zoom Preferences.
You'd still need to use one of the Zoom tool ways to undo zoom, this option just means that any things you do in between zooming in and out (like scrolling) aren't undone with this option ticked.

Personally I use the option Drag upwards -> Zoom undo:

[Smittefar]

I don't know, if this is only my setup, or the functionality is generally broken.

I love the SWS loudness extension and I use it a lot in my workflow. One of my favourite features is that you can click on the "Maximum short term loudness", and it takes you to the point in the item, where this occurred.

I even made a (LOONG) video about how I use it in my mastering workflow https://youtu.be/aCDkmmkr1Rg

But recently, this functionality has been broken for me - In this short video, I show how double clicking on the max true peak still does the right thing, but when I double click on max short-term or momentary loudness, I end up far outside the items, so it is obviously not the right place https://youtu.be/4yidrsbLHKA

[nofish]

Originally Posted by Smittefar

I don't know, if this is only my setup, or the functionality is generally broken.

Hi and welcome to Reaper forums.
I guess you're using high precision mode for analyzing (set via the Options button)?
If so, there's indeed a bug in current SWS going to max short-term/momentary when having analyzed in high precision mode.
So to get around it, you can disable high precision mode, analyze again and it should work ok.

Note that high precision mode was only implemented for a corner case use and in majority of cases 'normal' mode works just fine.

Hope this helps.

[Smittefar]

Originally Posted by nofish

Hi and welcome to Reaper forums.
I guess you're using high precision mode for analyzing (set via the Options button)?
If so, there's indeed a bug in current SWS going to max short-term/momentary when having analyzed in high precision mode.
So to get around it, you can disable high precision mode, analyze again and it should work ok.

Note that high precision mode was only implemented for a corner case use and in majority of cases 'normal' mode works just fine.

Hope this helps.

THANK YOU - This helped a lot - I just tested, and the problem is gone

[dalim.biswas]

Its been a year no updates yet .SWS works are pretty good.I want some scripts for play selected media item simultaneously on different track .
only one media item play on single track Reaper has lack this function even in Project tab .Reaper also lack this inbuilt function of playing media items on different track on different area of track.

[SG Deluxe]

https://www.youtube.com/watch?v=a99xarYr284

[Triode]

I've just noticed that when you execute this command and the region/marker lane is thick so that overlapping regions and markers are drawn on seperate lines they become overlapping again unless you drag the division line above the TCP and ruler or do a Renumber Marker IDs command.

[matt37137]

Hi,

Possibilities are great with sws, I love it. Have a question thou.
I want to replace fx chain on selected track. It works great and without any latency, but it doesn’t work while recording. How to fix that?

Second thing I was hoping to find is option to select next possible fix chain, instead of selecting with numbers, tried with writing n+1 or +1 to promped frame, but with no luck. Anybody know how it can be done? I want to have fx chain presets that I can change live with midi. For now I got to work toggle effect on/off while recording.

Sorry for photo of a screen, but did that in a hurry

[nofish]

Hi and welcome to Reaper forums.

Originally Posted by matt37137

I want to replace fx chain on selected track. It works great and without any latency, but it doesn’t work while recording. How to fix that?

Indeed some SWS actions don't work during recording. They were disabled during recording 'for safety reasons' at some point. Needs to be discussed/decided if they could be safely re-enabled but that didn't happen (completely) yet.
https://github.com/reaper-oss/sws/issues/913
So for now that means it's the way it is, sorry.

[80icio]

Are you guys experiencing any issues with contextual toolbars over TCP?
mine don't appear over the TCP in arrange window

[matt37137]

Thats a pitty, thanks anyway nofish. I saw that someone post a solution in link You provided, but not for whole safety feature, but only one action. Need to look for different route.

[nofish]

Originally Posted by 80icio

Are you guys experiencing any issues with contextual toolbars over TCP?
mine don't appear over the TCP in arrange window

If you're using Reaper v6, latest SWS beta is needed for contextual toolbars to work over TCP:
https://www.sws-extension.org/download/pre-release/

[80icio]

Originally Posted by nofish

If you're using Reaper v6, latest SWS beta is needed for contextual toolbars to work over TCP:
https://www.sws-extension.org/download/pre-release/

it's working! thanks so much!

[Funkybot]

Where should SWS issues get reported? The SWS/BR Cycle Record Modes action will crash Reaper after the second or third running of that action. I created a custom Cycle Action to work around it, but figured I should report it.

[_Stevie_]

GitHub

[cfillion]

Originally Posted by Funkybot

The SWS/BR Cycle Record Modes action will crash Reaper after the second or third running of that action.

Thanks, fixing!

[ruinatokyo]

Sorry if this is not the place...

I would love some extra functionality in SWS Reposition, to have an option to maintain overlapping items. Non-overlapping items would be stacked up all against each other while overlapping items would stay overlapping while being stacked up against the surrounding items.

Is that possible?

Thanks!

[lb0]

Hi nofish et all,

Just a heads up - don't know if this has been mentioned yet as I haven't read the entire thread - but found a bug in a function I use quite a bit.

BR_TrackFX_GetFXModuleName

The bug is that it ignores video processor entries in the FX list.

and because it ignores them - all the fx indexes become out of sync for any subsequent fx in the chain.

So say I have

FX 0: ReaEQ
FX 1: Video Processor
FX 2: ReaComp

looping through 0-2 track fx indexes and running BR_TrackFX_GetFXModuleName on the index - you get

FX 0: ReaEQ.dll
FX 1: ReaComp.dll
FX 2: <nothing>

I'm guessing it's just not looking out for the <VIDEO_EFFECT tag or maybe it gets confused by the additional < > characters used to identify the CODE section.

An example of video effect chunk data:

<VIDEO_EFFECT "Video processor" ""
<CODE
|// Item fades affect video
|input_track(0) > 0 ? (
|  input_info(0,project_w,project_h,0,ta=0);
|  ta < 1 ? (
|    gfx_blit(input_next_item(0),1);
|    (gfx_a=ta)>0 ? gfx_blit(0,1);
|  );
|);
>
CODEPARM 0.0000000000 1.0000000000 0.0000000000 0.0000000000 1.0000000000 0.0000000000 1.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000
>
FLOATPOS 1695 1479 897 553
FXID {FE26B8AD-3BC4-478F-A131-BE729344B478}
WAK 0 0

Anyway - thought I'd mention this. And as always - thanks for all your work on this amazing extension - without it - it would be impossible to create pretty much all of my scripts.

Thanks,
Leon.

EDIT: Just realized I should have posted this on github - which I have now done:

https://github.com/reaper-oss/sws/issues/1326

[zenykmusic]

(Xenakios/SWS: Switch item source file to next in folder) how to make what he switch midi file.

[David Carlyon]

Originally Posted by nofish

If you're using Reaper v6, latest SWS beta is needed for contextual toolbars to work over TCP:
https://www.sws-extension.org/download/pre-release/

I am having this problem too (along with radial menu) i installed latest SWS beta and still no luck, have i done something wrong?

[nofish]

Originally Posted by David Carlyon

I am having this problem too (along with radial menu) i installed latest SWS beta and still no luck, have i done something wrong?

Hm..works here.
Could you check which SWS version is displayed in Extensions > About SWS Extension? (just to make sure Reaper 'sees' the correct version).

[David Carlyon]

Originally Posted by nofish

Hm..works here.
Could you check which SWS version is displayed in Extensions > About SWS Extension? (just to make sure Reaper 'sees' the correct version).

Will check that out now and report back.

I also have one more SWS related question. I dont know where to ask it, but i also don't want to start a new thread to ask something that may have been covered many times.

I have shortcuts set up for 'show plugin 1' through to 'show plugin 8'
Is there any way i can make more actions, so i can go up to, say, 10 plugins?
There are a number of actions that stop at number 8, i often wish they would go higher.
Cheers!

[GonZ]

Hello. I have a toolbar with some "Grid: Set to X / X". Moreover I have the SWS / AW: Toggle triplet grid. If I'm in 1/4 grid division (as instance) and I click in the triplet icon, the 1/4 is deselected. If I run the action instead, both, the 1/4 and triplet icons are selected. I thinks it's an odd behavior, doesn't it?

[Breeder]

Originally Posted by GonZ

Hello. I have a toolbar with some "Grid: Set to X / X". Moreover I have the SWS / AW: Toggle triplet grid. If I'm in 1/4 grid division (as instance) and I click in the triplet icon, the 1/4 is deselected. If I run the action instead, both, the 1/4 and triplet icons are selected. I thinks it's an odd behavior, doesn't it?

It is, it's due to other SWS team members messing the commit I did. Talk to them here and have them revert it to my original commit (which has been installed on my machine for months and works 100% in all situations I've tested it): https://github.com/reaper-oss/sws/pull/1258

[nofish]

Originally Posted by Breeder

It is, it's due to other SWS team members messing the commit I did. Talk to them here and have them revert it to my original commit (which has been installed on my machine for months and works 100% in all situations I've tested it): https://github.com/reaper-oss/sws/pull/1258

Your pull request #1258 isn't merged yet into the beta/official codebase so 'it's due to other SWS team members messing the commit I did' is not correct.

[Breeder]

Originally Posted by nofish

Your pull request #1258 isn't merged yet into the beta/official codebase so 'it's due to other SWS team members messing the commit I did' is not correct.

Okay, hopefully all will work when it's released, it was a bitch to code properly so everything everywhere stays properly updated

[KODA JYNX]

I just installed the most recent build, and it took away everything that I rely on for every project!!!!!!! WTF?????!!!!

Help please!

[JonasHAnd]

Could someone on MacOS test the notes window?

I'm having the following issues;

1. Wrap Text not working
2. Global notes not showing for new project tab, only works for new project at startup.


SWS v2.10.0
Reaper 6.07
OSX 10.9.5


EDIT: Global notes seems fixed with bleeding edge version, but still no wrapping...

In Github i can read the following:

Notes:
+Fix bad encoding conversion when toggling "Wrap text" on Windows (Issue 1252)
+Fix bad encoding conversion and truncation to 256 characters when toggling "Wrap text" on Windows (Issue 1252)
+Fix non-working word wrapping on Linux and macOS

!v2.11.0 pre-release build
<strong>Reminder: this new SWS version requires REAPER v5.979+!</strong>

Shouldn't this mean that word wrapping is fixed in the bleeding edge version?
Or has this change not been written into the build yet?

I'm sorry for being a noob, just wondering what to make of this, is it still a bug or is it fixed but not rolled out even in the bleeding edge version?

I've tried both the 20191203 and the 20191207 builds of 2.11.0


Thanks
/Jonas

[nofish]

The authoritative change log for current pre/bleeding edge version can be found here:
https://www.sws-extension.org/download/pre-release -> whatsnew.html

So no, the Notes fixes you quoted are not yet in current pre/bleeding edge version (v2.11.0), unfortunately.

[ovnis]

Hello, is it possible to add an action to focus/activate the window (the main window or the midi editor window) which is under the mouse ?

[JonasHAnd]

Originally Posted by nofish

The authoritative change log for current pre/bleeding edge version can be found here:
https://www.sws-extension.org/download/pre-release -> whatsnew.html

So no, the Notes fixes you quoted are not yet in current pre/bleeding edge version (v2.11.0), unfortunately.

Ok, would it be possible to get a compiled version with the notes wrap fix added?

As kind of a Bleeding edge of a bleeding edge release.

Or if this is not possible could I somehow edit the latest pre release myself and add the lines from here...

https://github.com/cfillion/sws/blob...nM/SnM_Notes.h


...to the dylib file? (To fix the wrap issue on mac)

[nofish]

Ok, would it be possible to get a compiled version with the notes wrap fix added?

As kind of a Bleeding edge of a bleeding edge release.

Personally I can only do SWS builds for Windows currently, so can't help with a Mac version.
But you could build the Mac version from source yourself:
https://github.com/reaper-oss/sws/wi...-SWS-Extension

Or if this is not possible could I somehow edit the latest pre release myself and add the lines from here...

https://github.com/cfillion/sws/blob...nM/SnM_Notes.h


...to the dylib file? (To fix the wrap issue on mac)

The dylib file is a binary file, not possible to alter the source code in it after the fact (i.e. after building) to my knowledge.

[cfillion]

Originally Posted by JonasHAnd

Ok, would it be possible to get a compiled version with the notes wrap fix added?

Here you go (macOS 64-bit): https://cfillion.ca/files/sws/sws-2....8-fda51041.dmg.

[vsthem]

Having Track Height Lock not work with SWS track sizing scripts is absolutely killing me. I see that it was fixed in a previous version, but I guess that created some of its own bugs and was removed.

Could I revert to this previous version of SWS? Or were the bugs worse than what's currently there?

Is it safe/reasonably easy to revert to a previous version of SWS?

Would I lose my custom actions/shortcuts?

Any other advice on this? If there was a hint as to when an update might come out, I could just put it off.

Thanks all!

[JonasHAnd]

Originally Posted by nofish

Personally I can only do SWS builds for Windows currently, so can't help with a Mac version.
But you could build the Mac version from source yourself:
https://github.com/reaper-oss/sws/wi...-SWS-Extension

Cool, thanks for the link

I'm not sure I'm capable of building it myself though as I'm not a programmer. But I'm tempted to try to follow the instructions in your link anyway.

Here's what I've tried so far;



My first attempt was with this older version of git that seemed to be pre installed.

git --version
git version 1.9.5 (Apple Git-50.3)

Then I did this as per the instructions in the link

git clone --recursive https://github.com/reaper-oss/sws

Which created a SWS directory. And then:

cd sws

Then did step two from my portable Reaper install, saved the file to the vendor directory in SWS repository as per instructions

Then # Step 2: Generate reaper_plugin_functions.h
# - Run the REAPER action "[developer] Write C++ API functions header".
# - Save the file inside of the vendor directory.

I didn't have cmake installed as the terminal didnt recognize the command "cmake"

So I tried installing via homebrew but got this:

brew install cmake
Warning: You are using macOS 10.9.
We (and Apple) do not provide support for this old version.
You will encounter build failures with some formulae.
Please create pull requests instead of asking for help on Homebrew's GitHub,
Discourse, Twitter or IRC. You are responsible for resolving any issues you
experience while you are running this old version.

==> Installing dependencies for cmake: gdbm, openssl@1.1, readline, sqlite, xz, python and sphinx-doc
==> Installing cmake dependency: gdbm
Error: An exception occurred within a child process:
NoMethodError: undefined method `source' for nil:NilClass

So installing via homebrew didn't work.

So then I installed cmake gui version from cmake.org

Then I tried installing the cmake command line tools with

$ sudo "/Applications/CMake.app/Contents/bin/cmake-gui" --install
Password:
Linked: '/usr/local/bin/cmake' -> '/Applications/CMake.app/Contents/bin/cmake'
Linked: '/usr/local/bin/ctest' -> '/Applications/CMake.app/Contents/bin/ctest'
Linked: '/usr/local/bin/cpack' -> '/Applications/CMake.app/Contents/bin/cpack'
Linked: '/usr/local/bin/cmake-gui' -> '/Applications/CMake.app/Contents/bin/cmake-gui'
Linked: '/usr/local/bin/ccmake' -> '/Applications/CMake.app/Contents/bin/ccmake'

After that cmake seemed to be installed, so I did step #3 in the intructions

$ cmake -B build -DCMAKE_BUILD_TYPE=Debug
-- The C compiler identification is AppleClang 6.0.0.6000057
-- The CXX compiler identification is AppleClang 6.0.0.6000057
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PHP: /usr/bin/php (found version "5.4.45")
-- Found Perl: /usr/bin/perl (found version "5.16.2")
-- Found WDL: /Users/JonasHAnd/downloads/sws/vendor/WDL
-- Found LICE: /Users/JonasHAnd/downloads/sws/vendor/WDL/WDL/lice
-- Found PNG: /Users/JonasHAnd/downloads/sws/vendor/WDL/WDL/libpng
-- Found ZLIB: /Users/JonasHAnd/downloads/sws/vendor/WDL/WDL/zlib
-- Found SWELL: /Users/JonasHAnd/downloads/sws/vendor/WDL/WDL/swell
-- Found JNetLib: /Users/JonasHAnd/downloads/sws/vendor/WDL/WDL/jnetlib
CMake Deprecation Warning at vendor/taglib/CMakeLists.txt:6 (cmake_policy):
The OLD behavior for policy CMP0022 will be removed from a future version
of CMake.

The cmake-policies(7) manual explains that the OLD behaviors of all
policies are deprecated and that a policy should be set to OLD only under
specific short-term circumstances. Projects should be ported to the NEW
behavior and not rely on setting a policy to OLD.


-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of short
-- Check size of short - done
-- Check size of int
-- Check size of int - done
-- Check size of long long
-- Check size of long long - done
-- Check size of wchar_t
-- Check size of wchar_t - done
-- Check size of float
-- Check size of float - done
-- Check size of double
-- Check size of double - done
-- Performing Test HAVE_STD_ATOMIC
-- Performing Test HAVE_STD_ATOMIC - Failed
-- Performing Test HAVE_GCC_ATOMIC
-- Performing Test HAVE_GCC_ATOMIC - Success
-- Performing Test HAVE_BOOST_BYTESWAP
-- Performing Test HAVE_BOOST_BYTESWAP - Failed
-- Performing Test HAVE_GCC_BYTESWAP
-- Performing Test HAVE_GCC_BYTESWAP - Success
-- Performing Test HAVE_VSNPRINTF
-- Performing Test HAVE_VSNPRINTF - Success
-- Performing Test HAVE_ISO_STRDUP
-- Performing Test HAVE_ISO_STRDUP - Failed
-- Found TagLib: /Users/JonasHAnd/downloads/sws/vendor/taglib (found version "1.11.1")
-- Performing Test HAVE_WFORMAT_OVERFLOW
-- Performing Test HAVE_WFORMAT_OVERFLOW - Failed
-- Performing Test HAVE_WDEPRECATED_REGISTER
-- Performing Test HAVE_WDEPRECATED_REGISTER - Success
-- Found Git: /usr/bin/git (found version "1.9.5 (Apple Git-50.3)")
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/JonasHAnd/downloads/sws/build

So there was some failure messages but a build was created.

I then tried doing step #4 while in the SWS folder

$ cmake --build build
Scanning dependencies of target z
[ 1%] Building C object CMakeFiles/z.dir/vendor/WDL/WDL/zlib/adler32.c.o
clang: error: unknown argument: '-fstack-protector-strong'
make[2]: *** [CMakeFiles/z.dir/vendor/WDL/WDL/zlib/adler32.c.o] Error 1
make[1]: *** [CMakeFiles/z.dir/all] Error 2
make: *** [all] Error 2

That didn't work so I thought maybe I should update git to the latest version and start over again..

So I went to https://git-scm.com/download/mac

and got the latest version for mavericks which was v2.23.0

after installing the pkg I still get

git --version
git version 1.9.5 (Apple Git-50.3)

So now I'm a bit stuck... What am I doing wrong here? Is my git version to old or am I doing something else wrong?

And sorry for the long post!