Hi, have been interestedly playing with RipX DAW Pro (trial) recently, but have noticed some weirdness when I perform a rip. The python process seems to be calling out to Supercollider's sndfile.dll for some reason (see attached s/s).
I can check this by uninstalling supercollider, doing a rip and getting no "not found" dialogs.
If I re-install SC, then the failure dialogs resume. I wouldn't mind so much, but if one does not OK the dialog, the ripping process seems to wait until I do finally click OK. The "not found" dialog is generally presented twice in a row, and then not again until the next rip session.
It does not seem to be dependent on type or length of audio.
This started occurring after a crash in RipX. I tried starting with shift+Ctrl, but it seemed to make no difference.
If there are logs somewhere I can send you, I am happy to do so.
Is SC a dependency of RipX? I had a brief look, but didn't see anything obvious suggesting it might be (but I didn't perform a forensic examination, by any means).
if there's some way of stopping this message, that'd be great! Any hints gladly appreciated. I'm using the latest build of RipX DAW (v7.1.0 20th march 2024)
Cheers
Richard
I'm sorry to hear that you're experiencing difficulties. I've been unable to reproduce this. Which version of Windows are you using?
Hi David, I've got:
Edition Windows 11 Pro
Version 23H2
Installed on 1/21/2023
OS build 22631.3296
Experience Windows Feature Experience Pack 1000.22687.1000.0
I do have another (system) python installed (v3.12) but there's no magic going on there. Nothing untoward in my environment PATHs or anything. I take it Supercollider isn't in any way a dependency then?
Cheers
R.
We can reproduce this issue by adding C:\Program Files\SuperCollider-3.13.0 to the PATH environment variable. The SuperCollider installer doesn’t appear to do this so presumably isn’t required by SuperCollider, so if you're happy to remove that value from your PATH then that would be the easiest solution for the time being.
@dave Thanks very much! I am clearly an idiot, supercollider was in the system path and I missed it. :/
A quick test rip seems to indicate this has fixed the problem! Thanks again!
I'm glad to hear it's now working. Thanks for letting me know.
