• 1 Post
  • 10 Comments
Joined 5 months ago
cake
Cake day: March 19th, 2024

help-circle
  • I’d lean towards the pi being the problem, but you can test the network throughput with iperf, and would want to test the videos outside of Kodi on the pi, so you could also check top and see what the processing looks like.

    If I remember my pi 4 hardware decoding specs correctly, I believe h.264, MPEG 2, and VC1, and some support for HEVC. If I had to guess, you may have some codecs that aren’t handled by hardware acceleration, and instead just CPU.

    My best rec would be to use either a dedicated stream box (like a fire stick, Nvidia shield, etc) which has better codec support, or pick up like a little Intel n100 based system, which will handle a drastically wider set of codecs with full acceleration support.

    Right now I’ve got a Roku and a Google TV Chromecast, and I’ve been trying with various environments on an old Lenovo m910q so I can find my favorite fit of UI/distro. The Roku and Chromecast never stutter, and I don’t do transcoding for inside the home. Works with 4K HDR HEVC no problem.

    Edit: Autocorrect annoyances.


  • Tiny/mini/micro makes up my server environment (and two customs using old cases and replaced parts).

    Storage is a 1520+ and the two customs, with the 1515+ for backups I don’t want to lose (syncs to two other locations).

    Tiny/mini/micro is the majority of compute tasks, mostly proxmox, LXC’s, and a few VMs.

    The little machines have plenty of processing power, usually nvme but I can add it on if needed. Combine it with network storage, and you don’t need anything else imo.

    Bonus is they are small and cheap as off lease machines being auctioned off.





  • Most mobile clients you’re going to get your search and browsing through OPDS - so a library and a search function, but no tag support. Just (afaik) author, title, publisher, year, etc.

    So that kind of fuzzy sorting is, at best, limited to the web interface for servers that support it (like Kavita). Which means browsing in almost any context native to a reader device/app is not going to support tagging.

    If that changes, then sure, it could be plenty useful as a single giant list with neatly browsable tags. As of what’s out there now and usable (again, afaik) it is not.


  • Kavita does that, which is what I use (though through the web interface, not using opds on an android app for example), but it would still make browsing just a giant single list.

    And I agree, fuzzy has value, which is why I don’t want to separate major things like Science Fiction vs Fantasy. But there isn’t exactly going to be significant overlap between historical romance novels and an instructional book on erlang, so that book on erlang is just going to get lost in the library.

    That’s why I separate, it’s just too much for a single large directory.