No products in the cart.
DISCLAIMER: I’ve searched the forum and could find similar topics but not the same issue I’m facing. Apologies if this has already been covered. If so, please just direct me to that thread.
PREFACE: I have been using SD2 on Reaper through my Line6 Studio UX2 interface with ASIO drivers with my Yamaha DTX900 eDrum kit for many years without issue. I have now (reluctantly) upgraded to SD3 before the end of 2018 as the discounted upgrade price will be discontinued.
ISSUE: When playing back a recording I did on SD2 with the SD3 VST it performs without issue. When I do a new performance/recording on my eDrums with SD3 I get a performance killing amount of audio glitches. I contacted Toontrack support directly, they suggested a change of buffer size but anyone who knows anything about recording on a DAW will know that will increase latency and make the recording/performance impossible. Toontrack support also suggested Line6 was the issue. I’m not convinced, the only change to my workstation recently has been SD3 and that’s when the problems started. I’m using less microphones and bleed on SD3 compared to SD2. I’m using the SSD for SD3 through my USB3.0 connection. Reaper is showing max 10% CPU usage when playing/recording, very occasionally it peaks at 25% when one of these glitches occur. Other than changing drums and cymbals, SD3 is still in it’s default state. Is anyone able to offer any more advanced support please or can share similar issues and resolutions?
Thank you in advance!
Well, you can remove Reaper from the equation…Do you get the same glitchy behavior in S3 standalone mode using the same Line6 device?
I don’t know your OS, but you can remove the Live6 driver from the equation…have you tried using a different ASIO driver (the free ASIO4ALL for example)? Try the ASIO4ALL driver with S3 standalone. What are the results? Then ASIO4ALL and Reaper. Results?
Scott Sibley - Toontrack
Technical Advisor
Hi Scott, thank you for your response.
I can’t get the standalone version to open. It crashes every time. I’ve attached two of the crash dump files that were generated.
One of the programmers will need to look at the dmp files to see what’s it’s crashing.
Scott Sibley - Toontrack
Technical Advisor
Thank you Scott. Just in case, Toontrack have already offered me this solution for the crashing of the standalone application but the problem remains.
“Please open the Windows Command Prompt on your PC then copy/paste the text below. You should be able to open the standalone and select a different ASIO driver.
reg add HKCU\SOFTWARE\Toontrack\Superior3\Host64 /v AudioAPI /t REG_SZ /d “Windows Audio” /f “
Have you tried using the ASIO4ALL driver in Reaper instead of the Line6 driver?
Scott Sibley - Toontrack
Technical Advisor
Hi Scott, thank you for this suggestion. I’ve just tried that (set to the largest buffer size I can without getting noticable latency – around 256), instead of the audio glitches I’m now getting dropouts instead. This occuring on playback now too.
I don’t know if this is cause or coincidence but the glitches with UX2 ASIO and dropouts with ASIO4ALL drivers seem to occur more when I’m opening and closing the hi-hat.
The new situation you’re facing sounds to be more of a memory issue (filling up) or a hard drive (slowness) issue.
Couple things you might want to look at:
Hopefully this will help. Good luck!
1
Thanked by: Alan CoxHi everyone, apologies for the delay in getting back to you on this. I’ve struggled to get back into the studio over Christmas and New Year. Thank you for your responses and patience whilst I get back to you.
I conducted some fault finding following the information that WGN5150 gave and it looks like this user is bang on the money. Toontrack’s suggestion that Line6 is to blame is incorrect. The issue that I’m experiencing goes away when I change SD3 to either 16-bit mode or remove some of the microphones/bleed/surround channels. This is freeing up memory to let the VST work more seamlessly. With most other variables tested and no change in behaviour experienced this is the only conclusion I can come to. So I thought, let’s double check my system specs against the minimum and recommended system requirements for SD3. I have 8GB DDR4 memory on my system which meets the recommended system requirements on Toontrack’s site. So now I wonder why a system that meets the requirements of the software is struggling to run it. I also now have an SSD of the SD3 sound library that is unusable because if I want the samples at 24 bit resolution I can’t use anything but the basic sound library.
What is your RAM usage without S3 loaded? How much of your 8GB of RAM is in use before loading S3?
Scott Sibley - Toontrack
Technical Advisor
What is the RAM usage using the kit and effects in S3 that you want to use?
And you say that playback is fine but recording MIDI is glitchy using the same buffer size? But changing to 16-bit makes the glitches go away?
I would suggest recording MIDI at 16-bit then setting it back to 24-bit after recording and mixing with full quality.
Scott Sibley - Toontrack
Technical Advisor
Having both your audio device and ssd on the usb bus, or even different usb busses is going to fall over a lot quicker.
Try to get your ssd to sata internal. If its a lappy, sacrifice your DVD drive (USB dvd drives are cheap as) or get an mSata or M2 drive for the OS and take out your mobile sim module.
Stutters and sometimes dropouts? Have a look at tuning your graphics card drivers:
———————————————————————————
Performance Tip for AMD GPU users for stutter/lag
Microstuttering and laggy playback is an all-too-known issue with any gaming system, and some good people on the net have come up with a possible issue with AMD installs:
AMD installs a service to write to the Event Log called ATIeRecord. If your event logs are huge and/or fragmented, then this service will record while you are gaming, and the recording lag from bad fragmented system files will hammer your performance with lags and stutters.
The fix? Disable the service:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Atierecord]
“eRecordEnable”=dword:00000000
Set to “1” by default which enables it. Disable it by setting it to “0” …………….
NOTE: If you install, re-install or update the AMD Radeon drivers it is set back to ‘1’ !!
———————————————————————————————————————————————————————–
Also USB needs to be tuned, switch OFF power management, and there’s more … J
Thanks for all your feedback guys.
Scott – I’m not sure what to say. You’ve suggested something that I’m already doing.
Bcslaam – the soundcard is USB and the SD3 SSD is USB. Both in their own USB 3.0 ports, I’m not sure what I can do to change that.
Jack 007 – I have NVidia GPU
No products in the cart.