Similar problem. I use a post-processing script that first creates a .mp4 file, then deletes the original .ts file. Interestingly, if I don’t delete the .ts file in the script, library scanning works fine. But if the script deletes the original .ts file after creating the .mp4 file, then scanning fails. The script works fine… the appropriate directories are created and the .mp4 file is properly moved from .grab. I just have to manually re-scan if the script removes the .ts file.
To be clear: Partial library scanning works fine as long as my post-processing script doesn’t remove the .ts file originally created by my HDHomeRun tuner. It only fails if my post-processing script removes the .ts file (after creating a .mp4 file).
It thus appears to me that the partial library scanning is now being done right after the .ts file is saved in .grab (or as it is being saved), but not after post-processing and moving the file to the Library subdirectory (because pre-scan detects the original file but not the re-named, processed file).
Thanks for that bit of info. Was my next question “Can I revert to a previous version?”.
When I go to the download page, logged in with Plexpass checked, it still only offers me v1.14.1.5488. I’ll wait another day or 2 and see if this gets resolved. Have my server set to auto check and install updates, beta channel. It’s been fine like that for a long time. But that’s one of the “perks” of living on the beta channel, stuff breaks sometimes
after updating to PMS 1.15.0.659 I cant’ update my libraries at all, PMS don’t detect ANY new files at all, no matter what I do. This is a serious bug, if you haven’t got that already… It needs to b e corrected a.s.a.p.
FYI: The old versions are available in the folder Library/Applications Support/Plex Media Server/Updates under your user. Go into the version you want and unpack the zip file and replace the Content folder under Plex Media Server in Applications.
I recommend backing up everything beforehand though…
I have tried this before, but not in the last year or so.
Just wanted to make sure the developers know that I have the same issue. Mac mini and all was well with the automatic scanning until this latest PMS version (1.15.0.659). Hoping this is fixed with the next PMS update.
I went back to v1.14.1.5488.
Tip 1: Shut down the server before you start this.
Tip 2: Remove updates from the Library folder that are newer than what you installed.
After I downgraded, scanning is back. I switched back to the Public channel for the time being. But it would ask to upgrade every time I opened Plex. So I removed the 2 newer updates from the folder and that went away (Tip 2)
What I did notice is that I had 2 updates on Feb 7th. v1.15.0.647 and some hours later v1.15.0659.
I found the easiest thing to do is edit my post-processing script. Rather than copying the comcut-edited and converted .ts file to a .mp4 file and deleting the original .ts file, I have the script simply rename the final processed file to be the same as the original input.ts file. The .ts extension is misleading, because it is actually a .mp4 file, but if I do this, automatic scanning works just fine. After Plex gets this bug fixed, I’ll go back and rename my .ts files to .mp4 . Anyway, with this modification to my post-processing script, everything seems to work for me (new mac mini, all Plex and other software up to date).
No, They have not done so. I have even Messaged a prominent Moderator to ask that exact question. What is now alarming, Plex Inc communication is very selective at best. I truly understand the hysteria of some Plex users leaving due to their poor customer relations on many support issues. So @ elan can you explain why this keeps happening?
I flagged this post for moderation just to get an employee to look at it. I got a response saying “Thanks for letting us know. We’ve removed the post.” /shrug.
I don’t see anything in the 1.15.0.659 release that is needed for my implementation, so I downgraded back to the public release v1.14.1.5488 and changed my upgrade preference in PMS back to “public”
All I can say from a Product Management perspective (and I have extensive experience as a Product Manager), it is best practices to NOT release firmware (even to beta) without passing (mostly) QA testing…and QA testing absolutely should be testing/validating long-working, existing features like this one. If stuff like this isn’t in the quantifiable test-plan, then product management and testing is not working correctly. Something like HP-ALM or JIRA can go a long way to tracking development progress and defects. No way breaking a feature like this that has worked forever should’ve not been caught in QA. Plex is not the only one…too many “wrong” short-cuts being taken these days by too many people. The shame should be great.
(One of my first “Engineering” classes brought up the fact that Engineers need to be prepared for higher-ranking folks who don’t know their butt from a hole in the ground trying to intimidate you into making bad Engineering decisions for the wrong reasons. I’m not sure they still teach this these days, or (if so), the lesson is apparently not sinking in…)
I also have experience both in QA and Project Management. My issue with the situation is not that the bug exists (■■■■ happens), but that nobody from Plex has pulled the build down or even acknowledged this thread. This appears to be the only way to get support so short of blasting them on social media, how do we know when or if this bug is being addressed?
But I still submit that breaking things in new releases that have worked flawlessly forever in prior releases is unacceptable. If you know you are changing code that could affect long-established working features, then you need to have a prioritized QA test for it in your PM tracking software, test for it, and make sure it passes, BEFORE you release the new code. Additionally QA Test plans must include QA tests for all prioritized features, as well as for any/all defects found and corrected throughout the Product Lifecycle. Then you run the new release through the latest QA test plan, and don’t end up releasing software with bugs that have already been fixed 3 years ago…
