Update AAS-Plugins - Tassman now with 64 Bit Bridge

[pottering]

I thought "native" just meant it does not need special hardware to run (like UAD?).

[lolilol1975]

No. Native means the whole software has been recompiled in 64 bits, which often means some change throughout the codebase especially if it hasn't been coded properly or if it makes use of 32 bit assembly, in which case these parts have to be recoded.
64 bits bridging is the lazy way, it only insures compatibility with 64 bits DAWs, but internally, everything is 32 bits. On recent CPUs, this means a potential loss of performance of up to 10 or 12%, and of course the impossibility too adress more than a couple of Gb usually (although this might not be an issue for Tassman).

[Michael L]

Apparently the 64-bit bridge is a temporary fix until AAS redesigns Tassman to fit their new UI. Its the last of their synth updates and ETA is later this year-ish.

[pottering]

No. Native means the whole software has been recompiled in 64 bits, which often means some change throughout the codebase especially if it hasn't been coded properly or if it makes use of 32 bit assembly, in which case these parts have to be recoded.
64 bits bridging is the lazy way, it only insures compatibility with 64 bits DAWs, but internally, everything is 32 bits. On recent CPUs, this means a potential loss of performance of up to 10 or 12%, and of course the impossibility too adress more than a couple of Gb usually (although this might not be an issue for Tassman).

I guess it got a bit confusing, but the comment previous to mine (bumping a 2 years old thread) was questioning compatibility with "AAX Native plug-in hosts".

Also Tassman 4 uses far less CPU than the newer AAS plugins, I think they are removing CPU optimizations (or adding higher internal oversampling) in favor of better sound quality, in tune with Diva's or Serum's current popularity.

Tassman 5 is going to use as much as Chromaphone 2, or more.