Warping as a case of Live´s work flow/interface difficulties
I´ve used Live for a couple of years but still I´m
not quite a sure about the basic logig of the Warping
from the USER WORK FLOW point of view.
Of course I´ve used warping several times and know basicly all technical points mentioned in the user manual.
But what the developer in their interfaces and manuals often
misses, is the very pragmatic user work flow point of view,
manuals are based on the chapters and separate index words
and often don´t give enough information HOW and WHY, or all
this is anyway very hard to find, if you don´t have to time search different sources,
send mails and notes and view tutorials (or try and make errors ),
In the case of Warping, lets take the very basic workflow case:
I open an audio file and bring it to the Live´s audiotrack. The very moment
the Lives Clip View shows me Warp-button active (yellow).
Why? I haven´t warped the file (or intented to do so), as a
user I´m now uncertain if the Live has something to my file
when I brought it inside the Live, because the Warp is active
(or does the activated Warp button mean that it is active at all?).
Why the Warp is active as default - or has anything done to my file yet
(although the Warp is active in the clip view)?
Can someone in very detailed way to clarify what is the logic from the work flow
point of view in the Warping: 1) what happens automatically (with the basic Live defaults) when I bring an audiofile to the Live, if anything? 2) why is the Warp button active as a default? - or how the "active" is shown in the Live, 3) when is the Warping really executed?
BTW, same kind of (in my mind) inconsistencies/difficulties to be sure what happens and why, which generates the uncorfotable feeling that the user is not quite sure about the Live´s work flow, is the Live full of: let´s take an other example, namely rendering the audio file.
If I want to render (or Export accrding to Lives terminology) the MONO audiofile, Live gives me the Audio rendering options window where one parameter is: Convert to Mono, the Live´s factory default in this field is "No". Well, according to the intuitive and logical user workflow the user most likely thinks "I don´t want to convert my mono file to mono, because there´s no sense to conver somehing to one it already is". But after the operation the user is surprised: the exported mono file IS CONVERTED TO STEREO. Why? What is the Ableton logic here? I think Ableton should change the user interface/labels here that the work flow would be logical. (Of course the user after a couple of trials and errors learn the Lives "originalities" very soon and here always convert the mono file to mono file is he want´s to keep it in mono, but the risk in this kind of inconsistencies is that in a new situation the user can´t be sure if the interface is intuitive and logical or what he really should do to get the desired result.
You need to be logged in, have a Live license, and have a username set in your account to be able to answer questions.
Give us your feedback.