Posts by ashlar

    I pre-ordered a Luma video processor, and wondering if I would really benefit from it with my projector.

    Sorry for the offtopic but... have you checked with them about DTS? Because for audio they state, and I quote: "Audio passthrough — byte for byte: LPCM to 7.1, Dolby Digital, Dolby Digital Plus and TrueHD with Atmos. Lip sync adjustment."

    No mention at all of DTS formats. Considering how LG is handling stuff, I wouldn't give that for granted.

    (but yeah, maybe that PR you've linked ends up solving the problem)

    If I understand what they're discussing correctly, it should implement stuff at kernel level. At that point it should (could?) work out of the box. Crossing fingers for you :)


    no I can't collaborate since I haven't got libreelec running :( (and I need to see it work and the AI doing what I ask it to and iterate) maybe when I get a USB I can play around with it. but if you can easily add my stuff using source code zip (attached) then that could work. please give it a try, just start with the ability to pick which menus load

    Got it. Thanks for sharing. It won't be today, it won't be tomorrow... but I'll look at it. I've also my eye on webOS YouTube development, since they take the leanback approach too, what they do we should be able to replicate as well.

    I'm having difficulty logging in my github right now, I plant to have PR to vacuumtube

    I kindly *beg* you to do that (PR, I mean).

    The less I have to "fight" Gemini chatting and battling with its context compression crap the better.

    I absolutely appreciate any and all contributions that anybody could bring to this. Or feel free to lift whatever you want from my builds for yours (I mean, it's implicit in the license and everything but, once more: I'm not a dev, I don't have any claim and I feel strongly about doing this just for me and whomever else might be interested in using it, however they see fit).


    hcliec001 thinking more about this, if you want to join forces I could make you a collaborator on my GitHub. I'd like to remain in charge of quality control and releases but you'd be able to fork there and we could work together instead of splitting development in different directions. PM me if interested. I don't guarantee full time involvement (absolutely not), nor I would demand anything from you. But I feel it would make sense to join our efforts.

    Nice work, thanks! One question, would be possible to have more auto translated subtitle to add? The smartube app can add, one default auto translate possibility, not just a few from the menu. thx

    I can investigate. It basically depends on what the "leanback" interface exposes, as this is not a "real" program, it's more of a wrapper that tricks http://www.youtube.com/tv in thinking we are accessing from an approved TV device.

    How do you guys navigate YT from the couch? Bluetooth keyboard+mouse?

    Usually I control my Kodi with the TV remote via CEC or with the Yaste phone app, but when launching Vacuummtube, the LE instance is killed or suspended and these interfaces are no longer exposed, so I can't control YT, nor go back to LE.

    Is there a workaround to this? In a future release could this kind of support be implemented?

    First of all: https://github.com/LibreELEC/LibreELEC.tv/pull/12013

    I personally use FLIRC USB, so it just emulates the keyboard with a programmable IR remote. In your case, there is nothing I could do to have the apps working, since, as you stated, they rely on Kodi being available to connect to and, while using flatpaks, Kodi is not operative. As far as CEC is concerned... what PC are you using that lets you use full CEC capabilities? I don't doubt it exists but I'm interested in the exact hardware setup to investigate.

    The real problem for me is that I have two machines to test with. One NUC 11 (CEC on/off functionality and that's it) and one HTPC with Nvidia RTX 4070 (that I don't even know if it supports CEC at all). So even if I were to give this a try... it would be impossible for me to test. And to do it blindly while providing test builds for external testers... it would take ages.

    A really quick check tells me that this theoretically could be possible to achieve. But with no hardware for me to test with... nigh impossible. :(


    I have not tested if the addon remains compatible with CroqueMr's R1.0.1 RC1 but I intend to support just his finalized releases, no RCs. Just saying. So absolutely do point out bugs and incompatibilities but fixes will be down the road if they concern new LibreELEC releases.

    I do this through Gemini, with no agentic access, so it's really time consuming, even for little work.

    I tried HLG -> DV, but unfortunately the GPU hits 100% usage and it stutters.

    Tried HLG-->DV on my NUC 11 i3 and it works fine. GPU at about 70%, no dropped frames.

    I think it would be nice if the upscaler in use was displayed somewhere in the O player info window.

    And I still believe there should be rules based selection of scalers. But I'll work on something and we'll see. Maybe I'll convince you, CroqueMr :D

    One new problem I've just discovered with the GMKTec K12 is if you do turn off HDMI CEC in the bios it seems to cause other devices on your HDMI chain to also not be able to use CEC.

    Year after year after year I'm constantly astonished by how badly the HDMI consortium managed to enforce their "standard". It's breath taking.
    Thanks for reporting this.

    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).

    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

    Are you planning to dual boot Windows/LE or why the more than 16GB RAM? CroqueMr has stated that 4GB will be enough, my pc's that run LE DV with 16GB RAM only uses 15% of it.

    I wonder how moderate to heavy usage of the Firefox flatpak addon might change this outlook on RAM. That's my main reason for wanting a decent amount of RAM onboard.


    But I will add some CNN upscaling algorithm in the futur

    On top of what already exists in your 1.0 release, you mean? Sorry for the offtopic.

    I've had a look into cec on a intel nuc. Don't think the code is there to support it, but the hardware seems to be able to transmit any literally any cec message you would like and receive a response - so you could control your tv volume, etc. What is does not seem capable of doing being set up to listen for and recieve cec data like button presses from a tv remote.

    From my investigations in the past couple of weeks I don't think you got that right, as I've only read about CEC on/off functionality. If you have sources stating the opposite, I'd be happy to have them (not ironical, please post them :) ).

    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.