ReaCoMa / ReaCoMa-1.0

ReaScripts that interface with the FluCoMa tools
https://www.reacoma.xyz
BSD 3-Clause "New" or "Revised" License
28 stars 0 forks source link

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

Open tinpark opened 4 years ago

tinpark commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

Awesome, James, thanks a lot. Works for me now. It’s the windows path \ thing, I think. If you use ~/AppData, as you’ve shown, works fine, if you use windows path names

C:\Users\mparker\AppData it doesn’t like it.

Brilliant and thanks for doing this work… really helpful. Much appreciated. Martin~

From: James Bradbury notifications@github.com Reply-To: jamesb93/ReaCoMa reply@reply.github.com Date: Tuesday, 13 October 2020 at 15:54 To: jamesb93/ReaCoMa ReaCoMa@noreply.github.com Cc: tinpark mp@tinpark.com, Author author@noreply.github.com Subject: Re: [jamesb93/ReaCoMa] Reaper claims it can't find the executables on windows (#6)

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

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

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?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

jamesb93 commented 4 years ago

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 :+1:

jamesb93 commented 4 years ago

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

jamesb93 commented 3 years ago

I will one day fix this...