REAPER Update Utility

[FeedTheCat]

Originally Posted by reapero

Stopped working for me. It closes Reaper, then never starts installing it.

Any recent change or clue of whay might be happening? I am trying to update to 6.80

Hey reapero, sry it took so long to reply. I just checked and it works fine on my Windows 10 install. It's always hard to know if it's the utility at fault or something else is at play. (I read someone posting about having issues installing 7.80, so something else might be going on).

If you enable logging to file (utility menu), attempt the update and send me the created log file, I might be able to figure out what's going wrong.

But as Coachz mentioned before, it sometimes just starts working again. So not easy to debug...

[PitchSlap]

I'm surprised I missed this.
I can get a bit ADD refreshing landoleet for new pre-releases.

Just yesterday I was looking for a browser add-on that would notify me when the page was updated, but this script is much better.

I've always wished Reaper had this natively. The only updates it will notify of are main releases, which are the only ones I never install!

[dyross]

I started running into an unexpected behavior with this:

The last few (prerelease) builds installed via the tool are causing Reaper to initialize as a portable installation in my Applications folder (mac), rather than pointing to my existing settings.

When I install the build directly from Landoleet, this isn't happening.

[FeedTheCat]

Originally Posted by dyross

I started running into an unexpected behavior with this:

The last few (prerelease) builds installed via the tool are causing Reaper to initialize as a portable installation in my Applications folder (mac), rather than pointing to my existing settings.

When I install the build directly from Landoleet, this isn't happening.

Can you send me the startup log? (menu > debugging > Dump startup log)

I'll have a look on the weekend.

[dyross]

Originally Posted by FeedTheCat

Can you send me the startup log? (menu > debugging > Dump startup log)

I'll have a look on the weekend.

I'm having a little trouble reproducing this, but here's a log file in case it's helpful.

[dyross]

This just happened again. Uploading startup log.

Note that when I go into my Applications folder and delete the reaper.ini file (which is just at the root level of Applications when this happens), it goes back to the usual config path.

[FeedTheCat]

Originally Posted by dyross

This just happened again. Uploading startup log.

Note that when I go into my Applications folder and delete the reaper.ini file (which is just at the root level of Applications when this happens), it goes back to the usual config path.

Did you delete the reaper.ini before or after creating this startup log?

(in the log reaper reports the its resource path as "/Users/dyross/Library/Application\ Support/REAPER", which is correct right?).

I'll have a look again and see if I can reproduce. On MacOS the script does the same installation procedure, whether portable or not. Maybe that's the problem actually, but it also makes it weird that it doesn't happen on every upgrade.

[FeedTheCat]

Hmmm, afaik reaper only makes a portable install when there's a reaper.ini file present in the installation directory. The script just copies what's inside the downloaded dmg file, so there's no way it would create a reaper.ini itself. So reaper probably creates the reaper.ini itself for some reason. Maybe there's some permission stuff going on and it can't access the existing reaper.ini.

Please enable the "log to file" option before doing your next update, that log contains a lot more information than the startup log.

[dyross]

Yeah, it was after, because in the clean install, I didn't have the plugin installed to access.

I enabled the extra logging and will report back next time.

[PitchSlap]

Malwarebytes recognizes this script as an exploit and blocks it when loading Reaper. I'm not sure if anything can be done about it, but I figured I'd post the log information.

I had a very costly malware nightmare not long ago so my settings might be more strict than the defaults.

Malwarebytes
www.malwarebytes.com

-Log Details-
Protection Event Date: 9/11/23
Protection Event Time: 3:48 PM
Log File: 65909a66-50f5-11ee-b45f-b42e9933cd2b.json

-Software Information-
Version: 4.6.2.281
Components Version: 1.0.2131
Update Package Version: 1.0.75189
License: Premium

-System Information-
OS: Windows 10 (Build 19045.3393)
CPU: x64
File System: NTFS
User: System

-Exploit Details-
File: 0
(No malicious items detected)

Exploit: 1
Exploit.PayloadProcessBlock, C:\WINDOWS\System32\WindowsPowerShell\v1.0\powersh ell.exe powershell.exe -windowstyle hidden (new-object System.Net.WebClient).DownloadFile('https:\www.reaper.fm\download.php', 'C:\Users\Ryan\AppData\Local\Temp\reaper_uutil_mai n.html'), Blocked, 701, 392684, 0.0.0, ,

-Exploit Data-
Affected Application: cmd
Protection Layer: Application Behavior Protection
Protection Technique: Exploit payload process blocked
File Name: C:\WINDOWS\System32\WindowsPowerShell\v1.0\powersh ell.exe powershell.exe -windowstyle hidden (new-object System.Net.WebClient).DownloadFile('https:\www.reaper.fm\download.php', 'C:\Users\Ryan\AppData\Local\Temp\reaper_uutil_mai n.html')
URL:



(end)

[FeedTheCat]

Originally Posted by PitchSlap

Malwarebytes recognizes this script as an exploit and blocks it when loading Reaper. I'm not sure if anything can be done about it, but I figured I'd post the log information.

I had a very costly malware nightmare not long ago so my settings might be more strict than the defaults.

Maybe you can add an exception in Malwarebytes to not block it? If possible, that would be the easiest/best solution.

Another idea would be to make the script use "curl" to download from the internet (like on MacOS and Linux). IIRC this is only possible after a certain Windows 10 version (but this script tries to be compatible with older Windows versions). Maybe Malwarebytes won't think that using curl is an exploit...

Change line 1150 from:

if platform:match('Win') then

to

if false and platform:match('Win') then

Haven't tested this properly though, so there might be side-effects.

[PitchSlap]

Originally Posted by FeedTheCat

Maybe you can add an exception in Malwarebytes to not block it? If possible, that would be the easiest/best solution.

Another idea would be to make the script use "curl" to download from the internet (like on MacOS and Linux). IIRC this is only possible after a certain Windows 10 version (but this script tries to be compatible with older Windows versions). Maybe Malwarebytes won't think that using curl is an exploit...

Change line 1150 from:

if platform:match('Win') then

to

if false and platform:match('Win') then

Haven't tested this properly though, so there might be side-effects.

Thanks for the reply. I added the URL to the allowed list, next I might try changing the script as suggested.
My guess is for a working exception in MB I'd have to add powershell.exe which doesn't seem like a good idea since it could also be used by things that are actually malicious.

Either way not a huge deal. I check LOL often enough anyway (old habits die hard.)

[DarrenH]

Thank you @FeedTheCat for a really useful script!

FR for future versions: allow notification filtering of pre-release versions.

I have the latest version installed (as seen below) but I'm getting pop-ups every day for 7.0 (but have "main" selected for "only show window when new version is available")

[FeedTheCat]

Originally Posted by DarrenH

I have the latest version installed (as seen below) but I'm getting pop-ups every day for 7.0 (but have "main" selected for "only show window when new version is available")

Should be fixed in v1.8.6.

Originally Posted by DarrenH

FR for future versions: allow notification filtering of pre-release versions.

I didn't add a new category. Pre versions now count as dev versions (for notifications). I guess that makes sense, but if anyone has objections let me know...

[DarrenH]

@FeedTheCat
Thanks for the quick turnaround! Updated. Appreciate your work

[Coachz]

Is there a way to have the updater get the latest pre without going through the history menu?

[MonkeyBars]

Originally Posted by Coachz

Is there a way to have the updater get the latest pre without going through the history menu?

6.83rc1 is the latest – it dropped after all the 7.0 versions so far.

[MonkeyBars]

The versions are out of order in both main version menu and submenu – imo they should all go from newest at top to oldest at bottom (highest to lowest). The way it's ordered here is confusing as it skips around.

[Coachz]

Originally Posted by MonkeyBars

The versions are out of order in both main version menu and submenu – imo they should all go from newest at top to oldest at bottom (highest to lowest). The way it's ordered here is confusing as it skips around.

Can I suggest an option to allow only showing updates on the 7 versions?

[FeedTheCat]

Originally Posted by Coachz

Is there a way to have the updater get the latest pre without going through the history menu?

The script showcases the latest pre-release version as featured on landoleet (the version that the devs currently want you to test). When a new RC for v7 comes out, it will be showcased.

Originally Posted by Coachz

Can I suggest an option to allow only showing updates on the 7 versions?

What do you mean by "showing updates"? As in showing startup notifications? Or what version is displayed in the pre-release section (right side of the script)?

[FeedTheCat]

@MonkeyBars

Just pushed v1.8.7 that should improve the menu order for old versions (I wasn't sorting previously, just took the order from the Landoleet website). Let me know if there's still something off about it.

Edit: Hmm, just had another look, RC versions should probably be below +dev versions...

[MonkeyBars]

Originally Posted by FeedTheCat

@MonkeyBars

Just pushed v1.8.7 that should improve the menu order for old versions (I wasn't sorting previously, just took the order from the Landoleet website). Let me know if there's still something off about it.

It's perfect, thanks!

Edit: Hmm, just had another look, RC versions should probably be below +dev versions...

Disagree! RCs are newer than dev so they ought to be on top as it is now

[FeedTheCat]

Originally Posted by MonkeyBars

Disagree! RCs are newer than dev so they ought to be on top as it is now

It's a bit confusing, but RCs are older than +dev and newer than "pre" (or I'm just confused rn )

The normal cycle would be something like this, right?:

6.73
6.73+dev1234
6.74rc1
6.74rc2
6.74
6.74+dev1234

Just uploaded v1.8.8, +dev versions are now always placed at the top.

[MonkeyBars]

Originally Posted by FeedTheCat

It's a bit confusing, but RCs are older than +dev and newer than "pre" (or I'm just confused rn )

The normal cycle would be something like this, right?:

6.73
6.73+dev1234
6.74rc1
6.74rc2
6.74
6.74+dev1234

Just uploaded v1.8.8, +dev versions are now always placed at the top.

You're right! Apologies for my mistaken comment above.

I do have one more FR in this regard: please filter out "+" from your ordering, since they don't use that character consistently and it'll throw off the order if going back alphanumeric order (since it's a symbol).

[FeedTheCat]

Originally Posted by MonkeyBars

You're right! Apologies for my mistaken comment above.

No worries, had the same gut instinct.

Originally Posted by MonkeyBars

I do have one more FR in this regard: please filter out "+" from your ordering, since they don't use that character consistently and it'll throw off the order if going back alphanumeric order (since it's a symbol).

Yee, thought of that as well, but then I saw this:



(they remembered the + but forgot the dev )

I think I'll let the inconsistencies be for now, the 7pre versions will soon vanish anyways.

Edit: Aaah, you mean from the ordering only (not the display). That makes a lot of sense. Will do later

[MonkeyBars]

Originally Posted by FeedTheCat

(they remembered the + but forgot the dev )

Edit: Aaah, you mean from the ordering only (not the display). That makes a lot of sense. Will do later

Good catch, that typo does complicate things even for internal ordering... I guess you could just count it as "+dev" or something...

[Coachz]

Originally Posted by FeedTheCat

The script showcases the latest pre-release version as featured on landoleet (the version that the devs currently want you to test). When a new RC for v7 comes out, it will be showcased.



What do you mean by "showing updates"? As in showing startup notifications? Or what version is displayed in the pre-release section (right side of the script)?

I'm on the 7 train so all I would like to see is 7 versions.

[FeedTheCat]

Originally Posted by MonkeyBars

Good catch, that typo does complicate things even for internal ordering... I guess you could just count it as "+dev" or something...

Urgh, you're right, it does complicate things even further. I'll leave the typos for now.

Originally Posted by Coachz

I'm on the 7 train so all I would like to see is 7 versions.

You'll soon get your wish when v7 is released I won't make changes to the script (big effort -> small return).

[todoublez]

Just made a icon for this useful script.


thanx to FTC!

icon download here :
https://stash.reaper.fm/47703/Arthen...R%20UPDATE.png

[McSound]

Originally Posted by todoublez

Just made a icon for this useful script.


thanx to FTC!

icon download here :
https://stash.reaper.fm/47703/Arthen...R%20UPDATE.png

Nice! Thanks for this!

[dna598]

I haven't been able to update with the script for a long while now. I think it's because windoze keeps setting my folders to read only, and i cannot, for the life of me, turn it off.

I've tried every solution i have come across to no avail. Manually setting the drive/folders to write, turn off defender, command line stuff (i'm not an expert, just following all those "help" sites with all the same instructions)

Anyone else experiencing this?

[DarrenH]

I haven't had any issues with folder permissions or inability to update anything but will keep an eye out. I have defender "on" i guess, in whatever the default setting is.

I'm running portable which may or may not be relevant.

Originally Posted by dna598

I haven't been able to update with the script for a long while now. I think it's because windoze keeps setting my folders to read only, and i cannot, for the life of me, turn it off.

I've tried every solution i have come across to no avail. Manually setting the drive/folders to write, turn off defender, command line stuff (i'm not an expert, just following all those "help" sites with all the same instructions)

Anyone else experiencing this?

[KSstudio]

Hello,
I have this error message when I launch Reaper 7.05 on Win10

check_updates.lua:637: attempt to concatenate a nil value (global 'za_string')

Is anything wrong with the script?

Thanks

[FeedTheCat]

Originally Posted by KSstudio

Hello,
I have this error message when I launch Reaper 7.05 on Win10

check_updates.lua:637: attempt to concatenate a nil value (global 'za_string')

Is anything wrong with the script?

Thanks

That error doesn't look like it comes from this Update Utility. Anything else you got installed that could be checking for updates?

[KSstudio]

I synchronized but nothing new! Very strange Thanks anyway!

[KSstudio]

Hey, is it normal I can retrieve the error by double click the action?