Updates, fixes and improvements to OSRTIME Syncbox TCR.
Submitted for Google Play review.
This update expands 24-bit recording support for tested USB audio interfaces and improves audio level monitoring and the recording format shown in Settings.
Some USB interfaces expose audio to Android through a 32-bit integer capture format. OSRTIME Syncbox TCR can now use this capture path and convert the samples to 24-bit PCM for recording.
The format Android uses to capture audio does not always match the format saved in the recording.
For compatible devices, OSRTIME Syncbox TCR can capture 32-bit integer samples and convert them to 24-bit PCM. In this case, Settings correctly shows 24-bit as active. This is a planned format conversion, rather than a fallback to 32-bit recording.
This path uses integer PCM and does not provide 32-bit float recording.
Manual testing on a Xiaomi Redmi Note 11 included:
The supported recording format depends on the connected device and the format Android makes available. The wired 3.5 mm input was tested at 16 bit.
Additional checks confirmed 24-bit PCM WAV files containing 1, 2, 3 and 4 recorded channels, matching the selected recording channels. Multichannel recording remains an existing feature.
Support has been verified for the tested configurations. This does not guarantee 24-bit compatibility with every USB audio interface or Android device.
A 24-bit file describes the stored digital sample format. The effective resolution and dynamic range also depend on the connected hardware and Android’s audio path.
32-bit float recording is not included in this update.
Thank you to everyone contributing device tests and feedback. If you encounter unexpected behaviour, please let us know which Android device and audio interface you used, which recording format you selected, and what happened.
This update focuses primarily on external audio devices, USB audio routing, and 24-bit recording stability.
During beta testing, we discovered that Android audio devices can report 24-bit support in different ways. A device may appear to support 24-bit audio while Android is not necessarily able to open that particular format through the same recording path. Previously, attempting to switch to 24-bit in such a situation could leave the audio system in an unstable state or cause the audio path to stop responding.
OSRTIME Syncbox TCR now handles these situations much more safely.
If you select 24-bit and OSRTIME Syncbox TCR reports that it has fallen back to 16-bit, this is a normal compatibility behavior and does not indicate a crash or malfunction.
Because different USB audio devices expose 24-bit audio to Android differently, support depends on both the connected hardware and the audio format Android makes available to the app. Rather than forcing an incompatible configuration that could freeze the audio system, OSRTIME Syncbox TCR now safely and seamlessly falls back to a working 16-bit format.
We are continuing to expand compatibility with additional 24-bit USB audio implementations.
Testing included several different input configurations, including:
The purpose of testing different devices is not only to support individual products, but to make the audio system more robust across the wide variety of USB audio hardware available for Android.
OSRTIME Syncbox TCR is still being actively tested. If you encounter unexpected behaviour, a device that does not work correctly, or a workflow that could be improved, please let us know.
Real-world testing across different Android devices and audio hardware directly helps us improve compatibility and stability before release.
Thank you to everyone participating in the OSRTIME Syncbox TCR beta and contributing feedback, hardware tests, and bug reports.