I don't have KU at present, so I'm not sure which ones would or wouldn't have proper time reference, sorry. Though IF you are set to only sync to Transponder time, and are watching a channel live and time starts going wonky, that's a good indication.
I recommend anybody having a clock issue with TNAP, to flash the latest available TNAP 4.1 in a vacant slot, and DON'T restore any old files. DON'T do auto restore. Scan all satellites and channels fresh. Create new bouquets. I did this and my clock appears stable whether the receiver is on or in Standby. It has been like this since Saturday night.
I might give this another stab but I don't intend to spend a lot of time trying to make it work.
I'm not flashing any images that aren't release versions. I'm still on 4.0, and now using a hybrid of transponder time with Bars & Tone as a startup service/parking channel, and NTP time otherwise, and it works perfect for me.
I'm not 100% sure about that. The times I've actually seen mine go off, as opposed to finding it later, it's reset to January 1, 1970. That's T=0 for Unix systems. Maybe there are a lot of transponders broadcasting that, I have no idea. It's been years since I looked at the time broadcast on any satellites, but when I did, most of them seemed to just be their local time rather than UTC.
That can happen if you lose signal. Was it a regular satellite channel, or an IP channel recording? I've had it happen on an IP channel also, when there was a stream glitch/hesitation. It won't restart actual recording after the glitch/hesitation, though it'll keep looking like it's still recording.
Remember, keep at least ONE other working image in a different slot. Makes it easier to restore, IF something happens to your main image. Also, nothing says you can't put the same image in multiple slots... You could have 4 cloned slots for that matter.
That's good to hear. Not looking forward to a complete new setup of everything from scratch, BUT, if it works, guess it'll have to be done.
Will put the same new image in a couple of other slots. A complete setup from scratch isn't so bad. It provides an opportunity to update each satellite and channel listing.
Good point, and it's not as if it'll be my first time, or learning the receiver for the first time. If the newest image is fairly bug-free, that makes it all the better.
Regular sat channel. H&I East AND ABC. I have a workaround in place by creating cron jobs that reboot the receiver 5 minutes prior to the recording which seems to have "fixed" the problem.
E-Channelizer. Works perfect and has for me. DBE corrupted my lamedb. Jenseneverest over on linuxsat suggested E-Channelizer a couple of years ago. Using the free version and no hitches whatsoever.
NTP time hasn't worked perfect for many of us since mid-TNAP 3.x. El Bandido thinks he now may have it fixed in TNAP 4.1, but that isn't a full release candidate just yet.
Not ruffling feathers. El is a good dude. It just must be a tnap thing because openatv is and has been perfect here.
el bandido;102311 said:
el bandido;102313 said:
MikeB;102314 said:
www.unixtimestamp.com
