All the little detail problems with Ableton Live Collection

[3phase]

190

life misses a note off handling on clip end.. its easy to produce hangig notes. the clip end should silence the last notes of the sequence when they overlap..

[andydes]

190

life misses a note off handling on clip end.. its easy to produce hangig notes. the clip end should silence the last notes of the sequence when they overlap..

Disagree on this one. It can be quite useful to have the end of the note outside the clip end. I admit it's also easy to do accidentally when nudging notes around at the end of a phrase though.

Not really been any discussion on the points you've raised except for some people slagging you off. I think you've maybe raised too many to take onboard.

[3phase]

190

life misses a note off handling on clip end.. its easy to produce hangig notes. the clip end should silence the last notes of the sequence when they overlap..

Disagree on this one. It can be quite useful to have the end of the note outside the clip end. I admit it's also easy to do accidentally when nudging notes around at the end of a phrase though.

Not really been any discussion on the points you've raised except for some people slagging you off. I think you've maybe raised too many to take onboard.

ok..but than we defently need an all notes off comand..you cant allow the program to create hanging notes as a feature without giving a way to handle the situation..stopping the sequencer is a too minimal aproach.we maybe dont like to stop it on stage for example..

[3phase]

191

one i allways forget but still gets in my way when using midi...

Live has no midi delay parameter or tool plug.. The track delay cant be used for that because you interfear with the latency compensation when changing it.. and doing it in the midi editor only works the selcted clip ..not the track..

age old midi sequencer functionality and so very handy and really nothing one wants to buy max for life for..

in ideal transpose and delay would be clip parameters.. and track plug ins..

[742617000027]

190

life misses a note off handling on clip end.. its easy to produce hangig notes. the clip end should silence the last notes of the sequence when they overlap..

Not sure if I got you right on this one. Is it about the possibilty to let notes of a midi-loop-clip cross the end of that clip to be continuously played when the loop starts over? Let's say you have a one bar midi loop, triggering a half note on the 4 and want it to keep playing for the duration of it's note value (i.e. until the 2 of the new bar). In order to achieve that, as I see it, you have to move around the midi clip in the arrangement, tweaking it's placement and the placement of the note within the clip to your needs.


Also, if not stated before:

192
Let Beat Repeat's "Offset" parameter adjust dynamically to the "Interval" parameter. By now, when using an "Interval" higher than 1 bar, the "Offset" can only move around the effect within the first bar - you have to automate Device on/off to have the effect every 2nd or 4th bar.

192
Again Beat Repeat. Is there a reason the repetitions can only be pitched down, not up?

193
And again. The "Decay" parameter should also work as a "Swell", making the repetitions louder over time.

[742617000027]

Again, I hope these weren't mentioned before, didn't read through the whole thread. Sorry, if they are duplicates.

194
Only noticed that for the built-in Synth Strings "Concert Strings" preset up to now: at a random point, the preset will sound very differently to what you adjusted the sound to before. It helps twisting the "Intensity" parameter a bit (and then set it back to where it was), the preset will sound as intended again, at least for a while. This also affects the audio rendering when not taken care of.

195
Editing the pitch envelope of a midi clip sometimes results in extremely annoying glitches with the overall pitch of the specific track. This also affects audio rendering and can completely mess up a mix down. Didn't figure out a way to avoid this yet. To get it back to normal you have to play around with the pitch envelopes a bit. Yet waiting has been found to be most effective on this. At a random point it'll be back to normal.

[742617000027]

196
Lacking ability to drag and drop samples within Impulse and from Impulse to somewhere else.

[hoffman2k]

Again, I hope these weren't mentioned before, didn't read through the whole thread. Sorry, if they are duplicates.

194
Only noticed that for the built-in Synth Strings "Concert Strings" preset up to now: at a random point, the preset will sound very differently to what you adjusted the sound to before. It helps twisting the "Intensity" parameter a bit (and then set it back to where it was), the preset will sound as intended again, at least for a while. This also affects the audio rendering when not taken care of.

Could that be the Macro bug that got fixed in 8.2.2, where things controlled by a Macro could produce incorrect sounding results?

Fixed a problem with nested Macro mappings when the range of a mapped ON/OFF switch, or of a selector switch (such as a filter type switch), is not at default values. In such a case, the right value would be displayed, but the wrong value would be used internally.

Note: with this fix, you will now hear what you see, although this may mean that previously saved Sets that contained the bug may sound different.

[3phase]

As far i can say your points wasnt mentioned here before.. I defenetly see the point with the beat repeat pitch down/pitch up..that also is something i missed often an ther was something else about beatrepeat that got in my way i cant remeber wright now..

anyway..one thing.. ands i might be wrong here but dont see a workaround yet..

197

on third party plugs you find often the ability to assign fixed controlers.. what is very handy.. because than you have a fixed controler assignment that works as soon you open the plug independet from your projekt file..
With live you only can use that function when having midi inputmonitoring on the plug ins track on.. but than the plug dont recieves midi information from its midi clips anymore..so you have control but no sound.. is there a workaroundelton? probably...
maybe not.. in any case i dont see why a plug couldnt have access to a dedicated controler port and its midi track simultaniously..the auto setting should take care of that...

As mentioned early the whole input midi thru cheme in ableton live is highly inferior and quirky in comparison to other daw´s...
Probably because the midi was added later and stiched with the hot needle ableton style..

So when you dont do it wright from the start you have to do it twice..

I would say the whole midi input cheme needs to be redesigned towards latency free midi thru.. more flexibility and internal controler support of plugins..or the program will stay inferior against other midi capabel daw´s forever...


198

maybe mentioned before and related to the one above.. how to deal with complex controler assignements when combining projekts or just having live devices or 3rd party plug ins under heavy controler assignements.?
like 30 controls for one drummachine emulation alone for example..

i heard rumors that there are some possibilitys with scripts..but there seems to be no official documentation about that..

And.. for such a scenario the program should offer some on screen functionality..like we have it in logics enviroment for example where it was possible from logic 1 on to safe and reload parts of the enviroment independent form the song/projekt file..

especially with all the macro stuff live offers such a functionality is needed somehow..its getting more and more complex.. so nothing you want to set again and again..

for me a real workflow killer because i often go back to older projekt files and loose all controler support than..

[742617000027]

Could that be the Macro bug that got fixed in 8.2.2, where things controlled by a Macro could produce incorrect sounding results?

Doesn't seem so, updated Ableton yesterday and the bug still occurs. However, I found that all notes are played correctly sounding the very first time after opening a Live Set and as soon as they are played again, the sound changes. That is velocity independent, just has to do with the pitch of a note (e.g. a D' is played correctly the 1st time, the 2nd time a D' is played in the track it sounds as if I changed something on the macros - which I of course didn't). Maybe that's what is ment by "this may mean that previously saved Sets that contained the bug may sound different."

[hoffman2k]

My apologies for the people with issues. Been waiting like 140 entries for this joke

[hoffman2k]

Could that be the Macro bug that got fixed in 8.2.2, where things controlled by a Macro could produce incorrect sounding results?

Doesn't seem so, updated Ableton yesterday and the bug still occurs. However, I found that all notes are played correctly sounding the very first time after opening a Live Set and as soon as they are played again, the sound changes. That is velocity independent, just has to do with the pitch of a note (e.g. a D' is played correctly the 1st time, the 2nd time a D' is played in the track it sounds as if I changed something on the macros - which I of course didn't). Maybe that's what is ment by "this may mean that previously saved Sets that contained the bug may sound different."

If you can get it to behave unexpected quickly, use the "Get Support" entry from the help menu.
This creates a playback script and some logs on what Live currently is doing.
This option got introduced a few updates ago and it really helps to nail down these weird bugs that don't actually crash Live.

[3phase]

My apologies for the people with issues. Been waiting like 140 entries for this joke

and where is your entry 199?

you have a detail problem with this software aswell, dont you?

dont be shy..nobody would think you are no good fan no more if you mention a detail problem..

[hoffman2k]

199 A live.remote~ mapped to the song tempo using selected_parameter looks like it is controlling the tempo. But the tempo isn't altered and doesn't match the tempo that is displayed.

There you go
Sorry, I don't have much more to add at the moment. Bonjour crashes Live, but that is being worked on by the 3rd party providing that OSC support.
Everything else I reported got fixed with 8.2.2
There are still bugs left, but none that I encounter with my current workflow.
The big ones like improved PDC are probably for an overhaul of Live.
My detail problems were largely with MFL. I'm controlling Live mostly with other devices, so the only thing I'm really missing is even more API access.

You should really get MFL. How much worse do you really expect it to be than your overall Live 8 journey?

[3phase]

199 A live.remote~ mapped to the song tempo using selected_parameter looks like it is controlling the tempo. But the tempo isn't altered and doesn't match the tempo that is displayed.

There you go
Sorry, I don't have much more to add at the moment. Bonjour crashes Live, but that is being worked on by the 3rd party providing that OSC support.
Everything else I reported got fixed with 8.2.2
There are still bugs left, but none that I encounter with my current workflow.
The big ones like improved PDC are probably for an overhaul of Live.
My detail problems were largely with MFL. I'm controlling Live mostly with other devices, so the only thing I'm really missing is even more API access.

You should really get MFL. How much worse do you really expect it to be than your overall Live 8 journey?

As worse? half worse would be allready enough for me to give up my studio... so i wont invest a penny in more trouble..
have you read the list of all the mfl related bugs? sounds like fun

But back to the topic here.. thanks for the entry,.

Just want to mention that the thread its not about bugs..even when the one or other detail problem might lead to a hidden small bug..

Its rather about comfort that suffers from not ideal or missing detail implementations.. the little stuff you forget 5 minutes after you made your workaroundelton.. but also structural things you got used too but that are annoying nevertheless.. when they show up again and again and eat theire 5 seconds.

All this little things have a synergy effect for the user that builds up over time and leads to a suffering user experiance..

This thread is ment to create a synergy fx in the other direction by naming them all in one thread so giving them some wight they never would have when mentioned single... so a few hundred small problems are equal to one big problem.

and when at least some of them gets adressed live will be a better program..

you see.. even lives sync problems was wiped under the carpet by ableton because they are not worse than others..
but is that allready good? or good enough for a 21th century pro daw? no.its not..

you are either in sync..or you wobble around.. And live is a software in special demand for syncabilitys and they have made obvious mistakes in the implentation what became only audibkle when the os midisupport of apple finaly became tight.. so the excuse that the computer os is the reason for the fluctuations dont holds anymore..

that only as example that there are no half good solutions for a daw. quality shows in the details.