SWS Extension Updates

[Loulou92]

Originally Posted by mschnell

It's always a critical decision if it makes sense to have a (most of the time unproductive ) polling loop run faster.
There is only a single "GUI-Thread" in an application. Same is used in Reaper for everything, that does not take place within a track. Of course a single such thread only uses a single CPU.

That is why any polling loop eats valuable resources and making it faster on one hand improves the responsiveness of same, but might degrade the responsiveness of the total system.

In fact I don't know but doubt that the SWS console uses another thread but the standard GUI thread.

I don't know it it's possible to do an event driven approach fro hat you have in mind. This would be a lot better than doing a polling loop.

-Michael

Thx for your answer ! Sorry but I'm not english & not sure I follow everything you say ^^. You mean the loop might indeed be *faster* in its execution, but also have an impact on the responsiveness of all the rest, the GUI, and all Reaper -side effects basically- ? "technically speaking" you tend to confirm that in some context a loop is indeed a boost of some sort right, like the mushroom in Mario Kart hihi. If the loop is in a cycle action itself embeded into a script that prevents UI refresh, maybe the single thread UI thing would not be as much of a drag ?... Hard to know (and to test with a good degree of certainty); this is why I reach out to knowledgeable people like u !

[nofish]

Originally Posted by Loulou92

If the loop is in a cycle action itself embeded into a script that prevents UI refresh,

From SWS v2.12.1 pre-release onwards you can enable prevent UI refresh for a cycle action directly in the cycle action editor (no need to wrap in a script just for that).

[Loulou92]

Yes Nofish thanks, but the script doesn't do only that (prevent ui refresh) . On a side-note I also noticed that the prevent UI from the cycle action editor doesn't do exactly the same thing as the one launched from a script. The one from the cycle action editors still show some changes in track selection during a cycle action, whereas a prevent UI from a .lua script does not.

But that's a bit off-topic.

Without a definitive answer on my question, I think I won't bother to create loops here and there.

[Breeder]

Originally Posted by Loulou92

Yes Nofish thanks, but the script doesn't do only that (prevent ui refresh) . On a side-note I also noticed that the prevent UI from the cycle action editor doesn't do exactly the same thing as the one launched from a script. The one from the cycle action editors still show some changes in track selection during a cycle action, whereas a prevent UI from a .lua script does not.

But that's a bit off-topic.

Without a definitive answer on my question, I think I won't bother to create loops here and there.

As far as I remember there was a problem in old builds where preventing UI refresh made some zoom actions not work so this is probably the reason because there was a fix to handle that.

[Loulou92]

No I'm on one of the latest SWS version, a build provided by Cfillion that solves the 1MO W10 limitation for Cyclaction.ini. I'll wait the next big SWS update to update, but it's pretty up to date (the build has a month or so). What I see has nothing to do with zooms, it's just that I see track selection change (as required by the cycle action), but I should not see it with the prevent UI option ticked, right ? Yet it happens. And if the same action is executed within a script that prevent UI refresh etc etc (I'm a total noob with scripts, I copy paste stuff here and there), there is a perfectly still execution. Again, that has little to do with my initial question (although suspected bug report is probably welcome in this thread) ^^ so if someone knows one thing or two about the guts of the SWS console loop function, don't hesitate to chime in.

xxxxxxxxxxx

[cfillion]

Originally Posted by Loulou92

I see track selection change (as required by the cycle action), but I should not see it with the prevent UI option ticked, right ? Yet it happens. And if the same action is executed within a script that prevent UI refresh etc etc (I'm a total noob with scripts, I copy paste stuff here and there), there is a perfectly still execution.

A cycle action running with the Prevent UI refresh option enabled should behave the same as as script running the exact same actions using PreventUIRefresh. Can you share the cycle action that doesn't appear to do that and the script?

Originally Posted by Breeder

As far as I remember there was a problem in old builds where preventing UI refresh made some zoom actions not work so this is probably the reason because there was a fix to handle that.

The "fix" for that was making the feature optional (the affected zoom actions require REAPER to synchronously recalculate track heights).

[Loulou92]

Here you go. Notice that after I launch the action, a bunch of tcp tracks (a parent and its children to be precise)get selected for a moment. This corresponds to something that is done inside the cycle action. For this action, after verification, a prevent ui refresh via script does not work either.


BTW on the GIF you can see that the action takes 1-2 seconds to process, which is too long for my taste, this is why I ask for the Loop thing, to know if I could gain some precious milliseconds here and there (the cycle action here is very long for example (it does many things in the background, on hidden tracks (!!!), not only copy paste)).

[cfillion]

If you disable the Prevent UI refresh option in the CA editor then run that Lua script, do you get the same UI flickering as running the Cycle Action with the option enabled?

[Loulou92]

Yes !

[cfillion]

Sounds like one of the actions in the CA does a PreventUIRefresh(-1) first. REAPER redraws/recalculate stuff when the counter reaches 0. The CA editor option increases it by 1. Your Lua script does the same before running the cycle action (making it 2 when the CA editor option is also enabled). If one of the actions decreases the counter by 1 first, it will reach 0 (1-1) when running the CA directly (= redraw), but still be 1 (2-1) when wrapped by your script (= no redraw).

This is just a guess of course...

[Loulou92]

Originally Posted by cfillion

Sounds like one of the actions in the CA does a PreventUIRefresh(-1) first. REAPER redraws/recalculate stuff when the counter reaches 0. The CA editor option increases it by 1. Your Lua script does the same before running the cycle action (making it 2 when the CA editor option is also enabled). If one of the actions decreases the counter by 1 first, it will reach 0 (1-1) when running the CA directly (= redraw), but still be 1 (2-1) when wrapped by your script (= no redraw).

This is just a guess of course...

Ok understood, you might be right, I'll investigate.

[babag]

not sure if this is addressable but it's been driving me crazy recently:

Xenakios/SWS: Choose new source file for selected takes

been using this a lot on recent project because the native option in the media explorer always starts the inserted media at the start point of the file and does not respect when an item might be minutes in on a long file. the xen/sws action does respect positioning in this case. problem for me is that the action does not remember the last place i searched. it always defaults to my home directory, which is a long way from where my files are and results in a LOT of clicking, every time, to get to my files. would really appreciate the ability to remember the filepath.

thanks,
babag

[nofish]

^^ SWS related bug reports/feature requests should better go to the SWS issue tracker so they don't get lost here.

For now, as a workaround, maybe you could place shortcut(s) in your home directory which point to where your files are?

[babag]

thanks, nofish. posted there.

babag

[vsthem]

Is there a version of SWS that successfully allows A/B Track Height adjustments to obey track locking?

[cfillion]

v2.12 (currently in pre-release: https://www.sws-extension.org/download/pre-release/) added an action called "SWS/NF: Toggle obey track height lock in vertical zoom and track height actions" which affects the A/B action.

[Etc.etera]

I've just noticed that the Loudness Normalization seems to be 3dB too loud. I made a post about it here:

https://forum.cockos.com/showthread.php?t=247869

Is this a known issue?

[Technical Void]

The action "SWS: select one track(s) with selected item(s)" Is missing from my actions list. Does anybody know why?

[cfillion]

It's "SWS: Select only track(s) with selected item(s)" (SWS_SELTRKWITEM).

[Technical Void]

Originally Posted by cfillion

It's "SWS: Select only track(s) with selected item(s)" (SWS_SELTRKWITEM).

Ah! Thank you.

[nicholas]

Originally Posted by nofish

^^ SWS related bug reports/feature requests should better go to the SWS issue tracker so they don't get lost here.

Thanks for posting ...

[ryansalmond]

Is there a way to get snapshots to recall record-arm states for tracks?

Sorry if this is the wrong thread to ask in.

[EpicSounds]

2 years since the last featured release

v2.12.1 is up now
https://www.sws-extension.org/

https://www.sws-extension.org/whatsnew.php


I *might* make a 'what's new' video about the changes

[sws]

Yes I thought it would be fun to update exactly 2 years to the day.
Enjoy!

[matt_t]

Thank you!

[mozart999uk]

Originally Posted by EpicSounds

2 years since the last featured release

v2.12.1 is up now
https://www.sws-extension.org/

https://www.sws-extension.org/whatsnew.php


I *might* make a 'what's new' video about the changes

That would be very useful!

[BartR]

Originally Posted by EpicSounds

2 years since the last featured release

v2.12.1 is up now
https://www.sws-extension.org/

https://www.sws-extension.org/whatsnew.php


I *might* make a 'what's new' video about the changes

Thank you so much!

[EpicSounds]

https://reaperblog.net/2021/02/whats...n-2-12-update/

https://youtu.be/-ymOax9qFQY

[mozart999uk]

When using the SWS region playlist, I'm still getting an error message about nested markers or regions and also some weird playback behaviour.

I've got a region defined that has markers within it. The markers are important for my project so I don't want to delete them.

Is there a way round this?

[MagicRat]

I make a lot of use of the Region Playlist, it is great. But I can not get the shuffle regions option to work. Is it a bug or is it me?

[Yanick]

Apparently the API bug for finding the track under the mouse cursor. I have a script for creating an item by double-clicking on a track, I use the SWS API there (I will attach the script under the post). The script assigned in mouse modifiers. However, if you create an item, then change the vertical zoom with the mouse wheel, then without scrolling and mouse clicking try to create an item again, the track is incorrectly detected, it is created 1+ track higher than expected track

[RobertP]

Potential bug with sws notes action and Reaper 6.23 posted on github
https://forum.cockos.com/showthread....97#post2413097

[Kr3eM]

EDIT: Of course dyslectic me wrote down the wrong SWS action. however now I can reproduce the crash. Would be nice if someone else could confirm.

1. Install clean portable version
Reaper 6.25 x64 / Windows 7 SP1 x64
SWS 2.12.1.3

2. Run Reaper, cancel plugin Scan and Select proper Audio Device

3. Open Actions and run (set to ON)
SWS/NF: Toggle obey track height lock in vertical zoom track height and actions

4. Create two tracks

5. Create a Midi Item on track 2 and right click TCP and select Lock Height

6. Select Midi Item and run

SWS: Toggle zoom selected items, minimize others

or

SWS: Toggle zoom selected items or time selection, minimize others


This produce a crash everytime.

So is this considered a SWS bug or a Reaper bug?

[Finnish]

Latest SWS Extension working in Mac Big Sur M1 Reaper64.

[Tod]

I just installed the latest SWS and ran into a problem, a "SWS - Error" window appeared that I needed to delete the reaper_sws64.dll, which I did.

Did I lose anything by doing this?

[cfillion]

Originally Posted by Tod

Did I lose anything by doing this?

Only the previous version. The installer should have automatically deleted it though. By curiosity, in which folder was the old dll located? And was REAPER closed when you installed the update?

(reaper_sws64.dll is the old name, reaper_sws-x64.dll is the new version)

[jnif]

The SWS action "SWS/FNG: Set selected MIDI items name to first note" is crashing Reaper when "MIDI octave name display offset" is set to negative, for example -1, in preferences.

Looks like the crash is caused by out-of-bounds array access in CmdSetItemNameMidi::doCommand function.
Pitch becomes negative for low notes. And the remainder operator will return a negative value here

int nameIndex = pitch % 12;

and the negative nameIndex is used here

strcpy(noteName, noteNames[nameIndex]);

causing out-of-bounds access.

Tested using latest SWS stable version 2.12.1.3


jnif

[nofish]

^ Want to submit a pull request by chance, since you already debugged it?

[jnif]

Originally Posted by nofish

^ Want to submit a pull request by chance, since you already debugged it?

Thanks for asking, but I prefer not to do that.
To submit a fix I would have to install build tools, test the fix, and create a new github account. I don't have time to do that now.


jnif

[napochan]

Maybe this obvious to most users, but how do I remove an old version of SWS extensions so I can upgrade to the latest version?

I can install SWS v2.12.1 #3 but when I run Reaper (v6.25), it says several versions are installed and to remove the extra versions, but I don't know which files to remove and whether that will prevent Reaper from running.

Would appreciate some guidance so I don't wreck things and can enjoy the latest SWS features.
TIA