Just Evan

On the outlet [live.observer file_path] I get a slightly incorrect file path (having "\ at the beginning and \" at the end), which makes the path unreadable for [sfplay~], how can I fix this?

Here's an example of what it should look like:

From this: "\"disc:/folder/samples/packname/samplename.wav\"" 

To this: "disc:/folder/samples/packname/samplename.wav"

Hi, I need your help!

On the outlet [live.observer file_path] I get a slightly incorrect file path (having "\ at the beginning and \" at...

correcting-the-file-path

(otherwise, perhaps some [regexp]-based dark magic?)

Found the perfect solution on the forum! Works great with [sfplay~]

How are you doing that? ( mentioned in an earlier post )

When I drag a name to a post I get the https address…

https://cycling74.com/author/63e372b31c20792f47527d2f

I simply drag the name into the text field and then click on an empty space.

Another method: copy the link from the name and paste as a link on the selected text

First method- drag and drop only gives the link.

Wondering why first method works for you and not for me?

it only works with alien characters, otherwise they are not residential.

back to the topic, what is the reason why observer outputs the path string like this? when there is no space in the path how can it even be a symbol - and what is the backslash denominator good for first in place?

I'm tracking changes in: path ... - simpler - sample - file_path, and for some reason observer is outputting the path this way. 

But if it goes through objects (in the screenshot) then the problem is solved.

I didn’t try to figure out what the problem was, I just found a solution on the forum and it works! haha

when the observer output actually has a bug, and one day it is fixed, your patch will stop working for paths with a space character.

P.S.  I guess Live does not use backslashes as path delimiters on windows ?

Correcting the file path