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

Reaper claims it can't find the executables on windows #6

Open
tinpark opened this issue Oct 13, 2020 · 6 comments
Open

Reaper claims it can't find the executables on windows #6

tinpark opened this issue Oct 13, 2020 · 6 comments

Comments

@tinpark
Copy link

tinpark commented Oct 13, 2020

Hi James, try as I might to get these wonderful reascripts to work on Windows, I can't seem to make them play nice. I've put the fluid windows CLIs in ~\AppData but when I tell reaper to run a script and find the executables in that folder, it claims there aren't any executables there; "The Path you set doesn't seem to contain the FluCoMa tools.". I'll be glad to help troubleshoot this with you if you don't have a windows envrionment to play with. Apologies if I've missed an obvious step. I wondered it the scripts are looking for nix-like paths and not windows-like paths... Thanks in advance of any troubleshooting. Works like a charm on OSX.

@jamesb93
Copy link
Collaborator

Ah, I too am a windows user every once in a while so I have an install I can test on. I was certain I caught all the caveats here but evidently - no. Let me have a dig and see if I can recreate the issue and push a fix up ASAP. Can you just remind me what version you are using for both ReaCoMa and FluComa? The latter shouldn't effect much, but the former likely will.

@jamesb93
Copy link
Collaborator

jamesb93 commented Oct 13, 2020

Okay so I did a fresh REAPER install, I then downloaded the binaries like so:

image

And then ran the script with this input for my path:

image

Which worked for me.

I think the next thing to try is to expand the ~ manually so for me:

~/AppData becomes C:/Users/james/AppData which worked for me.

If you expand it manually and it works then I know where to go looking. If it doesn't work still then it's likely I am fucking up the path formation on windows with spaces or slashes or something in that ballpark. By any chance do you have any european characters or spaces in your username, or perhaps a non-standard drive letter? What I would try and detect here is how the ~ is translated under the hood.

@tinpark
Copy link
Author

tinpark commented Oct 13, 2020 via email

@jamesb93
Copy link
Collaborator

Argh!! I could have caught that one and will make a fix now so other backslashers don't get stuck at the same point too. Thanks for making a bug report and letting me know about the issue. Enjoy 👍

@jamesb93 jamesb93 reopened this Oct 14, 2020
@jamesb93
Copy link
Collaborator

Reopening this so I don't forget to fix it...

@jamesb93
Copy link
Collaborator

I will one day fix this...

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

No branches or pull requests

2 participants