Stereo Tool

BETA013 is available.

Changes:

• Report of segmentation fault on Pi -> CPU detection code did not set so parameter set failed
• Check Matt's Immersive Bass settings -> HPF to 30
• MicroMPX: Compare CPU load on Pi for MicroMPX with new resampler (higher temperature reported, but should have been lower!) -> No.
• Finish Pi low CPU mode
• Test resampler for 1 channel and > 2 channels -> Works (tested 1 and 6 channel audio)
• MicroMPX: 80008 do something with error message (add suggestion about raising threshold?) -> No, other bug will be fixed that makes this no problem
• Continue improving performance of resampler code - rewritten partially, test with floats instead of doubles on ARM -> Almost no effect, let's keep doubles for safety.
• The BIMP and SCA mode were broken in the last few beta's, fixed.
• Optimized Stereo Tool framework code for performance.
• Add GUI settings to test writing to screen in smaller chunks to avoid cracles at extreme latencies (< 5 ms, 1 < ms I/O).
• MB limiters don't use side chain for HPF yet
• Check what output is sent to streaming - pre-emphasized? - No, same as Normal Out, copied setting to clarify.
• UMPX LICENSE CODE protection Done, but needs testing

Limit Output instead of clipping under the advanced clipper is busted..

BETA014 is available and fixes this crash.

My license is gone and segmentation fault while starting Pi Decoder:

2019-06-07 14:21:14.536 info: Starting MicroMPX 2.1.0 beta / build 431a55c
2019-06-07 14:21:14.554 info: Broadcom throttle status: 524288
2019-06-07 14:21:14.897 critical: You do not have a license for MicroMPX decoder!
2019-06-07 14:21:16.416 info: License Request Code: xxxxxxxxxxxxxxxxx
Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1513
Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1837
Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1513
Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1837
Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1513
Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1837
Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1513
Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1837
Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1513
Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1837
Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1513
Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1837
2019-06-07 14:21:16.479 info: Opening output device #2 ("snd_rpi_hifiberry_dacplus: - (hw:1,0)" @ ALSA)
2019-06-07 14:21:16.480 info: Now listening on port 8855
2019-06-07 14:21:16.489 info: Enabled ALSA realtime scheduling
Segmentation fault

-Janne

Something is weird, I'm seeing something here as well (I get 10 seconds of audio and then silence). Not sure what happened with the license, but for now please keep using the older MicroMPX version... I'll put a note on the download page.

Hello Hans,

When the "No heavy CPU processing" function is activated, as soon as I activate the delossifier, the modulation is hatched

O. I'll look into it. By the way, "No heavy CPU processing" turns the spectral hole filler off (since that's heavy). This mode is most useful when you run ST on a Raspberry Pi or something like that, with it, all of the built-in FM presets can be run, even with composite clipping.

Edit: Confirmed.

Ok Hans,

you changed the processor management, I have a small AMD configuration, and it is difficult for me to find the right setting to avoid overloading my processor, that's why I wanted to use this function.

Hi, all the old settings are still there, but I've tried to make it easier. If you can tell me what you used before that worked that you can't select now anymore (or isn't part of the CPU presets), let me know and I'll add it.

It was on the previous beta 012, I had chosen the preset

CPU [ 4 processing cores, optimized for latency ] and No heavy CPU processing activated