PMS DVR fails to save recordings - Windows 10 1903, PMS 1.18.0.1846-f62172e99

After loooking at your logs I’m not positive that it’s just a permissions error. I do see an error at the start where it can’t verify space availability in .grab, but it proceeds. The error that I THINK is root cause is as follows.

Sep 30, 2019 19:30:07.781 [5500] DEBUG - Started session successfully: 21818ff5-fee5-4ce6-a103-7aa9a21238e0
Sep 30, 2019 19:30:07.781 [5500] DEBUG - DVR:Recorder: It took 6.3 sec to start the session for http://192.168.0.251:5004/auto/v4.1
Sep 30, 2019 19:30:07.781 [10696] INFO - Notification: Recording Jeopardy! - E16 - 09-30-2019 -
Sep 30, 2019 19:30:07.781 [2780] ERROR - [Transcoder] [mpegts @ 033fe800] sample rate not set
Sep 30, 2019 19:30:07.781 [8416] ERROR - [Transcoder] Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument
Sep 30, 2019 19:30:07.781 [3032] ERROR - [Transcoder]
Sep 30, 2019 19:30:07.781 [4336] DEBUG - Failed to stream media, client probably disconnected after 458752 bytes: 10054 - An existing connection was forcibly closed by the remote host
Sep 30, 2019 19:30:07.781 [4336] DEBUG - Completed after connection close: [127.0.0.1:54234] 200 GET /livetv/sessions/5cca748f-82df-4c5e-b30c-2e3f71a289cd/21818ff5-fee5-4ce6-a103-7aa9a21238e0/00006.ts (7 live) 12ms 458752 bytes (pipelined: 1)
Sep 30, 2019 19:30:07.797 [4336] DEBUG - Removed transcode data consumer, active count 7 => 7
Sep 30, 2019 19:30:07.797 [9116] DEBUG - Jobs: ‘C:\Program Files (x86)\Plex\Plex Media Server\Plex Transcoder.exe’ exit code for process 6168 is 1 (failure)

It can’t identify the sample rate, then gets an invalid codec parameter error (possibly the sample rate parameter not identified but is needed for the transcoder.) The subsequent set of errors regarding not being able to open files is because the files were never created in the first place because of the transcoder error. There is a similar set of errors where another show was trying to start recording at the same time.

Does this only happen when two recordings start at the same time? I found this thread where others were getting the same error, and they worked around by having one show start a minute early. Here is another with a different resolution.

Sorry, I can’t find a definite fix and haven’t had this problem myself, but perhaps this will get some thinking in a different direction. I personally do rather like the idea of Ubuntu as the base OS install. You can always run Win in a VM if it is needed.