Yeah Baby! Lookin' good, Feelin' good!


Yeah Baby! Lookin' good, Feelin' good!


Ok so I have a few more things to stitch up before I release. But I got everything Isolated in the statistics screen. This should spell the end to CPU issues. The only Huge spike you will see is when you load the Log of events, only because the amount of data it has to process.
Should I go to sleep or the update's coming? :P
I'm joking, no pressure!
Your work is exciting and I'm monitoring this tread (and update checks) like a maniac...lol
Should I go to sleep or the update's coming? :P
I'm joking, no pressure!
Your work is exciting and I'm monitoring this tread (and update checks) like a maniac...lol
Haha I found a bug with sorting the Players, I'm just about done with that. Then I just have to add the GUI settings in for User Images in the settings. so another hour or two. You can sleep if you want, Plex Notify will be auto-updated when you wake up ;)
Haha I found a bug with sorting the Players, I'm just about done with that. Then I just have to add the GUI settings in for User Images in the settings. so another hour or two. You can sleep if you want, Plex Notify will be auto-updated when you wake up ;)
lol, take you time man, you're already working amazingly fast.
Should I go to sleep or the update's coming? :P
I'm joking, no pressure!
Your work is exciting and I'm monitoring this tread (and update checks) like a maniac...lol
lol. This type of release is quite addictive as it is happening in real time. Reminds me very much of the initial launch of the RARflix channel and the endless updates by Ijunkie.
Not reporting correctly based on PMS:


Not reporting correctly based on PMS:
ok I have a fix for this too.
ok im tired so im going to release. I'll have user images tomorrow.
Ill fix that update bug again too....
Heh, it really wanted me to know there was an update huh.
Edit: I hope you're referring to the pushover notifications bug. Will this happen again when the next update is pushed out, because it just burned through 342 notifications in less than a minute. Luckily I was at my computer to kill the application otherwise it would have eaten the full quota in minutes.
Theres another huge bug. With logging states. Hotfix inc.
ok im tired so im going to release. I'll have user images tomorrow.
Excellent work in eliminating spikes of CPU usage. You have literally stuck the proverbial fork in it. Great Work!!!
Excellent work in eliminating spikes of CPU usage. You have literally stuck the proverbial fork in it. Great Work!!!
Hopefully that will be the last we see of CPU bugs.
Can we get some Likes on this and maybe someone can comment to bump it https://forums.plex.tv/topic/97575-statussessions-viewoffset-problem/ The view offset is not resetting when a user starts a Video over.
CPU after closing stat screen now looks great :-)
Additional functionality is spot on
I did wake up to over 900 growl push notifications around Notify updates lol
I woke up with exactly 3011 Pushover messages xD
There was something wrong with the update code: http://d.pr/i/uNAq/154uvAca
It kept looping I guess
Nope sorry the click once installer framework from Microsoft does not allow for that. It sounds like your missing a reference. Make sure you have .net 4.5 installed on your system
Sent from my SM-N900P using Tapatalk
I've reinstalled plex so it is on the OS drive, Reinstalled .net (I'm running 4.5.1) and I'm still getting the same error.
any suggestions?
Could those CPU spikes have been enough to cause transcoding to suffer? I did monitor the CPU usage server side and couldn't see enough spikes from PlexNotify to cause buffering issues with only 2-3 streams going, but as soon as I killed PlexNotify everything worked normally. Could the SQL be using that much disk I/O that it would cause buffering issues?
I woke up with exactly 3011 Pushover messages xD
There was something wrong with the update code: http://d.pr/i/uNAq/154uvAca
It kept looping I guess
Yeah, there was a small bug with that......sorry!