Stereo Tool

Hi Hans

I updated Stereo Tool (Windows 64 Bit standalone) and uMpx running the Thimeo build to v10.53 BETA012 and am unable to get audio flow to decode on the uMPX.

I rolled back the Stereo Tool version back to v10.51-011 BETA011, and it works (with and without RIST) with the uMPX remaining on v10.53 BETA012.
I updated Stereo Tool back to v10.53 BETA012 and the audio decoding stopped.

Does that make sense?

Ross

Confirmed. Something is wrong.

Wow. That was insane.

I have it working now. It took forever to figure out what was happening. If anyone is interested:
So, we're using a library in MicroMPX, Boost, which among others supports statically sized vectors. In the new build environment, we were using a recent version of Boost (we used a version from 2016 before). It turns out that the compiler that we use on Windows tripped on some of the smart code in the new Boost version to optimize the performance. The generated code was moving the CPU stack pointer, such that after putting something in a vector, the calling function returned without executing the rest of the code.

So basically my code said:
do_something
put_something_in_a_vector
do_something_else

And do_something_else was just silently skipped - no error messages or any indication that anything is wrong.

I'm now running a quick test build on Linux, if everything still works I hope that this fix also fixes the so far unexplainable MicroMPX ARM32 crash in these beta builds.

Good news: The Pi 2 crashes appear to be gone as well. Still waiting for the decoder build to finish, but the encoder starts now - it didn't before.

And now the Windows build also sounds good (it didn't crash before but it sounded horrible due to another compiler bug - it took a day to find a workaround). I'll run a build tonight.

I am not a programmer by any means, but after being involved in several projects, I know how much work it takes to move environments. Congrats on finding the issue, especially when it did not stand out.

Ross

I hope to see some progress on the Declipper plugin a la:
* Fix Declipper issues reported in https://forums.stereotool.com/viewtopic ... 4&start=30 and on Discord

This should be fairly simple to fix, just adding those blocks of code for the missing modules. I think.

Thanks!

_________________
America's Country
Totally RAD Radio

Hi Hans

Stereo Tool Windows 64B Standalone 10.53 BETA 018.

CPU usage is probably 1-2% lower now. I'm unsure if that is due to your recent changes, but I guess it is a positive outcome!

The uMPX audio stream is working again. I have updated the client on your PI image to the same release, and it also functions fine. Does GPS lock seem a lot quicker to get going and sync now as well?

I cannot see the tab to enable RIST under the Win client. It is present in the PI web interface. Is there something I need to do to make it visible or are you leaving it out of this build for now?

Is information on average bit rate and Total bit rate (excl. RIST) missing from the Windows build uMPX interface?

Ross

---------------------------
ThimeoWatchCat.exe - Systeemfout
---------------------------
De code-uitvoering kan niet worden voortgezet omdat zlib1__.dll niet is gevonden. U kunt dit probleem mogelijk oplossen door het programma opnieuw te installeren.
---------------------------
OK
---------------------------

Hi Hans

v10.53-BETA024 Win64 client, Thimeo PI image with the same version.

A GPS lock is achieved fine when running a conventional stream to a PI receiver. Suppose you switch out to use RIST, 9 times out of 10, under the "Resample Factor" area, the current buffer filling double size doubles, and you never seem to get a GPS lock again.

The only way to achieve GPS lock again is to reboot the PI. Turning off the client's uMPX stream or the receiver's GPS option does not reset it back to normal.

Regards

Ross