Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release v2.13 #1589

Merged
merged 95 commits into from
Dec 20, 2021
Merged

Release v2.13 #1589

merged 95 commits into from
Dec 20, 2021

Conversation

cfillion
Copy link
Member

@cfillion cfillion commented Dec 16, 2021

This merges all pull requests that were ready for a new pre-release. Not included are the drafts (#1449, #1467, #1493, #1514), incomplete (#1291, #1444) and unreviewed PRs (#1301, #1562).

If there's nothing to add/changelog typos/other changes to make, all that's left is amending the last commit with the correct release date in the whatsnew then merging the branch into master.

  • The submodules WDL, TagLib are updated and reaper-sdk added (run git submodule update --init)
  • reaper_plugin_functions.h is read from the new official SDK repository if it doesn't exist in the vendor subfolder (delete to migrate to the new SDK)
  • The value of some cached CMake variables changed, recreating the build tree might be necessary if it was created against the master branch (IDEs should do this automatically)

cfillion and others added 30 commits November 1, 2020 19:22
…91 chars

This prevents missing \n at the end of long lines leading to a corrupted
file. The long lines are still truncated when being read.

Fixes #1439
… non-Windows

SWELL skips line that do not contain =.
There is no need to make a copy of the string with all \n replaced by \0 when the original string can already have the \0.
The list was always scrolled to the top after clearing & rebuilding the entire list (+ an extra redraw causing flickering).

Fixes #1456
selection to dynamic commands.  Default number of slots is
16, max slots is SNM_MAX_DYN_ACTIONS.  Using these actions
will mark the project as dirty.

Fixes: #1405
This commits makes AWClrTimeSelClkToggle construct a single instance of the ConfigVar (and also simplifies the condition).
Booleans are always true if they aren't false.
…n right clicking above the list on Linux and Windows

HeaderHitTest is called from GetHitItem even when the position is outside the list view's rect. This was not handled.

Regression from v2.12 via 81a23d3.

Closes #1506
… if already contained in new filename/takename
…y exists, closes #407, closes #1498

combine 'Xenakios/SWS: Rename take source files...' and 'Xenakios/SWS: Rename takes and source files...' into one function for avoiding code duplication
API: import GetPeakFileNameEx()
…in NF_UpdateSWSMarkerRegionSubWindow description
@AppVeyorBot

This comment has been minimized.

@Edgemeal
Copy link

Edgemeal commented Dec 17, 2021

This is weird, I set name of a new track so SWS v2.12 auto colors it, then script optionally gets that track color, darkens the color and sets the track color, but with v2.13 instead of the track color getting darker it changes to a black color. If I force my script to wait a bit (using defer loop) then the track darkening works as it does in current SWS release. Very weird!

TESTED on: Win10_x64, REAPER 6.41 & v6.43_RC4
sws-2.13.0.0-Windows-x64-v2.13-8e57814d.exe

example,
NewTrackName = "Drums" -- SWS auto colors track to a light blue.
ControlKeyIsDown = false -- if true darken track color, but it doesn't work as expected with SWS 2.13.

function DarkenColor(trk_colr) -- simple color darkener
local r,g,b = reaper.ColorFromNative(trk_colr)
if b - 50 < 0 then b = 0 else b = b - 50 end
if g - 50 < 0 then g = 0 else g = g - 50 end
if r - 50 < 0 then r = 0 else r = r - 50 end
return reaper.ColorToNative(r,g,b)
end

track = reaper.GetTrack(0,0) -- SWS auto colors the track when named.
reaper.GetSetMediaTrackInfo_String(track, "P_NAME", NewTrackName, true )

-- Optionally make the track a slightly darker
if ControlKeyIsDown then reaper.SetTrackColor(track, DarkenColor(reaper.GetTrackColor(track))) end
-- with SWS v2.13 ^ this makes the track black instead of a darker blue.

@Edgemeal
Copy link

Guessing the problem is, if you try to get the color of a track right after SWS has auto colored it , 2.13 now returns the wrong value?

jeremybernstein and others added 12 commits December 17, 2021 13:18
* AC_AUDIOIN (audio-input): track has an assigned audio input
* AC_MIDIOUT (midi-output): track has an assigned hardware MIDI output
This allows for generalized scripts that take "arguments" by creating a
cycle action that first uses this new ReaConsole command to prime a
value in REAPER's non-persisted state, and then calling a custom script
that subsequently reads the value.
Broke since AppVeyor's September 2021 Ubuntu 18.04 image update
0065b61491a5580e3ee48b4c66d64c82176fe228 is required for enabling C++17, and also gets rid of all warnings about the register keyboard being deprecated.
@cfillion
Copy link
Member Author

cfillion commented Dec 17, 2021

If I force my script to wait a bit (using defer loop) then the track darkening works as it does in current SWS release.

Auto-color was indeed changed to be asynchronous (triggering on the next defer tick). This was done for performance reasons for the new track I/O and instrument FX filters and was applied to all filters for consistency.

I've replaced that with a different solution (downside is it's unclear if it cover all cases, relies on REAPER sending redundant control surface notifications in a particular order).
EDIT: Yup, doesn't work in all cases (eg. toggling record arm of selected tracks can freeze REAPER for a while–weird that it works if unselected!).
EDIT2: Replaced with a more robust fix, thanks to @jeremybernstein's idea!

@cfillion cfillion force-pushed the v2.13 branch 2 times, most recently from 71e6bf1 to 5459fac Compare December 17, 2021 22:13
@AppVeyorBot

This comment has been minimized.

@cfillion
Copy link
Member Author

I've updated the release date to tomorrow.

@nofishonfriday
Copy link
Collaborator

nofishonfriday commented Dec 20, 2021

Just a (maybe silly) idea...how about following the Reaper release tradition and letting users announce new SWS releases in the forum (the last ones you announced iirc).
Not sure if it would happen though, maybe nobody notices (edit: though I'd guess at least some have pre-releases notification enabled) or bothers to post lol.

@cfillion
Copy link
Member Author

I suppose the majority of users with pre-release notifications enabled aren't necessarily active on the forum anyway...

@cfillion cfillion merged commit 4ca0494 into master Dec 20, 2021
@cfillion cfillion deleted the v2.13 branch December 20, 2021 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants