Stereo Tool

Can you explain what the Basstardizer does (make the bass retarded??)? That beta only crashes and hangs on my desktop here so I can't check it. Someone also forgot to add a "is the ASIO device busy" check in there.

When i turn off the clipper it goes away, It seems that enabling the "Basstardizer" with the "clipper" Causes this problem.

Standalone x86
Intel i7 Core 2.00 Ghz, 8 GB of RAM DDR, Windows 7 x64, Reltek Audio DELL Laptop.

_________________
Fidelity over loudness

Which generation i7? It works fine on mine, which is a 6th gen.

4th Gen

_________________
Fidelity over loudness

Hi Hans

8.55 beta 6 running fine over the last two weeks.
Updated to 8.55 beta 14 and getting this on startup.
Does a restart, reports same and then stops.
i7 6th Gen, windows 10 64 bit v1709, 4k monitors.

Best regards and a happy and successful 2018 to you.

Rossco

@livewireaus: That was a missing NULL-pointer check for Basstardizer in low latency mode (which doesn't have a Basstardizer since it doesn't work in low latency mode). Added. This may have caused issues (crashes, or not) for people who were using Low Quality Low Latency output. Oddly, it didn't complain on my pc, not even in debug mode...

I also think I solved the NAN issue in Basstardizer. (if a NAN went in, it would stay at NAN and output silence forever).

There are some issues left with the GUI that I will fix... next year

New build is running.

Did not work:

1) low latency output
2) Self Test

Stereo Tool 8.55 BETA015

Windows 32 bit:
Windows stand alone: http://www.stereotool.com/download/ster ... 55-015.exe
Winamp DSP: http://www.stereotool.com/download/dsp_ ... 55-015.exe
VST: http://www.stereotool.com/download/vst_ ... 55-015.dll

Windows 64 bit:
Windows stand alone: http://www.stereotool.com/download/ster ... 55-015.exe
VST: http://www.stereotool.com/download/vst_ ... 55-015.dll


CHANGES:
- Enabling low latency output caused crashes
- NAN recovery added to Basstardizer
- Top area of GUI made a bit higher, not all menu items fit before

OLDER CHANGES:
- Bigger font and widgets on 4K screens
- Added Basstardizer
- Remove warnings that were shown for things that weren't even enabled.
- Fixed NAN in 8.54 in several versions in the clipper (reported by 1 person, appears to have been settings-related).
- Matt's bass effect Ready to get feedback, see "BASS EQ" before or between multibands! See note below.
- Fixed Mac multiband compressor gate error after NAN recovery.
- Add Breakaway Pipeline warning
- Add low input level warning
- Add too little AGC action warning
- Add too much noise gate warning
- Add too much BS412 action warning
- Added ASIO latency setting.
- Made streaming with libVLC easier, WARNING though, the audio quality is still the VLC streaming audio quality, there are better encoders out there. This only affects the stand alone versions.

NOTE: Bass EQ
1. This thing should not really be needed because there's already Auto EQ. However Matt Levin insisted that it's useful, especially now that they are playing very old Christmas music, so let's try it out!
2. There are 2 modes: Matt Mode (see checkbox) or Hans mode (unchecked). In Matt mode, the highest band is not adjusted but it is used to determine the levels. So in the last stage, the highest band is in bypass mode, but the other bands respond as if it's working as well. So the bass is adjusted compared to the full spectrum. In Hans mode, the highest band is ignored completely, so if you use 2 bass bands, they are adjusted to match each other, but not the rest of the audio.

TODO:
- Self test crashes
- Fix affinity for Linux and Mac - Mac doesn't support it.
- Edwin's bass effect - is that done now? (Maybe an extra HPF?) -> Not needed for now, based on preliminary tests...
- Put Bass EQ under license
- Do we need multiple Basstardizer bands? -> Doesn't seem like it. Not for now.
- Remove Hans mode from Bass EQ? -> Hid it (Extreme Tweaker mode, Matt mode is default, made it a pulldown instead of a boolean to clarify its behavior).
- Octaviafm extra logging? - Waiting. Once we know the cause I'll run a new build. But I'm not going to hold off releasing the current version, since 1. this issue doesn't have any side effects anymore and 2. it very likely isn't new. -> Nothing heard anymore
- Would multiple where_i_am start points improve attack? YES!!!! Think about how to implement it...
- Spectrum displays are broken in 4K mode
- Compressor/limiter on input before AGC to handle extreme sounds? / 2nd AGC with higher threshold for voice tracks Added, may need new mode. Waiting for feedback.
- MPEG detection is too insensitive now -> Probably fixed Waiting for feedback
- UECP UDP mode Waiting for feedback
- Add auto save to Linux build Waiting for feedback
- Revisit new Hard Limit / Final Limiter with Matt BUSY Waiting for feedback from Wes before continuing; extra settings to be removed after testing.
- VST delay appears to be wrong
- New compressor mode
- Basstardizer fadeout (Edwin)?
- Add AM presets
- Check MB2 1% something (see FB chat about crackling sound, which was ok in 8.00). Test with Rhodes54 preset -> Ok. But Spideys Web (7.41 vs 8.54) is different, let's test that.

- Raspberry Pi "gedeelde bibliotheek" melding.
- Check out Butt
- Add libVLC instability warning
- Loudness meter (also for streaming)
- Omnia.9 set Stereo signal. Probably fixed? Wait for answer.
- Omnia.9 test/fix logging
- Omnia.9 AutoPilot add flag for generating noise above pilot?
- WatchCat website
- Triple stuff

- SCA2 use as backup, feed to output without processing, bypassing normal chain. Use to have FM receiver as backup, and then just feed the full signal to the output.
- uMPX 24x2ch interface
- One bass page

- GUI: Hide disabled stuff, far less confusing / much cleaner interface.
- Talk to chip
- 2 jaar
- Fardau
- -24 dB side chain range?

BS 412 by Leif from Omnia9sg?

The following error occurred in the Windows VST64 version immediately after opening. Unfortunately, the error could not be reproduced, and came rather coincidentally.