Buffer overrun left click stopping play back and recording.

[greeny]

Hi I'm getting the Buffer overrun message while running big or small sessions, doesn't seem to matter if I'm running 2 tracks or 40.
Has anyone had this problem and a possible fix.

I am running the latest version of Sawstudio on Windows 10 and i've done all the Win 8 tweaks.

My machine is a i7 with 16 gig ram over locked to 4.2g
With 2 SSD drives both system and data.
Asus X99 motherboard.

I am running a current mix with 40 tracks and 30 plugin running and the Buffer over run pops
up on play.

This is a very fast PC and should be able to run heavy sessions.

Thanks for any suggestions in advance.

Greeny

[mr_es335]

Greeny,

First off, why two posts?

Secondly, it does not really matter how "great" your system is. It is important to keep mind that both SAW and SAC will run on pretty "light" systems.

Thirdly, is this a new system, or have you used the system for a time and this problem is just now appearing?
* Try to be as detailed as is possible here.

Fourthly, what I/O are you using?
* This would be more helpful than anything else. Problems like this are, at least in my understanding, related to the audio hardware and its configuration.

[greeny]

Hi
Sorry, accidentally posted it twice.
I use a Focusrite Scarlett 18i20 & a Focusrite Octopre MK2
This is a new system but I've seen this on my Windows 7 laptop as well in the past.

Just wondering is this a pc problem or Saw and the way it interacts with the audio driver?

Regards greeny

[mr_es335]

Greeny,

Well, it is NOT a SAW problem, so it boils down to a PC-then-driver problem.

Are you using USB then?

Can you tell us a much about your system as is possible?

[cgrafx]

Greeny,

Can you tell us a much about your system as is possible?

You also say your using 30 plugins..... What plugins???

[Danny O]

The first problem I see is that your running Windows 10, use Windows XP, or Windows 7
Second, 40 tracks with 30 plugins!!, is a very heavy load!!, try eliminating as many plugins as you can(ask yourself, do you really, really need them!!!),
not all plugins run with the same efficiency, use ram in the same way...etc.
Third, laptops usually have lower memory, slower processors, no matter what the operating system. They are a poor to use as a benchmark, especially with this load.
Forth, how many processors are you using?, should be no more than 2, more than 2 processors, won't make your system perform any faster. You can adjust this in SAW.
Fifth, try using 'Real Time Priority Class', and 'Use Region Memory Caching'

....and last but not least...what does your 'MT Load' read

[Danny O]

....some other things....you can usually turn processors off and on in the bios...I would seriously stay away from over clocking anything on the mother board.

[mr_es335]

Greeny,

So, are you actually using 30 plug-ins at one time?

Or is this how many plug-ins are available?

2680

[Richard Rupert]

I would suspect your problem lies with the plug-ins (or maybe just one of them). I would open the .edl and disable the plug-ins on all tracks (by going to each channel and clicking the bypass on the pre-FX and/or post-FX button). Then if the song will play, start re-enabling the FX channels ONE at a time until it chokes again. Then disable that one and continue with un-bypassing the remaining tracks, one at a time.

This has happened to me, with plug-ins I've successfully used previously, even on multiple tracks. Just one of them may cause the machine to stop.
It's worth a try. :)

[bcorkery]

Often you can reduce the plugin load by using on instance on the aux track instead of loading multiple instances on each track.

[Tom M]

As I have mentioned before, I, too, continue to have buffer overrun problems with SAW basic in Windows 10, using only 4-5 tracks at a time and NO plug-ins at all. My set-up is as basic as possible.

i never want to bash SAW because I think it is a fantastic piece of software, but I do have to say that I do not experience this overrun issue in Wave Pad or Audacity, ever.

A forum user convinced me that it's the way SAW interacts with Windows 10 and I have accepted this. I'm curious as to why so many are insisting it has "nothing" to do with SAW, though.

[Richard Rupert]

As I have mentioned before, I, too, continue to have buffer overrun problems with SAW basic in Windows 10, using only 4-5 tracks at a time and NO plug-ins at all. My set-up is as basic as possible.

i never want to bash SAW because I think it is a fantastic piece of software, but I do have to say that I do not experience this overrun issue in Wave Pad or Audacity, ever.

A forum user convinced me that it's the way SAW interacts with Windows 10 and I have accepted this. I'm curious as to why so many are insisting it has "nothing" to do with SAW, though.
Not to be argumentative, but there are a LOT of potential contributors to buffer issues. Admittedly chasing them down can be daunting. However, last night I had a remote session where I successfully recorded 16 simultaneous tracks to SAWStudio with a Behringer UMC 1820 USB interface connected to my old (8 years) laptop, now running Windows 10. The tracks recorded perfectly and play back without a stutter. It's critical that you use ASIO drivers... so make certain that's what you're using.

[Tom M]

....It's critical that you use ASIO drivers... so make certain that's what you're using.

Yup, I'm using ASIO drivers.