Ali Somay

Uncertainity from the title is there for a reason, because there can be many reasons for this including me overlooking some stuff. 

The issue is about the inconsistency about what live.drop gives as a file path in two different computers.

Screenshot 2021-12-22 at 16.40.38.png

Screenshot 2021-12-22 at 16.40.17.png

In computer 1 live.drop gives the full absolute path to the file.

In computer 2 live.drop gives the file name.

Uncertainity from the title is there for a reason, because there can be many reasons for this including me overlooking some stuff. 

The issue is about the inconsistency about what live.drop gives as a file path in two different computers.

Computer 1
Mac OS Montenerey 12.1 M1 Max 
MaxMSP 8.2.1

Computer 2 
Mac OSX Mojave Intel (Mac mini)
MaxMSP 8.2.1

The patch is the same.

Computer 2 ->

In computer 1 live.drop gives the full absolute path to the file.
In computer 2 live.drop gives the file name.

Have you realized this behavior before?
Am I missing something or is this a bug?


Uncertainity from the title is there for a reason, because there can be many reasons for this including me overlooking some stuff. 

The iss

a-possible-bug-in-live-drop-maybe

I think this happens because one of the two computers has the audio file in the search path and the other does not.

Hey Ali,
I think this happens because one of the two computers has the audio file in the search path and the other does not.

So I would assume that the one who does have the audio file in the search path would only output the file name? Is that true?

Is it possible to unify the behavior where live.drop always outputs an absolute path or should I just apply a workaround where I make sure that the folder for the audio files are not in the search path?

By the way I don't have access to the other computer currently, I will check if that one has the folder for the audio files in the search path tomorrow but from intuition it makes sense that this might be the case.

Thanks a lot!
So I would assume that the one who does have the audio file in the search path would only output the file name? Is that true?
Is it possible to unify the behavior where live.drop always outputs an absolute path or should I just apply a workaround where I make sure that the folder for the audio files are not in the search path?
By the way I don't have access to the other computer currently, I will check if that one has the folder for the audio files in the search path tomorrow but from intuition it makes sense  that this might be the case.


Aaand it turns out that this object exists since even Max 4.

Screenshot 2021-12-23 at 01.06.48.png

Looks like it :) :blush:
Aaand it turns out that this object exists since even Max 4.
How did I miss this :) 


A possible bug in live.drop (maybe)