Sounds like I should try to find an audio file format converter to see if I can export something that works.

Could you test playback of files recorded with AHIRecord on your machine? That would be a quick way to check if it is indeed a file format issue.

The only way I see it being an audio driver issue, is if AE4 expects some kind of driver feedback to be exactly what Davy's drivers return. Even then it's still most likely an AE4 bug.

Ok, we are clearly out of sync so I stop here.

Yes, I can select the correct input (Don't mistake enabled sound for the correct input.)
The monitor will feedback audio to the linout and hp out no matter if you have selected the correct input to the ADC. The monitor will provide sound for any valid input.
(This will result in free mixing when recording from the monitor input instead of mic/line because the monitor itself will provide the hardware mixing for you)

Be aware that MIC inputs will give two channel mono. Only Linein will give real stereo.

Now for the not working part.
When I attempt to record from linein in the AE4 record window, the right channel is noise and the left channel is distorted. Even with the recommended HIFI 16bit Stereo++ mode at 48kHz.

Recording works fine with AHIrecord. (Which I have used to verify the driver)

When I record a sample with AHIrecord in 16bit AIFF format then this sample plays fine with multiviewer and AmigaAmp. But when import the same sample in AE4 then the sound itself is fine but the progress cursor/line thinks that the sample is about twice as long.

I do not know what dark magic is performed in the drivers written by DW that AE4 apparently works fine with those drivers.

Why recording doesn't work within AE4 is also a complete mystery to me. Could be that there are also some hidden DW driver communications to circumvent the limitations of AHI.

Be aware that AHIrecorder isn't perfect either. The "Monitor" selection doesn't work at all. It shows the outputs instead of monitor inputs but nothing happens when you select anything in the monitor. I can't see any request being fed to the AHI driver. So maybe AHIrecord makes assumptions or relies on hidden direct driver communication as well.

May I ask why AmiSphereServer (and therefore Updater) doesn't itself use AmiSSL and instead uses an outdated, obsolete, statically linked OpenSSL 1.0.2o? It should be easy to make the switch and it'll make AmiSphereServer much smaller too! Please support AmiSSL, rather than waste time messing with OpenSSL directly.

As the OpenSSL team itself says: "All older versions (including 1.1.0, 1.0.2, 1.0.0 and 0.9.8) are now out of support and should not be used."

It appears to be using libcurl too - the latest libcurl has built-in AmiSSL v5 support, but you may not even need to use libcurl at all either. OpenSSL 3.0 has its own simple built-in HTTP(S) client.

You are correct, it is not possible rename disk with RAWBInfo. Memory can be tricky... :)

Has the AmigaOS4 DOS moved on from tripos where on classic machines you had to align your FileInfoBlocks to word boundaries?

For some reason(s) Multiviewer doesnt start properly on my system. Its tc_State is suspended in Scout Task&Process list. Doesnt open.

InfoWB doesnt allow disk renaming via name stringbox. Drawers and files can be renamed as with RAWBInfo.

If I change icon via InfoWB, Transparent part of icon will turn visible black.

the precision is 16 (using double).

Broadblues, I am not a looser but a too confident person.

I was thinking wrongly that the comparison in gcc was smarter.
For example, if a=1.0 and b=1.0, a==b would always return true.

But it is not true because the comparison will examine all digits (here 16) and not only a few (here only one digit, smarter as the variables used in my code were equal to numbers from 1 to 4 with a step of 0.2) and as you wrote, the conversion is not precise.