Not all have Pictures in "Stats/Movies/"
Not the right picture (customize) as i have set in PMS in "Stats/Movies" or "Stats/TV Shows" have u set it to tvdb?
Only some of them :-|
But STILL keep going with the good work, you have lot of progress with PN, some errors will there allways be in Alpha's
Not all have Pictures in "Stats/Movies/"
Not the right picture (customize) as i have set in PMS in "Stats/Movies" or "Stats/TV Shows" have u set it to tvdb?
Only some of them :-|
But STILL keep going with the good work, you have lot of progress with PN, some errors will there allways be in Alpha's
It tries to get it from Your PMS first, then it goes to tvdb. I will have a cache manager later tonight.
I have noticed that some TV episodes are errantly showing S00, E00 on some titles.
From PMS: 
From Plex Notify: 
EDIT: It appears that any TV episode played is exhibiting S00, E00 on Plex Notify.
I’ve just made a few additional test runs of version .62 and noticed another error which I did not report in my earlier post.
This error is that I am no longer able to find any version update command. That command icon is no longer present in the ‘Settings’ window.
I’ve checked all available display windows and pages offered by the program, in case the command was moved, but can find it nowhere.
The only remaining option related to program updates is the auto update.
Is manual update no longer supported ?
Best regards: dlanor
I've just made a few additional test runs of version .62 and noticed another error which I did not report in my earlier post.
This error is that I am no longer able to find any version update command. That command icon is no longer present in the 'Settings' window.
I've checked all available display windows and pages offered by the program, in case the command was moved, but can find it nowhere.
The only remaining option related to program updates is the auto update.
Is manual update no longer supported ?
Best regards: dlanor
Yes I removed manual update because it was causing too many problems with updates. Plex Notify automatically checks for updates every minute. Additionally you can restart Plex Notify, and it will check on startup with the option of updating.
Yes I removed manual update because it was causing too many problems with updates.
I don't see why the update procedure should be any different just because it is triggered manually ?
If anything such a manual trigger should have less potential for system errors than a trigger activated from some background thread.
The only real problem with manual updates that makes sense to me would be if you're using the incorrect method of partial incremental updates, where a manual update might miss some of the partial update steps. But the very same thing can happen with auto updates for any user who hasn't had the application running 24/7. (Which is why such partial update is an erroneous method.)
Plex Notify automatically checks for updates every minute. Additionally you can restart Plex Notify, and it will check on startup with the option of updating.
Well, at present it can't do that since I have auto updates disabled, which is how I want it for every application.
Auto updates means that system behaviour can change radically when I am not at the system to check for errors, and that's unacceptable.
That's why I disable auto updates for all applications and system components for which that is allowed.
The only exception is the auto updating of definitions for anti-virus and anti-trojan software.
In any case I have now tried a simple uninstall and reinstall of Plex Notify, using the original "Plex Notify.application" file.
But the result is still erroneous, generating a flood of complaints about the same broken XML code as mentioned in my earlier report.
The program does not hang now, but more such error messages are constantly being added to the log files,
and under so faulty conditions I see no point in running the program until that bug has been fixed.
Fortunately my ability to attach files here has somehow recovered, so here is a log from a short test run:
PlexNotify.log.xml (76 KB)
Best regards: dlanor
I don't see why the update procedure should be any different just because it is triggered manually ?
If anything such a manual trigger should have less potential for system errors than a trigger activated from some background thread.
The only real problem with manual updates that makes sense to me would be if you're using the incorrect method of partial incremental updates, where a manual update might miss some of the partial update steps. But the very same thing can happen with auto updates for any user who hasn't had the application running 24/7. (Which is why such partial update is an erroneous method.)
Well, at present it can't do that since I have auto updates disabled, which is how I want it for every application.
Auto updates means that system behaviour can change radically when I am not at the system to check for errors, and that's unacceptable.
That's why I disable auto updates for all applications and system components for which that is allowed.
The only exception is the auto updating of definitions for anti-virus and anti-trojan software.
In any case I have now tried a simple uninstall and reinstall of Plex Notify, using the original "Plex Notify.application" file.
But the result is still erroneous, generating a flood of complaints about the same broken XML code as mentioned in my earlier report.
The program does not hang now, but more such error messages are constantly being added to the log files,
and under so faulty conditions I see no point in running the program until that bug has been fixed.
Fortunately my ability to attach files here has somehow recovered, so here is a log from a short test run:PlexNotify.log.xml
Best regards: dlanor
Technical terms its because the check for updates in the click one framework is static. So when you check for a update theres a asynchronous event fires that tells me if there is an updated available. I dont know the source of who checked for the update. I tried putting logic in to try and differentiate between the 2 but because of the multi theaded nature of the check its throwing exceptions and crashing the program. So for the moment until I can find a more reliable way I have to disable manual updates.
I see. So basically this is a problem of how best to do this sort of thing in this 'click one framework'. I have no experience with that myself, but I agree that until a good method to handle it is found, temporarily disabling the manual updates may be the best way to avoid problems.
Even so, I don't think that my remaining issue can have anything to do with that updating method, as I have thereafter uninstalled Plex Notify and re-installed version .62 again, and it still keeps filling my log file with the error messages I posted earlier, concerning some broken XML code.
Have you had any luck identifying the cause of that error ?
Or is there any test you want me to make in order to clarify that problem ?
It's past midnight here, so I'm going to call it a day now. But I'm going to leave the program running overnight despite the error messages. As those error messages make that log file grow by appx 7KB per 20 seconds == 21KB/Min == 1.23 MB/Hour, the total size growth overnight should still be acceptable (Just 12.3 MB even if it takes me 10 hours until I sit at the computer again.)
Best regards: dlanor
I see. So basically this is a problem of how best to do this sort of thing in this 'click one framework'. I have no experience with that myself, but I agree that until a good method to handle it is found, temporarily disabling the manual updates may be the best way to avoid problems.Even so, I don't think that my remaining issue can have anything to do with that updating method, as I have thereafter uninstalled Plex Notify and re-installed version .62 again, and it still keeps filling my log file with the error messages I posted earlier, concerning some broken XML code.
Have you had any luck identifying the cause of that error ?
Or is there any test you want me to make in order to clarify that problem ?
It's past midnight here, so I'm going to call it a day now. But I'm going to leave the program running overnight despite the error messages. As those error messages make that log file grow by appx 7KB per 20 seconds == 21KB/Min == 1.23 MB/Hour, the total size growth overnight should still be acceptable (Just 12.3 MB even if it takes me 10 hours until I sit at the computer again.)
Best regards: dlanor
I just got home from work and I'm looking into it right now
I have noticed that some TV episodes are errantly showing S00, E00 on some titles.
From PMS:
From Plex Notify:
EDIT: It appears that any TV episode played is exhibiting S00, E00 on Plex Notify.
This should be fixed with the cache fix. please clear your cache and try again.
This should be fixed with the cache fix. please clear your cache and try again.
Fixed. All is working as intended once more. Thanks.
@JBurlison:
I’m happy to report that the cyclic error log entries have stopped after update to PN .63, which update I performed in response to the update query at a new launch. I’m still keeping auto update disabled, to avoid surprises while I’m away from that computer, and doing the updates as part of a new launch is probably the safest method too, as the app should not yet have started any complex server interactions at that point.
One small error remains in my new log file, re-created shortly after each new launch, as seen in this log:
This error does not repeat itself in a cycle, like the previous one did, though I assume that some of the PN work may cause repetitions of it that I’ve not yet noticed. The fact that it happens at all does indicate that something is still not quite right, though the error message gives no clear clues to what that might be.
0.0.0.63
Application started.
0.0.0.63
Object reference not set to an instance of an object.
at PlexNotify.DatabaseHelper.GetVideoSession(String transcodeID, DatabaseInterface dbi)
Object reference not set to an instance of an object.
at PlexNotify.DatabaseHelper.GetVideoSession(String transcodeID, DatabaseInterface dbi)
@JBurlison:
I'm happy to report that the cyclic error log entries have stopped after update to PN .63, which update I performed in response to the update query at a new launch. I'm still keeping auto update disabled, to avoid surprises while I'm away from that computer, and doing the updates as part of a new launch is probably the safest method too, as the app should not yet have started any complex server interactions at that point.
One small error remains in my new log file, re-created shortly after each new launch, as seen in this log:0.0.0.63 Application started. 0.0.0.63 Object reference not set to an instance of an object. at PlexNotify.DatabaseHelper.GetVideoSession(String transcodeID, DatabaseInterface dbi) Object reference not set to an instance of an object. at PlexNotify.DatabaseHelper.GetVideoSession(String transcodeID, DatabaseInterface dbi)This error does not repeat itself in a cycle, like the previous one did, though I assume that some of the PN work may cause repetitions of it that I've not yet noticed. The fact that it happens at all does indicate that something is still not quite right, though the error message gives no clear clues to what that might be.
Let me know if there's any test you want me to do in order to clarify this.
Best regards: dlanor
@JBurlison:
I'm happy to report that the cyclic error log entries have stopped after update to PN .63, which update I performed in response to the update query at a new launch. I'm still keeping auto update disabled, to avoid surprises while I'm away from that computer, and doing the updates as part of a new launch is probably the safest method too, as the app should not yet have started any complex server interactions at that point.
One small error remains in my new log file, re-created shortly after each new launch, as seen in this log:0.0.0.63 Application started. 0.0.0.63 Object reference not set to an instance of an object. at PlexNotify.DatabaseHelper.GetVideoSession(String transcodeID, DatabaseInterface dbi) Object reference not set to an instance of an object. at PlexNotify.DatabaseHelper.GetVideoSession(String transcodeID, DatabaseInterface dbi)This error does not repeat itself in a cycle, like the previous one did, though I assume that some of the PN work may cause repetitions of it that I've not yet noticed. The fact that it happens at all does indicate that something is still not quite right, though the error message gives no clear clues to what that might be.
Let me know if there's any test you want me to do in order to clarify this.
Best regards: dlanor
How are the optimizations to the statistics screen going? Has the load times been improved for you guys?
Im going to be using the same code for the rest api to get the video information so I need it to be as fast a possible. I have a few more things I can do to speed it up.
Sent from my SM-N900P using Tapatalk
How are the optimizations to the statistics screen going? Has the load times been improved for you guys?
How are the optimizations to the statistics screen going? Has the load times been improved for you guys?
Oh yes, very much so!
Initial opening of the statistics window is now less than 2 seconds here, and it used to be 6-8 seconds or even more.
Switching that window between its different pages (Movies, Users, etc) is usually done in less than 1 second, except for the "Log of Events" which takes a few seconds to complete (appx 3 seconds with 100 entries in the scrollable list).
Im going to be using the same code for the rest api to get the video information so I need it to be as fast a possible. I have a few more things I can do to speed it up.
Sounds good to me ! :)
Best regards: dlanor
Is there any interest in Music Support and pictures?
Are you seriously asking a bunch of Plex addicts if there is a need for more features that will give us more data? You can assume that the answer is always yes :)
