Unable to retrieve images with Cast API after firmware upgrade

[simi05]

Since the firmware upgrade to API-Version 12.2.2 (Cast API) we are unable to use the Cast API in our application. We have obtained the latest binaries from https://github.com/clariusdev/cast/releases and added them to our application, as well as completely rebuilt the caster example from https://github.com/clariusdev/cast/archive/refs/tags/v12.2.2.zip. The build process was successful, and the connection parameters, WLAN interface, and firewall were set up successfully. Nevertheless, the following two errors occur during the call of castInit() function:

error: Failed to initialize native OpenGL functions
error: Failed to create offscreen context

If these two errors were ignored and the imaging is started anyway, the offscreen context error happens again, and the application crashes:

We tested this on different machines, one of them had never seen the Cast API before. The behaviour is the same for all tested systems.

Environment:

• SDK variant: Cast API
• Development platform: Windows 11, Visual Studio Community 2022, MSVC Toolset, v143, C++ Standards C++14 and C++17 both tested
• SDK version: 12.2.2
• Clarius App version: 12.2.3-766

[Sunderlandkyl]

We've seen the same error pop up in our application with v12.2.2.

[clariusk]

thank you for reporting, our team is investigating the issue and we'll update the forum with information as they make progress, seems there are a few other tickets regarding the Windows Cast implementation.

In the meantime, a few potential workarounds:

• Use a Linux OS or macOS operating system, confirmed these platforms work with Cast properly
• Downgrade the App on Android using the older APKs found on the mobileapi repository here and subsequently downgrading to the 12.0.x cast binaries

[haraldhoppe]

Sorry - but these workarounds are not applicable for us. Concerning workaround 1, we would have to switch from Windows to Mac or Linux with our whole development environmet and source code. That's impossible! And workaround 2 is only useful for applications on Android devices, not for Windows.
Please provide the old Clarius App (not Mobile API) which worked with the old windows libraries. Everything was fine before the last week update.

[clariusk]

Hi dear, sorry for the misunderstanding. With the second point I meant you can use the Android Clarius app and the older Windows cast Library which will work

[haraldhoppe]

The Clarius App updated itself (together with a firmware update on the probe). Afterwards, the old Windows cast library did not work with the new Clarius App. So I guess that we need the old Clarius App (as it was before the update), probably with another firmware for the probe. Where can we find older versions of the Clarius App?

[clariusk]

Hi there, we place the old App in APK format here: https://github.com/clariusdev/mobileapi/releases, so I suggest installing the last one there 12.0.3 which will match the update we previously had on our App stores. If there is a way to get the Apple version I will see, but I think sometimes it is not easy to provide a downgrade on iOS.

Our team is diligently working to understand the OpenGL problems we are facing under Windows with the Cast API, and hopefully we can provide new libraries quickly to provide the fix, but in the meantime, hopefully the downgrade of the APP can work.

To prevent automatic upgrades, for studies which may be sensitive to software changes, we also recommend to turn off Auto Updates on the mobile devices, whether it is an iPad or Android device. We appreciate your understanding and commitment to using Clarius.

[clariusk]

Please find new a new release and binaries that should fix the above issues: https://github.com/clariusdev/cast/releases
Note the problem was with a 3rd party library upgrade that was not handling OpenGL properly, thank you to our developers for spending the last few weeks re-implementing OpenGL stuff to make this work.

[Contused]

Did you receive any feedback if the new release solved the issue on windows?
I still get the same crash behaviour with 12.2.4 as before.

In detail:
I used the cast.dll/lib and .pyd for both python 310 and 311 from cast-12.2.4-windows.x86_64.zip
Both programs (running with python3.10 and 3.11) are able to connect to their scanners, but as soon as an image should be received (freeze state off) the program crashes with "Process finished with exit code -1073740791 (0xC0000409)"
App: 12.2.7-832
V1 Firmware: 12.2.1-780
HD/HD3 Firmware: 12.2.1-766

I have both a PA HD3 and a C3 HD3 with the same behaviour

[michel-clarius]

Did you receive any feedback if the new release solved the issue on windows? I still get the same crash behaviour with 12.2.4 as before.

In detail: I used the cast.dll/lib and .pyd for both python 310 and 311 from cast-12.2.4-windows.x86_64.zip Both programs (running with python3.10 and 3.11) are able to connect to their scanners, but as soon as an image should be received (freeze state off) the program crashes with "Process finished with exit code -1073740791 (0xC0000409)" App: 12.2.7-832 V1 Firmware: 12.2.1-780 HD/HD3 Firmware: 12.2.1-766

I have both a PA HD3 and a C3 HD3 with the same behaviour

We were unable to reproduce the crash using the latest cast-12.2.4-windows.x86_64 library. Imaging works as expected across Python versions 3.10, 3.11, 3.12, and 3.13 without any issues.

Test Setup:
Windows 11
Python 3.10 - 3.1.3
Clarius App 12.2.4, 12.2.7
Cast 12.2.4 for Windows: https://github.com/clariusdev/cast/releases/download/v12.2.4/cast-12.2.4-windows.x86_64.zip

[Contused]

Thank you for the fast response. I'll have a look at the differences and report my findings.

[Contused]

Sorry for the late response.
I installed the clarius example and my own python code onto a fresh windows 11 machine and both worked with 12.2.4.

Therefore the problem is not caused by your library but seems to be some weird problem with the dll handling of
ucrtbase.dll, Version: 10.0.26100.8246. I'll try to investigate further, if there is a fix specifically for my machine.