Page 1 of 1
is it a bug or a removed feature.
Posted: Tue Jan 03, 2006 4:39 pm
by smog g
i think ive discovered a bug in the latest version (live 5.3.x) .
usualy when i doubleclick on the stop switch in the transport panel, all clips in the set are resetted to their startpoint.
this is not the case in the new version. after stoping the set, the clips start at the point, where they were stopped.
what can i do to fix this?
just to mention. the little stop switch in the master track console (where the crossfader is) works great...
Posted: Tue Jan 03, 2006 5:22 pm
by mosca
its a bug and a major pain in the arse
i get it too
mo
Posted: Tue Jan 03, 2006 5:33 pm
by madlab
5.03 alright for me on mac but already happened to me with a previous 5.x version.
Posted: Tue Jan 03, 2006 6:10 pm
by oddtones001
A major pain in my ass as well......
Posted: Tue Jan 03, 2006 10:24 pm
by timothyallan
Ahh, I thought it was only me who found this to be awful. Especially if you have 16 bar clips with chord progressions that only sound good if they are started in sync...
tim
Posted: Tue Jan 03, 2006 11:54 pm
by Alex
Hi folks,
this is also posted in this thread:
http://www.ableton.com/forum/viewtopic.php?t=31545
madlab,
does it really happens for you in a previous Live 5 version?
regards,
/Alex
Posted: Wed Jan 04, 2006 9:30 am
by madlab
Yes, it happened to me once or twice with version 5.0 or 5.02 I think. Tried it again yesterday but it works ok with 5.03.
Posted: Thu Jan 05, 2006 8:00 am
by madlab
Alex wrote:Hi folks,madlab,
does it really happens for you in a previous Live 5 version?
regards,
/Alex
Happened to me yesterday in 5.03 with a midi clip sent to Kontakt 1.5.
1 midi track holding stylus RMX + 5 midi tracks sent to Stylus 2-6 + 2 midi tracks sent to two instruments in Kontakt. The clip on the track holding Ktkt doesn't start anymore at the beginning except if you fire the clips from the scene button.
Posted: Thu Jan 05, 2006 8:14 am
by Machinate
madlab wrote:
Yes, it happened to me once or twice with version 5.0 or 5.02 I think. Tried it again yesterday but it works ok with 5.03.
there are some specific things you need to do to experience the bug. Try this:
- start a two bar clip.
- Retrigger it (with play button on clip) before the second bar.
- Stop it.
- Hit play again, the clip should start from 2.1.1, even though the arrangement position and start marker both read 1.1.1 .
Retriggering again with the play arrow on the clip does not solve the problem, but retriggering with the clip button works.
As far as I know this appeared briefly in the 5.0 betas, disappeared, then reappeared for 5.03.
Posted: Thu Jan 05, 2006 8:35 am
by funk313
i have the same shit going on when for instance recording say a midi clip..
it just starts from an akward position ie not from the startmarker as it used to do.
therefore i have to stop all my clips and then hit the play button on the specific
clip to make it sync to the other clips.. its an arse. and did not appear in 5.02..
Posted: Thu Jan 05, 2006 6:09 pm
by kennerb
I posted this on the other discussion about this. I know they say it is as designed but it has affected my workflow greatly. I am constantly having to stop and start clips to get them to realign. This defies my logic at least. If this is how the abes want it then please give me the option to not use it.
Posted: Thu Jan 05, 2006 6:17 pm
by Machinate
Posted: Fri Jan 06, 2006 12:50 pm
by smog g
a little help is this: when i record a midi clip, i set the feature "record, when trigger clips" in the preferences menu on. then i click on the play button on the master track console linking to the session where the clip shall be recorded. then all clips in this line will start properly