Great work on the new builds, sounding sweet.
Just a few points I've come across:
- Running the latest VST beta 901-001 in Adobe Audition CS6 in the tabs can only see about 2/3 across the screen, unable to get to any adjustments/buttons further than that, for example in the Processing tab only as far as half way across the Multiband 1 button. Audition is 32-bit with the 32-bit VST.
1. Can you try if this was ok with version 8.54? Someone else reported this before I released version 9, and because of that I (thought I) removed all the changes w.r.t. Windows DPI sizes for VST plugins. This issue ONLY seems to affect Audition though. Long story here, but Windows DPI support was added in Windows 7, changed in Windows 8 and changed again in Windows 10, and every program has to indicate which things it supports or doesn't support. In this case, the problem might be caused by a conflict between how Audition handles it and how Stereo Tool handles it. I have restored the default settings (let Windows handle it, I don't resize myself), which *should* have fixed this issue - and it works fine in every other program I've tested, including older Audition versions. So right now I don't know if this is a bug in Audition or in my code. Could you do 2 things?
1. Test version 8.54
2. Make a screenshot of how the window looks and send it to me (or post it here). DO NOT resize the image, as I need to be able to see if Windows is resizing the image that I'm sending to it, and the Audition part of the window.
If you set your DPI size to 100% the issue should be gone - but then everything is probably way too small (I'm assuming you have a 4K screen?)
- Processing a file in the VST has your jingle placed over it a couple of minutes in when using unlicensed AutoEQ/BassEQ however this doesn't happen when using the Winamp plugin. Everything is licensed except AutoEQ/BassEQ however this works fine in the winamp plugin without any jingles or beeps. If I switch off AutoEQ & BassEQ in the VST it still says unlicensed in use but so far has not placed a beep or jingle. I will probably buy the AutoEQ license when there is a full/final release, bugs fixed and I can justify the extra 150 euro, but so far I've spent 250 and I use this purely for personal use, re-mastering music for CDs/iPod so it sounds nice and crisp Being that I'm only processing a few files at a time it seems a bit odd that I can play the winamp plugin for hours with no interruption yet the VST won't allow me to process any audio without interruption.
That's on purpose. VST plugins are often (and typically) used to process files, so I need to somehow block that for the unpaid version
- the Winamp plugin is mostly used for long term listening, and it's not very suitable for file based processing; for one it doesn't support correction for processing delay, so if you use the DSP plugin to process files, you'll always get some silence (or worse, the end of the previous track) at the start and the end gets cut off. This isn't the case for the VST plugin. Hence the different way of handling unlicensed features.
Of course both can also be used for 24/7 processing, and in that case the VST nags are way over the top,. but it's not really possible to see which of the two is happening.
- That being said, I have done an A/B comparison between the VST and the Winamp plugin, the VST has excellent peak control whereas the Winamp plugin has some overshoot, however on the flip side, the Winamp plugin sounds warmer, more open and natural whereas the VST sounds constrained and too 'digital'. Same preset settings, same source material. Clipper enabled, hard limit enabled, etc.
Hope this helps
There could be all kinds of reasons for this, but it's almost certainly not Stereo Tool. People have reported things like this in the past, I've done comparisons multiple times where I wrote the output to file and subtracted it, and the only difference I ever saw was a rounding difference in the last bit (leading to white noise at -120 dB when using 16 bit audio).
How do you see that there are overshoots?
- If you're actually running it in Winamp: The Windamp equalizer might be used. Or the volume slider in Winamp could be used, which causes audible artifacts if it's not set to 100% full!
- Source material: If it's not a lossless file, different decoders might sound different. Very different even in some cases.
- Sound card: I think Winamp by default uses MME, a VST program might use Wasapi, Kernel Streaming. If the sample rate doesn't match what's set in Windows, Windows will resample any MME audio and the resampler causes clearly audible artifacts, and overshoots. So if you're measuring Winamp's output you could very well see overshoots that are generated by the Windows resampler.
- Some programs purposely send a different signal to a Winamp/DSP plugin than to a VST plugin. There are many DSP plugins that only support 44.1/48 kHz and sound weird if you feed it something else, and some programs "protect" DSP plugins by resampling any audio to a standard sample rate. If they convery back afterwards, that can also lead to overshoots.
- Some programs oversample audio to overcome bad quality lowpass filters in sound cards. If they show the oversampled audio, you might again see overshoots, and on low quality sound cards, the sound might improve.
Note: There is a DSP plugin that lets you run VST plugins, so you can run the VST plugin in any program that supports DSP plugins. That's probably the safest way to compare. As soon as you use different programs to compare things, there are far too many variables.