Sweet… thank you for your continued assistance, @sa2000!
Done: 33f563247b21d9afd771aa0f1d616e8d9e7621a.bundle.zip (896.6 KB)
So the problems here occur with either TheTVDB enabled or not. I’ve tried debugging this a couple times switching back between the two and attempting to use different settings.
Currently the setting for this library is on TheTVDB as it was demonstrating the same problems with Personal Media Shows enabled as well.
I’ve also changed it back to Personal Media Shows and can verify that the same error message is displayed when trying to save the sort order field. I will also continue to keep it back on Personal Media Shows for this weekend to re-verify that the 1900 issue remains there, as well.
Unfortunately I do not have content from this weekend. After the content is captured, I do another pass through MCEBuddy Custom Cuts to further compress and cut out missed commercials. This process overwrites the original file. Before doing so I verify that the 1900 bug exists, so the problem happens before this. Incidentally enough, there was a problem also with MCEBuddy capturing 1900 for the release date of processed video but this has been confirmed as fixed and it is no longer occurring.
All that stated I will make sure to get you the requested data from one of the next recordings this next weekend. ![]()
So this is a good point. We are not using the built-in guides but are using zap2xml as described here. Could this be part of our problem? For your reference I have included our current guide here:
xmltv.zip (2.0 MB)
I did do a cursory look and see that start and stop fields are provided throughout, so it would seem dates are being provided as expected:
Please let me know what other information you require to continue diagnosing this. I sincerely appreciate you taking the time to assist and improving the quality of your beta. ![]()
