No, there's no decoding in real time - all imported MP3s are converted to 16-bit wav/aiff files on your hard drive.braj wrote:I'm not using MP3s so maybe that's the problem. They have to be decoded in real time, right? Maybe that along with time stretching is a bear.
BTW, the beat detection system doesn't work well with Grateful Dead tunes like Dark Start
Well, far be it from me to dispute an expert in the field...but I find this unlikely in the extreme. What sense does it make to use a kracked version to identify the supposed continual copyprotection checks? Why not do it with an unlocked version? And from your description of the problem, wouldn't this mean that a demo copy of Live would run faster than an unlocked copy? I would believe that a few certain functions (like Save) would check the copy protection, but I doubt that it does it as much as you say. But to be fair, I have not done any experimentation.beachnote wrote:actually.....
they said it about live v4 on the forums before they said it in the recent cubase 3 nfo file. and they said it in a forum which i wont disclose here. and on top of that its blantently obvious to anyone who programs that in fact you do suffer for copyright protection. and being a senior software engineer for a high security software development company, i can assure it is very much the truth: performance is a high price we pay because of copyright protection schemes.
and i never said that a dongle is any better, its the same thing. they both constantly check for violation routines, and they both take performance hits.
you want proof? go download any live v4 cracked version from gnutella and run it. keep moving faders and pan controls and you'll see the little mouse flashing a bit wierd...thats the copyright protection in action for you. keep doing it and after a whilke the cracked version will give you a copyright protection violation and youll have to reformat your system drive (or do something else which i wont share here).
or, run regmon or filemon and move faders and pan controls, and ask yourself why the fuk is live checing hundreds of reg keys and files just to move a fuckin fader.
every single action live performs has a copyright protection sheme put into it, its not just when you unlock the thing, so get your head out of your ass. and so do apps that use dongles. period.
Certainly people using Macs do get an additional performance hit, and on a 2 GHz P4 I can't do an infinite number of tracks with plugins, but it hasn't affected my creativity yet.one last thing, if we were them we'd be doing the same exact shit. its the only protection they have, and if losing a chunk of performance will help them make revenue and stay in business, its what they got to do....but they should seriously spend some manhours working on the problem, cause in live the performance is not up to par with cubase, logic, and others. just test it yourself, man. putting together a test environment and seeing the results is basic shit.
Just curious. Did you say somewhere up in the thread that you'd paid for it?but fuk, i still use live, so be it. and i'm glad im starting some shit, maybe they'll fix something.
That's not from Ableton news. That traces back to some guy who made one post on this board referring to another post on kvr-vst which made the claim out of nowhere. I poked around some and found no official confirmation of this claim. If someone else knows something real please post it.beachnote wrote:it was from ableton news, and there was a post about it on here a while back. im sure someone will bring it up or link to it eventually.
actually here you go: http://www.ableton.com/forum/viewtopic. ... rg+warping
so yes, cubase does all the realtime warping live does, and i can run 3+ times as many vst's on it....heh, go figure
i still love live, just wish they would spend on manpower on optimizations
Hell man, your setup has more juice than mine, wish I had it! I don't ever use Live live either; strictly as my main DAW like you. But even with your track setup listed above you're only getting a 40% peak/25% avg CPU usage ... so what's the problem? Apparently, you can almost double your track and/or plug count ... you have a lot of headroom to continue there. Am I missing something?Gigatron wrote:[...snip Ableton PR claim for Live]
Ok so I bought Live because I wanted to compose music in it. It seemed like a good product, but I can't believe how bad the performance gets once you get 15+ tracks of midi/audio going with lots of vst plugins. I'll give you an idea of the song I'm trying to finnish up:
[..snip detailed description of track and plug arrangement ... see his post above..]
Peak CPU usage: 40% (25% Avg)
CPU Usage when Idle: 15%
Win XP Home SP2, P4 2.8, 2GB DDR 400, 160GB 7200 rpm sata, PreSonus FirePod
536 Samples - Total delay 24 ms
I don't know, maybe it's just me, but doesn't this seem like a pretty simple setup? Maybe it's just my crappy hardware then? I'll fin out next week when I try out Cubase SX3.
Wow, that's some nice detective work....too bad I stopped believing anything I read on the web a few years ago...braj wrote:http://www.zplane.de/showPage.php?SPRAC ... products11
Elastique is liscenced by Ableton, not developed by them:
Test out the amazing quality of our élastique time stretching and pitch shifting engines in (listed alphabetically):
ableton Live 5
ALCATech BPMStudio 5
ALCATech DigiScratch 2
Bias Inc. Peak 5
Image-Line FLStudio 5
Native Instruments Kontakt 1.5 and higher
Native Instruments Intakt
Native Instruments Traktor 2
Zero-X BeatQuantizer (PolyStretcher) 1.x
Yeah, don't believe Ableton's 'About' box then eithernebulae wrote:Wow, that's some nice detective work....too bad I stopped believing anything I read on the web a few years ago...braj wrote:http://www.zplane.de/showPage.php?SPRAC ... products11
Elastique is liscenced by Ableton, not developed by them:
Test out the amazing quality of our élastique time stretching and pitch shifting engines in (listed alphabetically):
ableton Live 5
ALCATech BPMStudio 5
ALCATech DigiScratch 2
Bias Inc. Peak 5
Image-Line FLStudio 5
Native Instruments Kontakt 1.5 and higher
Native Instruments Intakt
Native Instruments Traktor 2
Zero-X BeatQuantizer (PolyStretcher) 1.x
That's where I initially read who the developer was.Funny you asked this, I just converted my Live project over to Cubase SX3 . And my cpu is only 10%. Go figure.rasputin wrote:[Hell man, your setup has more juice than mine, wish I had it! I don't ever use Live live either; strictly as my main DAW like you. But even with your track setup listed above you're only getting a 40% peak/25% avg CPU usage ... so what's the problem? Apparently, you can almost double your track and/or plug count ... you have a lot of headroom to continue there. Am I missing something?
I see you're using legal Live 5 too. It would be interesting to compare a roughly equivalent arrangement once you get SX installed and see what the CPU hit is for that setup.
I have no cpu spike when using locators, I'm not sure what's wrong with your system. I have a 3.2 P4 HT 1 GB RAM with a crappy Audigy2zx.Gigatron wrote: I still can't get over how much more responsive cubase's interface is compared to Live's. I can scroll around and zoom in and out with no lag like I use to get in Live. Anyone ever try moving around using the new locators? Someone tell me why my cpu would jump up to 60-80% everytime I click on a locator and then drops back down to normal?
.