All the little detail problems with Ableton Live Collection

[Dr. Fluffenstein]

012
And speaking of zooming, why is there still no mouse scroll wheel zooming after 8 major versions, and almost a decade of updates.

+9999999999999999

[3phase]

013

there is a nasty prohibition that excludes controlers assigned for remote functions from being recordable in midi clips..

is there a good reason why? you see, there are fancy flagship keyboards out there that can act as controlers while adjusting internal parameters in the same time..

so the user just might want to open the filter on his/her internal keyboard, ad record that move into a midi clip while simultaniously open an fx send in ableton live..

This is not possible...

why?

without a good reason, i actually like to know, please remove that useless limitation..

[3phase]

014

no vertical zoom in arrange..

makes working a bit dreadfull.. could be at least an auto expand function on the selcted track.or/And a expand/collapse all...

in any case an area that could get a little prortion of the elsewise nice zoom functionality in live...

[3phase]

015

the general zoom of L8 is nice.. but there should be a seperated setting for the browser.

While the program stays good operatebale even in the 60% zoomrange any readybility in the browser is long gone..

this also could be done in an automated fashion.. so that the browser only shrinks to a certain point or switches to an extra font from a certain zoomstage.

[Digital_Damage]

yaaaaaaah another crying thread...

[3phase]

016

colourchemes... the ones in live are pretty dreadfull.. there are editors out there.. but they have to fight with certain limitaions that actualy request changes in the program...

the selcted clip needs to be highlighted much better..maybe with an extra frame as we have it for the selected controler area...

the browser section should have extra colourfields / font colour choices...


while dark colour chemes can be beneficial on stage the browser just gets unreadable.. so having the browser as somthing much brighter popping up when needed would be beneficial

nothing very important... but belongs in the detail list never the less because its one of the issues that get on you nerves again and again over the years..

[3phase]

yaaaaaaah another crying thread...

shut up fanboy and play with your poo..

its a constructiv list about issues that get on your nerves when working with live..

all the little ones that only pop up in your mind when you come alog them ..but usually you thik they are to little to even place a wish on the wishlists.

But its theese littkle anoymemts that build up over the years to a bad user experiance..

see the thread as a user survey what people think could be done better..

a survey the proud little company ableton never would do because they allways know better what is good for us.

sometimes they do..sometimes they dont.. in any case they are to stressed out to take care about basic and very much needed sync issues..

how can they keep track of the details?

however.. when you fix or change one thing in the program you just might optimize a detail in the same region with it..

so its good to list the shortcomings and get rid of them one after the other instead buildig up more ad more of the little drawbacks in any version...

and because there are differemt workflows out there its sometimes not easy to realize something as a shortcoming that is not in your way.. i only can list the thigs that are getting in my way... and because i dont like to open a thread for any little shit, one thread to concentrate them all is usefull..

so shut up and keep it clean..


ther is no little thing that gets on your nerves when workig with ableton live? really nothing?
come on.. you cant have such a primitiv mode of working..please share

and dont forget to nummber the issue

[3phase]

017

Lives HiQ setting for the SR algorythm is useless.. or better.. the low quality one is useless..

a redundant setting..

the high q dont eats up more resources really but sounds much better.. while the low q dont is bad enough to qualify as fx and dont saves anything anyway.. ..


actually the low q we have now is the high q of former live versions..while the old low q, that was so bad that it was sometimes nice again, got abadoned...


so we are not backward compatible in the actual state and dont win anything... just redundant controls on the screen and preff tabs.


so..

by getting totally rid of the actual low q setting that is in all regards useless..

either

1) bring back the old low q.. it safes really some calulation power and sounds so hasrh that it actually changes the position of a sound in a mix..so can be seen as fx...

2) get rid of this hi/lo thing totaly and safe screen space and pref tabs for something more usefull


3) have the actual hi Q mode the standard.. and add a real HI Q one for demanding situations..


in any case the actual state is useless..

is anybody not using HiQ all the time?

[Digital_Damage]

yaaaaaaah another crying thread...

shut up fanboy and play with your poo..

its a constructiv list about issues that get on your nerves when working with live..

all the little ones that only pop up in your mind when you come alog them ..but usually you thik they are to little to even place a wish on the wishlists.

But its theese littkle anoymemts that build up over the years to a bad user experiance..

see the thread as a user survey what people think could be done better..

a survey the proud little company ableton never would do because they allways know better what is good for us.

sometimes they do..sometimes they dont.. in any case they are to stressed out to take care about basic and very much needed sync issues..

how can they keep track of the details?

however.. when you fix or change one thing in the program you just might optimize a detail in the same region with it..

so its good to list the shortcomings and get rid of them one after the other instead buildig up more ad more of the little drawbacks in any version...

and because there are differemt workflows out there its sometimes not easy to realize something as a shortcoming that is not in your way.. i only can list the thigs that are getting in my way... and because i dont lie to open a thread for any little shit one thread to concentrate them all is usefull..

so shut up and keep it clean..


ther is no little thing that gets on your neves when workig with ableton live? really nothig?
come on.. you cant have such a primitiv mode of working..please share

and dont forget to nummber the issue

bla bla bla

[3phase]

018

inserting instruments or fx sometimes dont works when there is no clip selectetd in a track..

work around is to allways insert fx in the tiny titel bar, and not in the huge free field uderneath the session grid...

but.. actually it would be nice if the program would switch automatically when the user takes the effort to move a device to that big free field underneath... its pretty obvious what the user might want to achive and ther is no need to protect him from the possebily bad results of his evil doings.


i dont know how many minutes it has created over the years to run into this trap.. but i am doing it again ..and again and again..

might be one hour allready.. what would say that it went 3600 times wrong
Arteficial intelligence would be nice sometimes..

In general pseudo failor protection routines get in the way of user workflows... ther is no guitar out theire with protection algorythms to prevent you touching the strings with wet hands.. so why we need such things on a daw with undo functionality?
We get a double do functionalty this way as we find in many corners of ableton live..

[3phase]

019


one for the dedicated controlers...

the lunchpad.. the really nice fader mode..


but..

why this fader mode jsut jumps in a linear scale as no other fader in the world is doing?

and why are there the first 2 buttons needed for the lowest value?


this could be done much better..even with inbetween steps when touching 2 buttons simultaniously...

I went a bit more into detail in the wishlist.. but this is just one example of a half baked implementation.. or again a brilliant idea not worked out..

why not investing 2-3 hours more coding time to make this lunchpad fader double resolution..2 steps more and getting finer stepped in the upper range? and much more usefull this way...

6 db steps are a lot in the upper range..that is doubling the volume..

ok.. i forget about this.. i could fill 10 points just with the lunchpad implemetation..
actually a brilliant example of ableton style.. brilliant initial ideas..crippled by too limited development times..

actualy a design crime on controlers where people learn the moves and later changes get difficult this way...

however maybe usefull to list the bad details of dedicated controler implementation here aswell..
At least we easily get to 999 this way

anybody in berlin like to buy my lunchpad? never used on stage..it turned out to be too huge for that...
( i use too much other hardware to spare the space, it just dont fits on any keyboard or space inbetween the drummachines you usually have on stage..)

[zee verkawound]

Thanks for the constructive thread 3phase. For me, the #1 attribute missing from Live is what prevents it from being a "true daw of choice", no 64bit. These days, that's about as basic as it gets. We can call it 020 or whatever, but I can't think of any greater short coming Live has to date.

[davepermen]

Thanks for the constructive thread 3phase. For me, the #1 attribute missing from Live is what prevents it from being a "true daw of choice", no 64bit. These days, that's about as basic as it gets. We can call it 020 or whatever, but I can't think of any greater short coming Live has to date.

"as basic as it gets". well, not for developers, there it's really hard work. but i can guarantee you it's allready in the works. there are 64bit binaries of all live instruments in my folder. it's on its way. but it takes a lot of time to do it.

[3phase]

Thanks for the constructive thread 3phase. For me, the #1 attribute missing from Live is what prevents it from being a "true daw of choice", no 64bit. These days, that's about as basic as it gets. We can call it 020 or whatever, but I can't think of any greater short coming Live has to date.

"as basic as it gets". well, not for developers, there it's really hard work. but i can guarantee you it's allready in the works. there are 64bit binaries of all live instruments in my folder. it's on its way. but it takes a lot of time to do it.

true.. and its defently not a detail they will oversee.. rather the shiny new feature department.. you will see 64 bit support soon.

this thread is ment for the little things or maybe even bigger things that interfear with user workflows.

lets call it a design optimisation studie.. if someone cant read the labelings of a certain plug in i would think its worth to mention. in the end quality shows in the details..and ableton is aiming for quality..or?

[davepermen]

and ableton is aiming for quality..or?

and you always are aiming to such statements..or?



you should try a blog. abletonfail.blogger.com or something. or how about twitter? post every annoying thing you find there to the whole world.

the abletonians have blocked you in here anyways, they don't read your stuff anymore. you want to get it out to the masses.