stygmate

No more than 2 audio inputs/outputs !!!! ? (live side chain input ??????)

Difficulty to do a simple delay controlled by midi note...

No real possibility of doing a real Vocoder / Convolver !!!!

+1 this thread to let Cycling74 and Ableton know that it is really insane !

No more than 2 audio inputs/outputs !!!! ? (live side chain input ??????)
No midiin in audio effects ????

Difficulty to do a simple delay controlled by midi note...
No real possibility of doing a real Vocoder / Convolver !!!!
....

max4live-petition-for-more-audio-inputsoutputs-and-midi-in-out-in-audio-effects

It's not Max For Live. It's Live itself. So you'd need to register this as a feature request for Live 9 on Ableton's forum. Cycling '74 can't do anything about it.

stringtapper is right about this. All Live channels are stereo channels.

yes I know that, but cycling'74 could also push Ableton in this direction...

It may be noted that side chain input is supported in Live but *not* in Max4Live.

@Broc - Yes I wondered about that - if live can do it natively then why can M4L not access that part of the program.

As much as I love M4L it is greatly limited in this area. I hold out hope for Live 9 but... the growing list of 250 odd requests for Live 9 is going to mean a lot of people will not be satisfied.

@Broc - Yes I wondered about that - if live can do it natively then why can M4L not access that part of the program. 

As much as I love M4L it is greatly limited in this area. I hold out hope for Live 9 but... the growing list of 250 odd requests for Live 9 is going to mean a lot of people will not be satisfied.


This has been a quite common request for several versions now. I think I read a while ago that it is one of the basis of the code of the software and that, like the ability to record automation in session view, it would require a complete rewrite. I'm not a programmer and can't comment on that but as a user mostly in multi speakers setups, this has been quite a pain in the ass. I sure like flexibility and fast workflow in Live, but this is a pain... And one of the reason I came to Max. Dog bless them !

And of course there is another (IMO legitimate) issue to consider... If M4L would provide nearly everything one can do with Max then wouldn't that tempt people to buy into Live + M4L and leave Max for what it is ? That wouldn't exactly be a healthy situation either.

If you want more out of M4L then sometimes moving to Max can help (depending on what your goal is of course). Still, IMO something to consider. I eventually got myself Max 5 besides M4L and having that option has helped me out in several occasions.

And of course there is another (IMO legitimate) issue to consider...  If M4L would provide nearly everything one can do with Max then wouldn't that tempt people to buy into Live + M4L and leave Max for what it is ?  That wouldn't exactly be a healthy situation either.

If you want more out of M4L then sometimes moving to Max can help (depending on what your goal is of course). Still, IMO something to consider. I eventually got myself Max 5 besides M4L and having that option has helped me out in several occasions.


Shelluser : your point is right, and I bought Max complete license for the same reason...

+1 that M4L should be able to access sidechaining in Live.

+1 For more flexibility with Audio & MIDI I/O in M4L. It's really a bummer when Live's internal instruments like impulse and the racks/drumracks can have all the Audio I/O's in the world and M4L is only limited to a single stereo pair.. And from what I've heard, all "hacks" you can do to get around the Audio I/O limitations are unreliable in terms of latency.. ! ! :(

If Ableton is really committed to M4L, they need to show a lot more love to using it in Live 9.. Just sayin.

ps... i'll open a petition for midi-learnable native max UI objects in M4L, folder support for live.drop, attributes for live.* UI objects ( live.menu included i.e. autopopulate etc. ) with setmin, setmax, etc.. midi ports access from M4L devices. anyone has opinions on this limitations? are they coming from Ableton LIve structure or from M4L itself?

ps... i'll open a petition for midi-learnable native max UI objects in M4L,  folder support for live.drop, attributes for live.* UI objects ( live.menu included i.e. autopopulate etc. ) with setmin, setmax, etc..  midi ports access from M4L devices. anyone has opinions on this limitations? are they coming from Ableton LIve structure or from M4L itself?


Max4Live Petition for more audio inputs/outputs and midi in out in audio effects