-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fire a System Message when the bitrate for a recording is too low or too many segments #1
Comments
Does the HD-PVR work in VBR mode? if not, isn't the filesize always going to be as expected even with just a plain black screen? |
Fuzzy, I don't recall if it's VBR or CBR mode...but I know for sure that the file sizes are about 25% of normal when its all black screen (I measure by looking at about a dozen recordings I had done). |
Sometimes there is a delay in tuning DVB-T radio in the UK which typically show some kind of static image that changes infrequently. Different behaviour on different extenders (mvp tunes much more quickly than say an HD300) maybe is related? Sent from my iPhone
|
Update me\sagetv from google\sagetv
Added travis build file so that we can do automated builds, per checkin, on travis-ci.com
I've committed one relating to too many halts during a recording, it's here: 1d5f49c |
And the other one for bitrate is done too: 980a772 For the bitrate one; I just made it based on a property setting for the capture device...was much easier to implement that way. Of course after I did this one...I realized that the bitrate one would likely cover both cases..I'll find out next time my HDVPRs get jacked up. :) |
One of the few problems I still have on occasion with SageTV is when one of my STBs goes off due to a device upgrade by Verizon; or one of my HDPVRs just starts having issues. This manifests itself in 1 of 2 ways.
I should add code in the Seeker which detects when either of these 2 cases occurs and then generates a unique system message. I already suppress the one in my own system for when recordings have breaks in them (since this happens too frequently with the HDPVR); which is why I want a new one for this.
I'd make 2 separate property settings for this since not everyone would want this type of detection. There'd also be a setting for the # of segments to cause this to be hit. I'd also have a property for either a specified rate to fire this at; or just have it go through the recordings for that tuner and then calculate an average rate correlated with resolution and then have a configurable threshold for when this fires based on that average.
The text was updated successfully, but these errors were encountered: