I have 2 tuners.
1. A Twinhan 1022a DVB-s (just setup and causing the problem)
2. A Hauappage DVB-T
The Hauappage runs absolutely fine. I use it for DVB and sVid (inputs from a Sat box). The Twinhan does not.
The Twinhan 1022a has BDA drivers, is scanned and working in config under map channels. In PVRX2 though when calling up any channel played via the Twinhan it will play for a moment, maybe two and then PVRX2 will crash. The recording will continue in the background.
The solutions on these posts seemed to be either:
1. uncheck the 'ignore PMT CRC errors always' checkbox
Done and makes no difference.
2. Don't use 'Live TV mode'.
Tried and it works.... GREAT.... But if I don't use Live TV mode I can't get sVid to work on my Hauappage card. When selecting a channel it just says 'There is not card.... etc..'. Put live TV back on and svid works again.
I have tried various combinations of decoders, and renderers and it makes no difference and I am starting to run out of ideas.
I can't post any logs for the crash as there aren't any I'm afraid. But if anyone has any ideas its much appreciated.
I am finding that several digital channels are getting messed up when mapped. I did a scan (I have an HVR 1600 card) and then I viewed the channel in the preview window and then selected that channel in the drop down box to map it to a channel.
When I did some recordings I found several channels where recording or watching live are the wrong content. For instance, ABC Family content was appearing on FS Sports channel and vice versa. (I found out when my Bridge to Terabitha recording was a Bowling Tournament...)
I scanned again and carefully mapped them again. Same thing. About 80% of the channels are right, but others display no channel or the wrong one.
How could the preview window show one thing and then the actual recording or live display another?
I was convinced that all shows in HD was transmitted using H264 codec, but when I accidently converted a 50 min show from Nat.geo HD to H264 it shrunk from 8 gig to 3 gig (and yes, it took forever to convert :o). Could this mean that it is mpeg on DVB-C? (I know that the modulation is QAM256 so the bitrate is quite high).
If you're recording a program and that program is extended is there a way to extend the recording time as well. I was recording a basketball game that went into over time and wanted to continue recording but couldn't figure out how except to wait till the recording finished and started a new one.
I don't think there is a way to import custom messages into the GBPVR interface. For example, I have a batch process that responds to a remote button to poll through different screen resolutions; I would like to briefly display the current and new resolution on the screen.
I can do this with a message box, but a) that's shonky, and b) it doesn't work when using Full Screen Exclusive playback. I can imagine, but am too stupid to design, a system where GBPVR watches for messages and displays them for a set number of seconds once received.
I've been trying to catch a moment to log a problem across which I may have accidentally stumbled. I thought I would describe it here in case someone can explain it without a log.
I was running a polling process that used the CLI to check for current and pending recordings, and periodically restart the recording service if none were imminent. There are some deeply involved reasons that I wish to do this, and I can bore you with them in a different message if you wish.
In the meantime, here is what happened: I started to notice that my programs were often being cut off at the end. Looking at my own log, I saw that the polling process was restarting the service during post-padding time; not always, but often. Since Australian listings are ridiculously inaccurate (often as much as 20 minutes off), this would sometimes interfere with the program.
I tried to duplicate this from the command prompt, and couldn't. The CLI always accurately reported a recording in progress, even during postpadding time. However, now that I have disabled my polling process, the problem has gone away. So, it's a mystery.
