VacuumTube with Multichannel Audio and Auto HDR Switching

  • ashlar it would be best if you created a separate thread for your vaccuumtube changes, we can then ask a forum mod (eg Da Flex or CvH ) to move the posts over there.

    so long,

    Hias

    Oh... sorry, I did not want to hijack the discussion and opening a new discussion seemed presumptuous on my side, since I really haven't done much.

  • Quote

    i would be open to a pull request for this but it modifies chromium and ffmpeg which i can't reasonably maintain on my own. would love if i could support this without having to modify chromium :(

    Full multichannel audio compatibility through E-AC3 support · Issue #301 · shy1132/VacuumTube
    I leave this here: https://github.com/atrugiel69/vacuumtube-5.1-eac3 I did it for LibreELEC but I suppose the same approach could be taken for all platforms.…
    github.com

    no E-AC3 support :(

  • I just noticed Vacuumtube version 2.1.0 has been released with bumped electron and (hopefully) working multi-channel support.

    As the developer explained (and I was aware of, hence why I did not create a pull request), for this to work you have to compile Electron in custom form. He cannot be burdened with this thus, understandably, he won't include it.

    All hope is not lost, as Thorium's developer announced he is going to make available custom builds of Electron with AC3/E-AC3 active. I'm keeping his repository monitored and we'll see...

  • Working on HDR autoswitching. It needs Hyprland instead of labwc but it can be applied just to VacuumTube, leaving the other flatpaks working normally. Starts in SDR, switches to HDR when playing HDR content, switches back to SDR when stopping playback and returning to the GUI.

    I have it already working locally but I'll put up some install files later for others to test/play with it.

  • Working on HDR autoswitching. It needs Hyprland instead of labwc but it can be applied just to VacuumTube, leaving the other flatpaks working normally. Starts in SDR, switches to HDR when playing HDR content, switches back to SDR when stopping playback and returning to the GUI.

    I have it already working locally but I'll put up some install files later for others to test/play with it.

    damn, this is great! awesome work!

  • Here it is: https://github.com/atrugiel69/vacuumtubemod

    It was built against CroqueMR DV-R1.0.0-RC4-Preview-Update3. I hope it works with the current release.

    There are clear (I hope) instructions for installation on GitHub.


    HiassofT maybe this latest development could be of interest to you. Not necessarily to bring everything over to the official release but, I don't know, as inspiration. I obviously couldn't have done anything without your development. I'm just a user with too much time and Gemini (not even an agentic AI, you can imagine the copy and paste involved in doing this), absolutely NOT a coder.

    Edited once, last by ashlar: Merged a post created by ashlar into this post. (November 17, 2026 at 1:18 AM).

  • Here it is: https://github.com/atrugiel69/vacuumtubemod

    It was built against CroqueMR DV-R1.0.0-RC4-Preview-Update3. I hope it works with the current release.

    There are clear (I hope) instructions for installation on GitHub.


    HiassofT maybe this latest development could be of interest to you. Not necessarily to bring everything over to the official release but, I don't know, as inspiration. I obviously couldn't have done anything without your development. I'm just a user with too much time and Gemini (not even an agentic AI, you can imagine the copy and paste involved in doing this), absolutely NOT a coder.

    One suggestion would be to build your VacuumTube fork (with your electron and ffmpeg patches) as a Flatpak which you can just install normally, rather than having some patching process the modifies the already installed version.

    That way someone could use your Flatpak on Linux or in LibreElec without the Hyprland session if they don't want HDR but do want to try EAC3.

  • One suggestion would be to build your VacuumTube fork (with your electron and ffmpeg patches) as a Flatpak which you can just install normally, rather than having some patching process the modifies the already installed version.

    That way someone could use your Flatpak on Linux or in LibreElec without the Hyprland session if they don't want HDR but do want to try EAC3.

    Considering that Hyprland usage is limited to the specific vacuumetubemod addon, I don't see much to gain. If somebody does not want to install the modded version (which anyway can coexist with the official release), I made available the patches and binaries to do so.

    Re-reading what you just wrote, I am unsure whether you checked the new page I posted. The new page provides instructions to install two addons (read the instructions for the order of installation) that lead to the vacuumtubemod to be installed on LE. It can coexist with the regular vacuumtube flatpak (although, at least currently, I don't see the advantage in keeping both).

    Having a version of the addon with just EAC3 is not something I'm particulary interested in doing. As mentioned above, patches are available in a separate repository if somebody wants to do that (but why, considering that hyprland is totally inactive until vacuumtubemod is launched?).

    Also, and most importantly, if the official devs want to lift everything and bring it to the official addon, I'd be simply honored. I have no ambition here, I'm just doing something I wanted to use myself, even just for testing the limits of what I could achieve through Gemini in non-agentic mode.

    I hope my answer is clear but in case it isn't, absolutely feel free to ask further questions. :)

    I would really appreciate if somebody using regular builds (not CroqueMR's) could test this.

  • I've read your page and reviewed your code, I'm simply offering a cleaner way for you to achieve the same thing you already have.

    Currently your Flatpak.vacuumtubemod has lots of custom code to download and patch the normal VacuumTube flatpak. You can just build a Flatpak file with your patches, host that on your GitHub and get your add-on to fetch and install that as a normal Flatpak, no vacuumtuberuntime-x86_64.tar.gz needed.

    Your free to ignore me obviously, just trying to offer some advice.

  • I've read your page and reviewed your code, I'm simply offering a cleaner way for you to achieve the same thing you already have.

    Currently your Flatpak.vacuumtubemod has lots of custom code to download and patch the normal VacuumTube flatpak. You can just build a Flatpak file with your patches, host that on your GitHub and get your add-on to fetch and install that as a normal Flatpak, no vacuumtuberuntime-x86_64.tar.gz needed.

    Your free to ignore me obviously, just trying to offer some advice.

    Sure. But this does not have much to do with isolating AC3/E-AC3 compatibility from HDR switching functionality. Or am I missing something? I absolutely do not want to ignore you, I hope I haven't given you that impression. :)

    EDIT: It might well be that I wanted to avoid having to set up a flatpak build environment but, as I stated, I am not a developer. I'm learning things as I go. Maybe I already have it setup for doing what I've done so far... if only I was a dev, I'd knew it LOL

    Edited once, last by ashlar (November 17, 2026 at 3:43 PM).

  • Sure. But this does not have much to do with isolating AC3/E-AC3 compatibility from HDR switching functionality. Or am I missing something? I absolutely do not want to ignore you, I hope I haven't given you that impression. :)

    It wouldn't change functionality at all, I'm just suggesting something that would make your code simper and more inline with how Flatpaks are designed to function. Their whole point is to bundle applications and dependencies together isolated from the rest of the system, exactly what you are doing, and be portable and installable on a wide range of systems.

    But it's fine, I understand this is more of a proof of concept and you just want something working, rather than doing it right.

    Edit:

    It's very easy to build a Flatpak with a custom electron build just use a command such as:

    Code
    npx electron-builder --linux flatpak \
      -c.electronDist="<path to custom build" \
      -c.flatpak.runtimeVersion=25.08 \
      -c.flatpak.baseVersion=25.08

    Edited once, last by nissel (November 17, 2026 at 4:18 PM).

  • But it's fine, I understand this is more of a proof of concept and you just want something working, rather than doing it right.

    I am honestly sorry to read this. I clearly specified that I wasn't ignoring you, so I don't see why you say that I'm not interested in doing it right. I am learning, I stated so multiple times. Be patient with me, if you can, and don't assume that I am in some sort of passive-aggressive mode, because I really am not. I will investigate what you are suggesting and, if it's within my (truly limited) capabilities, I'll adopt it. I made an effort to build the addons in a way that left untouched the rest of the system and that could coexist with the official vaccumtube addon, so I would have thought it was obvious I was interested in "doing it right".

    If all I needed was something that worked, I had that already on my machine before going through all the trouble (and hours of work) needed to publish on GitHub the installable addons.


    Currently your Flatpak.vacuumtubemod has lots of custom code to download and patch the normal VacuumTube flatpak. You can just build a Flatpak file with your patches, host that on your GitHub and get your add-on to fetch and install that as a normal Flatpak, no vacuumtuberuntime-x86_64.tar.gz needed.

    I've investigated on this.

    default.py does not download or patch the upstream rocks.shy.VacuumTube Flatpak. My build pipeline already pre-builds the patched Electron + FFmpeg runtime into vacuumtube-mod-runtime-x86_64.tar.gz, and default.py extracts that tarball into addon_data and generates a thin Flatpak wrapper around it.

    Having said this, replacing tarball+wrapper with a single self-contained flatpak might be cleaner design and I do not exclude to do this, maybe the first time I will need to update the addon, for whatever reason (I have in mind to add automatic refresh rate switching but I have yet to begin my investigation for that).

    Edited once, last by ashlar: Merged a post created by ashlar into this post. (November 17, 2026 at 4:44 PM).