Studio One on the Surface Book

Surface Session Ep13 – PreSonus Studio One and Surface Book performance testing

Posted on Posted in Article

How well does PreSonus Studio One run on the Surface Book and Surface Pro 4? Well let’s find out. In the last testing I did back in May 2016 Studio One struggled on the SP4. It would glitch and pop unless you disabled multi-processing and ran it on one Core. That worked but didn’t exactly give you access to the SP4’s full potential. Testing now in January 2017 there have been some massive improvements to both the Surface, Windows and Studio One. This has resulted in much better audio and virtual instrument performance – and with multi-processing fully enabled.

I run some of the Studio One demo projects so that you can get a useful comparison to your own system. I also run a 16 track test audio project and a load of virtual instruments. Check out the video below for all the details.

Specs:
Surface Book i7 6600U 2.6GHz 16GB with Nvidia
Surface Pro 4 i5 6300U 2.4GHz 8GB
PreSonus Studio One 3.3.3
K-Mix USB Audio interface running ASIO drivers at 256 samples.







9 thoughts on “Surface Session Ep13 – PreSonus Studio One and Surface Book performance testing

  1. Thanks for the video! I have been using studio one on the same model SB, it works well but I quickly reach cpu overload when use a reasonable amount of plugins. It use an RME babyface pro which is usb powered, but it actually (surprisingly) works better with windows audio. Do you think there would be any limitations to using a bus powered interface on the SB, or any suggested settings that could be tweaked to improve performance? I would think using the babyface pro interface should give much better performance than windows audio.

    1. I think it should yes, but by using Windows audio you’re adding a lot of latency which helps increase the performance. You would probably get better performance on the Babyface if you went to 1024 samples or something like that. Bus powering shouldn’t be a problem provided it’s only a couple of devices. I always use a powered hub which removes any powering issues.

      1. Thanks agreed I prefer not to use windows audio. Tried all sample settings. My only guesses are bus power or Rme driver issue on the sb, which would be surprising given their usual robustness.

          1. Just curious if you have the Slate “everything bundle” tutorial mix sessions? I tried their daw sessions for both Pro Tools and Studio One. The Pro Tools one plays on my surface book just fine, the Studio One maxes out the cpu at a few points in the song. Wondering if you have the same issue, but I also realize you may not have these sessions. They are free if you subscribe to the slate subscription.

  2. hi, I use Studio one 3 using an 1818vsl audiobox made by presonus on my surfacebook with NVidia graphics, 8 gigs of ram, and an i5 cpu . I use studio one as a live daw interface to send individual quemixes to each member in my band. They also can edit their own Mix by using studio one remote, which is quite handy. However, my question is regarding how I can make each mix good sounding without effecting its latency. Should I use the audiobox driver, or use ASIO for all? I have been using the audiobox driver with no latency setting built into studio one at the moment. It works great when I do live sessions with my guitar player and I (drums), but as soon as I add the bass and lead guitar I have to increase the sample rate and it leads to some latency and an overall drop in sound. Is it the audiobox driver that is not efficient, or is it the hardware on my surfacebook? should I look into a new audiobox that can handle more channels without loading the cpu? or can I tweak ASIO for all to outperform the audiobox driver? at the moment I use all 8 channels of the audiobox when I have the full band and send to 3 quemixes (vocals/rhythm guitar, Lead guitar, bass,) and I (drums) listen through the main out. how can I get an overall better sound without sacrificing latency.

    Thanks ,
    Derrick

Leave a Reply

Your email address will not be published. Required fields are marked *