Since upgrading my QNAP NAS to Plex version 1.7.5.4035 (from version 1.7.2.3878), the recording schedule shows a ‘recording’ and ‘recorded’ icons, but not a ‘playable’ icon. See picture of before update (Sun 7/2) and after update (Mon 7/3).
Is this a bug with this version of Plex or something that can be fixed with a configuration change?
Have those programs recorded, but not been processed yet and made available, or have the recordings been lost? The media is not in the expected destination directory, but possibly could be somewhere else?
How might I investigate?
I’m using a HDHomeRunConnect and a QNAP TS-453A NAS drive running Plex.
I have the same on WD PR4100 file is 100% completed but there is no file to play.Also i noticed that it says recording and there is no file on corresponding folder
I have the same problem with one program only, Wheel of Fortune. Other program record and playback fine. Maybe because WoF’s regular season has ended and these are reruns? But I checked the option to record new and reruns, so it should technically work? Maybe because it was recorded before and since deleted so PLEX does not want to record it again? Anyways… its frustrating…
@dansmithy said:
Since upgrading my QNAP NAS to Plex version 1.7.5.4035, the recording schedule shows a ‘recording’ and ‘recorded’ icons, but not a ‘playable’ icon. See picture of before update (Sun 7/2) and after update (Mon 7/3).
What version of PMS were you on prior to 1.7.5.4035?
I uninstalled / reinstalled the 1.7.5.4035 version, and recordings seem to be working. However, I haven’t been able to test it much, so am not confident it is totally fixed. Will keep an eye on it.
Also note, uninstalling removed all Plex metadata, so had to recreate all my media directories.
Still have the issue, even with the latest 1.7.6.4058 version.
Looks like lots of others have the same issue, judging by these threads:
There are no doubt others, that was just a few I’ve found. The first of those threads is particularly active, so I will add to that one. In the meantime, only solution is to downgrade to a 1.6.x release.
There are no doubt others, that was just a few I’ve found. The first of those threads is particularly active, so I will add to that one. In the meantime, only solution is to downgrade to a 1.6.x release.
Thanks for the tip, yes, having this issue as well. I took your advice and have downgrade to 1.5.7, don’t have access to 1.6.x releases unfortunately.
