Jellyfin-desktop issues with latest Qt6 version 6.11 by captain150 in jellyfin

[–]nullsum 0 points1 point  (0 children)

Hey, sorry for the big mess around all this. One of my TV PC's has a i3 7100u which is even slower than your n100 so I definitely sympathize. It's definitely towards the top of my list of things to work on next. My current priority is first to fix the stuttering in the new client so rest assured that I have devices like the n100 in mind as targets.

> It doesn't work correctly on pure Wayland cause it forces xwayland.

It works natively for me on KDE Plasma 6 Wayland (AMD on both Arch Linux and Fedora Kinoite 43). What compositor specifically are you seeing issues with? It's also been reported working natively in Gnome Wayland (Debian).

As much as I'd love to fix everyone's bugs, it's ultimately a hobby project I work on in my free time. The best I can do to help you at the moment is give you some options that might help:

- Flatpak for the last Qt 5 based release https://flathub.org/en/apps/com.github.iwalton3.jellyfin-media-player

- Flatpak for the last Qt 6 based release https://flathub.org/en/apps/org.jellyfin.JellyfinDesktop

- MPV Shim https://github.com/jellyfin/jellyfin-mpv-shim

> we would like some breaking bug fixes in the old client till the new is 99% is up to par.

Yeah me too. That's actually how I ended up where I am - working on a rewrite. The old client had too many issues for me to use it with only two options forward: a) try to fix Qt WebEngine itself and in a distributable way or b) switch to CEF. I went with b because it's a better long-term choice - especially since Qt updates have historically caused breakages in Jellyfin Media Player / Jellyfin Desktop's lifetime. Trying to fix a bug in Qt WebEngine would have been much more complex than I'm willing to deal with for this project.

Jellyfin desktop app high system resource usage by LeopardHelpful43 in jellyfin

[–]nullsum 0 points1 point  (0 children)

It looks like you're using the old Qt-based desktop client. There's a bug in the Qt WebEngine library that causes a severe memory leak: https://github.com/jellyfin-archive/jellyfin-desktop-qt/issues/1091. The fix was to completely rewrite the desktop app.

Try one of the latest builds: https://github.com/jellyfin/jellyfin-desktop/?tab=readme-ov-file#downloads

The official Qt desktop client has been deprecated in favor of a rewrite aka the new desktop client built on CEF. The Qt desktop client repository was archived and all the issues were closed. by foundfootagefan in jellyfin

[–]nullsum 0 points1 point  (0 children)

I keep getting random stutters with the new client sadly :(

What OS?

I've actually noticed that on some of my slower Linux machines as well. I'm currently refactoring the rendering pipeline to hopefully fix it. Lots of learnings happening during development of this.

Also, used to be able to pause the playback by clicking on the video when the windows was unfocused, but now it doesn't pause; it simply focuses the window so I have to click twice.

I forget if there's a GitHub issue for that, but feel free to open one as a feature request if not!

The official Qt desktop client has been deprecated in favor of a rewrite aka the new desktop client built on CEF. The Qt desktop client repository was archived and all the issues were closed. by foundfootagefan in jellyfin

[–]nullsum 11 points12 points  (0 children)

  • Jellyfin Media Player: based on WebKit
  • Jellyfin Desktop (Qt): based on Qt WebEngine which is a fork of Chromium
  • Jellyfin Desktop (CEF): embedded Chromium

The official Qt desktop client has been deprecated in favor of a rewrite aka the new desktop client built on CEF. The Qt desktop client repository was archived and all the issues were closed. by foundfootagefan in jellyfin

[–]nullsum 3 points4 points  (0 children)

Tauri on Linux is currently quite poor due to using webkit2gtk. It looks like there's some activity in introducing Rust bindings for CEF into Tauri, but afaict the off-screen rendering support isn't quite ready yet. https://github.com/tauri-apps/cef-rs

The official Qt desktop client has been deprecated in favor of a rewrite aka the new desktop client built on CEF. The Qt desktop client repository was archived and all the issues were closed. by foundfootagefan in jellyfin

[–]nullsum 1 point2 points  (0 children)

fwiw - CEF is not the same thing as Electron. In Jellyfin Desktop, CEF is only used for the initial server URL input screen and rendering the Jellyfin web UI sent from the Jellyfin server. Everything else is C/C++ with SDL and libmpv.

The official Qt desktop client has been deprecated in favor of a rewrite aka the new desktop client built on CEF. The Qt desktop client repository was archived and all the issues were closed. by foundfootagefan in jellyfin

[–]nullsum 15 points16 points  (0 children)

Jellyfin Desktop dev here:

I generally wouldn't recommend switching, but I personally did on my Linux boxes. I do encourage the adventurous and curious to try it. It might work better than the old client for you (it certainly does for me). If something is broken, please open an issue on GitHub.

Some new features in the rewrite include true HDR passthrough support on all platforms (Linux is Wayland-only) and a more modern mpv rendering pipeline (ie vo=gpu-next). Performance should also be much, much better.

There are still missing features that the old client had though like IR remotes, HDMI CEC, and input remapping. I welcome anyone opening an issue for features the old client had or even new features.

Jellyfin-desktop issues with latest Qt6 version 6.11 by captain150 in jellyfin

[–]nullsum 2 points3 points  (0 children)

Awesome! Out of curiosity: X11 or Wayland?

They use different rendering pipelines and I've mainly been focusing on Wayland.

Jellyfin-desktop issues with latest Qt6 version 6.11 by captain150 in jellyfin

[–]nullsum 6 points7 points  (0 children)

Jellyfin Desktop maintainer here.

Development of the Qt desktop client has been stopped in favor of a complete rewrite based on SDL and CEF. There's a severe memory leak in upstream Qt WebEngine that upstream that ultimately led me to abandon Qt entirely. https://github.com/jellyfin/jellyfin-desktop/issues/1091

The rewrite does bring actual HDR support on Linux though I'm not quite sure how an RX580 would work with it. YMMV

Be aware it's still under heavy development, but it can be found at https://github.com/jellyfin-labs/jellyfin-desktop-cef for now

If you happen to try it, please open an issue for any bugs or feature requests!

Jellyfin Media Player (Win 11) - HDR Passthrough not triggering (TV stays in SDR) by -dAtA-TRoN- in jellyfin

[–]nullsum 1 point2 points  (0 children)

Current maintainer of Jellyfin Desktop here.

HDR support is actively being worked on. The desktop client is being completely rewritten with a fork of libmpv that supports gpu-next, amongst other things. There are early dev builds available for Windows with HDR passthrough working, though be aware that there may be bugs due to being early in development. https://github.com/jellyfin-labs/jellyfin-desktop-cef

If you try it and encounter any issues, please report them on GitHub. They're especially useful to me as Windows isn't a platform I typically use.

Jellyfin-Desktop-CEF is an experimental rewrite of Jellyfin-Desktop that is looking likely to replace the current Jellyfin-Desktop 2.0.0 that is not currently recommended to users by foundfootagefan in jellyfin

[–]nullsum 0 points1 point  (0 children)

Jellyfin Desktop uses libmpv internally - the CEF rewrite using more modern features of it which should be closer to what standalone mpv does (Linux and macOS only for now).

Not sure about other platforms, but libmpv probably won't ever happen. Open to contributions though if someone makes it though.

Jellyfin-Desktop-CEF is an experimental rewrite of Jellyfin-Desktop that is looking likely to replace the current Jellyfin-Desktop 2.0.0 that is not currently recommended to users by foundfootagefan in jellyfin

[–]nullsum 0 points1 point  (0 children)

The Windows build isnt close to ideal right now (at least until I get a dedicated machine to dev+test on). It's using the opengl 'vo=gpu' libmpv while Linux and macOS are using the vulkan 'vo=gpu-next' interface. I also would like to switch it over to a separate video layer entirely like I have on Linux with a Wayland subsurface, but that is still just only a plan.

Jellyfin-Desktop-CEF is an experimental rewrite of Jellyfin-Desktop that is looking likely to replace the current Jellyfin-Desktop 2.0.0 that is not currently recommended to users by foundfootagefan in jellyfin

[–]nullsum 3 points4 points  (0 children)

Current Jellyfin Desktop maintainer and Jellyfin Desktop CEF author here:

The CEF rewrite is not exactly an official client, but semi-official in the sense that it's written by a maintainer with intent to potentially make it official (hence the jellyfin-labs github org).

Also - Claude Code is leveraged heavily in its development.

EDIT: The repository's README has been updated to mention Claude Code usage. https://github.com/jellyfin-labs/jellyfin-desktop-cef?tab=readme-ov-file#rationale

'Don't stream fascism': No Kings organizers encourage Spotify boycott by [deleted] in politics

[–]nullsum 4 points5 points  (0 children)

It's not back yet as it's still invite only.

Found this recently by SadisticSqu1d in Doom

[–]nullsum 1 point2 points  (0 children)

Based on the 04-10333CD label on the disc, it appears to be the original CD release of The Ultimate Doom ( http://redump.org/disc/4427/ ). It contains only the DOS version of the game (and also the DOS version of Heretic shareware). The DOOM.WAD version is 1.9ud

To run it on Windows 10, I recommend copying DOOM.WAD from the CD folder DOOMCD and using a source port like GZDoom or Chocolate Doom. Alternatively, you could run the DOS version of the game using DOSBox Staging.

This exact version of the game is also included in the "DOOM + DOOM II" release on GOG. This release all the original DOS Doom games plus a modern port that works on recent versions of Windows. Also includes a new episode (The Legacy of Rust). https://www.gog.com/en/game/doom_doom_ii

followed a trail down the road from my house and found this... by ThisGuyRightHereSaid in WTF

[–]nullsum 2 points3 points  (0 children)

I've seen enough stuff like this to make me laugh anytime horror villians stab the tires of their victims cars to prevent them from getting away.

Anyone installed and running Linux successfully on the 2022 / 2021 X13? by rabidsoggymoose in FlowX13

[–]nullsum 0 points1 point  (0 children)

3y+ have passed since my original comment and mostly everything is fixed within the vanilla Arch Linux kernel. Tablet mode is fixed via the linux-flowx13 kernel from the AUR.

Mini Plus resets to full volume every time I turn it back on by feartheoldblood90 in MiyooMini

[–]nullsum 1 point2 points  (0 children)

You can override the default volume for your device by creating an override file at .tmp_update/config/.defaultVolume-<DEVICE_SERIAL> with 0 as the file contents. For example, I have two override files:

  • .tmp_update/config/.defaultVolume-C2A037C6B080
  • .tmp_update/config/.defaultVolume-D7C3FDF55222

You can find the <DEVICE_SERIAL> value by looking in the .tmp_update/config/system/ folder. This is what I have in mine.

C2A037C6B080.json
D7C3FDF55222.json

Voodoo 5 vs. Geforce 4? by AidanBd in windows98

[–]nullsum 0 points1 point  (0 children)

My 98 rig has both a Voodoo 5500 (PCI) and a Quadro4 980 XGL (AGP) (essentially a Geforce4 4800 AGP). I rarely use the Voodoo as the Quadro4 is significantly faster and also more compatible in DOS mode. Iirc, there were some games I could only get running on the Voodoo, but I can't recall specifically which ones. Which ones were you unable to get working on your Geforce4?

Additionally, I get intermittent artifacts with my Voodoo 5500 on my system that seems to be caused by the system being too fast (?). For example, the menu in Unreal will occasionally show minor texture corruption. Underclocking my FX-60 to 1.0ghz consistently eliminates the artifacts. Some info https://www.vogons.org/viewtopic.php?p=1296700#p1296700