Has anyone figured out how to access Browser 'Places'???

[prebentious]

Hello,
After finding a showstopper bug with hosting vst~ objects in an M4L patch, I'm looking to try and load devices on the fly from the 'Places' section of the browser.
I've researched clyphx etc, which seems really close, but it doesn't access Places.

Before I bite the bullet and learn Python (I've never coded anything in my life, though I'm quite experienced with Max) I thought I'd see if any of you smart people have already done it.

Anyone have any hints?

Thanks
Ben

[prebentious]

If anyone is capable of hacking this together, I'd be willing to pay.

[S4racen]

Don't think it's possible….

Stray did a release that gave access to the browser, think Places is out of bounds even with that?

Cheers
D

[prebentious]

Hmmm I wonder. Push can access places, so I imagine there's some way to do it.
Stray, can you weigh in on its readability, even if you're not interested in actually doing it?

[Valiumdupeuple]

scroll_browser function maybe ?
I've never tried it but I've notice it since L9. I'll check later on.

[prebentious]

scroll_browser function maybe ?
I've never tried it but I've notice it since L9. I'll check later on.

Thanks!

[chapelier fou]

i didn't manage to have it working, if you could post an example that would be great !

[regretfullySaid]

You can navigate the browser fine with the M4L, just not actually fire the selection, at least that's what I found a little after the 9.0 release. Shortly thereafter is when Stray released his workaround. Also I think it's just an M4L limit; can probably do it with python.

It's a shame too, because I can get some smooth scrolling and directional navigation in the browser using quneo encoders.

[chapelier fou]

What do you mean by 'fire the selection' ?
I'd be curious if i could navigate in my sets and load them with Mira.

[regretfullySaid]

Fire like double clicking with the mouse, loading it to the actual set.

I mean, you even have access to hot-swap options, where you want the device to be loaded, but not able to actually load it....maybe that's changed, or maybe they want it exclusive to python, I'll have to check.

There have been some automation options added to the API as well, and I'm not sure those are accessible with M4L either. Will have to check...

[chapelier fou]

bummer...

[regretfullySaid]

That is, if you are able to load a device, I've overlooked, so please let me know if there's a way without a workaround.

[Myralfur]

haven't tried accessing the browser since the live 9 beta. thought the functionality had been added when i found a few new functions/properties in Application.View, but unfortunately not for m4l. last i heard it was kind of blocked in max for live, although it is definitely more accessible through the python api.

what you can do from m4l though:

you can toggle on and off the "browse_mode" property of "live_app view" with the function "toggle_browse". a.k.a hot swap mode. this only works for swapping devices though.

you can then use the "scroll_view" function to scroll through the browser.

you can then toggle off "browse_mode"/hot swap. if i remember correctly this will then load the newly selected device in the browser.

haven't tried it since live 9 beta though, so could be mistaken. as soon as i realised you couldn't load in audio clips i stopped working on it.

[Myralfur]

@shadx312

yeah found some interesting functions for automation like "begin_gesture", i think it was called anyway. but then they're not documented in the m4l object model. haven't messed around with them yet though. would be interested to see if/how they work.

may be able to find what they do in the push script, try it in m4l.

[regretfullySaid]

Right. I haven't noticed begin_gesture, but you can now show/hide clip envelopes (yay!), re-enable clip automation, tell if a clip is an arrangement clip or not...

What I did was compare 'getinfo' restults from live paths to this (thanks Julien)
and you can see what's left out of M4L.

For example there's a clip automation section not in M4L:

Live.Clip.AutomationEnvelopeClass
Describes parameter automation per clip.

Live.Clip.AutomationEnvelope.insert_step()Method
insert_step( (AutomationEnvelope)arg1, (float)arg2, (float)arg3, (float)arg4) -> None : C++ signature : void insert_step(AAutomation {lvalue},double,double,double)
Live.Clip.AutomationEnvelope.value_at_time()Method
value_at_time( (AutomationEnvelope)arg1, (float)arg2) -> float : C++ signature : double value_at_time(AAutomation {lvalue},double)\

which is probably how you can step-sequence automation in the Push update.