un
Okay, so what I was trying to hint at initially was that, currently, the .sh script points to a path that is supposed to be a folder inside the resampler folder called "moresampler-0.8.4". That folder doesn't exist for you for normal installation reasons!
Probably easiest to fix this with a quick script change to make sure it points to just the same folder the script is in. Open your .sh script and change the RELPATH= line to say just RELPATH="moresampler.exe" instead of RELPATH="moresampler-0.8.4/moresampler.exe" and hopefully thats the problem.
Unfortunately it didn't work, the bug window still says "no such file directory exists". Im wondering if it has to do with the usr/local/bin part cause when I search my Mac I have a usr/local directory but no usr/local/bin
edit: ok I just received crucial information that can probably help us. This is copy and pasted from a reddit thread.
"macOS does not come with a file named bin in /usr/local/bin. (It might come with a directory of that name, but not a regular file. But I do not have a virgin macOS system handy to check that.)
What likely happened was OP ran some poorly written install script for who-knows-what that just assumed /usr/local/bin was an existing directory and tried to copy its executable to /usr/local/bin with a command like cp NewThing /usr/local/bin. If bin is a directory, that works fine, creating /usr/local/bin/NewThing as a new file. If bin does not exist (but /usr/local/ does), it creates a new file named bin and copies NewThing into that file.
(If macOS does start with a directory /usr/local/bin, then there would also have been a step in which it was somehow removed or renamed before an install script would put a regular file in its place as described above. I am not sure how that would have happened, other than by a user tinkering with the system.)"
There are multiple terminal commands given in apple discussion threads as well to create a directory, but I'm feeling hesitant. There are files named bin in my Mac, but someone said something about the files named bin possibly interfering with creating a directory. Im not totally confident in fiddling with directories through the terminal. I also have a ton of files named local that are just empty, two local folders have something in them. I'm wondering if when I try to run stuff it makes up a new local folder since usr/local/bin isn't a directory but this is just a guess.