|
|
|
11-17-2019, 09:52 AM
|
#1
|
Human being with feelings
Join Date: May 2017
Location: Leipzig
Posts: 6,621
|
Environmentvariables and Reaper...
Does somebody of you know, which environment-variables affect Reaper directly?
We have the strange phenomenon, that a Hackintosh doesn't accept a portable Reaper but loads the regular install instead. Same installation works portable on real Mac flawlessly and we think, it could be weirdly set environment-variables.
|
|
|
11-17-2019, 10:56 PM
|
#2
|
Human being with feelings
Join Date: May 2015
Location: Québec, Canada
Posts: 4,937
|
What does "does not accept" mean?
|
|
|
11-19-2019, 09:00 AM
|
#3
|
Human being with feelings
Join Date: May 2017
Location: Leipzig
Posts: 6,621
|
It loads only the normal installation, but not the portable one.
The same folder loads the portable one on a real Mac.
Funny thing, it worked on an earlier version of Reaper without a problem.
|
|
|
11-19-2019, 09:09 AM
|
#4
|
Human being with feelings
Join Date: May 2015
Location: Québec, Canada
Posts: 4,937
|
So... opening REAPER64.app shows no errors, just nothing? The REAPER process does not appear in the Activity Monitor nor the icon in the Dock? What if you launch the executable directly (not the .app bundle) from the terminal? Is the macOS version the same on both the Hackintosh and the Mac?
What if you remove reaper.ini from the portable install (turning it into a regular install)?
Last edited by cfillion; 11-19-2019 at 09:25 AM.
|
|
|
11-19-2019, 09:28 AM
|
#5
|
Human being with feelings
Join Date: May 2017
Location: Leipzig
Posts: 6,621
|
It starts, but it starts Reaper, as if I would have used the Reaper64.app in the Applications-folder, totally ignoring, that it's made as a portable.
So it uses the config in ApplicationSupport, rather the one in the folder, where the Reaper64.App lies, although it's properly installed(reaper.ini in the same folder as the Reaper64.App).
The version is 64 bit, OS as well as Reaper.
It's totally strange...
|
|
|
11-19-2019, 09:36 AM
|
#6
|
Human being with feelings
Join Date: May 2017
Location: Leipzig
Posts: 6,621
|
The only thing I can imagine(will try that) is that it's in a folder, where there are just limited rights to read and write...
Can't test it that easy, as it's not my computer, but the one of one of our Ultraschall-users....
|
|
|
11-20-2019, 01:10 AM
|
#7
|
Human being with feelings
Join Date: May 2015
Location: Québec, Canada
Posts: 4,937
|
I completely misunderstood then.
Strange issue indeed. It it were your computer I'd suggest using dtruss to intercept the system calls opening reaper.ini, to see where it's looking for it and what goes wrong.
Portable install:
Code:
$ sudo dtruss -f sudo -u $USER '/Volumes/Data\ Drive/portable_reaper/REAPER64.app/Contents/MacOS/REAPER' 2>&1 | grep reaper.ini
stat64("/Volumes/Data Drive/portable_reaper/reaper.ini\0", 0x7FFF5E836C00, 0xA3900) = 0 0
open_nocancel("/Volumes/Data Drive/portable_reaper/reaper.ini\0", 0x0, 0x1B6) = 14 0
Normal install (portable reaper.ini not found):
Code:
stat64("/Volumes/Data Drive/portable_reaper/reaper.ini\0", 0x7FFF5A9DDBE0, 0xA3500) = -1 Err#2
open_nocancel("/Users/cfillion/Library/Application Support/REAPER/reaper.ini\0", 0x209, 0x1B6) = 14 0
Portable reaper.ini unreadable and unwritable (+ whole directory unwritable) doesn't cause it to fallback to the standard install either (it just loads with defaults and fails to save any settings):
Code:
stat64("/Volumes/Data Drive/portable_reaper/reaper.ini\0", 0x7FFF51D8DCA0, 0x10AF00) = 0 0
open_nocancel("/Volumes/Data Drive/portable_reaper/reaper.ini\0", 0x0, 0x1B6) = -1 Err#13
Last edited by cfillion; 11-20-2019 at 01:50 AM.
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 09:47 PM.
|