Amplitube 3 - screenshot (from NAMM)

[blueman]

Bump!

Ok, we know the modeling in Amplitube Fender is very good but I think Metal and Hendrix already sound great so, why were they were re-modeled? Was it so they can integrate into the new Amplitube 3 architecture? If so, does this mean that SVX has been redone as well?

[redshift factor]

I'd like to know that too. I assume Ampeg SVX got the Fender treatment, but will Ampeg and Fender be getting the AmpliTube 3 treatment? Obviously both have had their cab sections updated to integrate into AmpliTube 3. But will they be getting standalone v2.0 updates?

On a separate noe, something extremely important to me, will AmpliTube 3 finally kill the 96kHz tuner bug for good? It keeps getting fixed and then sneaking back into the next update. I believe the current versions of all AmpliTube powered plugins are afflicted.

[autodafe]

I pre-orderd the upgrade a week ago or so...I've got an email confirming the order, but should I see something in my user area, like a new download/authorization slot or whatever?

[firepile]

Who says we can't get something out on the weekend?

In Italy?

I seem to remember they released Metal on a Saturday

[Peter - IK Multimedia]

Who says we can't get something out on the weekend?

In Italy?

I seem to remember they released Metal on a Saturday

I'm not sure of that offhand, but I do know that the developers don't just work M-F 9-5... I know it was meant in a lighthearted manner, but bear in mind that it was at the expense of people who do work through weekends and many more hours of the day than most people work - in order to get this release out as quickly as possible. They also work their tails off normally, but in the case of AmpliTube 3 this is a huge effort. There was a patch made to the code overnight while at NAMM, if that's any indication of the work ethic.

Again, I know it was lighthearted, but I didn't want anybody to take that wrong.

[edit]There is no longer a tuner bug[/edit], and as far as SVX goes the cabinets would of course be reworked to fit into the new methodology there as mentioned but I'd have to check on the rest. The GUIs definitely changed from their X-GEAR state as mentioned, to make redshift happy

EDIT - changed it above, too, be sure to note there is no longer the tuner bug.

[Peter - IK Multimedia]

I pre-orderd the upgrade a week ago or so...I've got an email confirming the order, but should I see something in my user area, like a new download/authorization slot or whatever?

Not yet, you will not see anything there until it is released.

[autodafe]

ok thanks

[redshift factor]

I do know that the developers don't just work M-F 9-5... I know it was meant in a lighthearted manner, but bear in mind that it was at the expense of people who do work through weekends and many more hours of the day than most people work

Hey, that joke wasn't at the expense of the developers, it was at the expense of the Italians!
You're just lucky you don't work for Arturia...

[tadam]

Has anyone asked Peter about VST3 development of AT?

[Funkybot's Evil Twin]

As far as release date for AmpliTube 3, we're looking at the last week of this month. We're VERY close.

I really hope you guys don't slip on that date. If it even comes out March 1st, IKMM will be lambasted around here for another late release (look at some of the comments in the audiomidi thread for a sneak peak). Anyway, my birthday's at the end of the month, and I've already pre-ordered through IKMM as a nice gift for myself. I really hope you guys get it out on time.

[Funkybot's Evil Twin]

Has anyone asked Peter about VST3 development of AT?

Why? I think it's safe to say VST3 has been an utter failure. It's been years, and most developers and hosts still do not support it nor do they have any plans to. If anything, x64 development should be a priority, not VST3. I don't want to argue about it, but Amplitube wouldn't gain anything in VST3 version that couldn't be done in a VST2.4 version. However, the VST2.4 version will work in every host, and the VST3 version will work in, what, 2 hosts?

[redshift factor]

I think it's safe to say VST3 has been an utter failure. It's been years, and most developers and hosts still do not support it nor do they have any plans to. If anything, x64 development should be a priority, not VST3. I don't want to argue about it, but Amplitube wouldn't gain anything in VST3 version that couldn't be done in a VST2.4 version.

I must take issue with a few of your points here. While I do agree that x64 development needs to be a priority, your VST3 facts are wrong. VST3 isn't an utter failure. Many companies are now finally beginning to embrace it, with SPL being just the latest. Waves supports it in v7, which I think is really going to get the ball rolling for industry-wide support.

But the above is a minor issue. What I really take issue with is your claim that AmpliTube wouldn't gain anything from VST3. Indeed it would. And in no small quantity, either.

One of the the biggest VST3 exclusive advancements is the ability for plugins to not process when there is no audio, potentially reducing the overall CPU load on a project greatly. If you are running many different guitar tracks that come in and out, this could make the difference between mixing in realtime or not.

The question here for a plugin like AmpliTube is about LFO style effects. If you have some of those loaded, then the sweep would probably not be in the correct phase when it came back in. However that could possibly be addressed by recalculating the phase position based on song position.

[Funkybot's Evil Twin]

A few points:

How many hosts support VST3? Do you think plugin developers who already are asked to support PC, Mac, VST 2.4, AU, RTAS and now x64 versions are really going to invest a lot of time developing VST3 when only 2 hosts support it? What's the total marketshare of VST3 compatible hosts? How many non-VST 3 compatible hosts are there? Do you see the problem? There's no incentive to make VST3 plugins, and every reason to stay on VST 2.4.

Also, I remember reading a post by Noel from Cakewalk in the Sonar forums where he specifically stated that there's nothing in VST 2.4 that prevents a VST effect from shutting down when it has no input. Any developer could implement this using VST 2.4 (in fact, a lot of synths already do). The problem with this method is that you could easily an environment where you'd hit a point in your song where you'd send your CPU off the charts creating system instability.

As you say yourself, there'd be ways to work around the phase issues.

And you say there's a lot of companies supporting it. Ok, how many? Now compare that to all the companies not supporting it. What's the ratio of plugin companies not supporting VST3 to ones that do? 50 to 1? 100 to 1? Greater?

Until the hosts all come around, if they ever do, VST3 will remain under-supported. And therefore, I'd much rather see IKMM's development resources get used for something that's more useful like x64 versions. In 18 months, I imagine most people running DAWS for serious work will be running a x64 bit OS and host. In that same amount of time, I'd estimate that the overwhelming majority of us will not be using a VST3 compatible host.

Remember: VST3 support is a business decision, and right now, it appears to be bad business.

[redshift factor]

While I don't disagre with the points you've made, I've heard all of your arguments against VST3 used against x64, too.

They used to make those arguments against Windows support, and native plugin support in general.

And back when DirectX ruled the roost *shudder*, they said it about VST support.

I've even seen developers on KvR make that argument against updating to VST 2.4, saying instead they would leapfrog straight to VST3.

See, in order for something to be widely embraced, it must first be widely embraced. It's a tricky balancing act. Our battle for x64 support is no different than the battle for VST3 support. In many ways, I see them intrinsically linked.

[hibidy]

I have to disagree there. x64 support is going to become something that will be hard for developers to ignore soon and vst3 doesn't seem to be taken as seriously. Btw, what is the other host than cubase that uses vst3?