is it a bug or a removed feature.
is it a bug or a removed feature.
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...
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...
5.03 alright for me on mac but already happened to me with a previous 5.x version.
Aboard from V. 1
MBP M1 Pro 2021 - 16 Go RAM - OSX 15.7.7 / MBP 2.5 Ghz I7 16 Go SSD OSX 10.15.7 - iPad + Knobbler
RME FF UC Live 12.4.2 M4L Max 9.14
Band : https://elastocat.org/
Madlab sound unit / objects, guitar, electronics / end_of_transmission
MBP M1 Pro 2021 - 16 Go RAM - OSX 15.7.7 / MBP 2.5 Ghz I7 16 Go SSD OSX 10.15.7 - iPad + Knobbler
RME FF UC Live 12.4.2 M4L Max 9.14
Band : https://elastocat.org/
Madlab sound unit / objects, guitar, electronics / end_of_transmission
-
oddtones001
- Posts: 43
- Joined: Sun Jul 25, 2004 6:44 pm
- Location: Chesapeake, Virginia USA
-
timothyallan
- Posts: 5788
- Joined: Wed Nov 24, 2004 11:05 pm
- Location: Melbourne Australia
- Contact:
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
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
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.Alex wrote: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
Aboard from V. 1
MBP M1 Pro 2021 - 16 Go RAM - OSX 15.7.7 / MBP 2.5 Ghz I7 16 Go SSD OSX 10.15.7 - iPad + Knobbler
RME FF UC Live 12.4.2 M4L Max 9.14
Band : https://elastocat.org/
Madlab sound unit / objects, guitar, electronics / end_of_transmission
MBP M1 Pro 2021 - 16 Go RAM - OSX 15.7.7 / MBP 2.5 Ghz I7 16 Go SSD OSX 10.15.7 - iPad + Knobbler
RME FF UC Live 12.4.2 M4L Max 9.14
Band : https://elastocat.org/
Madlab sound unit / objects, guitar, electronics / end_of_transmission
Happened to me yesterday in 5.03 with a midi clip sent to Kontakt 1.5.Alex wrote:Hi folks,madlab,
does it really happens for you in a previous Live 5 version?
regards,
/Alex
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.
Aboard from V. 1
MBP M1 Pro 2021 - 16 Go RAM - OSX 15.7.7 / MBP 2.5 Ghz I7 16 Go SSD OSX 10.15.7 - iPad + Knobbler
RME FF UC Live 12.4.2 M4L Max 9.14
Band : https://elastocat.org/
Madlab sound unit / objects, guitar, electronics / end_of_transmission
MBP M1 Pro 2021 - 16 Go RAM - OSX 15.7.7 / MBP 2.5 Ghz I7 16 Go SSD OSX 10.15.7 - iPad + Knobbler
RME FF UC Live 12.4.2 M4L Max 9.14
Band : https://elastocat.org/
Madlab sound unit / objects, guitar, electronics / end_of_transmission
there are some specific things you need to do to experience the bug. Try this: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.Alex wrote: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
As far as I know this appeared briefly in the 5.0 betas, disappeared, then reappeared for 5.03.- 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.
mbp 2.66, osx 10.6.8, 8GB ram.
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..
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..
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.
3ghz Pentium 4 (Prescott), XP Sp2, 1gig Ram, Dual Monitor with Matrox Millenium, MOTU Traveler, Event EZ8 Adat card. Also IBM THinkpad t40 1.6 1 gig ram