Jellyfin

Why can't this piece of shit natively handle fricking DVD / BR subtitles (DVDSUB, PGSSUB)? Why should I waste compute on a fricking media server just for transcoding some burned subtitles (therefore ruining the image quality)?

>inb4 it's hard
Plex has been handling this for at least 2 years. Also this exists: https://github.com/MathNuts/SUPtitles

Unattended Children Pitbull Club Shirt $21.68

The Kind of Tired That Sleep Won’t Fix Shirt $21.68

Unattended Children Pitbull Club Shirt $21.68

  1. 1 week ago
    Anonymous

    good idea, all you have to do now is implement the feature and submit a merge request

    • 1 week ago
      Anonymous

      >implement the feature
      I had a look at the codebase looking for relevant parts and the whole thing is a fricking JS nightmare mess. Not to mention both the client and server have to be changed (since the server checks whether the sub is compatible and does the transcoding via ffmpeg), so both parts have to be changed. Not to mention also that the custom html player alone is hundreds and hundreds of lines of spaghetti code and if/else statements to handle every possible fricking usecase.

      Web "apps" truly were a mistake.

  2. 1 week ago
    Anonymous

    then do it yourself or stop crying about your poorgay Raspberry Pi dying over some pgs subs you b***hass poorgay homie

    • 1 week ago
      Anonymous

      To put it differently, understanding the relevant parts of the codebase alone from scratch would take me fricking weeks, which is way more than the cumulated time I will spend in my entire life looking for SRT subtitles manually online.

      You see, this is the problem with open source software. They are often maintained by a handful of people who are the only ones to be able to meaningfully and majorly upgrade the codebase. I'm not talking about changing fricking colors, fonts, translations, or adding a simple field and button in the configuration panel. Not to say what I'm asking for is complicated, should be quite easy if the codebase wasn't such a disaster.

      >raspberry pi
      I'm using a fricking HP Elitedesk. Are you telling me I need to buy a fricking 4090 for that? Also the transcoding fails in the middle of the movies every fricking time (not a CPU / disk / RAM issue, it's a software bug that is still not fixed).

  3. 1 week ago
    Anonymous

    ffmpeg -i file -scodec mov_text outputfile
    Use a simple script and BAM, all your fricking files are transcoded fast as frick

    • 1 week ago
      Anonymous

      >ffmpeg -i file -scodec mov_text outputfile
      homie this is cool and all but the main goal when using jellyfin, radarr and stuff is not having to mess with the terminal (guess I'm moronic thinking a UI would help the UX to be smoother)

      • 1 week ago
        Anonymous

        The problem is that on standard web browsers such as Chrome (or my WebOS LG TV), only SRT (maybe ASS as well) is supported. PGSSUB and DVDSUB are third-class citizens, while it is has been the standard format of DVD and BR rips for decades now. VLC and MPV can handle it without a problem.

        Why can't Jellyfin? Short answer: it's a fricking web-"app".

        I end up mass-editing files after downloading because not all formats and shit are suported on all devices I use, sad but I want my collection to be perfect.
        In your case, you could mass edit your files like that, imagine your input file having:
        0:video
        1:language
        2:subtitle_pgssub

        And end up with the file:
        0:video
        1:language
        2:subtitle_pgssub
        3:subtitle_srt

        Using -vcodec copy -acodec copy -scodec mov_text would only transform the subtitles without re-encoding the audio and video, the only limiting factor would be your disk speed.
        Do some tests and you could convert your entire library deleting the previous file automatically in no time.

        • 1 week ago
          Anonymous

          The thing is I'm not even asking my collection to be "perfect" (I'm not that autistic), just for shit to be working. If transcoding was transparent and light / instantaneous I wouldn't even care. But the shit is slow as frick even on a modern CPU and crashes when watching a movie. Amazing user experience they got here.

          In your case, how do you find the right SRT file? That's right, you have to spend 15 minutes downloading various subs and testing them until you find the right one. While the true, matching PGSSUB exists already with your downloaded kino.

        • 1 week ago
          Anonymous

          >scodec
          Maybe I misunderstood, is this doing some OCR under the roof? If yes, how's the accuracy?

          • 1 week ago
            Anonymous

            Extract with ffmpeg, convert with subtitleedit, remux with ffmpeg
            I think everything can be automated in one script

          • 1 week ago
            Anonymous

            >subtitleedit
            >cli fork uses .NET 6 and repo has 15 stars
            It's over.JA2M

  4. 1 week ago
    Anonymous

    whats the problem

    • 1 week ago
      Anonymous

      The problem is that on standard web browsers such as Chrome (or my WebOS LG TV), only SRT (maybe ASS as well) is supported. PGSSUB and DVDSUB are third-class citizens, while it is has been the standard format of DVD and BR rips for decades now. VLC and MPV can handle it without a problem.

      Why can't Jellyfin? Short answer: it's a fricking web-"app".

      • 1 week ago
        Anonymous

        The real problem is your devices not supporting the format, because muy licensing fees.
        Can't you just jailbreak your tv and install whatever the frick you want? There isn't any app that natively supports them?

        • 1 week ago
          Anonymous

          This is true to some extent. My TV is already rooted, so I can install Kodi etc. watever. But the interface is incredibly shitty and could not yet install the Jellyfin add-on (don't know how it works).

          Any app you would recommend for WebOS?

          • 1 week ago
            Anonymous

            If there isn't a jellyfin app for that then you're out of luck, try to ask devs to make one

      • 1 week ago
        Anonymous

        Are Jellyfin still doing that deep rewrite of the entire codebase, maybe it'll get fixed in that process?

        If the browser (chrome) don't support the subtitle format, then jellyfin can't really implement it. Its not a jellyfin problem, its a platform problem.

        • 1 week ago
          Anonymous

          As I mentioned in my original post, some guy easily hacked something with pure JS to display the image subtitles on top of a video played with HTML. This works with any JS-compliant browser.

        • 1 week ago
          Anonymous

          As I mentioned in my original post, some guy easily hacked something with pure JS to display the image subtitles on top of a video played with HTML. This works with any JS-compliant browser.

          (cont.)
          Also, Plex handles it and has been for years now. Works on my TV. But don't want to support Plex.

      • 1 week ago
        Anonymous

        You're an idiot. Jellyfin is the server. Then you have clients which are responsible for the subtitles. The client doesn't have to be "a web app". You don't even possess the least amount of knowledge required to talk or operate something like Jellyfin, yet you boast on here as if you're some programming ace.
        Hint: ask your mom to abort you and never post online again and waste people's bandwidth.

        [...]
        (cont.)
        Also, Plex handles it and has been for years now. Works on my TV. But don't want to support Plex.

        >gets told it's the browser's fault
        >but it works on my TV!
        You truly are an idiot.

        • 1 week ago
          Anonymous

          Jellyfin is both a client AND a server, Black person. Also the Jellyfin WebOS client is simply a wrapper for the regular Jellyfin web client, which IS a webapp. It is literally written in JS, and runs within a browser.

          They could have written the WebOS client differently, like with an actual programming language, you know? But no, they had to stay lazy and simply wrap their shitty web-app instead. Not to mention the fact that the actual web client (which runs on your Dekstop) does not support the most basic subtitle format in 2024 is completely moronic. Keep defending this shit you moronic Black person. I'm not saying LG OS and their subhuman korean software is also not moronic btw.

          • 1 week ago
            Anonymous

            No, the clients are:
            >jellyfin-web
            >jellyfin-androidtv
            >jellyfin-android
            >jellyfin-roku
            >jellyfin-chromecast

            Regarding the subtitles: works on my machine, because I know how to use the software and I can read its documentation and find a solution which works for me. If it doesn't, I move on and look for something else. I have, like most people, superior subtitles thanks to Bazarr. You most likely download it manually. Everyone who isn't technologically moronic here is lmaoing @ ur life.

  5. 1 week ago
    Anonymous

    Use kodi and just play the file natively without transcoding. Never understood why ppl bother with upnp/dlna jankware.

    • 1 week ago
      Anonymous

      Tried Kodi on my TV, and it absolutely can natively handle every sub indeed. Of course the UI is atrocious and somewhat even worse than Windows pajeet stuff.

      Guess you're either stuck with slick-UI JS homosexuals and a spaghetti codebase, or competent geeks incapable of creating a decent UI.

    • 1 week ago
      Anonymous

      i guess it's so you can get your library everywhere

      although maybe you could always vpn to your home network

  6. 1 week ago
    Anonymous

    Are Jellyfin still doing that deep rewrite of the entire codebase, maybe it'll get fixed in that process?

  7. 1 week ago
    Anonymous

    >THIS SOFTWARE IS SHIT
    >keeps using it
    >doesn't stop using it
    >doesn't use anything else
    have a nice day moron

Your email address will not be published. Required fields are marked *