Not exactly CPU spiking like in the past but meter is indicating red zone. X3e

Author
wmb
Max Output Level: -77 dBFS
  • Total Posts : 658
  • Joined: 2004/03/18 00:49:16
  • Status: offline
2014/04/08 19:50:43 (permalink)

Not exactly CPU spiking like in the past but meter is indicating red zone. X3e

I've noticed in projects that one CPU will be nearly maxed out while the other 7 are very low. I'd say they are in the 15% range. How come the application is leaning so hard on one CPU. If I put Ozone 5 on the main output it will either not play or just be unbearable to listen to. This is a pretty modest project at 96k. I've actually mixed much larger projects than this one and while the one CPU is pretty high and the others more moderate I'm sort of curious what the load balancing issue is all about. My system specs are listed below. Drivers are up to date. Most plugs are UAD and the Quad card is running about 80%. The rest are mostly bundled plugs with a few nomad factory and waves pieces in there. Not a much automation, Everything is 64bit.
 
Usually I will do "mastering" type stuff in a new session with a bounced mix but since the project is small I thought I could get away with it.
 
Any thoughts?

X2 & X3c - GA-Z77X-UP5 TH mobo | i7 3770k | 16 gigs RAM | Win7/64 | Audio Drive 2TB RAID0 | Data & Backup 2TB RAID1 | OS drive 256 gig SSD | Apogee AD16x -> Tascam DM3200 -> IF-FWDM-mk2 via Apple FW to Thunderbolt adapter -
#1

3 Replies Related Threads

    Sanderxpander
    Max Output Level: -36.5 dBFS
    • Total Posts : 3873
    • Joined: 2013/09/30 10:08:24
    • Status: offline
    Re: Not exactly CPU spiking like in the past but meter is indicating red zone. X3e 2014/04/09 01:42:16 (permalink)
    I think Ozone specifically is not written for multicore operation. Sonar can normally distribute the load from multiple plugins but not when it's a single one. Having the advanced version might help in this case since it splits into multiple distinct plugs. Upping your latency during mixing/mastering may help some.

    Also, by default the first core will be taxed a little more because that is what the GUI runs on.
    #2
    CJaysMusic
    Max Output Level: 0 dBFS
    • Total Posts : 30423
    • Joined: 2006/10/28 01:51:41
    • Location: Miami - Fort Lauderdale - Davie
    • Status: offline
    Re: Not exactly CPU spiking like in the past but meter is indicating red zone. X3e 2014/04/09 14:55:47 (permalink)
    I've noticed in projects that one CPU will be nearly maxed out while the other 7 are very low. I'd say they are in the 15% range. How come the application is leaning so hard on one CPU. If

    Thats normal operation as every project will need different resources. It also has to do with your sound card drivers and its driver mode and driver settings. There are variable that you need to take into account. All projects are not the same, so with that said, all projects will use CPU differently than other projects.
     
    CJ

    www.audio-mastering-mixing.com - A Professional Worldwide Audio Mixing & Mastering Studio, Providing Online And Attended Sessions. We also do TV commercials, Radio spots & spoken word books
    Audio Blog
    #3
    sharke
    Max Output Level: 0 dBFS
    • Total Posts : 13933
    • Joined: 2012/08/03 00:13:00
    • Location: NYC
    • Status: offline
    Re: Not exactly CPU spiking like in the past but meter is indicating red zone. X3e 2014/04/09 15:53:33 (permalink)
    I think that not only is Windows drawing heavily from the first core (perhaps someone can shed some light on that) but also the fact that not every VST spreads it's load across multiple cores.

    James
    Windows 10, Sonar SPlat (64-bit), Intel i7-4930K, 32GB RAM, RME Babyface, AKAI MPK Mini, Roland A-800 Pro, Focusrite VRM Box, Komplete 10 Ultimate, 2012 American Telecaster!
    #4
    Jump to:
    © 2025 APG vNext Commercial Version 5.1