[–] 3 points 10 hours ago

I started dabbling with Linux in 2019/2020, then fully switched in ~2023 because I got fed up with Windows 10 draining my laptop's battery while idle.

In the beginning of 2024 I switched from a Galaxy S10 to Graphene OS on a Pixel 6.

  • source
  • [–] [S] 3 points 6 days ago* (last edited 5 days ago)

    Nope, I was only semi-aware of the forums' existence. Thanks for the hint, I'll look into that tomorrow.

    And yes I love my LMS setup too. The software definitely has its odd quirks, but the protocols underneath are just rock solid. I actually own 3 SqueezeBox Radios (one with a battery which lasts many hours!) and a SqueezeBox Touch. I got pretty lucky, all the radios were 20 € used each, and the sb touch a friend had lying around from the time where the Logitech servers were still running.

    Also regarding Airplay, I've had a Raspberry Pi + HifiBerry DAC on my AVR for ages. I just wasn't expecting AirPlay to work well. But it really is insanely good. If you have any device with AirPlay, I sincerely recommend you try connecting it that way and save yourself the hassle of a Raspberry Pi etc.

    Edit:
    Honestly, my motivation for creating another account etc. is very slim. Feel free to share this in whatever way, I don't mind at all.

  • source
  • parent
  • context
  • [–] 2 points 6 days ago

    This is the way. I have an HP ProDesk 600 G4 with an i5-8500T, and it has been sipping 7 W for years now. Just be aware, most of these boxes only have one 2.5" SATA and one M.2 2280 bay. For HP, the ProDesk 600 and EliteDesk 800 have another M.2 2280 slot. Also be aware, you need a special internal cable for that SATA bay, so if you buy one of these make sure it has that cable in it already.

  • source
  • parent
  • context
  •  

    I just set up my Onkyo AVR to be a player for my LMS setup, using the AirPlay Bridge. As I was a little confused regarding the volume mapping, I thought I'd share how I made it work here.

    Connecting was dead simple, just install the plugin and make sure your AVR has AirPlay enabled. Everything worked flawlessly, except that the volume shown in LMS didn't match that shown on my AVR. The bridge has a 'Volume Mapping' option for this, where you can specify which AirPlay volume level corresponds to which LMS volume level.

    Now, the AirPlay volume levels are a bit confusing, as they go from -30 to 0. What's also confusing to me, the bridge seems to round the values reported by my AVR very oddly. Either way, whenever you change the volume on your AVR, you should be able to find the corresponding AirPlay volume value in the logs of the LMS docker container (or if you don't have it in a container wherever else the program outputs them to). Here is an example from my testing earlier:

    2026-11-08 12:23:46.142363+00:00[13:23:46.142] ActiveRemoteThread:1060 raw active remote: get /ctrl-int/1/setproperty?dmcp.device-volume=-13.536585 http/1.1
    2026-11-08 12:23:46.142412+00:00host: server.local.
    2026-11-08 12:23:46.142427+00:00active-remote: <some ID>
    2026-11-08 12:23:46.142439+00:00user-agent: airplay/366.0
    2026-11-08 12:23:46.142450+00:002026-11-08T12:23:46.142450036Z
    2026-11-08 12:23:46.142460+00:002026-11-08T12:23:46.142460668Z
    2026-11-08 12:23:46.142471+00:00[13:23:46.142] ActiveRemoteThread:1094 [<some ID2>]: remote command setproperty?dmcp.device-volume=-13.536585
    2026-11-08 12:23:46.142483+00:00[13:23:46.142] ActiveRemoteThread:1149 [<some ID2>]: volume feedback 45 (-13.54)
    2026-11-08 12:23:46.143354+00:00[13:23:46.143] sq_callback:354 [<some ID2>]: volume ignored 44
    2026-11-08 12:23:46.150985+00:00[13:23:46.150] PlayerThread:595 [<some ID2>]: processing volume device:29 request:-13.54
    

    When reading these logs, make sure to take the remote command setproperty?dmcp.device-volume=... value, as for me the rounded values were often incorrect.
    Now, get your AVRs AirPlay volume for one over 0 and the AVR volume levels which correspond to AirPlay level -15 and -30. This will lead to three value pairs, which you can enter into the mapping field. For me with an Onkyo TX-NR686, the mappings are -29.63:1, -15:41, 0:82 (yes the AirPlay volume caps at 100 % when the AVR reaches volume level 82).

    For me the AirPlay connection terminated as soon as no music was playing, which made it 'impossible' to get the AVR volume for AirPlay volume 0. I solved this by creating an mp3 file with silence, which I played during my testing. The following ffmpeg command will generate a 300 s (5 min) silent mp3:

    ffmpeg -f lavfi -i anullsrc=r=44100:cl=mono -t 300 -q:a 9 -acodec libmp3lame out.mp3
    

    After all this effort, the volume levels often still don't correspond exactly, due to the bridge turning e. g. -29.43 into -28.88 for some reason. But in my heart I at least now that my mapping is correct.

    I hope this is helpful to someone. If you have a different AirPlay device which is not an AVR, just substitute "AVR" with the device you have.

     

    I haven't seen any posts about this here yet, the Oasis Driver for Windows Mixed Reality headsets added Linux support two weeks ago.

    As I also got waitlisted for the Steam Frame, I have directed my enthusiasm there instead and now I have my HP Reverb G2 working again on Fedora 44. I still have to polish some small issues, but overall it works very well, even better than it did on Windows 10 before.

     

    I stumbled upon an old Android Tablet today running Android 6. Even though it is quite old, it has a 1440p screen, decent speakers and the battery still lasts a few hours.

    I already tried Jellyfin in the preinstalled Chrome and the official Jellyfin App. The Jellyfin UI worked, but when I went to play an episode it would just show the show background and not respond anymore.

    Does anyone have any ideas or know of some obscure client which supports older Android versions? It seems like a waste to get rid of the tablet, when all the main components are still perfect for watching media.

    Edit:
    I had completely forgotten the obvious solution: Kodi!
    Kodi with the JellyCon addon works great. The only important thing I had to change, was enabling force transcoding of h265 and av1 video in the JellyCon settings.

    view more: next ›