Issues with sample paths (Win10) about stargate

[L3337]

Hi @DreadDendy ,

Thanks for reporting. I'm looking into this, I'll let you know when I have it figured out.

[L3337]

I fixed the main problem, which was this:

0|0.0|/:snare/212234__alexthegr81__tapesnare-21.wav
1|0.0|/:snare/212234__alexthegr81__tapesnare-21.wav
2|0.0|/:kick/266764__hard3eat__synth-kick-3.wav
3|0.0|/:kick/266764__hard3eat__synth-kick-3.wav
4|0.0|/:kick/266764__hard3eat__synth-kick-3.wav
5|0.0|/:kick/266764__hard3eat__synth-kick-3.wav
\

I did not yet try to implement an automatic correction of the problem in existing projects, I am still looking into that.

If DAW make copies of added samples may be it would be more logical to use relative paths, like !/timestretch/4.wav?

This system that is in place has been there for many years, not easily possible to change it without risking breaking backwards compatibility with existing projects. In the case of dragging samples from a DIFFERENT project, this is the expected behavior, because the samples came from outside the project. What should have been working, but was not, was being able to drag samples from the same project in Windows.

I have added some folders with files in C:\Users\DreadDendy\stargate\projects\Test\audio\samples.

Be careful, that folder was not meant to be manually updated (although I get you were fixing the project in this case). The only project folder meant to be manually modified by the user is:

C:\Users\DreadDendy\stargate\projects\Test\user

Modifying the audio folder by hand (audio or project files) is quite risky if you don't understand how all of the files relate to each other.

[L3337]

BTW, I'm doing some rather intense testing of #40 before the next release, this will probably make it into a release by next weekend.

[DreadDendy]

Thank you for fixing and explaining.