Ableton Forum

llllll1111116 wrote:A vst/au latency indicator for each plugin

as much as I favour more information, I'm not sure of the benefit of this number for manual use.
If the VST is reporting latency to the application incorrectly so that PDC is not working for you then seeing that incorrect number wont be of much assistance as an alternative.
Alternatively if the number is correct, but Live's PDC is working incorrectly (due to some strange confluence of events)then you will be left with a number with no real application. You plan on using the track delay for it? It wont work ... because ...

Thirdly, in the case of latency offsetting it's a compound number taking in stacked chains in racks, and compression look-aheads, and IR reverbs on sends. You would need to manually perform this sum across the application after every parametric change in order to really use the number you propose showing.

i go vote for vst and/or au latency indicator for each plugin

OMF2 import with handles. Not just something I want...I need it to work.

Give Thanks!

Angstrom wrote:

llllll1111116 wrote:A vst/au latency indicator for each plugin

as much as I favour more information, I'm not sure of the benefit of this number for manual use.
If the VST is reporting latency to the application incorrectly so that PDC is not working for you then seeing that incorrect number wont be of much assistance as an alternative.
Alternatively if the number is correct, but Live's PDC is working incorrectly (due to some strange confluence of events)then you will be left with a number with no real application. You plan on using the track delay for it? It wont work ... because ...

Thirdly, in the case of latency offsetting it's a compound number taking in stacked chains in racks, and compression look-aheads, and IR reverbs on sends. You would need to manually perform this sum across the application after every parametric change in order to really use the number you propose showing.

I was thinking more like a function in every plugin window that test the plugin and show some value, sure the number will change everytime, but we're supposed to use ableton in live so latency is our best ennemy and getting a closer information about can be usefull. I don't know if it can be possible, that's just an idea.

I want a shortcut for "Duplicate Track - {Remove Side Chain Compressor if on the track} - Freeze - Flatten - {Add Side Chain Compressor}".

And Automation Curves.

And "Snap Automation Points" to Grid.

That's all. For now.

So I came from the Pro Tools world and am steadily and certainly being converted to the Ableton Live way of life. I checked box the workflow box because Pro Tools does unfortunately still have Ableton beat in the regular musicians' tracking studio. In the composer/producer role, Ableton Live is AWESOME! Which is why I love it. But when I'm just playing engineer and am tracking musicians vocalists, my workflow is way off. Mainly, I need virtual tracks or "playlists" to organize separate takes on a single track to be compiled later (after the musicians leave the studio). Second, it'd be really nice if there was a way to break my bus tracks off from the bus section and place them directly adjacent to audio tracks. Also, being able to group the busses and audio and midi tracks would be useful (think full drum kit w/triggered samples).

If I am mistaken and these features do already exist... SOMEONE PLEASE TELL ME HOW!

jagpaw.com

I vote for
global LFO for automation
Multi aftertouch from MIDI-instruments (it's part of the standard!!) that will give me full benefit of the keys on my Ensoniq TS-10

JagPaw wrote:So I came from the Pro Tools world and am steadily and certainly being converted to the Ableton Live way of life. I checked box the workflow box because Pro Tools does unfortunately still have Ableton beat in the regular musicians' tracking studio. In the composer/producer role, Ableton Live is AWESOME! Which is why I love it. But when I'm just playing engineer and am tracking musicians vocalists, my workflow is way off. Mainly, I need virtual tracks or "playlists" to organize separate takes on a single track to be compiled later (after the musicians leave the studio). Second, it'd be really nice if there was a way to break my bus tracks off from the bus section and place them directly adjacent to audio tracks. Also, being able to group the busses and audio and midi tracks would be useful (think full drum kit w/triggered samples).

If I am mistaken and these features do already exist... SOMEONE PLEASE TELL ME HOW!

jagpaw.com

I just use the group tracks function to record several takes into one group, later I delete all that sucks on those takes, then I compile it into a new track.

JuanSOLO wrote:MIDI MAP the likes of Traktor. Like a mini Bomes built in. AND everything is mappable and value adjustable etc.

THIS!!! At least partly. What would take performances and studio workflow really to the next level would be some options to give your midi mappings additional conditions. Like in Traktor where you have modifiers and can make things happen only when modifier 1 or 2 for example are set to a specific value.
Having "only if..."-conditions for the midi commands would allow great things like Shift Buttons and super crazy mappings like for exampling triggering a third effect automatically when two other effects are triggered simultaneosly. Super dope.

+ The templates feature from the poll would be a great addition to this.

Ableton Live's huge advantage are its live performance capabilities, so we should really expand on that sector!

More than one MIDI track visible in the MIDI window, maybe using different colours for different tracks. Would make harmonising parts so much easier.

It's the one thing about other DAWs I really miss when I'm writing.

32 bit plugin support!

Cr.093 wrote:Ableton Live's huge advantage are its live performance capabilities, so we should really expand on that sector!

Two of Live's biggest disadvantages in regards to performance,
#1 parameter recall on tracks per launched clip (session view)
#2 recording automation of parameters to session view clip envelopes, wether those parameters are being bluehanded, OR midi mapped.

these 2 work together of you think about it.

If Ableton wouldn't like to include shift button/modifier functionality but would implement a new "midi-mappings can be saved as templates"-functionality anyway they could offer a kind of workaround by allowing to map the instant load of a specific mapping template on a midi button. Then you could for instance have three buttons, one giving the command to load mapping template A, one to load mapping template B and one to load mapping template C. So this would work more or less like a shift button !!

That sounds cool.

I would hope they would ALSO, make a python editor, like you would have in Maya or something.
Then you could work on remote scripts right within Live, do testing and trouble shooting.
We'd see a lot more inventive abilities with that kind of thing.