Processor usage during fast bounce

Author
John T
Max Output Level: -7.5 dBFS
  • Total Posts : 6783
  • Joined: 2006/06/12 10:24:39
  • Status: offline
2015/01/04 05:39:27 (permalink)

Processor usage during fast bounce

Something I've been wondering for a while: how come Sonar doesn't max out processor usage during fast bounce?
 
I use Izotope RX 3 quite a lot, and for non-realtime operations, it goes full whack on all cores to get them done as quickly as possible.
 
Not a criticism particularly, just curious as to what's going on in Sonar that makes this a bad idea / hard to do / something else.
 

http://johntatlockaudio.com/
Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
#1

3 Replies Related Threads

    mettelus
    Max Output Level: -22 dBFS
    • Total Posts : 5321
    • Joined: 2005/08/05 03:19:25
    • Location: Maryland, USA
    • Status: offline
    Re: Processor usage during fast bounce 2015/01/04 06:07:41 (permalink)
    I am not quite sure either, but the coding itself can throttle usage, and this can be for very good reasons. Video editing is the only time I have seen programs run "full bore" (encryption is another case) and the CPU temperature ramps up quickly on my machine even with good cooling. With heat increase in the CPU, page fault/thread errors rise as well (have noticed this with benchmarking software), so I assume this is very intentional behavior. The worst offender I have seen (temp wise) is Windows Movie Maker... if rendering a full-length movie, CPU temp will exceed limits and the BIOS front end (ASUS AI Suite II) intercepts these processes and throttles them (was sort of painful to watch the CPU reach max recommended temp and stay there for 20+ minutes)... if it were not for the BIOS, it would have burned up in one run. Adobe Premiere Pro actually throttles itself prior to the CPU temp being reached. The coding for bouncing in SONAR is probably chosen for the most conservative case (again, I am assuming).

    ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
    #2
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: Processor usage during fast bounce 2015/01/04 14:00:05 (permalink)
    Bounce involves writing a new file to disk. The processing time may be more limited by disk write speed than CPU.

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #3
    John T
    Max Output Level: -7.5 dBFS
    • Total Posts : 6783
    • Joined: 2006/06/12 10:24:39
    • Status: offline
    Re: Processor usage during fast bounce 2015/01/04 15:13:07 (permalink)
    Hmm... possibly yeah. I've not noticed any difference between bouncing to an SDD or an HDD though.

    http://johntatlockaudio.com/
    Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
    #4
    Jump to:
    © 2025 APG vNext Commercial Version 5.1