Hi,

Auburn Sounds (me) has released Panagement, it's a spatialization multi-effect that tries to solve two problems:

• "this track needs more stereo content"
• "regular panning doesn't sound that great on headphones"

Here is what it does:




Introductory video:
https://www.youtube.com/watch?v=YytzPk09cQk


Requirements

Panagement works in VST and AU for Windows Vista or later and OS X 10.7 or later.
In addition to VST 2.4, Panagement works as a 32-bit and 64-bit Audio Unit.

Panagement can be used:

• for free with the Free Edition but with a limited feature-set,
• with premium features with the Entreprise Edition. Introductory price is only €29 (+ VAT in EU).

Clich here to start using Panagement!
https://www.auburnsounds.com/products/Panagement.html


Let me know what you think.

Hi, I'm a developer and would like to clear up things a bit.

About 32-bit vs 64-bit program bitness:

First, it is possible for both 32-bit and 64-bit programs to use 32-bit or 64-bit instructions.
And whatever the bitness of a plugin, he is able to use the full instruction set: FPU, SSE, AVX...
Some developers think that FPU instructions are not available in 64-bit mode. No, they are there and work well.

64-bit programs have plenty of address space (what is also known as "virtual memory"). That is only valuable if you were maxing out your memory in your 32-bit DAW, which seems a bit unlikely to me but well. Bridging can work-around the restriction of 3gb by program in 32-bit Windows.

True advantages of 64-bit programs are in the speed department. A 64-bit program will typically be 15% faster from what I've seen. 64-bit programs are all kinds of good:
- more registers, larger registers: x86 is traditionally starved by the number of registers, 64-bit instructions solve that.
- more consistent C ABI accross platforms
- red zone: this is a low level optimization
- because there is enough addressing space for anything, stability may be better for plugins with threads or that allocate on the "stack" a lot
- the assembler itself is actually pretty easy to port from 32-bit

About 32-bit vs 64-bit vs 80-bit operands:

This is completely unrelated to program bitness.

Difference between 64-bit and 80-bit is very likely not able to count in the slightest. 64-bit vs 80-bit sounds like splitting hairs.

Difference between 32-bit vs 64-bit computations do matter for some tasks notably recursive filters.

Accidental higher precision when using FPU:

You can get accidental higher-precision when using FPU instructions because they bring the bitdepth of all numbers to 80-bit.

So if porting a plugin to 64-bit, it is possible that a plugin developer was inadvertently relying on 80-bit precision in the FPU for doing computation, and now he's using SSE 32-bit float and it makes things sound worse by accident. This has happened to me before release of my last plugin.

Conclusion:
Naive translations of 32-bit plugins to 64-bit _might_ sound slightly worse for this reason. With a bit of care they sound the same up to say -80dB RMS.

64-bit programs make developer lives easier and are a bit faster. Though you probably won't see much difference as users.