Why is live.drop useless?

[tassock]

Looks like live.drop is still a work in progress judging by this thread:

http://forum.ableton.com/viewtopic.php? ... =live.drop

Personally, I don't think this object is useful on its own. What can you currently do with a file path? Find and load a clip in your Max environment? Isn't the point of Max for Live to let Live handle audio buffering and playback?

The presently useless state of this object leads me to speculate that there's something in the pipeline that will give it value. What I'm hoping for is the ability to insert clips into a session view cell by passing a file path. This would enable users working with large sample libraries to automate their workflow in countless ways. It could liberate users from having to drag files from the file browser, which is currently the only thing keeping me on my laptop during performance. Additionally, Live's file browser doesn't cut it when you want to sort by bpm, key, tags, etc. Functionality to insert files into a set would enable the development of customized file browsers within Live that address individual needs.

Anyone on the inside know if something like this is on their radar?

[pukunui]

Audio clips are probably the least of the things people will use live.drop for.

It works fine in devices, just not correctly in the editor. Check out the loopshifter device.

-A

[grooveWhiz Akeem]

What I'm hoping for is the ability to insert clips into a session view cell by passing a file path.

It's supposed to be on the feature request list. I was hoping for that one as well. See here http://forum.ableton.com/viewtopic.php?f=35&t=125093