KVR Audio

mcbpete · Post by **mcbpete** » Fri Oct 23, 2020 12:18 pm

tooneba wrote: Thu Oct 22, 2020 11:52 pm No reliability of backward compatibility unlike native devices are carefully taken care by ableton.

I'm not aware of *any* back compatibility issues with max for live - do you have any examples? I've used amxd patches dating back nearly 10 years in Ableton 10 and have yet to encounter any compatibility problems.

noiseresearch · Post by **noiseresearch** » Fri Oct 23, 2020 12:26 pm

/* whitenoise */

tooneba · Post by **tooneba** » Fri Oct 23, 2020 1:55 pm

mcbpete wrote: Fri Oct 23, 2020 12:18 pm
tooneba wrote: Thu Oct 22, 2020 11:52 pm No reliability of backward compatibility unlike native devices are carefully taken care by ableton.
I'm not aware of *any* back compatibility issues with max for live - do you have any examples? I've used amxd patches dating back nearly 10 years in Ableton 10 and have yet to encounter any compatibility problems.

A few of them were talked about in the first few posts of this thread I think.

mcbpete · Post by **mcbpete** » Fri Oct 23, 2020 2:23 pm

You mentioned the Convolution device having 'quirkiness' (anything more specific?!), and I just tried every control on that 2013 Shaper device in v10.1.25 with no issues (great little wave shaper, happy the OP brought it up!)

tooneba · Post by **tooneba** » Fri Oct 23, 2020 2:25 pm

mcbpete wrote: Fri Oct 23, 2020 2:23 pm You mentioned the Convolution device having 'quirkiness' (anything more specific?!), and I just tried every control on that 2013 Shaper device in v10.1.25 with no issues (great little wave shaper, happy the OP brought it up!)

If you want to research them just google "m4l convolution reverb issues". Plenty of hits. It's famous because it's officially included patch

and they don't acknowledge or fix. I won't copy paste detail reports here.

pdxindy · Post by **pdxindy** » Fri Oct 23, 2020 2:43 pm

mcbpete wrote: Fri Oct 23, 2020 2:23 pm You mentioned the Convolution device having 'quirkiness' (anything more specific?!), and I just tried every control on that 2013 Shaper device in v10.1.25 with no issues (great little wave shaper, happy the OP brought it up!)

I liked the convolution reverb... a lot! But I would only put it into a project when it was near done then render to audio! I always had to tiptoe around M4L. It seemed if I breathed funny, it didn't like it. Everything would seem to be working, then bam, random crash. Never repeatable, so could not report specific bugs. It wore me down, then I stopped using any M4L devices. I'm using other DAW's now, but still have Suite.

Seems like it is still having the same sort of issues for some and not others. I hope the day comes when it is super solid for everyone!

DrEntropy · Post by **DrEntropy** » Fri Oct 23, 2020 3:29 pm

I have windows 10 and Macbook, on both these platforms I have not had any issues with M4L. However I should caveat that I don't use very many of the M4L devices provided by others, I mostly use it for my own stuff (with the exception of some things in the essentials pack like LFO and envelope, which are truly essential!)

thecontrolcentre · Post by **thecontrolcentre** » Fri Oct 23, 2020 3:46 pm

Win8.1 and Live 10 here, without a single issue in M4L. I use both stock and 3rd party stuff regularly.

mcnelson · Post by **mcnelson** » Fri Oct 23, 2020 3:54 pm

liquidsound wrote: Fri Oct 23, 2020 12:00 am As pdxindy noted, the commercial devices are probably better coded and maintained.
You pay some reasonable amount of money but the functionality added to Ableton becomes unrivaled.

I only ever used commercial M4L devices, from K-Devices, MaxForCats or Isotonik - but still got a load of crashes in Live 9. I had to ditch Oscillot because it was so unstable for me.

Live 10 seems a lot more stable and it's pretty rare I get an M4L device crashing live now.

Ableton M4L stability