m4L fragmentation after Live 9?

[wasoota]

Just wondering. Live 9 running m4L 6 and Live 8 running max 5. Density for one only runs in m4L 5 (for now at least), not 6. I'm sure there's others too.

With the upgrade to Live 9 not exactly a no brainer, will that fragment the max for Live 'community' into Live 9 users and Live 8 users? Or is max 6 perfectly backwards compatible so all devices made by Live 9 users will run on m4L 5? I somehow doubt it, but fragmentation is the worst possible thing for something like m4L. Any ideas or comments?

[doghouse]

Seems to me there is no way around it. You've already given an example where forward compatibility is missing (Density) and I never expect backwards compatibility with a new version, let alone two (both Live and Max changing versions) plus possible 32 bit/64 bit issues...

Ah, the joys of the computer world

[wasoota]

Seems to me there is no way around it. You've already given an example where forward compatibility is missing (Density) and I never expect backwards compatibility with a new version, let alone two (both Live and Max changing versions) plus possible 32 bit/64 bit issues...

Ah, the joys of the computer world

Yeah, but it's not just the old backwards compatibility thing, because we're not talking about a word processor, but a programming environment. The whole point of m4L is to have 'the community' building great stuff in the Max for Live environment. And up until now, there was only one 'Max for Live'. Now there's basically 'Max for Live 9' and 'Max for Live 8'.

I wonder if they're going to add Max 6 support in Live 8 once the launch of Live 9 is through. They certainly should, if only for the sake of the m4L universe.

[paradiddle]

Plenty of m4l 5 devices that just crash live 9 with m4l 6 or just don't produce sound.

[madlab]

As a siodenote, I've been using max 6 as editor for M4L devices with live 8.34 for at least 6 months now...

[stringtapper]

Yeah Max 6 has been compatible with Live 8 since it was first released, just not officially supported.

[madlab]

Yes Stringtapper, we have to watch out for the zl family objects, as their name changed between 5 and 6. And no routepass...