Hello everyone!
This question was originally posted in the Media Portal Support section. After many months of procrastination (and fear of corrupting my MP Database) I finally got around to upgrading from Windows 7 to 10. After fixing some issues with Gigabtye software compatibility and Windows continually forgetting mapped (NAS) drive credentials I now have everything running smoothly. To my relief, MediaPortal and my database survived the migration and continues running as before; with one exception....
Moving pictures now displays every single movie file in red (False Invalid File Path) and notes that the file's are "currently not available" and that I should "reconnect the media (folder) labled 'video' to Y:\". The False Invalid is also restricting MovingPictures from recognizing and or importing any new files via the Import tab, yet does so automatically without a problem via launching MediaPortal.
The file path for the media and my entire database remain exactly the same as it was before the Windows update, they haven't changed. They're still the same Y:\ and Z:\ mapped drives, the credentials are solid, the sub-folders are identical; and the watch folders remain unaltered. Now here's the really strange part.... Even though MovingPictures config claims the paths to be invalid, Inside MediaPortal every single movie file plays flawlessly; so clearly the file paths cannot possibly be invalid. What am I missing here? Furthermore, my MP-TV Series extension media is hosted on the same Synology DS411 NAS drives via the same mapped drives and file path as my movies yet MP-TV imports media and functions without an issue.
Scratching my head over this one, stumped. This issue is clearly specific to MovingPictures! I've attached a bunch of screenshots showing the MovingPictures media which is constantly displayed in red and the error that's received whenver you try to do anything inside the extension that queries the false invalid file path. Along with the most recent Watchdog Log. I was advised to upgrade from MP 1.11 to 1.14 Final which I did, but it didn't change anything. The issue persists.
Please help!
This question was originally posted in the Media Portal Support section. After many months of procrastination (and fear of corrupting my MP Database) I finally got around to upgrading from Windows 7 to 10. After fixing some issues with Gigabtye software compatibility and Windows continually forgetting mapped (NAS) drive credentials I now have everything running smoothly. To my relief, MediaPortal and my database survived the migration and continues running as before; with one exception....
Moving pictures now displays every single movie file in red (False Invalid File Path) and notes that the file's are "currently not available" and that I should "reconnect the media (folder) labled 'video' to Y:\". The False Invalid is also restricting MovingPictures from recognizing and or importing any new files via the Import tab, yet does so automatically without a problem via launching MediaPortal.
The file path for the media and my entire database remain exactly the same as it was before the Windows update, they haven't changed. They're still the same Y:\ and Z:\ mapped drives, the credentials are solid, the sub-folders are identical; and the watch folders remain unaltered. Now here's the really strange part.... Even though MovingPictures config claims the paths to be invalid, Inside MediaPortal every single movie file plays flawlessly; so clearly the file paths cannot possibly be invalid. What am I missing here? Furthermore, my MP-TV Series extension media is hosted on the same Synology DS411 NAS drives via the same mapped drives and file path as my movies yet MP-TV imports media and functions without an issue.
Scratching my head over this one, stumped. This issue is clearly specific to MovingPictures! I've attached a bunch of screenshots showing the MovingPictures media which is constantly displayed in red and the error that's received whenver you try to do anything inside the extension that queries the false invalid file path. Along with the most recent Watchdog Log. I was advised to upgrade from MP 1.11 to 1.14 Final which I did, but it didn't change anything. The issue persists.
Please help!
Attachments
Last edited: