sometimes using m4l is like being up a creek without a paddle?
I search and search before I ever write a post, usually giving a few days of testing before asking questions. But Im hitting brick walls all the time with the m4l live api, with pretty basic things.
For instance, its not possible to get the name of a live_set, not even a unique id? I just want to be able to detect wheter a user has copied a device, or whether they are dragging in a new one, or saving it as an adv preset. Differently. Why these things are so hard?
Saving device presets and patches, without ridiculous javascript hacks, is a total pain.
I just want to get coding now, without having to make tons of workarounds every time, such as saving/restoring filenames, or locations.
Is anyone else having the same problems Im having? Would be great to put these in one place so we can improve the api.
Cheers N
HI, whilst I can't offer you immediate solution to your issues, I'm currently working on a js layer which will address alot of these issues. There's lots of stuff in the lom that requires lots of donkey work, error prone, coding which I'm trying to address. If you want to be on the beta list, pm me your dropbox address, but as a disclaimer, i'm probably a good couple of months from this being complete.... Over time I hope to address all of these issues, but due to what we have access to in the API, not everything can be solved....
btw, I've read alot of your posts and this is stuff I intend to address later rather than sooner...., but hey....
I don't understand why you want to detect how m4l devices or presets are used in a live set.
Hi broc have pmd you about the js script, would be great to test these and see whats coming.
Sorry, I think you are confusing me with leehu...
ahh sorry mate