Anyway ... I don't want to take your time. If it doesn't give other Windows users problems and errors, it's probably my tower throwing a tantrum. I was only using it to view the developments .... I still appreciate your scripts
Anyway ... I don't want to take your time. If it doesn't give other Windows users problems and errors, it's probably my tower throwing a tantrum. I was only using it to view the developments .... I still appreciate your scripts
I think I found the problem actually.
1. You're on a 32bit machine (or have a 32 bit install), which is why I couldn't replicate it
2. The devs added the licecap installer to the landoleet website, probably recently (which is what made the script fail for 32-bit machines).
Quote:
Originally Posted by Spookye
Ok ... thanks for your patience .......
Sorry ... what does "Sry for all the trouble" mean ??
Just wanted to apologize that I made you edit nasty script code
Ok thank you so much ...... I thought you were getting impatient. Anyway yes .... Tower x32 bit and also installation. Inserting that line of script (for me ...) was the sweatiest experience of my life. Thanks again .....
Check for updates: OK
Close reaper: OK
DMG downloads and mounts: OK
At this point the DMG unmounts and reaper.app gets corrupted.
Finder says "the application "reaper.app" can't be opened."
is this because of the portable install or something else?
The path is /Applications/REAPER
Is that an M1? I only have access to a Catalina machine at this point, and updating portable installs seems to be working fine afaict. Hopefully it's not some permission thing again...
Am I understanding correctly that it corrupts the "main" reaper app and not the portable install itself?
I have some changes in the works that will help a lot with debugging issues like this. I'll put in some time this weekend and hopefully I'll be able to finish them up.
Just updated the utility to v1.8. There's a lot of changes under the hood, so please report back if anything has broken.
@EpicSounds
Can you please enable Debugging > Log to file, then perform an update/downgrade and send me the created log file? (Also, please make sure again that you have given file access permissions to reaper and the terminal application).
I'm hoping the reworked debugging output in this version will make it easier to identify the issue.
Thx, the system crash log is very helpful as well! Good news is that afaict nothing unexpected/unintended is happening on the utility side. The system crash log error "SIGKILL (Code Signature Invalid)" would indicate that REAPER v6.56+dev0430 is not correctly signed. I read somewhere that code signing is also more strictly enforced on M1 Macs.
Could you please check if the same issue arises when manually downloading & installing v6.56+dev0430 from Landoleet? If that's not the case there might be few things we can do about it from the script side.
Thx, the system crash log is very helpful as well! Good news is that afaict nothing unexpected/unintended is happening on the utility side. The system crash log error "SIGKILL (Code Signature Invalid)" would indicate that REAPER v6.56+dev0430 is not correctly signed. I read somewhere that code signing is also more strictly enforced on M1 Macs.
Could you please check if the same issue arises when manually downloading & installing v6.56+dev0430 from Landoleet? If that's not the case there might be few things we can do about it from the script side.
no issues with manual install.
__________________
REAPER Video Tutorials, Tips & Tricks and more at The REAPER Blog
A friend of mine let me use his M1 and I think I tracked down the issue (using ditto command instead of cp to copy the REAPER.app should hopefully solve the issue on MacOS Monterey)
Been loving UU lately – finally set up a keycut for it
I got a bug just now. Downloading was taking a long time for some reason, so I hit the window close button, then got the warning asking me if I wanted to abort – I changed my mind and clicked "No", and the warning just popped up again. I tried 2x more then finally hit "Yes". So... I guess resume doesn't work?
A friend of mine let me use his M1 and I think I tracked down the issue (using ditto command instead of cp to copy the REAPER.app should hopefully solve the issue on MacOS Monterey)
Let me know if it works in v1.8.1
successful update to latest pre-release.
__________________
REAPER Video Tutorials, Tips & Tricks and more at The REAPER Blog
Cool. Let's hope that Apple doesn't change the security policies again with their next update...
Quote:
Originally Posted by MonkeyBars
Been loving UU lately – finally set up a keycut for it
I got a bug just now. Downloading was taking a long time for some reason, so I hit the window close button, then got the warning asking me if I wanted to abort – I changed my mind and clicked "No", and the warning just popped up again. I tried 2x more then finally hit "Yes". So... I guess resume doesn't work?
Ah yeah, the script window needs to be reopened when choosing to resume. This should be fixed in v1.8.2. (Finally a bug that's not so heavily OS-dependent! )
Can't say from the log, but why would you put portable to program files? Try to run Reaper as administrator. I still suggest you to move folder somewhere else, where Windows doesn't have protected folder.
Can't say from the log, but why would you put portable to program files? Try to run Reaper as administrator. I still suggest you to move folder somewhere else, where Windows doesn't have protected folder.
Will do. It is this way on the other computer too, and it works there... so it's strange.
Will do. It is this way on the other computer too, and it works there... so it's strange.
Same OS, same user rights? Then maybe FeedTheCat could discover what's the issue.
Are you running Reaper same way on both computers? Like using shortcut with unticked run as Administrator etc.? What about this script version? Did you update it on both machines?
same everything... im gonna definitely look into putting things into different folders.
I finally had some time today to look into this. I think vitalker was onto something. I can't even install a fresh portable install into C:/Program Files as the installer crashes due to the directory being read-only.
Did you copy the whole portable folder there from your other computer?
One thing you could try is right-click the portable folder and make sure that it's not in read-only mode (maybe check other permission thingies as well).
Also, does the update work when you download the installer manually from the REAPER website? That's always a good way to check if it's the script's fault or just some issue with your setup.
I finally had some time today to look into this. I think vitalker was onto something. I can't even install a fresh portable install into C:/Program Files as the installer crashes due to the directory being read-only.
Did you copy the whole portable folder there from your other computer?
One thing you could try is right-click the portable folder and make sure that it's not in read-only mode (maybe check other permission thingies as well).
Also, does the update work when you download the installer manually from the REAPER website? That's always a good way to check if it's the script's fault or just some issue with your setup.
updating normally does work. Let me double check read permissions.
it isn't read only. Moving the portable programs folder to C: didnt make a difference...
and actually, I copied it from here to the other pc. Maybe there's some other permissions thing.
I ran as admin, and not only did it work, it went through an entire rescan of my plugins
hmmmm
What did you run as admin? REAPER?
Looks like the script made a new portable install in a wrong directory, that explains the rescan of plugins. I'm guessing that's due to REAPER being run as admin, which I've never done. You can probably just delete that new folder (Portable Programs folder inside the original portable Reaper folder).
I don't use Windows a lot, so I'm not really sure how its permission system works. I tried creating a portable install in "Program files" and also moving an existing portable install into there. Both approaches give me a tons of permission problems. Why not just use another folder?