Close

Page 1 of 3 123 LastLast
Results 1 to 10 of 29
  1. #1
    Join Date
    Jul 2006
    Location
    SF Bay Area
    Posts
    1,509

    Default New Win10 LTSB Build with SAC/SAW64 - Initial Testing

    Initial bench testing with new Win10 LTSB build. I don't have preamps hooked up to system yet, just tweaking configurations and checking for dropped buffers and/or crashes.

    Hardware
    MSI H270M MORTAR ARCTIC LGA 1151 Intel H270 HDMI SATA 6Gb/s USB 3.1 Micro ATX Intel Motherboard
    Intel Core i3-7100 Kaby Lake Dual-Core 3.9 GHz LGA 1151 (Intel HD Graphics 630)
    SAMSUNG 960 EVO M.2 250GB NVMe PCI-Express 3.0 x4 Internal Solid State Drive (SSD)
    G.SKILL Ripjaws V Series 8GB (2 x 4GB) 288-Pin DDR4 SDRAM DDR4 2400 (PC4 19200)
    Dell U2515H 25" Widescreen LED Backlit LCD Monitor (2560 x 1440 Resolution)
    RME RayDAT PCI Card (Flashed to latest firmware and 32/64bit drivers)

    Software
    SAC64
    SAWStudio64
    Process Lasso Pro (This is used to automatically set CPU affinity and Real-time priority class for SAC)

    SAMPLE RATE & LOAD (I've done almost no system tweaks other than disable windows firewall and apply recommended display setting modifications)
    48kHz/24 bit Resolution
    1/32 Buffer Setting
    20-35% Load - ZERO slipped buffers (can f-key instantly in both SAC/SAW and switch between programs without issue)
    32 Channels Active
    4 Submixes
    2 FOH Mixes (Mains/Sub speakers)
    8 Monitor Mixes Active (1 monitor master and 7 mixes)
    8 channels with all 6 AUX sends active Post Fader with Studio Echo/Delay Enabled (FOH)

    Running all 64-bit has been more stable than the my initial tests with 32bit (SAW/SAC) running on Win64 as far as dropped buffers are concerned

    I've got more plugins to install and test but so far this is looking really promising.

    Plugins to add to system (not yet tested)
    - HoRNet3XOver (64-bit alternative to Dual Linkwitz filter)
    - HoRNetDeeLay
    - HoRNetSpaces
    - Anwida DX-Reverb Light 3.0 (64-bit reverb)
    - BlueCatChorus
    - Distorque Azurite (chorus)
    - Multiply (Chorus)
    - ValhallaRoom
    - Sanford Reverb
    Last edited by cgrafx; 03-19-2019 at 09:41 AM.
    ---------------------------------------
    Philip G.

  2. #2

    Default Re: New Win10 LTSB Build with SAC/SAW64 - Initial Testing

    Thank you for posting this. It really helps the other users to see the set ups that are used and how they are tested.

    Bright no dropped buffer days lay ahead!

  3. #3
    Join Date
    May 2004
    Location
    Toronto Canada
    Posts
    2,880

    Default Re: New Win10 LTSB Build with SAC/SAW64 - Initial Testing

    Great report! Thank you so much for posting.


  4. #4

    Default Re: New Win10 LTSB Build with SAC/SAW64 - Initial Testing

    Valuable info; thanks Phillip.
    Last edited by Richard Rupert; 03-23-2019 at 07:04 AM. Reason: Corrected OP credit
    Richard
    Green Valley Recording
    My cats have nine lives; my life has nine cats.

  5. #5
    Join Date
    Jun 2004
    Location
    Southern Tablelands, NSW, Australia
    Posts
    1,075

    Default Re: New Win10 LTSB Build with SAC/SAW64 - Initial Testing

    Thanks for the post. I am going to check out Process Lasso Pro.

    Cheers

  6. #6
    Join Date
    Oct 2009
    Location
    Maple Ridge, BC Canada
    Posts
    3,517
    Blog Entries
    1

    Default Re: New Win10 LTSB Build with SAC/SAW64 - Initial Testing

    [Richard,

    Valuable info; thanks Dell.
    ... Richard, I think you mean, "Thanks, Philip".

  7. #7
    Join Date
    Oct 2009
    Location
    Maple Ridge, BC Canada
    Posts
    3,517
    Blog Entries
    1

    Default Re: New Win10 LTSB Build with SAC/SAW64 - Initial Testing

    Philip,

    So what more does Process Lasso Pro do than simply enabling CPU affinity and Real-time priority class within SAC?

    Process Lasso Pro seems somewhat expensive for those two functions only.

  8. #8
    Join Date
    Jul 2006
    Location
    SF Bay Area
    Posts
    1,509

    Default Re: New Win10 LTSB Build with SAC/SAW64 - Initial Testing

    Quote Originally Posted by mr_es335 View Post
    Philip,

    So what more does Process Lasso Pro do than simply enabling CPU affinity and Real-time priority class within SAC?

    Process Lasso Pro seems somewhat expensive for those two functions only.
    It does a lot of other things that I'm not using. Its expensive for those two functions, but was the only utility that worked.

    You can command line assign affinity and force priority class, but that solution has other non-desirable side-effects.

    If you run SAC as admin, it won't connect to SAW Studio without also running Saw Studio as Admin.

    If you command line affinity, windows will launch multiple copies of SAC when you double click the icon rather than recognize that its already running.

    So $28 (with the discount code they sent me gives me reliable control of those two parameters without jumping through other non-standard hoops).
    ---------------------------------------
    Philip G.

  9. #9

    Default Re: New Win10 LTSB Build with SAC/SAW64 - Initial Testing

    Quote Originally Posted by mr_es335 View Post
    [Richard,

    ... Richard, I think you mean, "Thanks, Philip".
    You're absolutely right Dell. Sorry. I've corrected the post.
    Richard
    Green Valley Recording
    My cats have nine lives; my life has nine cats.

  10. #10

    Default Re: New Win10 LTSB Build with SAC/SAW64 - Initial Testing

    This is great news! SAW/SAC 64 is moving into hardware alpha testing! Thank you so much for doing this. Good results too. I was starting to lose hope.

    I'm very curious about Process Lasso Pro. What is the setup like? Are you pinning SAW/SAC to a single core somehow? If so, are they pinned to the same core - and is it possible to pin them to separate cores? What percentage of the pinned processor (if relevant) are you devoting to SAW/SAC? I've spent a short time on the PL site. I see CPU affinity (under dynamic local mode) but not real-time priority. And their CPU affinity seems to be automatic for whatever it sees as the highest-use threads, rather than by application. But I could easily be getting it wrong.

    Great work! And thanks some more!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •