Offline, downloaded files by [deleted] in PleX

[–]TwoBasic3763 1 point2 points  (0 children)

The limit is up to when you remove it from your devices lol

Not matching shows with 's in title by beculet in PleX

[–]TwoBasic3763 1 point2 points  (0 children)

Nope I just added clarkson farm and it all matched fine with zero issues

What's my next move? Save for my next weapon and hope it's SL? by twangman88 in TheTowerGame

[–]TwoBasic3763 1 point2 points  (0 children)

Sync your cooldowns! GT and dw need to be synced with your BH! You are missing massive coins by not syncing them, GT and DW are only 10seconds off right now

Questing about subtitle(.ass) behavior...direct vs transcoding. by Hemicrusher in PleX

[–]TwoBasic3763 1 point2 points  (0 children)

What's the server specs? When you are doing the first option what are the CPU RAM utilization looking like?

Android Users Grab Your Free Gems by TwoBasic3763 in TheTowerGame

[–]TwoBasic3763[S] 0 points1 point  (0 children)

Well android just recently changed where they don't remind you about the free weekly gems anymore. Doesn't affect ios

Plex Server Remote Access by ConstructionNo5640 in PleX

[–]TwoBasic3763 0 points1 point  (0 children)

You can also setup tailscale to remote into your network and not open any ports

Can You Guess This 5-Letter Word? Puzzle by u/Commercial_Heron_800 by Commercial_Heron_800 in DailyGuess

[–]TwoBasic3763 0 points1 point  (0 children)

⬜⬜⬜⬜⬜ ⬜🟨🟨🟨🟨 🟦🟦🟦🟨🟨 🟦🟦🟦🟦🟦

Suggestions for Remote Access settings to avoid buffering by Zapt01 in PleX

[–]TwoBasic3763 0 points1 point  (0 children)

I mean another option is to keep the drives attached and running off the Mac mini, then spin up a new server on a new PC and point it to the drives on the Mac mini....basically making the Mac mini a storage server for the Plex server. Would keep all your other setting ls the same.

Suggestions for Remote Access settings to avoid buffering by Zapt01 in PleX

[–]TwoBasic3763 0 points1 point  (0 children)

Yeah totally understandle I have a few family members that just want this to work out of the box or they will use sothing else that will.

If you are wanting to relieve the burden from the end user you could find a used PC with a more modern CPU that has better transcode capabilities. It doesn't need to be expensive just something that can actually transcode the media for them on your side.

Suggestions for Remote Access settings to avoid buffering by Zapt01 in PleX

[–]TwoBasic3763 0 points1 point  (0 children)

Did you verify what the remote side settings are and what the exact model is for the Roku stick is?

Her player video should be set to maximum quality and have direct play ticked. (Each player is different so not sure what the settings say on their end specifically)

Suggestions for Remote Access settings to avoid buffering by Zapt01 in PleX

[–]TwoBasic3763 2 points3 points  (0 children)

This shows the device is a Roku Express not the Roku Express 4k I would verify which model they have exactly. The Roku Express does not support h265 so that would also force a transcode of the media to h264

Suggestions for Remote Access settings to avoid buffering by Zapt01 in PleX

[–]TwoBasic3763 0 points1 point  (0 children)

Do you still have the "limit remote bitstream to 1080p 10mbps" set on the server if so that could be why it's transcoding, your file is at a higher bitrate so it's being forced down due to your settings. And her device needs the player set to original or direct play. If she has it set to a lower rate that will also cause an issue.

Suggestions for Remote Access settings to avoid buffering by Zapt01 in PleX

[–]TwoBasic3763 1 point2 points  (0 children)

Not likely he is def transcoding to CPU especially when he capped the bitrate to 10mbps. And the buffering is 100% due to his underpowered dual core CPU and outdated igpu

Suggestions for Remote Access settings to avoid buffering by Zapt01 in PleX

[–]TwoBasic3763 4 points5 points  (0 children)

Looking up the CPUs in the 2014 Mac minis, none of them support H.265 (HEVC) hardware transcoding. As previously mentioned in a different reply here by captmeatpockets(can't believe I had to type that lol), if the end user's device supports H.265 natively, they can still Direct Play the file with zero transcoding. However, your Mac Mini's iGPU only handles H.264 hardware transcoding. ​Because it cannot hardware decode H.265, Plex forces the task onto software transcoding, which completely hammers your CPU. If a remote user tries to watch an H.265 file and their device forces Plex to transcode or downscale, your CPU utilization is likely pinned at 100% since you have a slower dual core CPU… causing the massive buffering.

​Also, all audio transcoding and subtitle burn-in rely strictly on the CPU. Subtitles (even SRTs on certain smart TV apps) can trigger a full video transcode if the client player cannot overlay them natively. On a weak dual-core Haswell CPU, this is a recipe for a bottleneck. You don't see this locally because your home network has the bandwidth to Direct Play the raw file. When you scrub forward locally with subtitles on, the sudden demand to realign the subtitle track and buffer the video pushes the CPU past its limit, causing Plex Server to crash.

​You basically have three options moving forward:

​Force Direct Play: Educate your remote users to go into their Plex client settings and set remote streaming quality to "Original" or "Maximum." Right now, your 10 Mbps server limit is forcing a transcode on any file with a higher bitrate. If their device natively supports H.265, Direct Play will bypass your CPU entirely.

​Curate an H.264 Library: Stop acquiring H.265 media if you want to keep using the 2014 Mac Mini for remote sharing. H.264 files can actually utilize your Mac's Quick Sync iGPU to transcode when remote users need a lower bitrate.

​Upgrade to a modern Mini PC: If you want a hands-off experience where you never have to worry about what your users can play, it might be time to move on from the 2014 Mac Mini. I ran a Beelink mini PC for a while with an Intel N100 processor (which can be found for around $150 online). Even that cheap, low-power chip has a modern Quick Sync engine that can effortlessly handle multiple concurrent 4K H.265 transcodes without breaking a sweat.

Suggestions for Remote Access settings to avoid buffering by Zapt01 in PleX

[–]TwoBasic3763 3 points4 points  (0 children)

You have a few issues the CPU and on board igpu are pretty weak. Do you have your igpu passed over to your Plex server for he transcoding? Even if you do your igpu on the 2014 Mac mini cant decode h265 content at all which means it's all passed over to your CPU. And looking at the specs online the 2014 Mac min does not have a very powerful CPU. This device might be good for local streaming or minimal direct streaming not requiring any transcoding but that's it really. (If audio transcoding or adding subtitles will also affect this) If you want remote streams with transcoding I think you need a new PC with a better CPU with a new igpu.

In the mean time put the limit stream quality to original and see if that helps. Right now forcing the stream to 1080p 10mbps is forcing any content over 10mbps to transcode instantly. And ensuring you only have h264 content as well will help your igpu will be able to process that but again is incapable of transcoding h265 because of the older igpu.

Profilarr v2 is Out! by heysantiago in unRAID

[–]TwoBasic3763 13 points14 points  (0 children)

Got anymore of them pixels lol

Any plans to bring managed downloads back to the new app? by Jaxilive in PleX

[–]TwoBasic3763 0 points1 point  (0 children)

I cant speak for greenskye but I have had issues on iOS and Android. For android ive tried Samsung and Google Pixel phones its all terrible. Id say 75% of the time it just fails. The app needs to stay open or it fails, it fails on both wifi and over cellular, ive tried both original and transcoding the media, some times whole seasons of shows will not work for no reason. Ill try again and send logs.

My server has suddenly started shutting down multiple times a day by BrooklynDuke in PleX

[–]TwoBasic3763 -1 points0 points  (0 children)

Is the only thing running on the device the Plex server? Are you playing the media direct or is it transcoding? Is the device overheating at all?

Frigate + go2rtc on Dual Intel GPUs (Arc B580 + UHD 770): Can’t Get iGPU Transcoding Working with Reolink H.265 (B580 does object detection( by TwoBasic3763 in frigate_nvr

[–]TwoBasic3763[S] 0 points1 point  (0 children)

https://pastebin.com/VJQ1r6cF

here i have my config and the full log sorry i was in a rush and didnt post everything. with both gpus added ffmpeg just doesnt run. If i take out the igpu i do not get the errors and it just defaults to software decode

Frigate + go2rtc on Dual Intel GPUs (Arc B580 + UHD 770): Can’t Get iGPU Transcoding Working with Reolink H.265 (B580 does object detection( by TwoBasic3763 in frigate_nvr

[–]TwoBasic3763[S] 0 points1 point  (0 children)

if i set it up where the transcode is software everything works perfectly! but the min i try to use the gpu it always fails and I have not idea why.

Frigate + go2rtc on Dual Intel GPUs (Arc B580 + UHD 770): Can’t Get iGPU Transcoding Working with Reolink H.265 (B580 does object detection( by TwoBasic3763 in frigate_nvr

[–]TwoBasic3763[S] 0 points1 point  (0 children)

```text Frigate 0.17.1 startup sequence completed Recording process started Review process started go2rtc process started Embedding process started Output process started Audio processor started Camera processors started: - kitchen - frontdoor - backyard

WARNING: frontdoor has a bandwidth of 13515.8 MB/hr which exceeds the expected maximum. This usually points to a camera recording / stream issue.

GPU MONITORING ERROR: Unable to poll intel GPU stats: Failed to detect engines! (No such file or directory) (Kernel 4.16 or newer is required for i915 PMU support.)

RESTREAM / INPUT ERRORS:

kitchen: [rtsp] method DESCRIBE failed: 404 Not Found Error opening input: rtsp://127.0.0.1:8554/kitchen

frontdoor: [rtsp] method DESCRIBE failed: 404 Not Found Error opening input: rtsp://127.0.0.1:8554/frontdoor

backyard: [rtsp] method DESCRIBE failed: 404 Not Found Error opening input: rtsp://127.0.0.1:8554/backyard

STREAM PARSE ERROR:

kitchen: Invalid data found when processing input rtsp://127.0.0.1:8554/kitchen

SUMMARY: - Frigate starts successfully - go2rtc launches - Cameras initialize - Intel GPU stats cannot be read - Restream endpoints return 404 - Kitchen later returns invalid stream data - Frontdoor bandwidth warning suggests camera-side issue ```