Ableton Forum

madlab wrote:Stefan, is there a way to combine those two behaviour. As I wrote earlier in this thread, when working for theater or dance rehearsals, the new behaviour can be very useful.

We would love to provide an option in the Preferences dialog for this, but there's no room left in the dialog, so we would have to re-layout things to make it fit. This is not something we can do for a 5.0.x point release, sorry.

We will probably provide a way to choose between retrigger and pause by means of a text-based option in the Options.txt file, but I'm not sure if that will be convenient enough for you.

Stefan Haller wrote: We would love to provide an option in the Preferences dialog for this, but there's no room left in the dialog, so we would have to re-layout things to make it fit. This is not something we can do for a 5.0.x point release, sorry.

please consider planning to build in plenty of more room then, this isnt the only area where giving us more optional behavior would save major frustration and headaches

.

supster wrote:

Stefan Haller wrote: We would love to provide an option in the Preferences dialog for this, but there's no room left in the dialog, so we would have to re-layout things to make it fit. This is not something we can do for a 5.0.x point release, sorry.

please consider planning to build in plenty of more room then, this isnt the only area where giving us more optional behavior would save major frustration and headaches

.

MISC Tab 2?

Stefan Haller wrote: We discussed the matter again, and we realize that most of you actually want a retrigger behaviour when starting the song, so we are going to change it back.

so... when

w

WebSite! wrote:

Stefan Haller wrote: We discussed the matter again, and we realize that most of you actually want a retrigger behaviour when starting the song, so we are going to change it back.

so... when

w

as soon as they wrap up the miracle cure-all for the arrange grid lockups and the mystery glitching sounds fix.

rumor was ... by close of business today i think ...
.

just a quick note to stefan to say thanks for actually listening. I know Abes thought you were doing the right thing, so it's nice to actually see you taking the end users thoughts seriously.

now lets all rock on people

silicon1138 wrote:just a quick note to stefan to say thanks for actually listening. I know Abes thought you were doing the right thing, so it's nice to actually see you taking the end users thoughts seriously.

asskisser!
we are mad on them about this one. remember?
play strong!

w

yeah, they got it wrong, and yes i was mad too, but get a grip and move on, and be glad this is not steinberg

Stefan Haller wrote:Sorry for not responding earlier.

We discussed the matter again, and we realize that most of you actually want a retrigger behaviour when starting the song, so we are going to change it back. We are sorry for the inconvenience.

(It's funny though that nobody ever seems to have noticed the bug in the 5.0.2 retrigger behaviour: it only worked when you started the song from 1.1.1. Try starting from 2.1.1, and see how clips start in the middle; you don't really want to have that back, do you?)

Thanx alotso for listening u guys!! And no we dOnt want to have the 5.02 bug back!

Stefan Haller wrote:Sorry for not responding earlier.

We discussed the matter again, and we realize that most of you actually want a retrigger behaviour when starting the song, so we are going to change it back. We are sorry for the inconvenience.

(It's funny though that nobody ever seems to have noticed the bug in the 5.0.2 retrigger behaviour: it only worked when you started the song from 1.1.1. Try starting from 2.1.1, and see how clips start in the middle; you don't really want to have that back, do you?)

Hi Stefan,
true that no-one seemed to notice the bug in 5.02 start behaviour, I would suggest this is an indication that the majority of users re-start from 1.1.1, so never encounter the bug.

Why I never encounter the 5.02 bug:
I use session as a scratch pad for songwriting, trying variations on themes then when I am happy I record a session to Arrangement.
Working between many patterns in session and trying alternatives means that when things sound bad I hit stop twice to reset ... and this also sets the arrangement marker to 1.1.1 . I do this unconciously and naturally when working.
Once my work is in Arrangement I do fine edits in there and don't really use session again! If I need to work out a new section I hit 'stop all clips' in session to effectively switch arrangement off, then I work exclusively in session again until I have the new section worked out. These new sections are generally dragged into arrangement to preserve the previous work.


Fixes for the 5.03 bug / behaviour

I would be happy with an options.txt fix
and hope you can supply one in the near future as I am using 5.02 for now.
as others stated, you may need a new tab in preferences for Live6 though!

Can anyone explain briefly how this works ?

Angstrom wrote:

Stefan Haller wrote:Sorry for not responding earlier.

We discussed the matter again, and we realize that most of you actually want a retrigger behaviour when starting the song, so we are going to change it back. We are sorry for the inconvenience.

(It's funny though that nobody ever seems to have noticed the bug in the 5.0.2 retrigger behaviour: it only worked when you started the song from 1.1.1. Try starting from 2.1.1, and see how clips start in the middle; you don't really want to have that back, do you?)

Hi Stefan,
true that no-one seemed to notice the bug in 5.02 start behaviour, I would suggest this is an indication that the majority of users re-start from 1.1.1, so never encounter the bug.

Why I never encounter the 5.02 bug:
I use session as a scratch pad for songwriting, trying variations on themes then when I am happy I record a session to Arrangement.
Working between many patterns in session and trying alternatives means that when things sound bad I hit stop twice to reset ... and this also sets the arrangement marker to 1.1.1 . I do this unconciously and naturally when working.
Once my work is in Arrangement I do fine edits in there and don't really use session again! If I need to work out a new section I hit 'stop all clips' in session to effectively switch arrangement off, then I work exclusively in session again until I have the new section worked out. These new sections are generally dragged into arrangement to preserve the previous work.


Fixes for the 5.03 bug / behaviour

I would be happy with an options.txt fix
and hope you can supply one in the near future as I am using 5.02 for now.
as others stated, you may need a new tab in preferences for Live6 though!

I did, but I thought I was too simple to understand what had come of the original ominous ornage dot. Apparently I was right, but too simple, still to follow hang with what was going on.

yes I agree that the new behaviour could still be useful (in some cases) as well.

couldn't you just a have a keyboard key used as a modifier..

i.e.: modifier+spacebar

that would avoid having to put it in preferences

I guess the reason I didn't notice the also strange behaviour in 5.0.2 is because the arrange start marker is always set to 1.1.1 for me when I'm jamming in session view

Stefan Haller wrote:

madlab wrote:Stefan, is there a way to combine those two behaviour. As I wrote earlier in this thread, when working for theater or dance rehearsals, the new behaviour can be very useful.

We would love to provide an option in the Preferences dialog for this, but there's no room left in the dialog, so we would have to re-layout things to make it fit. This is not something we can do for a 5.0.x point release, sorry.

We will probably provide a way to choose between retrigger and pause by means of a text-based option in the Options.txt file, but I'm not sure if that will be convenient enough for you.

Hi Stefan, did you read my suggestion about having this option enabled in the clip properties. Under the "Groove" dropdown you can add a button which would choose whether or not the clip follows the new global timing. This would at least make best use of a bad situation and allow a clip by clip basis usage of the new function, thus extending its functionality.

sweetjesus wrote:Hi Stefan, did you read my suggestion about having this option enabled in the clip properties. Under the "Groove" dropdown you can add a button which would choose whether or not the clip follows the new global timing. This would at least make best use of a bad situation and allow a clip by clip basis usage of the new function, thus extending its functionality.

Holy crap ! Sweetjesus always makes sense !