SWS Extension pre-release builds

[Ed Rako]

Hello everybody! I make my repost also here just in case! )) I decided to create some actions through Cycle Actions.I use CONSOLE x Time Adjustment Delay. But the console does not add JS plugins with long names. It's some kind of bug or something I'm stupid? )))))))

[Gianfini]

Hi,
how comes this thread is not Sticky here? It's referenced from the SWS site as the thread to discuss about new developments/pre-releases but it's little active...

where should it be to discuss for new developments?

thanks
g

[EvilDragon]

There seem to be not much in new developments because nobody is actively at the helm of SWS anymore. Tim is still there but seems like he just doesn't have the time... Nofish did a couple of actions recently. Bugfixes are sorely needed but nobody seems to want to tackle them since there's so many...

[Gianfini]

Pretty sad... considering that part of what keeps Reaper on par (if not better) than competition are actually features possible thanks to SWS addons...

Hope this comes back to being a relevant piece of Reaper value prop

g

[lowellben]

Originally Posted by Gianfini

Pretty sad... considering that part of what keeps Reaper on par (if not better) than competition are actually features possible thanks to SWS addons...

Hope this comes back to being a relevant piece of Reaper value prop

g

This is absolutely true. But don't hold your breath Cockos will jump on SWS integration anytime soon. Call it a hunch.

[MRMJP]

The possibilities with SWS is probably what made the difference of me switching from Pro Tools to REAPER.

I hope that it's not abandoned.

A month or two ago Tim actually addressed some bugs that I had submitted since I started using REAPER. There was an official update and a few beta updates just a little while back but now it seems to be back to silence.

[sws]

Hey guys, I rolled in the way-too-long pending contributions in GitHub and posted a new 2.9.5 pre-release version. I'm especially interested in Reaper 5.5 compatibility issues, please let me know!

(btw known are various automation item issues with SWS actions)

[vanhaze]

Thats great, thanks a bunch sws !

[ovnis]

Great !

Have you advanced to solve the snapshot issue with send envelopes ?

[EvilDragon]

No changes there. From what it seems, snapshots were never meant to store send envelope data, so that's probably all there's to it.

[ovnis]

If we can't solve send envelope issue, why wouldn't we prevent Snapshot from handling the send envelope?

[EvilDragon]

That is a good question. I would assume it's a tricky matter since it's handling the RPP chunks directly.

[X-Raym]

Beware that this 2.9.5.0 release has incompatibility issue with scripts using BR_Envelopes (it makes REAPER instant crash).

[musicbynumbers]

Originally Posted by sws

Hey guys, I rolled in the way-too-long pending contributions in GitHub and posted a new 2.9.5 pre-release version. I'm especially interested in Reaper 5.5 compatibility issues, please let me know!

(btw known are various automation item issues with SWS actions)

Thanks, much appreciated!

[nofish]

v2.9.5 pre-release build (August 30, 2017)

Fixes:
Issue 587: "SWS/AW: Toggle auto group newly recorded items" now also works in takes recording mode
- Added related action "SWS/AW/NF: Toggle assign random colors if auto group newly recorded items is enabled"

This comes from me, so let me know if issues occur while testing this.

[X-Raym]

BR envelopes bug is in fact fixed is you use REAPER v5.50 RC versions :P

@nofish
Thanks for all your work on this release !

[sws]

Originally Posted by ovnis

If we can't solve send envelope issue, why wouldn't we prevent Snapshot from handling the send envelope?

This is a long standing issue. See https://github.com/reaper-oss/sws/issues/537 for details.

Originally Posted by X-Raym

@nofish
Thanks for all your work on this release !

This 100 times over. SWS needs help from people like you, nofish! Thank you, thank you, thank you.

[ertugrulgul]

Hi, I want to change my default track mixer height, insert number, send number and fx parameter number as I want. I think this is possible with "Apply track template to newly created tracks" action. Please add this action.

[sws]

Originally Posted by ertugrulgul

Hi, I want to change my default track mixer height, insert number, send number and fx parameter number as I want. I think this is possible with "Apply track template to newly created tracks" action. Please add this action.

I feel like you'd be just fine using the existing native "insert tracks from template" command instead of just adding tracks, or using the "SWS/S&M: Resrouces - Apply track template..." commands. The notion of "newly created tracks" isn't something the SWS extension knows, it really can only tell if a track is selected or not.

[drummerboy]

Related to: Fix small issue with action "SWS/AW: Toggle auto group newly recorded items"

I still have a small issue with auto group:

- I assigned "R" to "SWS/AW: Record Conditional (normal/time selection/item selection, automatically group simultaneously recorded items)"
- And space-bar to "SWS/AW: Play/Stop (automatically group simultaneously recorded items)"

I have to stop recording by pressing R in order to make auto-grouping work.
If I stop with space-bar (as I'm used to), it doesn't group.
Also tried with space-bar assigned to standard transport:start/stop - no difference.
Tried with latest Reaper RC 21 and the latest standard version.

Thx to everyone involved with SWS extensions!

[MorkV]

hi, not works snapshot if in a project have >100 tracks.
Suppose that we have 105 tracks, selects 102 and 103 tracks and creates a snapshot.
Save this project and reload him, now this snapshot not select these tracks.

[amagalma]

Originally Posted by nofish

v2.9.5 pre-release build (August 30, 2017)

Fixes:
Issue 587: "SWS/AW: Toggle auto group newly recorded items" now also works in takes recording mode
- Added related action "SWS/AW/NF: Toggle assign random colors if auto group newly recorded items is enabled"

This comes from me, so let me know if issues occur while testing this.

Thank you so much nofish for making it work with takes mode!

There is a small misbehaviour with the action "Toggle assign random colors...": if one records a new take over an existing take, then it changes the color of the previous take too. See:



My take 1 for both simultaneously recorded items was randomly painted cyan color (0:00). Nice! I can now clearly see they were recorded together. I then record a new take (0:04). My take 2 gets automatically painted orange-brownish (0:08). Good! But... my take 1 in the same region got automatically painted green and now I cannot clearly see that Take 1 and the region of Take 1 above Take 2 are actually the same take! (0:20)

[nofish]

@amagalma

I see the issue, thanks for the detailed report. I'll have a look.

[nofish]

Originally Posted by drummerboy

Related to: Fix small issue with action "SWS/AW: Toggle auto group newly recorded items"

I still have a small issue with auto group:

- I assigned "R" to "SWS/AW: Record Conditional (normal/time selection/item selection, automatically group simultaneously recorded items)"
- And space-bar to "SWS/AW: Play/Stop (automatically group simultaneously recorded items)"

I have to stop recording by pressing R in order to make auto-grouping work.
If I stop with space-bar (as I'm used to), it doesn't group.
Also tried with space-bar assigned to standard transport:start/stop - no difference.
Tried with latest Reaper RC 21 and the latest standard version.

Thx to everyone involved with SWS extensions!

The actions you list above should be no longer needed.
All that should be required now to make auto grouping work is toggle "SWS/AW: Toggle auto group newly recorded items" to ON and then use the normal recording buttons / shortcuts then it should auto group the recorded items on stop.

edit:
Demo:
https://i.imgur.com/4HOfhfs.gif

Doesn't that work on your side ?

[drummerboy]

It works!

Reason was this:
The Installer wants to copy the library to Macintosh HD/Library/Application Support/REAPER/User Plugins

But my stuff was in User/Library/etc.

All good now - thanks!

[ovnis]

Bug : "Close All FX chain windows" doesn't work with audio item FX chain window.

[vanhaze]

Since last couple of Reaper pre-releases i experience quite alot of Reaper hard crashes when applying SWS actions in Arrange on MIDI Items ..

Never experienced this before.
Here's for example a crashlog snippet.

I have installed the latest SWS beta.
Currently using Reaper 5.77rc3 - 64bit on OSX 10.13.3.

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 reaper_sws_extension.dylib 0x0000000114119e24 RprMidiEvent::getOffset() const + 4
1 reaper_sws_extension.dylib 0x000000011411eff0 removeDuplicates(std::vector<RprMidiNote*, std::allocator<RprMidiNote*> >&) + 128
2 reaper_sws_extension.dylib 0x0000000114120352 RprMidiTake::~RprMidiTake() + 226
3 reaper_sws_extension.dylib 0x00000001141164df QuantizeAllToGrid(int, void*) + 271
4 reaper_sws_extension.dylib 0x000000011410488c RprCommand::run(int) + 76
5 reaper_sws_extension.dylib 0x0000000113f512ab hookCommandProc(int, int) + 731
6 com.cockos.reaper 0x000000010006dd08 Main_OnCommandEx2(int, int, ReaProject*) + 120
7 com.cockos.reaper 0x00000001000d3a2f Main_OnCommandEx(int, int, ReaProject*) + 31
8 com.cockos.reaper 0x000000010036194b KBD_OnMainActionEx(int, int, int, int, HWND__*, ReaProject*) + 187
9 com.cockos.reaper 0x000000010036187c KBD_OnMainAction(int, int, int, int, HWND__*) + 12
10 com.cockos.reaper 0x0000000100642dcd ProcessCustomCommand(KbdSectionInfo*, int, int, int, int, HWND__*) + 3341
11 com.cockos.reaper 0x000000010036977b kbd_onAction(KbdAccel*, int, int, int, bool, KbdSectionInfo*, HWND__*) + 491
12 com.cockos.reaper 0x0000000100369508 kbd_translateAccelerator(HWND__*, MSG*, KbdSectionInfo*) + 472
13 com.cockos.reaper 0x000000010036e06f -[REAPERapp sendEvent:] + 3167
14 com.apple.AppKit 0x00007fff4ad56d9d -[NSApplication run] + 812
15 com.apple.AppKit 0x00007fff4ad25f1a NSApplicationMain + 804
16 com.cockos.reaper 0x00000001000117ec main + 28
17 com.cockos.reaper 0x00000001000117b4 start + 52

[nofish]

Originally Posted by vanhaze

Since last couple of Reaper pre-releases i experience quite alot of Reaper hard crashes when applying SWS actions in Arrange on MIDI Items ..

SWS / FNG action I guess ?
Which one exactly ? (edit: Seems like ""SWS/FNG: Quantize item positions and MIDI note positions to grid" ?)

And can you reproduce every time, for example with new project and just one MIDI item and running the specific action ?

Also, it would be good if you could open an issue in the SWS tracker for it:
https://github.com/reaper-oss/sws/issues

Thanks.

[vanhaze]

nofish, many thanks for your help.

I will try to replicate the crashes and report to SWS issue Tracker.
For now, it seems that SWS note transpose Actions on MIDI items in Arrange, seems to bring down Reaper to its knees alot, (hard crashes) thats for sure. (in my situation that is).

[EvilDragon]

Yes, those are FNG actions. Unfortunately those are quite nasty hacks done via chunks... Might be better to find ReaScripts that do the same thing in ReaPack and use them instead...

[nofish]

I'll try to PM fingers, although he doesn't seem present on the forum anymore maybe he's still available for supporting his actions (trying can't hurt at least )

[EvilDragon]

Last seen 2 years ago on this forum... methinks he's a goner. :/

[nofish]

Might be, PM'd him now, let's see...

[mpl]

I remember someone wrote script same as fingers action does.

Edit:
Lol it was me https://github.com/MichaelPilyavskiy...ect%20grid.lua
Fingers stuff used anyway, but I can recode them to new midi stuff since someone will have any issues with it

[mpl]

Probably all fingers (or even reaper) stuff should be recoded for using new getsetallevts API since 5.32+

[EvilDragon]

Originally Posted by mpl

Edit:
Lol it was me https://github.com/MichaelPilyavskiy...ect%20grid.lua

LOL


BTW, mpl... would you be kind to go through all scripts in your repository and set the Author tag identically to all of them. You use several different way to name yourself there, making it look a bit nasty in ReaPack Just saying mpl there would suffice, I think.


Cheers and thanks!

[nofish]

@ mpl

I seem to remember once you saying you don't do C++ but if you recode the FNG actions anyway I think it would be really nice actually if you did in C++ and submit to SWS to replace the seemingly broken FNG actions there.

The API is in principle not that different between say Lua and C++ I'd say.
Just a thought...

(FWIW, fingers didn't reply to my PM yet.)

[vanhaze]

Many thanks for the effort nofish, i really appreciate it

[mpl]

Originally Posted by EvilDragon

BTW, mpl... would you be kind to go through all scripts in your repository and set the Author tag identically to all of them.

I noticed that year ago or so and fixed it. The only thing I see author was not changed. Seems I need to push new versions so reapack indexer will rescan headers for new names. Thanks for report, doing it right now.

[mpl]

Originally Posted by nofish

you don't do C++

Actually I still at early stage of C learning curve (too much other work now).

Anyway I learned almost everything week ago by hard digging juliansader stuff (he is top wizard of MIDI stuff right now), so it is probably up to him. I think main MIDI issue is message contains ofssets from each other instead direct position data (also you should be damn careful when dealing with noteon/off messages), so I guess making MIDI things faster is up to way messages are changed/sorted, not sure FNG code can be even recoded to GetSetAllEvts philosophy directly (but I dont say it cant).