Ableton CPU on Windows 10

  On 6/2/2017 at 12:02 AM, Kidrodi said:

 

  On 6/1/2017 at 11:19 PM, auxien said:

Kidrodi did you ever get this figured out? I'm gonna be running Ableton on Windows soon and I'm curious what the problem was for you (assuming you figured it out/fixed it).

 

Yes, the sound card was garbage. I'm not entirely sure what went wrong technically speaking but I've since been using a Focusrite interface and everything's been running smoothly.

 

However, I have to say, Windows is fine at the end of the day but Macs are way easier to deal with when it comes to audio stuff. Just my 2 cents.

 

Yeah that makes sense. I've got a Focusrite Saffire Pro 40 myself. I wasn't having any major issues before it, but it did seem to reduce some latency once I got it integrated on my Mac, and hopefully it'll help me avoid any transition woes moving to Windows. I haven't worked with audio on Windows in many years, but I don't doubt that Mac is generally 'just easier' for it. Maybe I'll hate Windows and I'll go running back to a Mac in a year...but I doubt it.

my cpu is all over the place with live and win 10

any non native vst messes things up

That's no good bendish. Up to date Windows 10? Up to date Ableton? What sort of processor and RAM is it all running on?

maximum sex skylake

32 gigs ram

all up to date

The CPU meter is probably shooting about on Ableton as I think it just looks at Core 1, whereas VSTs can use multiple cores and thus probably freaking it out !

Bit confused by 'non-native VSTs' and 'messes things up' though ...

  On 6/2/2017 at 5:26 PM, bendish said:

maximum sex skylake

32 gigs ram

all up to date

Hot damn.

  On 6/2/2017 at 5:52 PM, mcbpete said:

The CPU meter is probably shooting about on Ableton as I think it just looks at Core 1, whereas VSTs can use multiple cores and thus probably freaking it out !

 

Bit confused by 'non-native VSTs' and 'messes things up' though ...

https://www.ableton.com/en/manual/computer-audio-resources-and-strategies/#managing-the-cpu-load

Ableton definitely supports multicore processors. If anything, it's possible (re: I have no idea) that some external VSTs don't...I don't know why they wouldn't be able to, but I guess maybe that's part of the issue?

They mention there that the CPU load meter only reads out the strain from the audio processing, not the graphical interface. So it's possible your computer could be straining more to process lots of ridiculous looking VSTs? I'd doubt it with the your system bendish, but I don't know what else it would be.

I know I almost always ran into either major or minor problems with VSTs back before Ableton and even when I first started using Ableton. They're hogs and they don't always play nice and aren't always up to date...at least back then. I quit using them entirely (yes, entirely) many years ago now. That's not the solution for many people, obviously. Would be curious to hear what's wrong if you get it figured out.

win 10 is shit for music production. im still on win 7 ...and osx, of course ;)

  On 6/2/2017 at 7:34 PM, auxien said:

I almost always ran into either major or minor problems with VSTs back before Ableton and even when I first started using Ableton. They're hogs

But yeah it's only a select few VSTs at the moment that support multicore processors. Some u-he range definitely does (Bazilla, Diva) but I can't off hand think of other multi-core supporting VSTis ...

  On 6/3/2017 at 1:55 AM, mcbpete said:

 

  On 6/2/2017 at 7:34 PM, auxien said:

I almost always ran into either major or minor problems with VSTs back before Ableton and even when I first started using Ableton. They're hogs

Something very wrong with your system(s) if that's the case - Been happily running VSTs since my Celeron 266Mhz PC back in the latte 90s/early 00s

 

Nope. I just don't enjoy using CPU hogs or glitchy programs. Some were viable and stable back when I regularly used VSTs (late 90s-2005ish), but in general there was occasionally a small or large issue with most of them, and a few of them were always crashing/glitching/whatever. These problems were sometimes fixed by updates to the VST, host DAW, or OS, sometimes the issues were made worse. And it was usually a crapshoot when trying to make music, and I never enjoyed that, despite the variety that some VSTs offered. I'm sure it's possible they're much more stable these days, but I wouldn't know as I haven't touched a VST in many years. And the ones I've seen pop up in videos/get talked about are occasionally interesting (I've considered using Reaktor as a VST in Ableton), I've never felt the need for them.

^Yeah, makes perfect sense. I'd hope anything you pay for is going to be reasonably well supported. I've just gotten used that no-VST limit and I feel it's done me good, having to work a little harder and learn a little more about the basic possibilities within the given tools (Ableton Suite is plenty fucking diverse) and Max For Live is a total wormhole with the amount of devices people are making for it.

I guess I should qualify my 'no VSTs' statement by saying I use Max For Live devices from anyone and everyone, as they're similar in usage to VSTs. And they're occasionally glitchy as well, but rarely (almost never) are they CPU hogs.