In case you haven’t realized, the user and pass in the docker compose are for setting the user/pass that you will enter on windows to access the share. It doesn’t have to be the same as the Linux server user account - though mine is the same because it’s easier to remember.

This very community seems to be the largest by far - around 45k followers if I’m seeing it correctly. It feels a lot more active than the average Lemmy community as well.

Hmm, well it doesn’t seem to be any problem with the docker compose then as best as I can tell. I picked a random ext4 flash drive and replicated your setup with the UID and GID set and it seems to work fine:

# /etc/fstab
/dev/sda1       /home/<me>/mount/ext_hdd_01  ext4    defaults 0 2

~/mount % ls -an
total 12
drwxr-xr-x  3 1000 1000 4096 Mar 27 16:22 .
drwx------ 86 1000 1000 4096 Mar 27 16:31 ..
drwxrwxrwx  3    0    0 4096 Mar 27 16:26 ext_hdd_01

~/mount/ext_hdd_01 % ls -an
total 6521728
drwxrwxrwx 3    0    0       4096 Mar 27 16:26 .
drwxr-xr-x 3 1000 1000       4096 Mar 27 16:22 ..
-rw-r--r-- 1 1000 1000 6678214224 May  5  2024 PXL_20240504_233345242.mp4
drwxrwxrwx 2    0    0      16384 May  5  2024 lost+found
-rwxr--r-- 1 1000 1000          5 Mar 27 16:27 test.txt

# ~/samba/docker-compose.yml
services:
  samba:
    image: dockurr/samba
    container_name: samba
    environment:
      NAME: "Data"
      USER: "user"
      PASS: "pass"
      UID: "1000"
      GID: "1000"
    ports:
      - 445:445
    volumes:
      - /home/<me>/mount:/storage
    restart: always

I was able to play the PXL.mp4 video from my desktop and write back the test.txt file

Have you checked the logs with docker logs -f samba to see if there’s anything there?

Also you could try to access the HD from within the container, using docker exec -it samba bash and then cd into /storage and see what happens.

I would suggest adding “UID” and “GID” environment variables to the container, and set them to the numeric values for user and group numbers that show in place of your name when you use “ls -an” inside of the “mount” folder (they will probably be the same number).

For example, if inside your mount folder you see:

ls -an
total 12
drwx------ 2 1001 1001 4096 Mar 27 13:54 .
drwxr-xr-x 3 1000 1000 4096 Mar 27 13:51 ..
-rwx------ 1 1001 1001    0 Mar 27 13:54 hello.txt
-rwx------ 1 1001 1001    4 Mar 27 13:54 test.txt

Then set UID: 1001 and GID: 1001

I get the same error as you when I copy your docker-compose and try to access a folder owned by my user. When I add the UID and GID of my user id to the docker-compose (1001 for me), the error goes away.

I think they mean that it’ll take time for everyone to get it. My carrier still doesn’t even have RCS at all.

What did you set UID and GID to and what is the output of “ls -an” when run inside of the shared directory? You can remove the file names for privacy. I just tested the docker container and it seems to work between my Linux laptop and my windows 11 desktop using this docker compose:

services:
  samba:
    image: dockurr/samba
    container_name: samba
    environment:
      NAME: "Data"
      USER: "samba"
      PASS: "secret"
      UID: "1000"
      GID: "1000"
    ports:
      - 445:445
    volumes:
      - ./samba:/storage
    restart: always

The files in my shared folder are owned by UID/GID 1000/1000 which is why I put those as my UID/GID, and when I logged in from Windows I entered samba and secret as the password and I was able to access and modify the files in the shared folder.

Have you done the steps under “How do I modify the default credentials?” and “How do I modify the permissions?” from the readme?

The bigscreen beyond used 1 inch displays so this could be useful for getting much higher resolutions in a smaller form factor. I don’t think my Index displays are even as big as 4 inches so I guess that explains why all the super high res headsets are so huge.

Edit: my index screens are under 3", just did a lens swap so I have the old eye tubes handy

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.