Beta of upcoming bug fix update available: Live 5.0.3b4!
no fix for tracks randomly unfreezing themselves in 5.0.2?
http://www.thesoundofyoungamerica.com
http://www.myspace.com/soundofyoungamerica
MacBook Pro, guitars, Live Suite 8.2, launchpad, iphone
http://www.myspace.com/soundofyoungamerica
MacBook Pro, guitars, Live Suite 8.2, launchpad, iphone
Hi Alex,
I'm not sure whether I'm currently working on any sets where this happens but in some 5.0.2 sets in the past I've frozen a track to save processor, normally with a guitar rig or operator on it, then after some more work on the set the track will unfreeze and start eating up my processor again. I haven't reported this before but thought I'd read of another user experiencing the same.
Thanks
I'm not sure whether I'm currently working on any sets where this happens but in some 5.0.2 sets in the past I've frozen a track to save processor, normally with a guitar rig or operator on it, then after some more work on the set the track will unfreeze and start eating up my processor again. I haven't reported this before but thought I'd read of another user experiencing the same.
Thanks
http://www.thesoundofyoungamerica.com
http://www.myspace.com/soundofyoungamerica
MacBook Pro, guitars, Live Suite 8.2, launchpad, iphone
http://www.myspace.com/soundofyoungamerica
MacBook Pro, guitars, Live Suite 8.2, launchpad, iphone
-
- Posts: 2
- Joined: Mon Dec 05, 2005 3:23 pm
Alex-
Thanks for your quick responses to all the ?'s on the 5.0.3b4 beta. Unfortunately, I am not a registered user (yet)- I'm still waiting to see if Ableton will implement more of the changes users have suggested regarding MIDI mapping certain controls.
For example, the "Select on Track" issue that was partially fixed in 5.0.2 (if the Clip View loses focus due to volume slider, etc, the clip is not selected) as well as being able to select a clip without launching it. Were these issues addressed in 5.0.3b4?
The other popular request was the ability to map the "del" key to a MIDI or key command. Has this been taken care of?
Thanks a lot!
Matt, Boston, MA
Thanks for your quick responses to all the ?'s on the 5.0.3b4 beta. Unfortunately, I am not a registered user (yet)- I'm still waiting to see if Ableton will implement more of the changes users have suggested regarding MIDI mapping certain controls.
For example, the "Select on Track" issue that was partially fixed in 5.0.2 (if the Clip View loses focus due to volume slider, etc, the clip is not selected) as well as being able to select a clip without launching it. Were these issues addressed in 5.0.3b4?
The other popular request was the ability to map the "del" key to a MIDI or key command. Has this been taken care of?
Thanks a lot!
Matt, Boston, MA
Last edited by mgoulet666 on Wed Dec 07, 2005 4:55 pm, edited 1 time in total.
you know what, i experienced this too a few time with 5.02, but i though i was imagining things. i rarely freeze so i never paid much attention. i'll re-test again with 5.02 and the beta...sidownes wrote:Hi Alex,
I'm not sure whether I'm currently working on any sets where this happens but in some 5.0.2 sets in the past I've frozen a track to save processor, normally with a guitar rig or operator on it, then after some more work on the set the track will unfreeze and start eating up my processor again. I haven't reported this before but thought I'd read of another user experiencing the same.
Thanks
Just a quick note to say thanks to the Abe's for all their hard work on this...
Just installed 5.0.3b4 and noticing major performance gains - even at the lower latencies. I've just run a 42 channel mix (with eq, fx & unfrozen VSTi's) that in 5.0.2 would just fall over, successfully for the first time in any v5.x. at a 128 buffer. Memory and even softsynth performance also seems improved with far less crackling and glitching. Haven't had a chance to really batter the MIDI timing, and a few other issues, as yet but just for the above improvements alone would like to extend my thanks.
Just installed 5.0.3b4 and noticing major performance gains - even at the lower latencies. I've just run a 42 channel mix (with eq, fx & unfrozen VSTi's) that in 5.0.2 would just fall over, successfully for the first time in any v5.x. at a 128 buffer. Memory and even softsynth performance also seems improved with far less crackling and glitching. Haven't had a chance to really batter the MIDI timing, and a few other issues, as yet but just for the above improvements alone would like to extend my thanks.
Excellent - very encouraging to read this thread.
I'm at work currently however I'm looking forward to applying this patch this evening.
Thank you Abletons.
Cheers
I'm at work currently however I'm looking forward to applying this patch this evening.
Thank you Abletons.
Cheers
JaseFOS
-Live10.1 |Push2|Maschinemk2|KeyLab61|LaunchPad|MCUpro|MCExt|MCExt|iPad2|TouchABLE2
-Mac Pro 5.1 (dual hex core Xeon 3.46gHz, 28Gb RAM) running MacOS 10.13.6
-Universal Audio Apollo Quad (firewire)
-SHITLOADS OF HARDWARE SYNTHS
-Live10.1 |Push2|Maschinemk2|KeyLab61|LaunchPad|MCUpro|MCExt|MCExt|iPad2|TouchABLE2
-Mac Pro 5.1 (dual hex core Xeon 3.46gHz, 28Gb RAM) running MacOS 10.13.6
-Universal Audio Apollo Quad (firewire)
-SHITLOADS OF HARDWARE SYNTHS
-
- Posts: 7251
- Joined: Thu Sep 29, 2005 8:34 am
- Contact:
yeah apparently we had been using it incorrectly due to some inconsistencies and now when we bring these songs into 5.0.3 the follow actions don't do what they used to cause now they are "fixed" which is frustrating but I think I understand that we used to be using it wrong because they used to not work right and now they work right so the using wrong doesn't sound right? if that makes sense.
It was as if someone shook up a 6 foot can of blood soda and suddenly popped the top.
-
- Posts: 7251
- Joined: Thu Sep 29, 2005 8:34 am
- Contact:
Hi Johnisfaster,
And you should get a copyright for this sentence too
regards,
/Alex
...........yes, I guess.yeah apparently we had been using it incorrectly due to some inconsistencies and now when we bring these songs into 5.0.3 the follow actions don't do what they used to cause now they are "fixed" which is frustrating but I think I understand that we used to be using it wrong because they used to not work right and now they work right so the using wrong doesn't sound right?
And you should get a copyright for this sentence too
regards,
/Alex
-
- Posts: 760
- Joined: Wed Oct 01, 2003 4:51 am
-
- Posts: 7251
- Joined: Thu Sep 29, 2005 8:34 am
- Contact:
Voted "technical sentence of the month"Johnisfaster wrote:yeah apparently we had been using it incorrectly due to some inconsistencies and now when we bring these songs into 5.0.3 the follow actions don't do what they used to cause now they are "fixed" which is frustrating but I think I understand that we used to be using it wrong because they used to not work right and now they work right so the using wrong doesn't sound right? if that makes sense.
Vey excited we're heading for 5.03! Will install the Beta this afternoon & have a good tweak....