Features you would like to see in Ableton 9?

[deva]

I would like to see a couple synths in a rack have the synths distributed across cores

[3phase]

I would like to see a couple synths in a rack have the synths distributed across cores

isnt that what instruments racks are for?

[3dot...]

^^^ nope.
you need to spread instruments out across tracks for better cpu util.
as far as I know.. 1 rack = 1 thread/cpu.

[dna598]

1.Slice audition (audition between markers)

2.Touch Automation

3.Bezier curves

4.Retrospective record

[Tone Deft]

4.Retrospective record

you mean a feature that fixes "man that was a great jam, why didn't I hit record?!?!?"

[3phase]

4.Retrospective record

you mean a feature that fixes "man that was a great jam, why didn't I hit record?!?!?"

tht would be a real workflow improovement that safes half a lifetime.. wouldnt it?

[Tone Deft]

4.Retrospective record

you mean a feature that fixes "man that was a great jam, why didn't I hit record?!?!?"

tht would be a real workflow improovement that safes half a lifetime.. wouldnt it?

yeah, but sometimes I think those epic jams were epic because I was 'in the moment' and didn't have to listen to how it actually sounded.

I still haven't learned that great bit of advice "ALWAYS be recording you can delete it later."



I really hope they can fix the Winblows anomaly where if a device is unplugged Live has to be restarted before it will pick it back up again. Macs have no such problems.

[dna598]

4.Retrospective record

you mean a feature that fixes "man that was a great jam, why didn't I hit record?!?!?"

Yes!

Something that i (wrongly) assume would have been in the minds of the developers at the concept stage.

[3phase]

4.Retrospective record

you mean a feature that fixes "man that was a great jam, why didn't I hit record?!?!?"

Yes!

Something that i (wrongly) assume would have been in the minds of the developers at the concept stage.

it a wish that is formulated since the first versions of live... they are just deff on that ear and think that one sould know before that one wants to record.. a general problem that ther are not enough rockn rollers between the coders..or better.. the rock n rollers between the coders are usually to expensiv for a company like ableton and anyway not intersted in fixed engagements...


and to tone deff..
i know very well when a run was brilliant.. usually i catch it in the middle... but the beginning is allways lost..

and to allways record? sure.. it just dont works... i allways try.. but usually i have one version allready. play a bit around.. and than ..wow.. .. never would have erased the previous version intentionally ..but when the new one is so much more interesting?

I would love if computers wouldnt help with age old studio session problems instead makeing things even more complikated

[deva]

I would like to see a couple synths in a rack have the synths distributed across cores

isnt that what instruments racks are for?

No, instrument racks are for taunting you with all the amazing functionality you would have at your disposal if they could use multiple cores on high CPU plug-ins. Layering ACE for example is pointless in racks... have to use multiple tracks instead to use multiple cores...

[dna598]

Roughly in order of importance:

1- Add delay compensated automation. Pretty essential as far as I'm concerned.
2- Add tension curves to automation, numerical value entry for breakpoints, snap to grid for breakpoints.
3- The ability to freeze a single clip and it's plugins (including MIDI clips), versus freezing the entire track. Freeze, duplicate, flatten takes forever...especially when I'm only concerned with one short clip. Also important: make the buffer size that is used for the freeze configurable in the preferences or in Options.txt. I'd like to have higher automation accuracy when freezing than is possible in real-time. Check out Reaper's ability to render takes - it is pretty mind blowing.
4- Clip envelopes, when automating a plugin parameter, need to be configurable to either bipolar or unipolar. This would allow automation to values above the current value, instead of just beneath (which is how it is currently).
5- The ability to freeze tracks with sidechains and other routing.
6- Nested groups.
7- Control over clip placement, sample path, etc. in the arrange view from the M4L API.

Screw working on included instruments and effects. That is what plugins are for.

This is a good list

[ark]

When you map a macro to a control, I want Live to set the macro's value to the control's current value rather than the other way around.

[cmreal04]

Slice to pre-existing racks.

[fx23]

9) instead the max for live trap more internal routing options within live itself like free assignable sidchains to any parameter..and that together with little helper like lfo plug.. envelope folower plug..pitch folower..
what can act as a tuner aswell... and.. an own step editor... why we have to buy expensiv software for such an cheasy stndard feature

In general the development of live should be like max for live did´nt exsists to not make the negativ results from that implementation any bigger...

in the end of the day max is nothing many people like to deal with during a production..otherwise max standalone would have been a bigger seller.. to force that onto people will kill any ableton life advantage of beeing easy to be operated

+1

[hoffman2k]

Something that i (wrongly) assume would have been in the minds of the developers at the concept stage.

Why would it be wrongly to assume that? There's even evidence that its already part there and has been so for years. The debugging event recorder..
During beta's it records all the events which can later be played back by developers to see what happened. If they somehow can rig that feature to do every action again but with the record button on, they essentially built retrospective recording.

I'm guessing this doesn't rank high up their priority list, but never assume that there aren't any developers with insane ideas at Ableton.