Ableton Forum

Does your workaround preserve automation?

I already have an account there from the last time someone told me that. I spent some few minutes the last time this came up to fill in my information apparently, with specs about my machine and my experience with Max and such.

However, there was and is nowhere on this site for my account at least ...

No, it could - in principle - be dynamically loaded. For example, there's a box called `pyext` that does for Python exactly what the Java box does for Java and it's entirely dynamically bound, and loaded at runtime.

EDIT: As I said, "in principle" probably conceals weeks of work. But they're going ...

Yes, I understand that entirely. I've been using Max for over 20 years...

But consider from a higher level what's happening. During the loading process for the M4L document, a box is encountered which cannot be resolved to code (for the specific reason you listed).

The loader is able to substitute ...

You shouldn't be forced to load anything you _might_ use; and why would it have been unreasonable to say, "Sorry, no Java in M4L patches" anyway?

It might very well be that not even one person is using Java in a M4L patch - I could find no one claiming to be doing that! Even if a few are, we're all ...

I didn't believe you were correct, but apparently you are .

I did a lot of Java in the past. It's likely that the explanation that since there's no web component there's no security violation is correct, but it's not certain. For example, the version of Java you're using might have been used for ...

It's not a "bug" in the way you mean it - but it's a serious feature deficiency that involves unnecessary and repetitive work for users. Ableton should be embarrassed by this beginner mistake, and in general at their wretched, execrable lack of response to years of reports of feature deficiencies ...

> If you wanna do it this way you should always START with your basic template.

Please don't try to sell this as anything other than a serious defect.

I just got a new controller surface - I have a lot of old material and I had no idea when I wrote it in the past I was going to get this ...

Not to my knowledge. Certainly Ableton has given no indication that they are interested in these bugs or that any fraction of their considerable manpower is being used to address any of them.

Here's a link to a document I wrote last year about bugs that had been in Ableton for at least five years ...

So it's six years after this initial bug report.

Is there any hope that we'll eventually be able to use system exclusives in Ableton or Max For Live patches?

It's not that people are doing this just to be difficult. So very many devices use System Exclusives. I'm here because of one common such ...

This is a big "WOW" for me! I'm probably not going to get a chance this week to use this - I have a big show on Saturday and will be spending my musical time cleaning up existing material, but this might solve many of my problems.

Huge thanks!

UPDATE on the workaround.

The above workaround didn't work in all cases - but a slight tweak is so far working for me.

1. Open the project in Live 8.
2. You should test to see it still works, but they all still worked for me.
3. Execute "Collect All And Save" from the File pulldown menu.
4. Close ...

Utterly brilliant. I knew some of these techniques - if you use Max For Live to control things, you just HAVE to use the Loopback technique all the time - but it's amazing how integrated your technique is. I'm going to start using that for my very next show!

That said, it's a crying shame that we ...

Unfortunately, it is NOT a feature that Live 9 has - I was misled by talking to someone who should know.

I've been complaining about this for *five years* and I've been basically been told that I'm being difficult and unreasonable - but pretty well every other sequencer has had this feature for the ...

Multimonitor support - my eyes aren't what they used to be.

I'm also very curious about the ability to glue together controllers with MIDI notes - that's the one killer feature that I had in Opcode Vision in 1990, and with Digital Performer and Logic today, but unfortunately don't have.

UPDATE: I ...