Sonic Reality

hibidy · Post by **hibidy** » Mon Dec 21, 2009 6:48 am

Two new vox pics and the unmistakable orange.

btw, in photo 49 they are a bit puzzled looking. I hope there isn't an issue

susiwong · Post by **susiwong** » Mon Dec 21, 2009 2:22 pm

hibidy wrote:btw, in photo 49 they are a bit puzzled looking.

Wouldn't you have all reason to look puzzled if you had Amplitube 3 on your screen before it's even released ?

Cheers,
susiwong

Peter - IK Multimedia · Mon Dec 21, 2009 4:17 pm

hibidy wrote: What are you trying to say peter? It could be sooner?

Maybe... http://www.ikmultimedia.com/3teaser.php

Ohhhh wait, that's from 2008

Squids · Post by **Squids** » Mon Dec 21, 2009 6:02 pm

One thing I like about this mystery product is the sound design aspects of it and the real-time... oh wait, sorry I think I said too much!

susiwong · Post by **susiwong** » Mon Dec 21, 2009 8:15 pm

Going by the latest leaked info the consensus seems to be :
Oh, wait ...

Cheers,
susiwong

Peter - IK Multimedia · Mon Dec 21, 2009 9:10 pm

RE: X-GEAR RAM/resources/loading: X-GEAR doesn't load any other outside plugins, if that's what folks were thinking. All the gear models from the AmpliTube line are present inside X-GEAR, which is why you need to download a new version every time we have a new title.

You can test this. Long ago, I did a similar test and posted results here, too. Anyway... Open up an AmpliTube 2 preset in AT 2. Then try opening the same preset in X-GEAR - you will see the same or less CPU usage. If X-GEAR was loading other modules, it would be way higher, but instead we've actually been optimizing the code so it should use less (depends on the cab, though, because of some changes we made to our convolution process).

As for the X-Stomp, X-Amp, etc. idea, I like the workflow aspect, but in terms of CPU management it really won't do any good. If you bypass a module in AmpliTube, it ceases to exist and uses no CPU. So if you were to, say, create a preset called "X-Stomp" and bypass the amp, cab, and rack FX section, and leave dual-rig off, those other sections are adding NOTHING to your CPU usage.

I hope that clears some things up. And we can get to more guessing.

susiwong · Post by **susiwong** » Mon Dec 21, 2009 9:29 pm

Thanks, Peter !
Basically that's what I'm doing now, switch off stuff I don't need for the track.
I take your word on the CPU usage info, haven't tested scientifically yet.
Then you might as well forget about my modular suggestion.

One related question if you don't mind :
I believe to have observed that a 2nd or 3rd instance of AT / X-Gear takes up considerably less CPU than the 1st one in a project - true ? false ? secret ?

And while we're at it, wouldn't it be possible to have the tuner switched on by default, maybe as a preference ? I'd gladly accept the tiny increase in CPU for the added convenience.

Cheers,
susiwong

Squids · Post by **Squids** » Mon Dec 21, 2009 9:41 pm

http://www.facebook.com/pages/IK-Multim ... 146?v=wall

hibidy · Post by **hibidy** » Mon Dec 21, 2009 9:52 pm

Squids wrote:http://www.facebook.com/pages/IK-Multim ... 146?v=wall

Ooooo OOoooo, I know that one......it's called a small stone

susiwong · Post by **susiwong** » Mon Dec 21, 2009 9:55 pm

hibidy wrote:
Squids wrote:http://www.facebook.com/pages/IK-Multim ... 146?v=wall
Ooooo OOoooo, I know that one......it's called a small stone

Respect, how did you figure that one out ?

Lol,
susiwong

hibidy · Post by **hibidy** » Mon Dec 21, 2009 10:06 pm

Was the small stone part of the metal??

susiwong · Post by **susiwong** » Mon Dec 21, 2009 10:35 pm

Ok, back to business.

------------------------------
Here's my preliminary list :

1 Vox AC30
2 Marshall Guv'nor 1
3 Boogie MK3
4 Leslie 122 ? 147 ?
5 Ibanez WH-10
6 Roland JC-120
7 Boogie MK3
8 Boogie MK3
9 Univibe
10 Orange 120
11 Orange 120
12 Orange 120
13 Marshall Super Lead 100 MK2
14 Maestro Fuzz Tone
15 EH Big Muff or EH Electric Mistress ?
16 -----
17 Orange Cab
18 Boogie MK3
19 Gallien Krueger MB150S-112
20 Roland JC-120
21 Marshall Super Lead 100 MK2
22 Acoustic 301/361
23 Vox AC30 - Royer R121 / 122 - Focusrite ISA-828
24 Maestro Fuzz Tone #2
25 Proco Rat
26 EH Big Muff
27 Roger Mayer Fuzz / Octavia
28 Trace Elliot AH ...
29 MESA Rectifier 3 Ch
30 MESA Rectifier 3 Ch
31 Univibe
32 Vox AC30 / Guv'nor 1
33 Super Lead 100 MK2 - MD421
34 Royer R121 / 122
35 Orange Cab - TLM 170
36 Neumann U67
37 Leslie 122 ? 147 ?
38 Vox AC30 - AKG C414 / Royer R121 / 122
39 Acoustic 301/361 - C414 - Royer R121 / 122
40 Roland JC-120
41 Boogie MK3 - SM57 - Sennheiser MD421 - Neumann U67
42 MESA 412 - MD421 - Royer R121 / 122 - TLM170
43 GrooveTubes Velo8
44 Gallien Krueger MB150S-112
45 Roland JC-120
46 Vox AC30
47 ---
48 ---
49 Boss OD-2 Turbo Overdrive - Marshall Guv'nor 1
50 Vox AC30
51 Orange 120
52 Vox AC30
53 EH Small Stone
54 Vox AC30
55 Roland JC-120
56 Trace Elliot AH ...
57 Mosrite Fuzzrite
. Univibe + pedal
. Maestro FuzzTone 1
. Roger Mayer Axis Fuzz
. Roger Mayer Octavia
. Roger Mayer Classic Fuzz
. Maestro FuzzTone 2 (with the suspicious "tone" pot)
58 MXR Flanger - yay !

. Digitech Whammy
. EH Big Muff
. ProCo Rat
. Boss SD-1 Super OverDrive
. Boss HM-2 Heavy Metal
. Boss DS-1 Distortion
. Boss MT-2 Metal Zone
. Boss DF-2 Super Feedbacker & Distortion
. Boss BF-2 Flanger
59 Leslie
60 Deluxe Reverb
. Twin Reverb
. another BF Fender
. MESA Rectifier 3 Ch & 412 cab
. ??? (backside)
. THD Bivalve
. Fender Vibrotone
. Fender MetalHead / 412
. Fender 810 PRO cab
. another SF Fender
. Sunn head (190L has the most similarity, though there are others)
. Silvertone 212 cab below
. Ampeg SVT Classic
. Sunn cab below
. Randall Warhead
. Orange412
. Vox AC30
. a few FX (Roger Mayer etc) on top of the Sunn
. Gallien Krueger MB150S-112
. more to the extreme left including a SF Fender head (Dual Showman, Bassman or similar)
61 MESA Triple Rectifier
62 Marshall - pre '76 US/Can export model, possibly KT66 or 6550
63 Boss OD-2 Turbo Overdrive - Marshall Guv'nor 1
64 Orange 120
65 Boogie MK3
66 Gallien Krueger MB150S-112
67 - 69 Acoustic 301/361 - AKG 414 - Royer 121/122
70 the "export" Marshall
71 the Rat
72 Orange 412, SM57, TLM170R
73 Axis Fuzz
74 Big Muff
75 Univibe
76 MESA Triple Rectifier - TLM170R - Royer - hard to see black mic, MD421 ?
77 Boogie MK3 - U67 - Royer - MD421
78 JC-120 - U67 - SM57 - MD421
79 Orange 412, SM57, TLM170R
80 Boogie MK3 - U67 - Royer - MD421
81 Export Marshall with 412 - MD421 - Royer - TLM170
82 AC30 - Guv'nor 1
83 Rectifier with 412 - MD421 - Royer - TLM170
84 AC30 - SM57

------------------------------------------
Please discuss / correct ...

Peter, don't know if you're allowed to, but some comment if the level of detail (e.g. the Neumann Uxx mic) is ok would be much appreciated.

Keep them coming, I'll update the list accordingly.

Cheers,
susiwong

hibidy · Post by **hibidy** » Mon Dec 21, 2009 11:15 pm

hibidy wrote:Was the small stone part of the metal??

No seriously, was the small stone modeled for AT metal, or is it something new?

Funkybot's Evil Twin · Tue Dec 22, 2009 12:08 am

Peter - IK Multimedia wrote:You can test this. Long ago, I did a similar test and posted results here, too. Anyway... Open up an AmpliTube 2 preset in AT 2. Then try opening the same preset in X-GEAR - you will see the same or less CPU usage. If X-GEAR was loading other modules, it would be way higher, but instead we've actually been optimizing the code so it should use less (depends on the cab, though, because of some changes we made to our convolution process).

Sorry Peter, but you misunderstood. CPU usage isn't the issue. It's the RAM usage.

Amplitube X-Gear: approximately 245MB RAM per instance
Amplitube 2: approximately 110MB RAM per instance

That means 4 instances of X-Gear (which is not a lot) eats up around 1GB of RAM!

That's waaaaaayyyy too high for any 32bit host.

I seriously use about 4 instances of X-Gear per project and in the real world, those numbers mean that I'm forced to freeze my X-Gear tracks to free up RAM for BFD2 and Kontakt libraries.

Anyway, I was under the impression that the reason the RAM usage is high is because the graphics for everything get loaded to RAM for faster loading, which is what I was alluding to earlier. No matter what the reason though, that's just way higher than I'd like.

*BTW, this is using the current version of X-Gear (1.5).

Funkybot's Evil Twin · Tue Dec 22, 2009 12:09 am

...Let me just add, that I think highly enough of Amplitube's sound to deal with working around the high RAM usage. After all, I do use about 4 in every project.

Sonic Reality

KVR Audio

I just love GEAR! Check out these IK pics