Since I updated to Ample Guitars 3.5, I found every sound is distorted. So, I can't keep working with the old projects. Probably, Ample Sound put a strong copy protection. Or the 3.5 version just eats lots of CPU power. They use over 70% of CPU now.
Rolled back before 3.5.

 

Last edited: Apr 14, 2022

Hello@Wolfgang, which operating system and DAW do you use ? What CPU are you using ?
Can you create a new project and see what the CPU says ?

Ample Guitars 3.5

New Features:

-New parameter system, with better efficiency and compatibility with the VST3 format and various DAWs.
-Optimized Amp system and FX module, with higher efficiency and lower CPU usage.
-Updated UI of main modules, improved display and animation.
-Optimized multiple sample rate support.
-New voice-based SAHDS modulation system.
-Riffer now supports 64 measures at max, with navigation markers.
-New standalone host - Rectangles.

System Requirements:

• Windows: Windows 7/8/10, 64-bit only (32-bit not supported).
• Mac: 10.9 or higher.
• VST2, VST3, AU, AAX and Standalone host.
• 10 GB Hard Disk, Intel i5 or higher.

 

i updated AGSH, AGM and AGLP to 3.5 they work fine. Do you have the 3.5 installers for AGTC, ABJ and AEU?

 

My system is Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz 2.59 GHz with 16GB ram and 1TB SSD. Windows 10 64bit 21H2. Studio One and Reaper.
They worked fine with the previous version. I opened an old project to check something and the guitar sounds horribly laggy.
Ye, that's why I also updated to 3.5 as they said OPTIMIZED. I don't use the built-in amp system and FX because they eat the resources mostly. I use Guitar Rig or Amplitude instead.
They sound fine with a new project, but we never know cuz my old project have at least 12 guitars. Please don't ask me why I didn't bounce them. I did and this version is one before bounced.

 

They work fine if you just pull a single guitar. Load more than 10 guitars and play at the same time. And then you may find the problem unless you have a really high-end computer. As I mentioned above, the previous version worked fine with the same project.

 

That's where you really struggle for resources. Like you, I would use low resource plugins.

Your CPU:
Max. Turbo clock frequency 3.50 GHz
Intel® Turbo Boost Technology 2.0 clock frequency‡ 3.50 GHz
Processor base clock frequency 2.60 GHz

You can get your PC ready for music production with this tutorial.
Don't let audio glitches ruin your performances!
www.cantabilesoftware.com/glitchfree/

 

Interesting that they said the CPU should be lower but with your system it's higher. I should test that [W7, Reaper 6.53]- still haven't updated to v3.5. I also turn off the internal FX and use Amplitude and Helix generally for in-the-box processing [when I can't bother with the pedals].

Offtopic, but useful: regarding the CPU, he said it worked fine before @BEAT16. ;) But I have a piece of advice regarding CPU settings: turn off turbo, turn off speedstep, turn off speed shifting and all C states in BIOS. Put it at a steady frequency which could be between 3-3.2GHz for your CPU [maybe even more, but watch the temps never to exceed 60c at 100% utilisation] and when you find it stable then lower the voltage a bit, then another bit etc. until it becomes unstable, then turn it up two bits. With CPUs undervolting helps a great deal with the fan noise and the longevity of the CPU.

 

Last edited: Apr 14, 2022

can you send me the 3.5 installers for AGTC, ABJ and AEU? in private

 

Ok, that means the version 3.5 is actually not optimized as they said.

 

Ok, here is the update so far. These are what I have been doing:
1) Downgraded ASIO4ALL to 2.14 from 2.15 as it worked fine with 2.14.
2) Downgraded Audiobox96 Driver with the same reason above.
3) Downgraded Ample Guitars from 3.5.

And here are the result:
1) It works perfectly fine with Studio One.
2) Still horrible stuttering with Reaper.

So, I looked into it why it's different and found an amp sim caused the issue. It was Ignite TSB and it was used to the Reaper project only.
Thus, here is the result of my experiment from yesterday.

1) Ample Guitar 3.5 version eats more CPU then the previous version, so it's not optimized actually.
2) Some guitar amp sim can cause really horrible stuttering issue.

 

Why are you using ASIO4ALL? Try uninstalling it and report what happens when you use only the Presonus driver.

 

Please install the drivers as @FrankPig already said from PreSonus for your audio interface.
www.presonus.com/products/AudioBox-USB-96/downloads
Do not use the ASIO4ALL Driver.

 

I'm using AudioBox for audio device in Studio One, but the performance of Asio in Reaper is better than other options.

 

Last edited: Apr 15, 2022

Thanks, but I'm already using as I mentioned in my experiment. This is my setting.

 

Last edited: Apr 15, 2022

https://answers.presonus.com/24478/audiobox-usb-compatible-with-reaper-why-isnt-it-responding

There's an error somewhere. There's no reason why Reaper shouldn't be seeing the AudioBox ASIO driver.

Try uninstalling ASIO4ALL. Uninstall the older PreSonus drivers and redownload the latest Universal Control. Untick all of the driver options except the AudioBox:






Restart Reaper. If it's still not working, can you post a screenshot of Reaper>Preferences>Audio>Device

 

How to set up your audio interface with REAPER on a PC

 

Dude, if you go back and edit all your posts that said you were using ASIO4ALL because Reaper doesn't see the AudioBox driver, I'm not sure how you can expect anyone to help you.

 

That is the worst thing you can do.

Optimizing Your Computer for Audio - Windows 10
https://support.presonus.com/hc/en-...Optimizing-Your-Computer-for-Audio-Windows-10

Audio Interface – Low Latency Performance By Vin Curigliano
www.heavyweightbass.net/index.php/2016/09/08/audio-interface-low-latency-performance-by-vin-curigliano/

Troubleshooting DPC latency
https://support.focusrite.com/hc/en-gb/articles/208360865-Troubleshooting-DPC-latency

 

Ye, I think that's what I did exactly. He also says that you need Asio.

 

What do you mean? I don't get your point.
For the editing my post is that I found I was wrong and fixed it to right. Sorry to make you confused :p

 

Last edited: Apr 15, 2022