Yes I have encounter some wierd problems with midi controller assignments developing a mind of their own, and some crackling audio playback using beat repeat...I have been to scared to use freeze again and I think I will just wait for a fix...envyro wrote:hi arar,arar wrote:Hmm, "freeze" is incredibly slow, but have not had other problems yet..
there are other problems with freeze, for example, when saving self contained set's with frozen tracks, the frozen audios just dissappear, from both live sets, the original and the selfcontained one, if u try to load the live set without these audios lots of crackles appear, there are some post's regarding this problem in the forum
lots of problems arise when you begin to use L5.01 intensively
L5, the worlds most developed & stable program...
I had to reorganize all my Sampletank2 banks and convert them into Kontakt format because of Live5's unstability with Sampletank2 and many unfinished projects.
Music is my job and if I am not able to make project in time I have no money for everydays live.
So today I use cracked Kontakt instaed of purchased Sampletank2...and I think about another cracked host instead of purchased Live 5...
why?
I have no time to wait for...I must earn
Music is my job and if I am not able to make project in time I have no money for everydays live.
So today I use cracked Kontakt instaed of purchased Sampletank2...and I think about another cracked host instead of purchased Live 5...
why?
I have no time to wait for...I must earn
Can't help wondering... have all those having these huge unsurmountable problems actually reported them directly to Ableton, instead of venting in this forum? That would probably be the best way to get them actually fixed.
And if you get a sudden urge to do that, then it would be great if you could: 1) first try again and make sure it wasn't you who screwed up this time; 2) make sure it is reproducible and include detailed steps to reproduce; and 3) be cool about it and don't act like the Abes have personally done you wrong.
And if you get a sudden urge to do that, then it would be great if you could: 1) first try again and make sure it wasn't you who screwed up this time; 2) make sure it is reproducible and include detailed steps to reproduce; and 3) be cool about it and don't act like the Abes have personally done you wrong.
I think we have to imagine how people would have been if Ableton had waited until September to release their first version. People were so impatient to have their hand on it. Even if it's not working so well, you can get familiar with it, and don't need to buy it until it works well. that's what I'm doing anyway.
In a way they were doing most people a favour, for like I said you didn't have to buy it.
In a way they were doing most people a favour, for like I said you didn't have to buy it.
Quad 6600 Intel, AsusP5Q, 2Gb ram, XP sp3, Evolution MK361c & UC33e, Line6 UX8
I understand what you mean, I joined the beta testing on beta 8, the release came out after beta20, so it's true that I had time to see that there were some problems.
If you looked at the forum before buying it, you must have seen some complaints and bug reports though.
patience, just leave it aside until next bugfix as if you knew there were some bugs and hadn't bought it yet, life might feel nicer
FYI I'm annoyed by some features and am really impatient to see what will be fixed/changed in the next update, believe me.
If you looked at the forum before buying it, you must have seen some complaints and bug reports though.
patience, just leave it aside until next bugfix as if you knew there were some bugs and hadn't bought it yet, life might feel nicer
FYI I'm annoyed by some features and am really impatient to see what will be fixed/changed in the next update, believe me.
Quad 6600 Intel, AsusP5Q, 2Gb ram, XP sp3, Evolution MK361c & UC33e, Line6 UX8
I agree. If the demo doesn't work for you, don't buy it. It's that simple.
I have over 500 scenes and 60 tracks in my current set and it works perfectly, apart from loading/closing times being long, which I don't mind, as I open it once and leave it open all night. (Saving times, tho, are short.... go figure!)
I tested the demo with my particular requirements before I parted with my cash.
Quit whining. Caveat emptor.
I have over 500 scenes and 60 tracks in my current set and it works perfectly, apart from loading/closing times being long, which I don't mind, as I open it once and leave it open all night. (Saving times, tho, are short.... go figure!)
I tested the demo with my particular requirements before I parted with my cash.
Quit whining. Caveat emptor.
I'm not using freeze... I'm not using waves apps (I'm on T-racks and I'm disgusted by reverbs and delays all together)... I'm using Battery 2... and no presets... I never save self-contained and I use Reason via Rewire for al my synths that I then bump to audio tracks... I've never ever hit over 30% cpu... not even with t-racks mastering on all tracks and three battery 2 samples running (not that they consume a terrible much)...
I've only experienced one crash which was with a Guitar Rig preset - and NI updated it...
My two cents...
I've only experienced one crash which was with a Guitar Rig preset - and NI updated it...
My two cents...
+++ ---- +++ ----- +++ ----- +++ ----- +++
33 Koncerts, no demo, no album
http://www.thespoofkats.com
33 Koncerts, no demo, no album
http://www.thespoofkats.com
-
AfrikaShox
- Posts: 31
- Joined: Sun Jul 31, 2005 1:32 am
I do not agree...hambone1 wrote:I agree. If the demo doesn't work for you, don't buy it. It's that simple.
Some of crashes are related to Save/Save As function and rendering, which are disabled in demo version...for example
For me DEMO is not for bug testing but for features and function testing (full working features and function).
DEMO IS NOT THE BETA VERSION!!!
I am not beta tester, I am customer and I pay whole price for the product which do not correspond fully with developer's proclamations.
I am responsible for 100% payment as purchaser. Ableton is responsible for 100% product as developer and every1 must accept that today's Live5 is nowhere near to be 100% product.
But I bear the consequence of this (I can not use the purchased program fully and I miss a lot of worktime and often whole work but all my money are away forever).
And finaly, Ableton is BRAND and in view of its prices (rather high) I expect high quality products and professional approach. If I see the list of bugs fixed in announced update (and this is not the last update surely), I must to say: "The first official release 5.0.1 is shame for Ableton".
I think that Ableton perceives this and I hope it will be much careful in the future.