Test

Server initiates connection and client wants 24-bit PCM

Start the server first, then the client. The server emits PCM in the 24-bit packed wire format (3-byte packed, little-endian, two's complement). The client advertises a listener and 24-bit PCM as its only supported audio format. The matrix compares canonical PCM hashes after the client unpacks the 24-bit stream. A client SDK with no 24-bit decode path misreads the bytes and produces a hash mismatch.

Total

pairings in this test

Passed

passing

Failed

failing

View test source

Runs

Server and client pairings

Open a case to inspect the full hello payloads, summaries, logs, and build output for that pairing.

Server

aiosendspin

Client

SendspinKit

Passed

PCM prefix matches; trailing samples omitted=40000

Server

aiosendspin

Client

aiosendspin

Failed

Client summary shows zero audio chunks

Server

aiosendspin

Client

sendspin-cpp

Failed

sendspin-cpp-client build failed: pressBuffer;

Server

aiosendspin

Client

sendspin-dotnet

Failed

sendspin-dotnet-client build failed: tnet/src/Sendspin.SDK/Connection/Noise/NoiseWireFraming.cs(245,21): warning IL2026: Using member 'System.Text.Json.JsonSerializer.Serialize<TValue>(TValue, JsonSerializerOptions)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. JSON serialization and deserialization might require types that cannot be statically analyzed. Use the overload that takes a JsonTypeInfo or JsonSerializerContext, or make sure all of the required types are preserved. [/Users/runner/work/conformance/conformance/repos/sendspin-dotnet/src/Sendspin.SDK/Sendspin.SDK.csproj::TargetFramework=net10.0]

Server

aiosendspin

Client

sendspin-go

Failed

Timed out waiting for file: artifacts/results/data/macos__server-initiated-pcm-24bit__aiosendspin__to__sendspin-go/client-ready.json

Server

aiosendspin

Client

sendspin-js

Failed

Server summary status is 'error'