SWS Extension pre-release builds

[Jeffos]

The latest SWS Extension pre-release build can be found here.
The related "What's new?" is here.

What's a pre-release? It's software that's not necessarily ready for full public consumption: pre-release software should be expected to have bugs, use at your own risk! Feature requests, and bugs should be reported in our issue tracker, or in this very thread.

The only way we can continue to provide great software is with your help and feedback.

Thank you!

[musicbynumbers]

All good Jeffos, Starting to test now when I get time.

Thought I'd mention something that is probably obviously on your "to do" list but just in case.

Was about to test out the new contextual toolbars in reaper 5 (since I've ran out of toolbars in Reaper 4 just on static ones) and noticed that toolbars above 8 are not registered yet in reaper 5/SWS in the contextual toolbar editor.

No rush for that but thought it worth mentioning.

[Breeder]

Originally Posted by musicbynumbers

Was about to test out the new contextual toolbars in reaper 5 (since I've ran out of toolbars in Reaper 4 just on static ones) and noticed that toolbars above 8 are not registered yet in reaper 5/SWS in the contextual toolbar editor.

No rush for that but thought it worth mentioning.

This is all in the works already, don't worry (actually the new toolbars part is already solved, the only thing left is to tackle new envelope fader mode and certain changes in MIDI editor in regards to mouse detection)

[musicbynumbers]

Originally Posted by Breeder

This is all in the works already, don't worry (actually the new toolbars part is already solved, the only thing left is to tackle new envelope fader mode and certain changes in MIDI editor in regards to mouse detection)

All good thought as much but just in case

This feature is going to be killer for me.

Now to ask the devs for the ability to go up to 32 toolbars (as a preference options perhaps) as I've used 8 just on static ones around my multi-monitor setup and 8 floating contextual ones might not be enough

[mim]

I'm checking v5 + lua + sws custom reascript ...

I'm not sure what error I made but this

volume=reaper.GetTrackEnvelopeByName(reaper.GetSelectedTrack(0,0), "Volume")
volenv=reaper.BR_EnvAlloc(volume, 0)
reaper.BR_EnvFree(volenv, 1)

Give me :

'reaper.BR_EnvFree' argument 1: expected BR_Envelope*

But Isn't volenv a BR_Envelope* ?

[musicbynumbers]

Was just doing some work now that needed for all the items to have the same fade in and out length and curves on all the new items I was bringing in and wondered if that's something you can might consider adding as actions if possible and when you have time.

Only if it's not a lot of trouble mind you!

[Commala]

Contextual toolbars are doing that thing again. I've got tracks hidden in the TCP, and the toolbar I assigned to the TCP won't pop up until I show those tracks. Thereafter, the command works, even if the tracks are hidden. Using Reaper 5 pre8 and SWS 2.6.2.0 pre

[Breeder]

Originally Posted by Commala

Contextual toolbars are doing that thing again. I've got tracks hidden in the TCP, and the toolbar I assigned to the TCP won't pop up until I show those tracks. Thereafter, the command works, even if the tracks are hidden. Using Reaper 5 pre8 and SWS 2.6.2.0 pre

The version that fixes this is not released yet.

[Argitoth]

why?



5pre9
sws 2.6.2
win 8.1 all x64

[Janne83]

Originally Posted by Argitoth

why?



5pre9
sws 2.6.2
win 8.1 all x64

Confirmed. Crashes here also

[Jeffos]

yes, something changed in a recent REAPER v5 pre but SWS isn't aware of that => many SWS windows will crash ATM.
schwa fixed it for the next REAPER 5pre10.
thanks for the report guys!

[heda]

@Jeffos: not crashing anymore in pre10

@Breeder: how is the two options for zoom vertical and minimize others ?
Is the second option to include automation lanes, as it was in previous versions, going to be included soon? Thanks!
http://forum.cockos.com/showpost.php...postcount=1716

[Breeder]

Originally Posted by heda

Is the second option to include automation lanes, as it was in previous versions, going to be included soon? Thanks!

Current actions has been reversed to old behavior and new ones that ignore envelope lanes have been introduced - it will be part of the next build.

[Aleksandr_Oleynik]

Is there (any) the ability to use the "NameTrack" in a local OSC messages -
Examples:
/track/"NameTrack"/fx/1,2/fxparam/1,1/value 0.25 0.5

Maybe there is another solution?

[Banned]

Originally Posted by Aleksandr_Oleynik

Is there (any) the ability to use the "NameTrack" in a local OSC messages -
Examples:
/track/"NameTrack"/fx/1,2/fxparam/1,1/value 0.25 0.5

Maybe there is another solution?

(I may be mistaken, but I don't see what this has to do with the SWS extension per se?)

I don't think so, since local OSC messages use the default OSC control surface configuration, and that doesn't use this pattern.

I wouldn't know how to do this for non-local OSC messages either; I don't think the OSC action descriptions can be used in such a manner (but I may be wrong about that).

In any case, using track names as identifiers seems like a bad idea to me, since they are not guaranteed to be unique.

[Aleksandr_Oleynik]

Originally Posted by Banned

In any case, using track names as identifiers seems like a bad idea to me, since they are not guaranteed to be unique.

Yes, but what will happen to my Cycle Action, if I move the track and it will be not 1, but 12? Or inserted at the beginning of the track and it will be - 2


Maybe something like this is possible? -
/selectedtrack/fx/1,2/fxparam/1,1/value 0.25 0.5

This would allow me to write this Cycle Action (if track name is - "guitar001") -
Console s guitar001
Console /selectedtrack/fx/1,2/fxparam/1,1/value 0.25 0.5

[Banned]

Originally Posted by Aleksandr_Oleynik

Maybe something like this is possible? -
/selectedtrack/fx/1,2/fxparam/1,1/value 0.25 0.5

I don't know how this works locally, with cycle actions; but you may be able to just do:

/fx/1,2/fxparam/1,1/value 0.25 0.5

If you do this with an OSC control surface, you need to already have the track selected in the OSC device; which can more or less be achieved by using

DEVICE_TRACK_FOLLOWS LAST_TOUCHED

and touching it first. Or you'd select the track explicitly by sending the desired track number:

/device/track/select 123

[Aleksandr_Oleynik]

Originally Posted by Banned

I don't know how this works locally, with cycle actions; but you may be able to just do:

/fx/1,2/fxparam/1,1/value 0.25 0.5

It does not work locally

[Banned]

Originally Posted by Aleksandr_Oleynik

It does not work locally

Well, I just tested it myself, and it *does* work here - apart from the specific syntax of the message to select the device track I posted. (I guess that's because that OSC action description expects an int, not a float; while ReaConsole sends numbers as float by default? In any case, the toggle pattern I used in the example below works fine.)

I guess you (1) don't have any effects in the master track, and (2) haven't explicitly selected any other tracks in the OSC Control Surface device - so it's still stuck in the default selected track, being track 0 = the master track.

Try inserting an effect in the first two slots of the master track and track 1, then send the OSC message again:

/fx/1,2/fxparam/1,1/value 0.25 0.5

Now send the message

/device/track/select/1

... and send the first message again.

Does that still not work for you?

[Aleksandr_Oleynik]

Originally Posted by Banned

Try inserting an effect in the first two slots of the master track and track 1, then send the OSC message again:

/fx/1,2/fxparam/1,1/value 0.25 0.5

Now send the message

/device/track/select/1

... and send the first message again.

Does that still not work for you?

It works, thanks!
I will think how to use it (command /device/track/select/1 not select track with specific Name)

[Infidel]

Pasting from the SWS bug report page:

When you import channels from a snapshot into new tracks in a blank project, these channels will have the Master/Parent Send option always on, even if the original channels had that option off.

[bladlus]

Not sure if this is exclusive to the pre-release build, but there's something weird going on with Auto Color in 2.6.2 for Mac - Reaper 5.0 pre12. Hope this is the right place to post this.



As you can see in the gif, (any) + Random works as expected; the color sticks to the track when moved. However with (any) + Custom, the color sticks to the position rather than to the track, and this can be quite confusing.

[Tod]

Something I've been looking for but can't find is an action to select Take Envelopes, especially the Volume.

[plush2]

5.0pre13 seems to be interpreted by SWS as a version less than the required 5.0pre6 on my machine.

Is anyone else seeing this?

[Breeder]

Originally Posted by plush2

5.0pre13 seems to be interpreted by SWS as a version less than the required 5.0pre6 on my machine.

Is anyone else seeing this?

Completely normal due to pre13 changes. Don't forget it's still early phase of V5 pre cycle and stuff are constantly changing so things are bound to get broken. Should get fixed with next SWS pre when it gets released.

[plush2]

Thanks for the quick response Breeder. I'm likely to downgrade 1 pre for now since I rely on the SWS stuff heavily these days.

[EvilDragon]

If you rely on anything, don't use prereleases for your work. Test them in a separate portable install, but keep using official v4 release for your work.

[planetnine]

Plush, some of the code backtracks could leave you with projects that don't open properly in later versions.

As much as I want to start using the VCAs...



>

[plush2]

Thank you for your concern. I'm aware of the risk. I've been operating like this for nearly all of the 8 years I've been using Reaper and am prepared to roll with the punches. This time it's a fairly minor roll.

[Win Conway]

Been operating like that since Reaper was first around, never did me any harm so far, minor set backs here and there but nothing worth worrying about.

[plush2]

Originally Posted by gpunk_w

Been operating like that since Reaper was first around, never did me any harm so far, minor set backs here and there but nothing worth worrying about.

I was just thinking this subject would make for an interesting new discussion thread here.

[richie43]

Originally Posted by plush2

Thanks for the quick response Breeder. I'm likely to downgrade 1 pre for now since I rely on the SWS stuff heavily these days.

I decided to roll back the SWS and keep the newest Reaper pre. I've used the pre's exclusively for almost 4 years now and never (yet...) had a MAJOR setback.

[Aleksandr_Oleynik]

Originally Posted by Banned

I don't know how this works locally, with cycle actions; but you may be able to just do:

/fx/1,2/fxparam/1,1/value 0.25 0.5

If you do this with an OSC control surface, you need to already have the track selected in the OSC device; which can more or less be achieved by using

DEVICE_TRACK_FOLLOWS LAST_TOUCHED

and touching it first. Or you'd select the track explicitly by sending the desired track number:

/device/track/select 123

Banned,
Please.......
How this Code - "DEVICE_TRACK_FOLLOWS LAST_TOUCHED" to get to work locally?

I have Console command - s "Track Name"
And if i had local (or pseudo local) command - "DEVICE_TRACK_FOLLOWS LAST_TOUCHED"


For me, it was the solution to my problem.

[Banned]

Originally Posted by Aleksandr_Oleynik

Banned,
Please.......
How this Code - "DEVICE_TRACK_FOLLOWS LAST_TOUCHED" to get to work locally?

See this part of the Default.ReaperOSC configuration file:

DEVICE_TRACK_FOLLOWS s/device/track/follows
DEVICE_TRACK_FOLLOWS_DEVICE t/device/track/follows/device
DEVICE_TRACK_FOLLOWS_LAST_TOUCHED t/device/track/follows/last_touched

... which enables you to do this:

/device/track/follows LAST_TOUCHED

... or this:

/device/track/follows/last_touched 1

I haven't tested how this works 'locally', though. I would recommend experiment a bit with this setting, also in conjunction with the various settings for REAPER_TRACK_FOLLOWS and DEVICE_TRACK_BANK_FOLLOWS; wrapping your head around how all this stuff works can be a bit difficult. And you should probably also read this post.

Hope this helps!

PS: perhaps start a new thread if you wish to continue discussing this; I think it's a bit off-topic for this one.

[matthewjumpsoffbuildings]

im using Lua, SWS 2.6.1 with Reaper 5 pre 13. I have also tested this with 5 pre 12, running SWS 2.6.1 and 2.6.2

If i create a new item with reaper.AddMediaItemToTrack() then attempt to run ULT_SetMediaItemNote() on it, nothing seems to happen, no notes are added.

i did a simple test

item = reaper.GetSelectedMediaItem(0, 0)

reaper.ULT_SetMediaItemNote(item, "test")

ran it on an empty item, nothing happened.

it seems like the ULT_SetMediaItemNote() function isnt working in Lua?

GetMediaItemNote works. and also if you do a Set on an item that has notes, instead of just failing and leaving the original notes, it deletes all notes. but it doesnt trigger a UI refresh, so you have to zoom/scroll to see it

[Kejnel]

Hi, is there any chance you might add some visual feedback to Snapshots window indicating which snapshot is currently active?

If you save your project with a snapshot active and reload the project, there is no way to tell which snapshot is currently active and one has to load a desired snapshot again in order to be sure he is not making changes to something else. It would be excellent if you could add it in some upcoming update.

Thank you very much for your amazing work!

[Aleksandr_Oleynik]

Originally Posted by Banned

See this part of the Default.ReaperOSC configuration file:
*******************************************
Hope this helps!

Thank you so much Banned!

DEVICE_TRACK_FOLLOWS_LAST_TOUCHED t/device/track/follows/last_touched
in Default.ReaperOSC
and locally OSC Comand -
/device/track/follows LAST_TOUCHED
/fx/1/fxparam/1/value 1

Works perfectly!

PS: perhaps start a new thread if you wish to continue discussing this; I think it's a bit off-topic for this one.

Yes, sorry.

[heda]

Hello SWS devs:
I'm having trouble with SWS auto coloring of Markers and Regions, when I create many regions quickly from a EEL script. Is there a way to redraw regions from ReaScript EEL to make sure they get the auto color? UpdateArrange(); seems not working.

See the script here http://forum.cockos.com/showthread.php?t=155582

Thanks!

[PitchSlap]

Any word on when an update is coming?

I'd assume many pre-release testers are also SWS users so there's probably a lot of us holding back on the last couple Reaper 5 pre-releases because SWS is incompatible.

[richie43]

Originally Posted by PitchSlap

Any word on when an update is coming?

I'd assume many pre-release testers are also SWS users so there's probably a lot of us holding back on the last couple Reaper 5 pre-releases because SWS is incompatible.

...or hold back on the newest SWS pre-release (that's what I am doing, and continuing to install the newest Reaper pre-releases). Only the newest SWS pre is not working with newer Reaper pre's.