Thanks, it’ll be earlier to iron out issues when I get watch history syncing working so I can spend more time using it to reproduce the the edge cases I get.

I think this is the tool you are looking for: https://github.com/luigi311/JellyPlex-Watched

I haven’t used it myself but I plan on it eventually when I do make the switch.

Same, I just placed an order for the 2e! I didn’t realize they opened up orders for both when they said eye tracking in Q3, I guess that’ll just be a software update. I’m hyped! I have to figure out what audio solution I’ll use - I like the Index speakers not touching the ears, I tend to quickly get ear pain with even gentle pressure from on-ears so I’m not sure about the official audio strap. If there was a way to attach the index head strap to the beyond that would be perfect for me.

Wow, I didn’t know what to expect when support told me yesterday that I should hold off on purchasing for another couple days, but this seems to solve just about every concern I had about the BSB1.

I share my headset so adjustable IPD means I don’t need to keep my old headset around as a loaner.

Lots of reviews mentioned the tiny sweet spot, it sounds like the sweet spot is massive now reducing the need to get the exact right face cushion thickness

Lots of reviews also complained about the glare when not in the exact right position, also sounds like that is fixed

I was also a little concerned about FOV compared to the index, it appears they’re about the same now. It also helps that I’m used to using the index with the lenses adjusted as far away as possible in order to fit my glasses, so I’m sure the BSB2 with prescription inserts can’t be worse than what I have now.

The only downside seems to be that adjusting ipd still requires manually entering in what you set it to - hopefully it’s easy to accurately read out what your adjustment is because that sounds a little error-prone if you’re passing the headset around at a social gathering (a frequent occurrence for me)

I’m planning on replacing my index with the eye tracking variant when that happens.

Gotcha, I’ve never actually considered the bandwidth limits. It looks like digitalocean includes 1TB per month and I used 242GB last month. If I ever get close to the limit I will just spin up another droplet. I don’t think I would even need to load balance unless the first one is struggling since the bandwidth allowance across all droplets is pooled together.

If you aren’t already using a reverse proxy, then do you currently just port forward or use the Plex relay? The only reason I use one is because of CGNAT. Before I moved to a place with only CGNAT I port forwarded for both Plex and Jellyfin.

We’re seeing this at work too - our public git frontend is constantly getting scraped as well as our self hosted issue tracker. We had to spend days working on fail2ban and other kinds of tools to mitigate all the traffic that’s adding tons of load to our instances, which otherwise would easily be able to handle the handful of employees who actually use these systems.

In case this helps as a reference point, I use a $5 digital ocean droplet as my Plex and Jellyfin reverse proxy and it seems to handle the traffic of 3-5 simultaneous streams just fine. I use Haproxy in tcp mode (so no http interpreting, just passing packets) in an attempt to keep the CPU load minimal and just make it a pure I/O task.

Then we’ll have to disagree about that - imo this is the perfect place to discuss Plex alternatives and what features are keeping us on Plex. I think this discussion needs to happen if we want to learn how to create viable alternatives.

I especially want to talk about this because I personally want nothing more than to switch myself and everyone who I share my library with onto Jellyfin, and I don’t think that will happen unless we talk about what’s missing. I’m personally invested in Jellyfin enough to donate to apps I don’t even use in hopes that they will improve.

Nothing is missing per se, but mysteriously 100% of my friends prefer the Plex UI. I’d have to ask them why. I find the jellyfin UI a little bare but serviceable, my only real complaint is the mysterious transcoder errors.

And I’m sure it is just a misconfiguration! The problem is I hardly changed any settings from stock, aside from enabling hardware transcoding for Intel quick sync. I have an Intel Nuc10i7FNK that has a comet lake i7-10710U so based on the table on Wikipedia which lists which generations of quick sync support what codecs, I set Jellyfin’s hardware acceleration to QSV with QSV device set to blank (it works and I can see the activity using the Intel quick sync top command - I forget what the command is but I verified it when I set it up so it seems it’s auto detecting it fine), and enabled H264, HEVC, Mpeg2, VC1, VP8, VP9, HEVC 10bit, and VP9 10 bit. Leaving 12 bit and all of AV1 deselected which seems to match what isn’t available for decode according to the Wikipedia article. I left low power HW encoder off and enabled VPP with gain 28 and contrast gain 1, regular tone mapping disabled, tone mapping algorithm the default of bt.2390 and all the other settings left on default.

I know jellyfin is working on auto detecting the hardware acceleration settings so I don’t hold it against them at all. I should also mention that the file that wouldn’t play before plays fine now, so it doesn’t seem like there’s a specific file that causes issues but an intermittent issue that causes transcoder errors. The file that wouldn’t play before is just 8bit HEVC with aac2.0 and English srt subs.

I welcome any tips you have - one issue I have when looking for help with Jellyfin is that people see users asking for help as a challenge to “prove them wrong”, which is frustrating (and ironically sometimes how people approach proselytizing the fediverse). I genuinely want Jellyfin to be good and to use it, which is why I keep an updated jellyfin container running along side my Plex container, I have basically every jellyfin app installed on all my devices so I can keep up with their development, and I donate to developers of those apps even though they aren’t complete enough to use in the case of Findroid. I would have already opened an issue for jellyfin web if it was easy to reproduce, but like I said I haven’t had much time to troubleshoot between job and working on the arrstack so this is all the details I have right now.

I just set up traefik for both Plex and jellyfin - the config is almost identical. Unfortunately none of my friends choose to use Jellyfin, probably because the official apps don’t look as nice. I would use it but certain files just don’t play for some reason and I haven’t had the time to investigate. Plus I’m still waiting for Findroid on android TV to be in a working state.

Yes? Is that odd to you? If jellyfin supported it then that would be one less reason against switching which would be a good thing, wouldn’t you think? If you advocate for using jellyfin then shouldn’t you want such basic features to be supported for those who want to use them?

Even though I still use Plex full time, I very much want Jellyfin to succeed (I run it and offer it to everyone I share with), and so I want Jellyfin to be usable for people of all skill levels. I can’t get my parents to use an app that requires them to know anything about file sizes or codec compatibility or converting anything. That is why Plex is as successful as they are.

If you’re satisfied with Jellyfin lacking certain features, that’s your perogative. But I don’t think it’s that hard to empathize with someone wanting more feature parity, especially if the motivation is to make Jellyfin accessible to more people and increase adoption.

It’s honestly kind of silly to suggest that only technically minded users care about file sizes. We’re lucky enough to even know why the file is so big. My regular friends will just complain that it won’t fit, blame jellyfin, and then go back to Netflix.

You know that regular people with 64GB phones exist right? Suggesting that a non technical person should just know that they need to convert a 30GB remux using ffmpeg is absurd.

I give all my friends the choice between Plex and jellyfin (I run both containers side by side pointed to the same media folders) and they all invariably choose Plex. I think it has a lot to do with the jellyfin UI, and I think an overhaul like jellyfin-vue or something that looks like findroid needs to happen in order for jellyfin to really appeal to regular people.

I’m pretty sure what was already the case was that you needed Plex pass to use the Plex hosted relay for when port forwarding failed when behind Nat. This seems to apply to all remote streaming, including when you’re directly connected through port forwarding or a reverse proxy and not costing Plex anything to transfer your traffic.

Half of my collection is DTS HD MA or TrueHD and many have HDR. Offline caching with transcoding is an essential feature if we want jellyfin to pull ahead. Berating people who are pointing out areas of improvement is not a winning strategy.

Tl;Dr

• Plex pass price increase (6.99/mo, 69.99/yr)
• Non-LAN streaming from a personal Plex server will require either server owner or user to have Plex pass or the new “remote watch” subscription tier
• No more $5 mobile unlock fee to watch in the mobile app, but now there will be a $2/mo “remote watch” subscription tier that unlocks remote streaming mentioned above

I’m glad this won’t affect Plex pass (lifetime for over a decade in my case) users who are sharing their server with non-paying friends, but I also hope this entices more development in Jellyfin. If Plex decided to make it so that my non-paying friends can’t stream easily from my paid for Plex server, I need jellyfin to be a good alternative, and it currently doesn’t appeal to any of the friends I share with so something like that would probably get my friends to switch back to paid streaming.

On one hand, it looks like this only applies to streaming from a remote server where neither the server owner or the user has Plex pass, so lifetime holders or committed server operators with a subscription can continue to provide access to all our non paying friends. It isn’t explicit whether non-paying users people who port forward / do reverse proxying themselves are affected but it sounds like they are, which is utter BS since direct connections hardly cost Plex anything.

It is however nice that they’re trading this for getting rid of the mobile unlock BS - it was always awkward explaining to friends that they could watch anywhere except on their phone unless they paid $5.

On the other hand, one notable side effect is that all non-lan streaming will now be associated with a paying server owner or a paying user, which makes it impossible to use Plex to share pirated media without a user on either end giving up PII / payment information. I have a gut feeling that this is an extension of the previous piracy crackdown on OVH(?) hosted servers meant to ensure they have the identity of all users who may be engaged in selling access.

Overall, yeah another reason to move to JF. I paid for lifetime more than a decade ago so I’m going to keep using Plex until my non-paying friends start to have issues, but I really hope this pushes more investment into JF apps. I really need a good android TV app that supports server transcoding (IIUC findroid’s beta TV builds are direct stream only).

Weirdly enough, the “100 miles within a border” rule also applies to coastlines, not just borders to another country. So US immigration officials are allowed to set up checkpoints, board vehicles without warrants, and search for people without immigration documentation there too. 60% of the US population is apparently included in this zone due to large cities being along the coast.

https://www.aclu.org/know-your-rights/border-zone

I was 100% sure this was a feature. Revanced even has a patch for this called “disable resuming shorts on startup”, maybe Google could learn something from them.

Nowhere did they say that those statements mean immutable to them. Just that your claims that OP “literally said they didn’t want immutable” is not based in reality.