[GH-ISSUE #189] line out

kerem commented

2026-02-27 19:28:28 +03:00

Owner

Originally created by @ultra-spark on GitHub (Feb 25, 2026).
Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/189

Hello,
I am using an RPi to run the test. Why is it not possible to use the RPi's audio output?

Originally created by @ultra-spark on GitHub (Feb 25, 2026). Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/189 Hello, I am using an RPi to run the test. Why is it not possible to use the RPi's audio output?

kerem commented

2026-02-27 19:28:29 +03:00

Author

Owner

@mr-manuel commented on GitHub (Feb 25, 2026):

What exactly are you testing and how are you testing?

Where have you running the Lox Audio Server?

What audio client do you use?

@mr-manuel commented on GitHub (Feb 25, 2026): What exactly are you testing and how are you testing? Where have you running the Lox Audio Server? What audio client do you use?

kerem commented

2026-02-27 19:28:29 +03:00

Author

Owner

@ultra-spark commented on GitHub (Feb 25, 2026):

I installed the lox-audioserver project on an RPi4.

I have tested it so far on an AirPlay output.
It's a shame that I can't test it on an RPi output jack.

Ultimately, we need a lox-lineout-bridge project that could also be used with the real Loxon audioserver because, as you know, the outputs of the audioserver and extensions are amplified outputs but not line outputs. It's a shame that this doesn't exist because when you want to use the solution...

@ultra-spark commented on GitHub (Feb 25, 2026): I installed the lox-audioserver project on an RPi4. I have tested it so far on an AirPlay output. It's a shame that I can't test it on an RPi output jack. Ultimately, we need a lox-lineout-bridge project that could also be used with the real Loxon audioserver because, as you know, the outputs of the audioserver and extensions are amplified outputs but not line outputs. It's a shame that this doesn't exist because when you want to use the solution...

kerem commented

2026-02-27 19:28:29 +03:00

Author

Owner

@mr-manuel commented on GitHub (Feb 25, 2026):

It's a shame that I can't test it on an RPi output jack.

Just run one of the supported audio players in addition to the Lox Audio Server on the Raspberry Pi. Then you can add it as output in the Lox Audio Server GUI.

armhf for 32 bit Raspbian
aarch64 for 64 bit Raspbian

For Squeezelite player run sudo apt update; sudo apt install squeezelite to install it, then run it by just entering squeezelite.

For Snapclient player run sudo apt update; sudo apt install snapclient to install it, then run snapclient ws://<lox-audio-server-ip>:7090.

For Sendspin player currently its a bit more work. Check the quick start guide for it. To run it then run sendspin --url ws://<lox-audio-server-ip>:7090.

Ultimately, we need a lox-lineout-bridge project ... because ... the outputs of the audioserver and extensions are amplified outputs but not line outputs

The Loxone Audio Server has a Line-Out and SPDIF-Out port.

The Loxone Stereo Extension has a SPDIF-Out port. Then just use a SPDIF to analog converter: https://www.aliexpress.com/w/wholesale-spdif-to-analog.html

@mr-manuel commented on GitHub (Feb 25, 2026): > It's a shame that I can't test it on an RPi output jack. Just run one of the supported audio players in addition to the Lox Audio Server on the Raspberry Pi. Then you can add it as output in the Lox Audio Server GUI. `armhf` for 32 bit Raspbian `aarch64` for 64 bit Raspbian For [Squeezelite](https://github.com/ralph-irving/squeezelite) player run `sudo apt update; sudo apt install squeezelite` to install it, then run it by just entering `squeezelite`. For [Snapclient](https://github.com/snapcast/snapcast) player run `sudo apt update; sudo apt install snapclient` to install it, then run `snapclient ws://<lox-audio-server-ip>:7090`. For [Sendspin](https://github.com/Sendspin/sendspin-cli) player currently its a bit more work. Check the [quick start guide](https://github.com/Sendspin/sendspin-cli?tab=readme-ov-file#quick-start) for it. To run it then run `sendspin --url ws://<lox-audio-server-ip>:7090`. > Ultimately, we need a lox-lineout-bridge project ... because ... the outputs of the audioserver and extensions are amplified outputs but not line outputs The Loxone Audio Server has a Line-Out and SPDIF-Out port. <img width="1636" height="1436" alt="Image" src="https://github.com/user-attachments/assets/fb9e3e48-5d0b-414e-bbb6-83304b3ebad1" /> The Loxone Stereo Extension has a SPDIF-Out port. Then just use a SPDIF to analog converter: https://www.aliexpress.com/w/wholesale-spdif-to-analog.html <img width="204" height="714" alt="Image" src="https://github.com/user-attachments/assets/fdccb45f-db1c-4b82-a521-7f53b3a4486d" /> <img width="960" height="960" alt="Image" src="https://github.com/user-attachments/assets/a589ee6d-6623-4b9d-8a6a-f55c4bc30e14" />

kerem commented

2026-02-27 19:28:29 +03:00

Author

Owner

@ultra-spark commented on GitHub (Feb 26, 2026):

Hello, I know it's possible to do this with the Loxone Audioserver, I'm very familiar with it. But there is only one analog output, which means two amplified outputs are lost.

If you want all the mono outputs to be online, it's not possible.

What I have already done on an 8-zone project is to convert a low-impedance amplified level to line level using a converter , i.e. 8 converters.

Regarding my request about the RPi line out,
imagine an installation in a house with 6 mono zones (ceiling speakers) + 1 stereo zone with a good amplified system in the living room.
All you would need is a Loxone audio server (4 zones) + 1 Loxone extension (2 zones) + an RPi with Lox audio server for the living room, with the option of choosing the RPi line out as the output (without going through Sendspin or another solution that adds load and latency).
Perhaps this isn't possible... We would need the developers to tell us.

@ultra-spark commented on GitHub (Feb 26, 2026): Hello, I know it's possible to do this with the Loxone Audioserver, I'm very familiar with it. But there is only one analog output, which means two amplified outputs are lost. If you want all the mono outputs to be online, it's not possible. What I have already done on an 8-zone project is to convert a low-impedance amplified level to line level using a converter , i.e. 8 converters. Regarding my request about the RPi line out, imagine an installation in a house with 6 mono zones (ceiling speakers) + 1 stereo zone with a good amplified system in the living room. All you would need is a Loxone audio server (4 zones) + 1 Loxone extension (2 zones) + an RPi with Lox audio server for the living room, with the option of choosing the RPi line out as the output (without going through Sendspin or another solution that adds load and latency). Perhaps this isn't possible... We would need the developers to tell us.

kerem commented

2026-02-27 19:28:29 +03:00

Author

Owner

@rudyberends commented on GitHub (Feb 26, 2026):

I’m not sure I fully understand what you’re trying to accomplish.

The server is not designed to run zone outputs directly. The intended architecture is: use a supported output (AirPlay, Squeezelite, Cast, etc.) to a dedicated player. I did look into supporting direct sound-card output for a zone, but it doesn’t make sense architecturally: it increases complexity, and you will never get reliable sync with other zones that are using networked outputs.

If I understand you correctly, what you actually want is an emulated Audio Extension that can connect to an original Loxone AudioServer. In that case I do understand the use case (and yes, direct sound-card output would be attractive there).

Audio Extension emulation is something we could explore, but I currently have no knowledge of the protocol Loxone uses between the AudioServer and its extensions.

If you can capture the traffic between a real AudioServer and an Audio Extension (pcap), so we can inspect and understand the protocol, I’m willing to look into implementing it.

This will also probably give us more insight in #102

@rudyberends commented on GitHub (Feb 26, 2026): I’m not sure I fully understand what you’re trying to accomplish. The server is not designed to run zone outputs directly. The intended architecture is: use a supported output (AirPlay, Squeezelite, Cast, etc.) to a dedicated player. I did look into supporting direct sound-card output for a zone, but it doesn’t make sense architecturally: it increases complexity, and you will never get reliable sync with other zones that are using networked outputs. If I understand you correctly, what you actually want is an emulated Audio Extension that can connect to an original Loxone AudioServer. In that case I do understand the use case (and yes, direct sound-card output would be attractive there). Audio Extension emulation is something we could explore, but I currently have no knowledge of the protocol Loxone uses between the AudioServer and its extensions. If you can capture the traffic between a real AudioServer and an Audio Extension (pcap), so we can inspect and understand the protocol, I’m willing to look into implementing it. This will also probably give us more insight in #102

kerem commented

2026-02-27 19:28:29 +03:00

Author

Owner

@mr-manuel commented on GitHub (Feb 26, 2026):

Audio Extension emulation is something we could explore, but I currently have no knowledge of the protocol Loxone uses between the AudioServer and its extensions.

Audio Server and Stereo Extensions are connected via Tree Turbo not via network. Therefore you would have to build your own hardware and you cannot capture the network. I‘m not sure, if you can build synced zones across multiple Audio Servers.

@mr-manuel commented on GitHub (Feb 26, 2026): > Audio Extension emulation is something we could explore, but I currently have no knowledge of the protocol Loxone uses between the AudioServer and its extensions. Audio Server and Stereo Extensions are connected via Tree Turbo not via network. Therefore you would have to build your own hardware and you cannot capture the network. I‘m not sure, if you can build synced zones across multiple Audio Servers.

kerem commented

2026-02-27 19:28:29 +03:00

Author

Owner

@rudyberends commented on GitHub (Feb 26, 2026):

Not sure if this is correct, but my understanding was that Tree Turbo is essentially “just” a network connection. But you’re right: I see tree turbo is a custom interface and you still need to be on the Tree Turbo network to (a) capture the traffic and (b) connect any emulated extensions — and that’s not realistically possible.

If I understand correctly from #102, grouping zones across multiple AudioServers should be possible. That makes an AudioServer-to-AudioServer protocol interesting as well, independent of extension emulation.

Unfortunately, I don’t have a physical Loxone AudioServer myself, so I can’t capture this traffic. If someone with real hardware can provide a pcap of the relevant communication, we can inspect it and see whether this is feasible.

@rudyberends commented on GitHub (Feb 26, 2026): Not sure if this is correct, but my understanding was that Tree Turbo is essentially “just” a network connection. But you’re right: I see tree turbo is a custom interface and you still need to be on the Tree Turbo network to (a) capture the traffic and (b) connect any emulated extensions — and that’s not realistically possible. If I understand correctly from #102, grouping zones across multiple AudioServers should be possible. That makes an AudioServer-to-AudioServer protocol interesting as well, independent of extension emulation. Unfortunately, I don’t have a physical Loxone AudioServer myself, so I can’t capture this traffic. If someone with real hardware can provide a pcap of the relevant communication, we can inspect it and see whether this is feasible.

kerem commented

2026-02-27 19:28:29 +03:00

Author

Owner

@ultra-spark commented on GitHub (Feb 27, 2026):

What I have always criticized about Loxone architecture is that there are not as many line outputs as amplified outputs.

And amplified extension modules connected directly to the false ceiling powered by the Loxone bus tree....

And network extensions with line outputs connected to a living room amplifier.

But for the latter, you've created the solution!
I've done my tests, so I installed Lox AudioSerer + Squeezelite on the RPi, which outputs to the line out. Great!

Just a quick question: how does Loxone view your developments? How were you able to develop this solution without Loxone's support?

@ultra-spark commented on GitHub (Feb 27, 2026): What I have always criticized about Loxone architecture is that there are not as many line outputs as amplified outputs. And amplified extension modules connected directly to the false ceiling powered by the Loxone bus tree.... And network extensions with line outputs connected to a living room amplifier. But for the latter, you've created the solution! I've done my tests, so I installed Lox AudioSerer + Squeezelite on the RPi, which outputs to the line out. Great! Just a quick question: how does Loxone view your developments? How were you able to develop this solution without Loxone's support?

Rows
Columns

[GH-ISSUE #189] line out #117