image description


Please fix the CPU bus bug
  Forum Index » Studio One General Discussion 
Author
Message
MarsBot
Prenoob

Joined: 03/08/2010 09:17:37
Messages: 18
Offline

S1 has extremely high CPU usage when plug-ins are inserted on buses. I've seen this behavior on both the Mac and PC versions of S1. This makes it basically unusable at 88.2 and 96 kHz. And on complex mixes at 44.1 and 48 kHz, the CPU usage is much higher than on other DAWs.

You can easily test this by setting up the same 96 kHz mix in both S1 and Reaper (free demo download). Insert the Slate FG-X or some other CPU-intensive plug-in combination on the master bus in both S1 and Reaper and notice the difference in CPU usage. S1 will be almost 3 times higher. Insert the same plug-in combination on a stereo track in S1 and you will see CPU consumption decline to where it is comparable to Reaper.

Please try to get this taken care of before you release 2.0. I really want S1 to succeed. But this problem is going to discourage serious users who work at higher sample rates from switching over to S1.
Pre Nehalem 8 core Mac Pro, OS 10.5.8, MOTU Traveler firewire interface, UAD Solo and Duo PCI cards, TC Electronics Powercore X8 firewire, Bootcamp XP
jonathan
Presonoid
[Avatar]

Joined: 16/04/2009 17:37:19
Messages: 1551
Location: Loveland, Colorado
Offline

Please put your system specs in your signature.

I've never noticed this, and just tried to duplicate what you're seeing in Win7 x64 on my Q6600 8Gram machine. I used my most CPU intensive plug-in (2C Aether on max settings...an incredible reverb by the way), and got exactly the same CPU usage if used on a stereo track, a bus, an fx channel, or the main out.

I'd like to dig in a bit, but need your system specs to continue. Thanks!
Jonathan, Product Manager, PreSonus
MacBook Pro, OSX 10.6/Win 7 x64
Q6600 QuadCore Vista 32-bit/Win 7 x64
themuzic
Baconator
[Avatar]

Joined: 17/04/2010 05:42:47
Messages: 8703
Location: Wheeling IL (North Chicago Suburbs)
Offline

I just did a few tests on both my machines and they do not display this behavior. Could it be a system issue? I piles on alot of plugs and saw no change, hmmmmmmm

http://www.homestudiotrainer.webs.com/
http://www.youtube.com/user/themuzic
Email - homestudiotrainer@yahoo.com
Skype - themuzic
Phone - 773-303-7260
I offer FREE assistance for Studio One (any version) and Presonus hardware, to anyone having issues or anyone who simply wants to learn

Gateway Tower - Intel Core i5 3330 CPU 3GHz 8GB Ram and 64bit Windows 8
[Email] [WWW] [Yahoo!]
Motoko
Baconator
[Avatar]

Joined: 25/04/2009 08:29:34
Messages: 8086
Location: Amersfoort, The Netherlands
Offline

Not able to reproduce here as well.
Mac OS X 10.9.3: iMac 21,5" - Core i3 - 8GB Ram
Mac OS X 10.9.3: MacBook Air 13" - Core i5 - 4GB Ram

PreSonus FireStudio Mobile || PreSonus AudioBox 44 VSL || Alesis Active M1 MkII || CME XKey || NI Maschine

PreSonus Studio One Pro 2.6 || Pro Tools 10 || Digital Performer 8 || Ableton Live 9 || Maschine v2

SSL Duende Native || Plugin Alliance Transient Designer, Rack Pro, DrumXchanger || Softube Studio & Mix Bundle || ArtsAcoustic CL1 bundle, Reverb, Big Rock || FabFilter Total Bundle || FXPansion All Plugins || NI Komplete 8 || Synapse Audio DUNE || Tone2 ElectraX || Waldorf Largo || Image-Line Drumaxx || D16 Group Total Everything || Novation V-Synth, Basstation, FX Suite || Camel Audio Alchemy

Motoko || 64 Measures Music || YouTube || Mass Overflow || Manta Tracks
[WWW] [MSN]
MarsBot
Prenoob

Joined: 03/08/2010 09:17:37
Messages: 18
Offline

OK. I added my system setup to my signature. If you guys can't reproduce this, especially on a Mac, then I'm actually excited because there should be a fix I can apply to my setup. Make sure to try this on a real mix that you have going with a bunch of plug-ins. Also, if you have another DAW, try checking the relative CPU of a CPU-intensive plug on both S1 and the other DAW inserting on the master bus.
Pre Nehalem 8 core Mac Pro, OS 10.5.8, MOTU Traveler firewire interface, UAD Solo and Duo PCI cards, TC Electronics Powercore X8 firewire, Bootcamp XP
Intergroove
Presonic
[Avatar]

Joined: 16/04/2009 12:28:37
Messages: 900
Location: Dallas, TX
Offline

I did a test with 5 plugins on 5 different channels and cpu was around 12-15% then i disable the plugins on all the channels and put 5 of the same plugins on the master bus and the cpu went up to about 25-30%. Is that what you are talking about? This was at 24bit 96k
AMD Phenom II X4 805 (Quad core) Windows7/XP 4g ram
2 Firestudio 2626 Firestudio Project, UAD-1, Waves Mercury, PreSonus Studio One Pro 2.0.1
MarsBot
Prenoob

Joined: 03/08/2010 09:17:37
Messages: 18
Offline

Intergroove wrote:I did a test with 5 plugins on 5 different channels and cpu was around 12-15% then i disable the plugins on all the channels and put 5 of the same plugins on the master bus and the cpu went up to about 25-30%. Is that what you are talking about? This was at 24bit 96k


Yes. But I've been putting them all on one stereo channel instead of several channels. I just tried to reproduce this again at 96 kHz and could not. But I can definitely make it happen consistently at 44.1 kHz. I just checked it again in an actual mix.

There are two problems that I see here and I kind of mixed them together in an unscientific way in my previous post. Sorry.

Problem one is that plug-ins seem to require more CPU on the master bus or other bus than they do on a stereo track.

Problem number two is that S1 is using WAY more CPU for a given plug-in than other DAWS. Both Reaper and Logic show that Slate FG-X uses about 10% of CPU at 96 kHz while S1 shows that it uses 60%. In Reaper and Logic Ozone uses 5% and in S1 it uses 30%. These are simple files with two tracks playing in the song just for comparison testing. This problem actually concerns me a little more because it seems like S1 is requiring 6 times the CPU per plug-in of other DAWs.

I hope this is something peculiar to my system.
Pre Nehalem 8 core Mac Pro, OS 10.5.8, MOTU Traveler firewire interface, UAD Solo and Duo PCI cards, TC Electronics Powercore X8 firewire, Bootcamp XP
Intergroove
Presonic
[Avatar]

Joined: 16/04/2009 12:28:37
Messages: 900
Location: Dallas, TX
Offline

Hey i tried it again and did not get the same results the second time. So i am not sure what it is.

This message was edited 1 time. Last update was at 05/08/2010 07:39:59

AMD Phenom II X4 805 (Quad core) Windows7/XP 4g ram
2 Firestudio 2626 Firestudio Project, UAD-1, Waves Mercury, PreSonus Studio One Pro 2.0.1
MarsBot
Prenoob

Joined: 03/08/2010 09:17:37
Messages: 18
Offline

Intergroove wrote:Hey i tried it again and did not get the same results the second time. So i am not sure what it is.


I'm able to consistently make this happen at 44.1 when I'm working with a real mix that already has a lot of effects and busses. Have you tried that? I also was unable to make this happen at 96 kHz the second time I tested it. Maybe it's intermittent. Also, have you compared CPU usage of plug-ins between S1 and other DAWs? Now that difference shows up consistently every time I test it (6 times now).

This message was edited 1 time. Last update was at 05/08/2010 08:06:27

Pre Nehalem 8 core Mac Pro, OS 10.5.8, MOTU Traveler firewire interface, UAD Solo and Duo PCI cards, TC Electronics Powercore X8 firewire, Bootcamp XP
jonathan
Presonoid
[Avatar]

Joined: 16/04/2009 17:37:19
Messages: 1551
Location: Loveland, Colorado
Offline

Are any of the powered plug-ins in use when you see the issue? There's a lot of variables in a 'real' mix...we'll need some steps we can reproduce the issue with if we are to fix whatever it is you're seeing. Otherwise, it's really unlikely we'll run into the same problem it seems.
Jonathan, Product Manager, PreSonus
MacBook Pro, OSX 10.6/Win 7 x64
Q6600 QuadCore Vista 32-bit/Win 7 x64
MarsBot
Prenoob

Joined: 03/08/2010 09:17:37
Messages: 18
Offline

jonathan wrote:Are any of the powered plug-ins in use when you see the issue? There's a lot of variables in a 'real' mix...we'll need some steps we can reproduce the issue with if we are to fix whatever it is you're seeing. Otherwise, it's really unlikely we'll run into the same problem it seems.


Yes. On all the mixes where this happens I'm using UAD plug-ins and Powercore plug-ins. I'll test to see if that is creating the bus CPU effect I'm observing.

But it is very easy to verify whether or not S1 has a CPU usage problem in general. Just set up simple 96 kHz song files in S1 and another DAW. Then you insert a CPU-intensive plug-in into both DAWs and compare CPU usage. S1 is taking approximately 6X the CPU usage per plug-in as other DAWs on my system. When I do this test, I have only two tracks running and no UAD or Powercore plug-ins. This is on the Mac not PC.

I love S1. I've used DP, Logic, Sonar, Samplitude, Tracktion, MIxbus and Reaper. S1 is the easiest to work with and sounds great.

I'm able to mix at 44.1 if I use plug-ins efficiently. But it's very difficult to mix at 96 kHz when my main bus limiter (Slate FG-X) is taking up 60% of CPU as opposed to 10% in Reaper. So I'm frustrated by having to go back on these high sample rate songs and use Reaper's interface which is tedious in comparison to S1.

This message was edited 1 time. Last update was at 05/08/2010 18:18:20

Pre Nehalem 8 core Mac Pro, OS 10.5.8, MOTU Traveler firewire interface, UAD Solo and Duo PCI cards, TC Electronics Powercore X8 firewire, Bootcamp XP
 
Forum Index » Studio One General Discussion
Go to: