AmpliTube Version 3.7.1 Now Available! Optimized: 30% to 40% less CPU & RAM

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

Dr.Gunjah wrote:
A.M. Gold wrote:
Dr.Gunjah wrote: Though since we all know this won't happen ( :D ) ... does anyone have expierence with disabling pdc for single plugins in Reaper ?(via right click on output-> pdc (x samples) -> disable)
I guess we (Reaper guys) might get the old behaviour by using this (?!)
Nope, doesn't work. Disabling it causes the plug-in to register as 0 samples reported but the total delay still goes up by 256. :? :help:
hm... I also can't find a global pdc disabling button anymore in Reaper 4... so how are we supposed to use the "workaround" ?

1. Disable pdc per plugin in reaper.

2. Hit play button (transport window)

3. hit stop button (transport window)


-> delay = 0 samples.

(reaper adjusts the delay while play button is pressed.)

Post

my bad... of course you're right.
it works this way.

For some reason I get only 7 samples latency(shown in performance view) on a channel that contains amplitube within one project.
Though I can't reproduce it... adding amplitube on another channel again adds 256 samples (?)
Is there maybe a "secret" way to disable the rounding up effect?

Post

Well, it sure fooled me.

Post

bishop666 wrote:
(reaper adjusts the delay while play button is pressed.)
Didn't know about that. Thanks for the tip.

Looks like that gets rid of the problem while tracking so IK is off the hook (not that they cared either way).
"You don’t expect much beyond a gaping, misspelled void when you stare into the cold dark place that is Internet comments."

---Salon on internet trolls attacking Cleveland kidnapping victim Amanda Berry

Post

Brian @ IK Multimedia wrote:Save 30% in CPU usage and 35% in RAM usage

Image

AmpliTube version 3.7.1 is now available as a free download/update.

This update is in response to players who wanted better allocation of CPU Power and RAM usage. Now, AmpliTube version 3.7.1 uses 30% less CPU power and 35% less RAM, allowing you to use more instances of AmpliTube on individual channel strips in your favorite DAW. The 30% reduction of CPU usage also means that player who use AmpliTube in standalone mode can run AmpliTube more efficiently on older, less powerful machines. This makes gigging out with AmpliTube even easier.

Other enhancements to AmpliTube include the addition of the Preset Up and Preset Down menu items in the StealthPedal controller dialogue menu, and overall stability enhancements.

Changes from version 3.7:

General:
  • Optimized RAM usage with an average savings of 35%
  • Optimized CPU usage with an average savings of 30%
  • Added preset browsing via StealthPedal external switches
  • Improved automation written from the StealthPedal controller
  • Fixed an issue that was corrupting the JCA20 audio response
Four Track Audio Player:
  • Fixed an issue that was corrupting the Pitch Shifter scale
  • Fixed an issue that may crash the application when adding an instance on the second track in the Four Track Audio Player
Existing users:
Download the AmpliTube 3.7.1 update from the "Downloads" section by logging into your User Area.

New users:
Check out AmpliTube 3 Custom Shop.
AmpliTube 3 FREE is a full-featured version of AmpliTube, with 24 gear models included. Plus, the included Custom Shop allows you to try and buy over 200 new gear models available as à la carte purchases.
Thanks for the improvements. Hope the new efficiency leads
to new sales. 8) Cheers

Post

Thanks. Other than hopefully forgiving AmpliTube for shooting Reaper from the grassy knoll, how's everybody getting on with it?

I know we didn't add gear this time, but the optimization was a big milestone for us so thanks for bearing with it being a gearless update. Any other ideas?

Post

Brian @ IK Multimedia wrote:BTW, in my testing of AmpliTube 3.7.1, I got up to 21 instances of AmpliTube going with no problems at all, using around 70% CPU in Studio One Pro 2.
Great to see you guys testing with Studio One Pro 2 as it is now my DAW of choice 8)

Post

Peter - IK Multimedia wrote:I know we didn't add gear this time, but the optimization was a big milestone for us so thanks for bearing with it being a gearless update. Any other ideas?
Yeah...more new gear! :hihi:

Post

blueman wrote:
Brian @ IK Multimedia wrote:BTW, in my testing of AmpliTube 3.7.1, I got up to 21 instances of AmpliTube going with no problems at all, using around 70% CPU in Studio One Pro 2.
Great to see you guys testing with Studio One Pro 2 as it is now my DAW of choice 8)
Yeah, I really dig working with Studio One. It pretty much covers everything from a testing standpoint - 32 & 64 bit, Windows & Mac, VST & AU, plus it has an advanced resource monitor that shows CPU usage per plugin instance! And setting up a project takes only a few clicks (or drag & drop!) and you're off and working.

Plus, Presonus are great guys & very helpful, which goes a very long way in my book. They don't make us authorize a new NFR every 3 months... So yes, they're good to developers which ensures very good compatibility with their DAW and quick turnaround on any issues that might arise. 8)

Post

I'd love to have the complete amp/cab chain of renowned Spotnicks solo marvel Bosse Winberg!

I suppose thet request dates me somehow… ;-)

Best,

Joachim
If it were easy, anybody could do it!

Post

Spitfire31 wrote:I'd love to have the complete amp/cab chain of renowned Spotnicks solo marvel Bosse Winberg!

I suppose thet request dates me somehow… ;-)
Date you? C'mon, the Gothenburg sound is very in right now! :hihi:

Post

Brian @ IK Multimedia wrote:… the Gothenburg sound is very in right now! :hihi:
I take that as a promise! :-D

/Joachim
If it were easy, anybody could do it!

Post

Just realized that you have closed my ticket (895520) without any fixes and without notifying me.
Y IK, Y?

Post

tico-tico wrote:Just realized that you have closed my ticket (895520) without any fixes and without notifying me.
Y IK, Y?
A ticket is automatically "closed" when you get a response from Tech Support, and reopened if/when you respond. That's just how the ticketing system works.

Post

Sorry, but it was "opened" a week ago. :(

Edit: I mean status was "open".

Post Reply

Return to “Effects”