Scrubbing backwards sometimes never resumes playing

Plex Media Server
,
1

Sometimes when I rewind or scrub backwards the video never plays and acts like it’s buffering forever. This can be fixed by stopping the playback completely and selecting and playing the movie/episode again which works immediately (which has just become a common habit for me because it happens so often).

This can happen on any plex player I’ve used, web player, android app and desktop app.
I was told by a reply to my review of the app on the android app store to report the issue here.

Plex Server: Version 1.40.2.8395
Plex Web: Version 4.130.0
Server OS: Unraid

2

To help troubleshoot, let us know of the OS and the server version. I’ve got a Ubuntu/docker built server on a beefy computer, and it doesn’t exhibit this issue for me.

However, when I first started out in Plex, I used the bundled Plex that came in my Synology NAS. Either the server version was really old, or the hardware was pretty weak, but I recall having some playback issues in various players at the time.

3

I often run in to that high higher bitrate files, trying to scrub much in either direction. On any player, even direct play. Plex simply doesn’t use much local ram/storage at all and the scrub doesn’t work smoothly like streaming services. I should add I usually use the back 10, plus 30 buttons. Using the actual timeline bar works fine.

4

Plex Server: Version 1.40.2.8395
Plex Web: Version 4.130.0
(added to original post too)

I’m running the Plex server on this hardware:
AMD Ryzen 5 2600X Six-Core @ 3600 MHz
32 GiB DDR4
8x Crucial MX500 4TB 3D NAND SATA SSD, up to 560MB/s (one used for cache)
OS: Unraid

I do have other docker containers running on the same machine but they are rarely using more than a single core and ram usage is usually ~6GB.
I don’t think this is a limitation of the hardware as I can immediately close it and start streaming it again and it works with only a second or two needed to buffer.
Note that when using VLC to access the same media from the same drive through a network share, I can scrub completely instantly (it’s seriously lightning fast) so it isn’t a HHD speed or network issue.

It usually only happens after I’ve been watching for awhile. Which makes it annoying to debug.

5

My videos are all stored at a max of 1080p and less than 20Mb/s because Chrome stutters with anything higher than that and I don’t want to use more storage anyway. Not sure if you consider that to be higher bitrate or not.

6

No those are not.

7

Happened just now completely different episode I’ve never watched before.

Here’s the logs from the last hour (the episode was only 17 min in though so I doubt the nvidia transcode errors have anything to do with it (It doesn’t have an nvidia card):

Jun 23, 2024 21:18:53.633 [22585050999608] INFO - [Req#4afb8] AutoUpdate: no updates available
Jun 23, 2024 21:18:53.924 [22585050999608] ERROR - [Req#4afc4/Transcode] [FFMPEG] - Cannot load libcuda.so.1
Jun 23, 2024 21:18:53.924 [22585050999608] ERROR - [Req#4afc4/Transcode] [FFMPEG] - Could not dynamically load CUDA
Jun 23, 2024 21:18:53.932 [22585050999608] ERROR - [Req#4afc4/Transcode] [FFMPEG] - Cannot load libcuda.so.1
Jun 23, 2024 21:18:53.932 [22585050999608] ERROR - [Req#4afc4/Transcode] [FFMPEG] - Could not dynamically load CUDA
Jun 23, 2024 21:18:53.935 [22585050999608] ERROR - [Req#4afc4/Transcode] [FFMPEG] - Cannot load libcuda.so.1
Jun 23, 2024 21:18:53.935 [22585050999608] ERROR - [Req#4afc4/Transcode] [FFMPEG] - Could not dynamically load CUDA
Jun 23, 2024 21:18:53.942 [22585050999608] ERROR - [Req#4afc4/Transcode] [FFMPEG] - Cannot load libcuda.so.1
Jun 23, 2024 21:18:53.942 [22585050999608] ERROR - [Req#4afc4/Transcode] [FFMPEG] - Could not dynamically load CUDA
Jun 23, 2024 21:18:54.099 [22585043172152] WARN - [Req#4afb7] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:54.099 [22585043172152] WARN - [Req#4afb7] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:54.111 [22585043172152] WARN - [Req#4afb7] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:54.111 [22585043172152] WARN - [Req#4afb7] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:54.483 [22585030736696] ERROR - [Req#4afee] Unknown metadata type: folder
Jun 23, 2024 21:18:54.483 [22585030736696] WARN - [Req#4afee] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:54.483 [22585030736696] WARN - [Req#4afee] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:54.610 [22585014586168] ERROR - [Req#4afef] Unknown metadata type: folder
Jun 23, 2024 21:18:54.610 [22585014586168] WARN - [Req#4afef] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:54.610 [22585014586168] WARN - [Req#4afef] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:54.980 [22585050999608] WARN - [Req#4b066] QueryParser: Invalid field 'sectionID' found, ignoring.
Jun 23, 2024 21:18:54.980 [22585050999608] WARN - [Req#4b066] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:54.980 [22585050999608] WARN - [Req#4b066] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:54.983 [22585022298936] ERROR - [Req#4b05f] Unknown metadata type: folder
Jun 23, 2024 21:18:54.983 [22585022298936] WARN - [Req#4b05f] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:54.983 [22585022298936] WARN - [Req#4b05f] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:54.988 [22585050999608] WARN - [Req#4b066] QueryParser: Invalid field 'sectionID' found, ignoring.
Jun 23, 2024 21:18:54.988 [22585050999608] WARN - [Req#4b066] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:54.988 [22585050999608] WARN - [Req#4b066] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:54.991 [22585026517816] ERROR - [Req#4b06f] Unknown metadata type: folder
Jun 23, 2024 21:18:54.991 [22585026517816] WARN - [Req#4b06f] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:54.991 [22585026517816] WARN - [Req#4b06f] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:55.074 [22585036708664] WARN - [Req#4b072] QueryParser: Invalid field 'sectionID' found, ignoring.
Jun 23, 2024 21:18:55.074 [22585036708664] WARN - [Req#4b072] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:55.074 [22585036708664] WARN - [Req#4b072] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:55.083 [22585036708664] WARN - [Req#4b072] QueryParser: Invalid field 'sectionID' found, ignoring.
Jun 23, 2024 21:18:55.083 [22585036708664] WARN - [Req#4b072] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:55.083 [22585036708664] WARN - [Req#4b072] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:55.154 [22585036708664] WARN - [Req#4b072] SLOW QUERY: It took 210.000000 ms to retrieve 50 items.
Jun 23, 2024 21:18:55.593 [22585104014136] WARN - [Req#4b093] QueryParser: Invalid field 'sectionID' found, ignoring.
Jun 23, 2024 21:18:55.593 [22585104014136] WARN - [Req#4b093] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:55.593 [22585104014136] WARN - [Req#4b093] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:55.600 [22585104014136] WARN - [Req#4b093] QueryParser: Invalid field 'sectionID' found, ignoring.
Jun 23, 2024 21:18:55.600 [22585104014136] WARN - [Req#4b093] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:55.600 [22585104014136] WARN - [Req#4b093] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:58.730 [22585028627256] WARN - [Req#4b104/Transcode/eefaxv8kno6dq9ikmgkb9cc0] Transcode runner appears to have died.
Jun 23, 2024 21:18:58.731 [22585026517816] WARN - [Req#4b105/Transcode/eefaxv8kno6dq9ikmgkb9cc0] Transcode runner appears to have died.
Jun 23, 2024 21:18:58.734 [22585043172152] WARN - [Req#4b111] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:58.734 [22585043172152] WARN - [Req#4b111] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:58.734 [22585024408376] WARN - [Req#4b073] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:58.734 [22585024408376] WARN - [Req#4b073] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:58.735 [22585014586168] WARN - [Req#4b112] QueryParser: Invalid field 'sectionID' found, ignoring.
Jun 23, 2024 21:18:58.735 [22585014586168] WARN - [Req#4b112] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:58.735 [22585014586168] WARN - [Req#4b112] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:58.747 [22585014586168] WARN - [Req#4b112] QueryParser: Invalid field 'sectionID' found, ignoring.
Jun 23, 2024 21:18:58.747 [22585014586168] WARN - [Req#4b112] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:58.747 [22585014586168] WARN - [Req#4b112] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:59.091 [22585104014136] ERROR - [Req#4b11b] Unknown metadata type: folder
Jun 23, 2024 21:18:59.091 [22585104014136] WARN - [Req#4b11b] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:18:59.091 [22585104014136] WARN - [Req#4b11b] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:19:19.778 [22585036708664] WARN - [Req#4b1a4] Invalid library metadata ID 602e67ae91bd55002cf8563f passed.
Jun 23, 2024 21:20:30.641 [22585006148408] WARN - NAT: PMP, timed out waiting for response.
Jun 23, 2024 21:20:33.650 [22585006148408] WARN - MyPlex: Invalid connection URL '[REDACTED_NON_PUBLIC_URL]:80'.
Jun 23, 2024 21:32:49.900 [22585104014136] WARN - [Req#4c64b] Invalid library metadata ID 602e67ae91bd55002cf8563f passed.
Jun 23, 2024 21:51:29.595 [22585050999608] WARN - [Req#4cf1d] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:51:29.595 [22585050999608] WARN - [Req#4cf1d] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:51:29.596 [22585045281592] WARN - [Req#4cf21] QueryParser: Invalid field 'sectionID' found, ignoring.
Jun 23, 2024 21:51:29.596 [22585045281592] WARN - [Req#4cf21] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:51:29.596 [22585045281592] WARN - [Req#4cf21] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:51:29.600 [22585043172152] WARN - [Req#4cf22] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:51:29.600 [22585043172152] WARN - [Req#4cf22] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Jun 23, 2024 21:51:29.607 [22585045281592] WARN - [Req#4cf21] QueryParser: Invalid field 'sectionID' found, ignoring.
Jun 23, 2024 21:51:29.607 [22585045281592] WARN - [Req#4cf21] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Jun 23, 2024 21:51:29.607 [22585045281592] WARN - [Req#4cf21] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.

Edit: I removed a url from the logs that I didn’t really mean to leak, not a big deal though.

8

Maybe this? Unable to connect to Plex except via Web | TrueNAS Community

9

Myplex is remote access but I would not use port 80. Does it only happen when remote from server?

is the playback transcoding or is that something else?

10

So that url isn’t accessible from the internet only my local network, and I don’t really use it. I just set it up so I could type it quicker when I’m at home. I usually use my bookmark which uses https://app.plex.tv/desktop
I had that url in Settings → Network → “Custom server access URLs” but looking at that again I don’t think that does what I thought it did when I put it in so I’ve now removed it.

Personally I’d be surprised if that was causing the issue though. Idk why plex would write their app in a way where publishing a url to plex.tv would cause a stream not going through that url to fail to scrub after playing for awhile. I’ll let you know if it happens again now that it’s removed though.

is the playback transcoding or is that something else?

It should have been using original quality, though I didn’t specifically check that. I was on the same local wired network as the plex server. Playing that episode again on the same PC it chooses to play in original quality.

11

“original quality” does not mean “don’t transcode”. it should say on dashboard if transcoding

12

I ask about transcoding because after scrubbing back it may need to restart a transcode from new spot

13

Looks like I was remapping port 80 to 32400 using docker so that my custom url didn’t need to have the 32400 port to work in the browser. Do you think that would cause this issue somehow? I’ll try removing that since I haven’t really been using it anyway.

Here’s the docker settings from my Unraid server (before I removed the port re-map):

image
image659×759 35.5 KB

14

“original quality” does not mean “don’t transcode”. it should say on dashboard if transcoding

Ah makes sense.

I don’t remember the exact episode but it looks like some of the episodes of that show do transcode the audio and some the video stream too. If you’re right do you have any ideas of how to fix that?

Here’s the transcoder settings:

image
image737×679 68.4 KB

Note I don’t have a gpu for it to use. Idk if that means I should turn off hardware transcoding? I left it on because it wasn’t clear if it might use some cpu supported hardware transcoding.

15

I would start by lowering that `transcode default throttle buffer" to something closer to the actual default which is 60.

16

Thanks, I’ll try that.

I had raised it based on a random reddit thread I found when trying to fix this issue though so I’m not very confident that’s it. The theory was maybe the transcoder is throttling so I set it to a really high number so it never throttles. Didn’t fix it though so reverting that makes sense.

Starting to wonder if I should just reset to default settings so my months of trying things doesn’t get in the way. Maybe just re-mount the media volumes to a new plex container or something. Might take me a bit to find a good time to work on that, might be able to find some time this weekend.

17

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.