this post was submitted on 05 Nov 2024
72 points (95.0% liked)

Mildly Infuriating

35427 readers
765 users here now

Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.

I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!

It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.


Rules:

1. Be Respectful


Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...


2. No Illegal Content


Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means: -No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...


3. No Spam


Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...


4. No Porn/ExplicitContent


-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...


5. No Enciting Harassment,Brigading, Doxxing or Witch Hunts


-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...


6. NSFW should be behind NSFW tags.


-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...


7. Content should match the theme of this community.


-Content should be Mildly infuriating.

-At this time we permit content that is infuriating until an infuriating community is made available.

...


8. Reposting of Reddit content is permitted, try to credit the OC.


-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.

...

...


Also check out:

Partnered Communities:

1.Lemmy Review

2.Lemmy Be Wholesome

3.Lemmy Shitpost

4.No Stupid Questions

5.You Should Know

6.Credible Defense


Reach out to LillianVS for inclusion on the sidebar.

All communities included on the sidebar are to be made in compliance with the instance rules.

founded 1 year ago
MODERATORS
 

I put on an episode of a show I'm watching, and about ten minutes into it, I missed something on screen, so pressed the skip back button on my remote. The spinning loading circle came up, but stayed for a while, and the episode froze at the point where I'd pressed the button.

No problem I thought, I haven't used Plex for a while, it might just need a little kick. I restarted my fire stick, and restarted the Plex server, just in case. A few minutes later, I didn't catch what a character said, so I tried skipping back again. Plex crashed again. Another set of restarts and we're watching again.

About 15 minutes later, the episode just freezes. No error message or warning, just a frozen screen. I gave it a minute and pressed play, and Plex crashed back to the episode selection screen. Pressing play worked again for a few minutes, until I got an error on screen telling me that my network is too slow for the video. It's a less than 1080p video streaming at 10 Mbps over a gigabit connection. This time, reopening the video took me back to the point of the last issue.

So much for relaxing in front of the TV...

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 2 days ago (1 children)

Can’t say I’ve experienced this myself. Are you transcoding? That’s the only time I have some issues with rewinding. Figure out why you’re not direct playing. There’s no buffering or issues with seeking if you’re direct playing. Jellyfin won’t really help in this circumstance.

[–] [email protected] 1 points 1 day ago (1 children)

I've checked the file. It's a bog standard h264 mkv and the video bitrate is only 10Mbps. There's nothing that the fire stick shouldn't be able to handle on its own. I'll try playing it on the fire stick again and see if it's trying to do something weird, but I can't see it being that.

[–] [email protected] 2 points 1 day ago (1 children)

Curious what you find out. I can’t say I’ve had an issue direct playing anything on any device really. What you describe sounds exactly like seeking while transcoding though, that’s a pain in the ass and I just don’t do it. Direct play all the way.

[–] [email protected] 1 points 1 day ago (1 children)

I just checked the episode through Plex, and it's direct playing. I didn't get any stuttering while I was skipping around though. I think it's Plex itself, either the server or the player.

My physical server is a bit old now, it's a Haswell i5, so if this was an ultra HD bluray rip I could understand it, but it's been playing HD and 4k videos without issues for years now.

[–] [email protected] 1 points 21 hours ago

Direct play should take very little CPU regardless of media quality, I can have multiple 4K streams going and my utilization is <10% on a Cameron J3455 (4c/4t Apollo Lake). When you’re direct playing it’s more a factor of HDD/network speed and the client than anything server side.

Is it just that one file?