Skip to content

[removed] - #599

Merged
iwalton3 merged 2 commits into
masterfrom
qt6
Nov 23, 2025
Merged

[removed]#599
iwalton3 merged 2 commits into
masterfrom
qt6

Conversation

@andrewrabert

@andrewrabert andrewrabert commented Apr 19, 2024

Copy link
Copy Markdown

[removed]

@sevenrats

Copy link
Copy Markdown
Member

This branch is fully unsuitable for release, and releasing it would currently add no value to the ecosystem. Qt6 does not give us anything in a world where 5.15.11 exists. The most reasonable way forward is to ride Qt5 until compat loses support. Within that time we should have built an OSC per #537 or the related Qt Bug will have been fixed. Then we can port to the native API and at that point we can discuss sunsetting the Qt5 build. Migrating now would be way beyond premature imho.

@iwalton3

Copy link
Copy Markdown
Member

This needs to be held until we either:

  • reach feature parity with the 5.x branch
  • are forced to switch to it because the ecosystem around it breaks

Notably the rendering pipeline is completely busted and we're using a UI cutout workaround to make it even slightly work that kills all overlay menus and trick play in the player.

@iwalton3 iwalton3 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comment.

@sevenrats

Copy link
Copy Markdown
Member

some of these other changes are very good @nvllsvm, do you intend to open a new pr with them?

@satmandu

satmandu commented May 3, 2024

Copy link
Copy Markdown
Contributor

Would you please add these ubuntu packages to the list of required packages for building for QT6 in Readme.md?
qt6-5compat-dev qt6-base-dev qt6-base-private-devqt6-declarative-dev qt6-webchannel-dev qt6-webengine-dev

@kenden

kenden commented May 6, 2024

Copy link
Copy Markdown

This would help with the message

Uses an end-of-life runtime
The runtime used by this app is no longer receiving security updates

from https://flathub.org/apps/com.github.iwalton3.jellyfin-media-player

@sevenrats

Copy link
Copy Markdown
Member

@kenden
I suspect this has to do with the flatpak itself. Qt5 is not EoL for another 12 months, so, whatever runtime you have that is outdated is probably unrelated to this issue.

@kenden

kenden commented May 6, 2024

Copy link
Copy Markdown

Thanks @sevenrats I think this is actually described in this issue: flathub/com.github.iwalton3.jellyfin-media-player#41

@zjeffer zjeffer mentioned this pull request Mar 2, 2025
@Pentaphon

This comment was marked as off-topic.

@huantianad

This comment has been minimized.

@ItsLiyua

This comment was marked as off-topic.

@clhodapp

This comment has been minimized.

@ItsLiyua

This comment was marked as off-topic.

@GDBlaster

This comment has been minimized.

catbrained added a commit to catbrained/dotfiles that referenced this pull request Sep 20, 2025
JMP depends on qtwebengine 5.X which is marked as insecure.
There seems to be some work in the JMP repo to port things to Qt6, but
so far there doesn't appear to be any official releases with that,
despite the fact that Qt5 is EOL and being dropped from various distro's
repos.

I will drop the package for now. If they don't provide a release soon
I'll have to see whether I want to allow the insecure package or use
something else to watch stuff.

Related issues and PRs:
- NixOS/nixpkgs#437865
- jellyfin/jellyfin-desktop#282
- jellyfin/jellyfin-desktop#599
- jellyfin/jellyfin-desktop#844

Signed-off-by: Linda Siemons <linda@catbrained.dev>
@iwalton3

Copy link
Copy Markdown
Member

Ahh yes the positioning workaround fix. I was never happy with it because it broke thumbnail previews and drop-down menus, hence I basically tabled this project and decided to wait until I was forced to revisit it due to Qt 5 being end of life.

I consider a proper fix to be fix rendering with upstream (unlikely) or implement a completely custom player UI.

The latter is a lot of work, and honestly may make sense to switch to a better technical baseline if we abandon the main reason we use the abomination of a rendering pipeline this uses as it would add things like proper HDR and Dolby vision support. (In other words, there's a reason the upstream Plex Media Player application passed it's sell by date and this is likely it.)

In this way MPV Shim always had a better technical foundation but the player UI leaves a lot to be desired for normal users. (I did add trick play to that though, proving you can paper over a lot of UX issues with it with enough LUA scripts though.)

Andrew Rabert added 2 commits November 22, 2025 18:16
Co-authored by: Izzie Walton <ian@iwalton.com>
Co-authored by: Satadru Pramanik <satadru@gmail.com>
Co-authored by: sevenrats <sevenrats@tutanota.com>
Co-authored by: xB <65196493+xBiei@users.noreply.github.com>
Co-authored by: zjeffer <4633209+zjeffer@users.noreply.github.com>
@ItsLiyua

Copy link
Copy Markdown

I've seen you working on this and I just wanna say thank you! Sadly I lack the skill to help. Thanks for doing this!

Comment thread native/mpvVideoPlayer.js
Comment on lines +377 to +378
// MPV doesn't support secondary subtitles - no-op for compatibility
console.log('[MPV] setSecondarySubtitleStreamIndex not supported, ignoring index:', index);

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iwalton3
iwalton3 merged commit 9afbb79 into master Nov 23, 2025
1 check failed
@iwalton3
iwalton3 deleted the qt6 branch November 23, 2025 02:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants