Ableton Forum

I'm using OSX 10.7.2 on a 15" MBP spring 2011 model.
Live 8.2.7
Max 5.1.9

In the set I am currently working on, if I drop in a max midi effect, and try to open/edit it, countless windows of that device open up.

What the hell is happening?

you or the one who created the device saved it with subwindows open.
solution: open the device, close all subwindows ( there is a max menu entry for that ) and save the device.

if still windows open when loading the device, the device might contain abstractions that were saved with their subwindows open too, then you need to repeat the procedure for those abstractions too. if the abstraction is part of a poly~ object with several instances then each instance will open the subwindows and you'll end up with lots of them. the title of these windows will contain an instance number: "blabla[12]".

hope this helps

Robert

Yep. Windows and their positions in the screen are saved with the patch.

I am talking about with any device, even the default 'Max Midi Device'

Even if I open an empty patch, it keeps opening identical windows, one on top of the other.


If I open a 'new' live set, the Max4Live devices dont do this.

wow. this sounds.... different.
can you post a screenshot ?
what are the titles of the windows?

r.

You can tell by how dark the windows shadows are getting. They just keep opening one on top of the other, No controllers hooked up, no other max devices in this live set.

yeah, that's been happening to me for years. I tried to get c74 to deal with it but they were stumped.
For me it happens when the live set is using up almost all available memory.
So I have to delete all samples and memory hogging vsts before opening the patch.

It's been going on so long that it's pretty much just a fact of my existence at this point.

Yikes. Yeah I have a bunch of samples in my drumRack and FM8, plus an external instrument rack going to a slimPhatty, yet my Set runs about 30-35% CPU.

This sucks.

it does suck! I don't know how many hours I've lost because of this.
PS I don't think the cpu meter matters; for me it's always memory. I have a set with a few samplers holding thousands of samples, and I need to delete all the samples before opening an m4l device

weird, weird, weird.
Sorry to hear that. Hope you bug report.

I do bug report, problem is this is not generating a report.

Ok please you guys send us these sets and full instructions for reproduction.

C74 support or direct to me is fine

Thanks

-A

I will try, but I am sure the set is a large file due to the amount of samples in my drumRack.

Maybe I will try via DropBox.

OK, I sent [email protected], an invite to a DropBox folder containing a stripped down version of my set that will cause the issue above, along with the simple instructions.

Thanks!

I can reproduce this.

We're having a look at it.

Thanks very much for the report.

Cheers


Andrew