Update to version 1.4 and the Trixie port (2.0) are already available

[hudiy]

We’re pleased to announce that Hudiy version 1.4 and the Trixie port (2.0) are now available. Thanks to your feedback and the discussions on our forum, we’ve once again introduced a range of fixes and improvements. You can find the release highlights below:

Hudiy for Raspberry Pi OS Trixie
The main highlight of this update is the Hudiy port to the latest Raspberry Pi OS Trixie.
Trixie is the newest release of Raspberry Pi OS and will be actively developed by the Raspberry Pi Foundation until the next major version.
The previous release, Bookworm, is still supported by the Foundation (until the next major version) but will now only receive security updates.

We will continue to develop Hudiy for Raspberry Pi OS Bookworm for as long as it remains supported by the Raspberry Pi Foundation, and we’ll strive to maintain maximum feature parity between the Bookworm and Trixie versions.

New features specific for Trixie
Trixie itself brings a number of new features that Hudiy can take advantage of – among them, an updated Bluetooth and network stacks.

Bluetooth
In version 2.0, we’ve implemented album art fetching in the Bluetooth (A2DP) player.
This feature is still marked as Experimental in the Bluetooth stack, so you’ll need to manually enable experimental Bluetooth features in the OS configuration.

The Bluetooth configuration is stored in the /etc/bluetooth/main.conf file. Enabling experimental Bluetooth stack features is done by setting the Experimental = true parameter in the [General] section of this file.

Wi-Fi
Another new addition – this time in the network stack – is the ability to use 80 MHz Wi-Fi channels in Hotspot mode.

In version 2.0, we’ve added configuration parameters that allow detailed setup of the Wi-Fi channel used by the hotspot.

An 80 MHz channel should provide significantly higher throughput, though at the cost of increased susceptibility to interference.

Documentation for this configuration can be found on our GitHub.

Features available on both Bookworm and Trixie
Aside from the Trixie-specific features, we’ve updated and improved various aspects of the Hudiy.
These updates are available in both version 1.4 and version 2.0.

UI control
In the new version, we’ve simplified Hudiy interface control using external controllers (e.g., keyboards).
Switching between input scopes now also works via scroll events, which means you no longer need to use the directional keys (Left, Right, Up, Down). The previous control method remains available.

DRM rendering
We’ve improved DRM-based rendering to better match the display’s refresh rate.
Thanks to enhanced frame synchronization, Android Auto animations should now appear smoother.

We’ve also added experimental support for 2K and 4K resolutions in Android Auto – available only in DRM mode (useRpiDrm = true). These new resolutions are considered experimental, as they push the Raspberry Pi’s hardware decoding block to its limits.

Various improvements
We’ve made numerous small improvements across various parts of Hudiy, for example:

• Improved USB hotplug handling,
• Forcing 32-bit color depth (RGBA) for both native UI and projections (in some cases, Raspberry Pi OS could select a 16-bit color depth for certain displays, even though 32-bit color depth was also supported by the screen),
• Ability to set a default path in the Storage Music Player’s file browser.

We’ve also improved the overall stability of Hudiy.

Migrating to Trixie
Since the Raspberry Pi Foundation does not provide an official way to upgrade from Bookworm to Trixie, we recommend performing a fresh installation of Raspberry Pi OS to use Hudiy on Trixie.

Installing Hudiy on Trixie works exactly the same way as on Bookworm.

You can download the updated installer in the same way as before – the link to the installer from your confirmation order is still valid and now points to the new installer compatible with both Bookworm and Trixie.

It automatically detects which version of Raspberry Pi OS it’s running on and installs the appropriate version of Hudiy.

Versioning
To distinguish between Hudiy versions for different Raspberry Pi OS releases, we introduced the following versioning scheme:

• 1.x – Hudiy for Bookworm
• 2.x – Hudiy for Trixie
• 3.x – Hudiy for the next Raspberry Pi OS release in the future

---------------------------

You can download and install the update for Bookworm using the updater program – https://github.com/wiboma/hudiy/blob/ma ... d#updating

A description of all new features and configuration options is available on our GitHub in the updated documentation – GitHub.

Since version 1.4 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.

---------------------------

Before running the updater, if you’ve changed the system locale, please make sure the Character Set is set to UTF-8.
It seems that when changing the language, Raspberry Pi OS may set the character set to ISO, which can cause display issues and prevent programs (including the updater) from working correctly.

You can change the Character Set in: Start → Preferences → Raspberry Pi Configuration → Localisation tab → Locale → Character Set

[Olli]

Hey,
I just installed the latest version of Trixie on my Raspberry Pi 5.

Now I want to install Hudiy, but I'm getting the following error during installation.

[hudiy]

Hey,
I just installed the latest version of Trixie on my Raspberry Pi 5.

Now I want to install Hudiy, but I'm getting the following error during installation.

Hello, you need to re-download the installer. Updated version of the installer is compatible with both Bookworm and Trixie. Link to the installer is in the e-mail with confirmation of the order (the same as for previous installer but now it points to the updated one).

[Olli]

Great... it's working now, thanks!

[ltlnmo]

Audio broken. No audio. Shows its there but not coming out of hifiberry DAC. same configs as old version. "hudiy_equalizer_sink" isn't in new main_configuration but i added it and it broke the software. now i can't ssh to change it.

[hudiy]

Audio broken. No audio. Shows its there but not coming out of hifiberry DAC. same configs as old version. "hudiy_equalizer_sink" isn't in new main_configuration but i added it and it broke the software. now i can't ssh to change it.

Check this thread regarding audio viewtopic.php?t=114.

How exactly is the software broken after changing the configuration and what change did you make specifically? Changing the Hudiy configuration file has no impact on SSH.

[ltlnmo]

followed the thread. made the change to startup.sh. now the Hudiy UI/screen just goes blank. audio works but no image

[hudiy]

followed the thread. made the change to startup.sh. now the Hudiy UI/screen just goes blank. audio works but no image

What changes did you do exactly? Please also post log file ($HOME/.hudiy/log/hudiy.*.log) and routing graph from qpwgraph.

What configuration you are actually trying to achieve? Do you use microphone in your setup at all (assume no if there are issues with echo cancel)? If no, the best way is to remove echo cancel and replace it by null-source.

[ltlnmo]

I applied the changed hudiy_startup.sh you posted in the other thread. i don't have a mic now but will.

if i make any change to hudiy_startup.sh the UI goes blank. I made a change then reverted to original and it still occurs.

Going through chatgpt and narrowed it down to any change to the hudiy_startup.sh is causing some graphical portion of hudiy to fail because hudiy is still running but is just displaying a black screen. tried to resolve it but its over my head.

can't post log. won't allow .txt file and character length too long

[hudiy]

I applied the changed hudiy_startup.sh you posted in the other thread. i don't have a mic now but will.

if i make any change to hudiy_startup.sh the UI goes blank. I made a change then reverted to original and it still occurs.

Going through chatgpt and narrowed it down to any change to the hudiy_startup.sh is causing some graphical portion of hudiy to fail because hudiy is still running but is just displaying a black screen. tried to resolve it but its over my head.

can't post log. won't allow .txt file and character length too long

You can zip the log file and then upload it here.

Also execute:

Code: Select all

rm -rf $HOME/.local/state/wireplumber
mkdir -p $HOME/.local/state/wireplumber

and try this variant of hudiy_startup.sh (with module-virtual-source instead of dummy-sink)

Code: Select all

#!/bin/bash

EQ_SINK="hudiy_equalizer_sink"
DUMMY_SOURCE="dummy_source"

sink_exists() { pactl list short sinks 2>/dev/null | awk '{print $2}' | grep -Fxq "$1"; }
source_exists() { pactl list short sources 2>/dev/null | awk '{print $2}' | grep -Fxq "$1"; }
until pactl info >/dev/null 2>&1; do sleep 0.1; done

# Gives PipeWire and WirePlumber additional time to detect all audio devices
sleep 1

sink_exists "$EQ_SINK" || pactl load-module module-ladspa-sink sink_name="$EQ_SINK" plugin=hudiy_equalizer label=hudiy_equalizer control=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
source_exists "$DUMMY_SOURCE" || pactl load-module module-virtual-source source_name="$DUMMY_SOURCE"

pactl set-default-sink "$EQ_SINK"
pactl set-default-source "output.${DUMMY_SOURCE}"

$HOME/.hudiy/share/hudiy &

viewtopic.php?p=785#p785