KVR Audio

LukeMornay · Post by **LukeMornay** » Sat Mar 10, 2012 12:24 am

looking forward to it !

Paulie Phonick · Post by **Paulie Phonick** » Sat Mar 10, 2012 12:45 am

Peter - IK Multimedia wrote:
Paulie Phonick wrote:Is it me or v3.7.1 doesn't sound the same? I just upgraded from v3.0.2 (I know, been a while) and my projects sound f..d up. Boomy low end on high gain presets; harshness and levels screwed up on others (80s Ballad for instance). If this is a side effect of the optimization, how do I get rid of it, besides downgrading?
The sound quality was not comprised at all during optimization. You should contact support. Thanks.

Ok, after a quick investigation:

1. The upgrade has reset all my quality prefs (oversampling, resolution etc.) to their lowest settings. Bringing them up again has helped.

2. The issue, however, seems to have more to do with recall of presets saved by the old AT 3.0.2. For instance, in one project I have a preset that is basically the 80s Ballad + a compressor. I open the project, it sounds harsh, middy and too loud. If I then select the 80s Ballad from the preset browser, add the Compressor and fiddle with settings, I can get a good sound again, albeit at different settings.

Anybody else gets this as well?

@Peter: I'll try to investigate further and get in touch with support, but I don't have much time for cross analysis of AT3 versions at the moment. Can you please verify that presets/models from the pre Custom Shop AT3 behave the same in v3.7.1?

filkertom · Post by **filkertom** » Sat Mar 10, 2012 12:51 am

For what it's worth, by the way, AT 3.7.1 seems to be working just fine in Band In A Box 2012.

A.M. Gold · Post by **A.M. Gold** » Sat Mar 10, 2012 1:02 am

Brian @ IK Multimedia wrote: A work around for this is to disable PDC in Reaper while recording.

I think a better workaround would be for an update to reestablish the previous protocol and have AT not report 7 samples latency again.

jensa · Post by **jensa** » Sat Mar 10, 2012 2:53 am

hibidy wrote:
Dr.Gunjah wrote:
Brian @ IK Multimedia wrote: Few developers report their latency accurately. That's actually the reason why you're seeing them all report zero - not because it's not there, but because they're just not reporting their latency at all!
sorry, but this is sheer assumption.
In my experience it's the other way around... most (serious) devs do it right and just a few don't.
In fact, my singles are the only ones that do report it (not going anywhere near 3.71) with ONE exception, and that is magnetic.

Nah, I think Dr.Gunjah is correct. I want facts, evidence, especially when it comes from a company like IK Multimedia that are experts in advertising...

hibidy · Post by **hibidy** » Sat Mar 10, 2012 3:09 am

I hope you don't think I was defending them

AudioGuy720 · Post by **AudioGuy720** » Sat Mar 10, 2012 6:57 am

That's awesome IK this has been long awaited by many! I'm sorry to read about the PDC problems, I'm sure this will all be sorted out soon.

Thanks for the tip on disabling PDC while recording as a temporary fix. Having properly reported delay is better than a lie/omission!

Harry_HH · Post by **Harry_HH** » Sat Mar 10, 2012 9:15 am

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

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.

.

So far I haven't learn how to browse the AT presets. Can you do that in
the way what is most logical and convinient for the user: i.e.
after you have chosen the instrument and the genre, these presets
appear to the window. If you activate the first preset in this list and then try to get the next one in the list by clicking the preset arrow in the
top side of the interface - no! - you don't get the next preset in the list.
(99 % of the plugins preset browser work in the way that the up-down arrow brigns the next/previous in the list - in the IK way you have double-click again and again and again and again and again ...)

IK - do I get something wrong or is this very basic feature that difficult to implement. Your way makes the browsing of the presets very confusing.
I don't give a damn about the browsing with the SteatlhPedal, first you should fix this fundamental issue I menion above, then maybe finetune pedal browsing.

Harry

Dr.Gunjah · Post by **Dr.Gunjah** » Sat Mar 10, 2012 10:14 am

A.M. Gold wrote:
Brian @ IK Multimedia wrote: A work around for this is to disable PDC in Reaper while recording.
I think a better workaround would be for an update to reestablish the previous protocol and have AT not report 7 samples latency again.

I'm incertain about this.
now that we have learned that amplitube always had this latency and just didn't report it, the only real solution would be to change the engine so that it does not introduce latency.
Though since we all know this won't happen (

) ... 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 (?!)

@midnight · Post by **@midnight** » Sat Mar 10, 2012 1:08 pm

So many plugins that introduce latency that never report it. It took Soundtoys forever to add their latency reporting. I think mfr's need to be more upfront about latency in their plugins as this can cause serious mixing issues even if you think you don't hear anything. Slight phase caused by a 7 sample delay might be inaudible but it might also be eating up headroom and then you might wonder why your track isn't sounding as loud and crisp, well you have some phasing going on that you didn't know about.

I wonder if Guitar Rig also adds latency but just doesn't report it. Any way to truly verify this?

bishop666 · Post by **bishop666** » Sat Mar 10, 2012 1:15 pm

@midnight wrote:So many plugins that introduce latency that never report it. It took Soundtoys forever to add their latency reporting. I think mfr's need to be more upfront about latency in their plugins as this can cause serious mixing issues even if you think you don't hear anything. Slight phase caused by a 7 sample delay might be inaudible but it might also be eating up headroom and then you might wonder why your track isn't sounding as loud and crisp, well you have some phasing going on that you didn't know about.

I wonder if Guitar Rig also adds latency but just doesn't report it. Any way to truly verify this?

...About Soundtoys... Decapitator is still 1 sample off...

It is reporting 1 sample delay more than it is actually using

Delay compenstion seems to be quite tricky

hibidy · Post by **hibidy** » Sat Mar 10, 2012 7:53 pm

@midnight wrote: I wonder if Guitar Rig also adds latency but just doesn't report it. Any way to truly verify this?

I don't know what all of this is but GR, Schuffam and AT 3.7 report NOTHING in reaper. They work fine

If I add an instance of any IK single, I get reporting and I can hear the difference.

metalifuxx · Post by **metalifuxx** » Sat Mar 10, 2012 8:27 pm

I don't care about the PDC that much or whatever people are mad about in this thread, because this plugin is now usable without being an extreme resource hog on my dated (6 year old) system.

______________

They said they fixed the Stealth Pedal write automation

, but this still does not happen automatically if I used the wah manually while recording. I have still never got this to work right or figured out how to set it up, especially using Live, which makes routing/assigning and midi control relatively easy and painless with any other controller.

A proper (video) tutorial would be great.

I know there is the midi setup on the plugin, and also a separate midi program configuration utility. This is all mind boggling to me, and I can usually figure these things out by reading the manual or online tips/hints from someone.

If someone knows how to do this, please explain.

(Edited to sound nice, the previous wording was to get IK's attention, not to sound harsh, but maybe it did)

Peter - IK Multimedia · Sat Mar 10, 2012 10:07 pm

hibidy wrote:
@midnight wrote: I wonder if Guitar Rig also adds latency but just doesn't report it. Any way to truly verify this?
I don't know what all of this is but GR, Schuffam and AT 3.7 report NOTHING in reaper. They work fine

If I add an instance of any IK single, I get reporting and I can hear the difference.

In Reaper... You are hearing it because of the rounding up, not because of a mere 7 samples of properly-reported latency. Have you reached out to Reaper support? All other hosts appear to be handling this minute amount of latency properly reported without a hitch. Obviously we've looked at this and Brian already answered correctly on our part but I'm surprised nobody has stated they've even asked Reaper support/devs about this.

Also, if you are adding Singles during tracking I can understand Reaper's round-up affecting things but in a mix environment with higher buffer settings being typically the norm, wouldn't your host handle reported latency correctly even with the rounding up and everything be perfectly aligned? In Cubase and Studio One it sure does, from experience.

hibidy · Post by **hibidy** » Sat Mar 10, 2012 10:35 pm

Why would I reach out to reaper support?

The other plug ins are fine

It's just the IK stuff.

3.7 doesn't report anything, just the IK singles (and apparently the 3.7.1 update)

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