We’re pleased to announce that Hudiy version 1.2 is now available. Thanks to your feedback and the discussions on our forum, we’ve introduced a number of fixes and improvements. Please find release highlights below:
Display support
We’ve made a number of improvements to display handling.
Thanks to the updates in Raspberry Pi OS Bookworm and labwc, Hudiy can now run fully on Wayland without the X11 compatibility layer.
This enhances rendering performance for the native UI, Android Auto and CarPlay. Full Wayland support mode is now the default.
Zero-copy improvements
We’ve introduced improvements to zero-copy handling in projections. All transformations are now performed directly on the GPU, which significantly reduces CPU load and eliminates unnecessary copying of large amounts of data.
DRM support in Android Auto
We’ve added an alternative Android Auto projection rendering system that uses a special phone codec compatible with the Direct Rendering Manager (DRM).
This system is dedicated to Raspberry Pi 5 but works also on Pi 4B. Thanks to DRM and mentioned codec, Android Auto projection rendering gains a substantial performance boost, especially on the Raspberry Pi 5. This should be particularly noticeable at higher resolutions, and on the Pi 5 it also reduces CPU usage.
The new rendering system works only on Wayland and can be enabled in main_configuration.json (under the AndroidAuto -> useRpiDrm section). You can try it out and decide which rendering system works best for your setup.
Configuration for FPS in projections
Due to reported issues on the forum and compatibility problems with some displays, we’ve decided to remove the FPS auto-negotiation system in projections.
From now on, you can set the FPS value (30 or 60) for Android Auto and CarPlay projections in the main_configuration.json.
It’s worth testing the 60 FPS mode to see if it smooths out the Android Auto/CarPlay interface – especially if your display reports a refresh rate lower than 60 Hz (e. g. 59.9999 Hz).
Audio
We’ve also made several changes to audio handling.
Performance
We’ve made several improvements to Hudiy’s internal ring buffer in audio subsystem. According to our benchmarks, this should reduce CPU usage by up to 6% in some cases. This is also related to the previously mentioned zero-copy improvements.
Subwoofer handling
Based on forum feedback, we’ve added a new mode for handling the LFE channel.
You can now control both the LFE balance and the percentage of the LFE channel’s volume relative to the overall audio sink volume.
You can switch between modes in main_configuration.json (under sound -> subwooferBalanceAsVolume).
PipeWire configuration
We’ve moved the loading of PipeWire modules (echo-cancel and the Hudiy equalizer) from the PipeWire configuration to Hudiy’s startup script.
Based on our observations and forum feedback, loading modules directly from the PipeWire configuration can sometimes cause issues with building the audio graph if audio devices are detected late by PipeWire.
We’ll keep monitoring this and will try to get support directly from the PipeWire project, which has become the default audio system on Linux.
WebView
We’ve added several improvements to the WebView component, mainly based on forum feedback. We’ve improved rendering for HTML/JavaScript components and handling onGoBack() callback.
We’ve also added new actions – quit_hudiy, go_back, and go_home – for greater convenience when using the API.
Splash
We’ve added support for a custom logo in the Splash program.
The logo can now be displayed instead of the “Hudiy” text during application startup.
You can download and install the update using the updater program – https://github.com/wiboma/hudiy/blob/main/README.md#updating
A description of all new features and configuration options is available on our GitHub in the updated documentation – GitHub.
Since version 1.2 requires updating Raspberry Pi OS Bookworm to the latest release, we recommend making a full system backup beforehand – just in case.
That way, you can easily revert to the previous state if any operating-system-level issues arise.
As always, we encourage you to follow us on Instagram, YouTube, X (formerly Twitter), and Facebook.
Enjoy!