I know I have talked to sub about this before, and I remember his response but I figured I would still make a humble request for it (since I keep wishing it would be done)
I have a ATI HDTV Wonder and just installed GB-PVR and found the known issue of it not supporting the AutoScan feature. I found the threads from BigBus01 about using TS Reader Lite to get the information and then entering it manually into the channel edit field of the configuration. However, after installing the Reader off the Cool wedsite, I can not figure out how to export the data or even see it on a per channel basis in the format he showed as an example. TS Reader does initially see all the freqs I am receiving for DTV, but I can only select one at a time and a lot of options are disabled unless I upgrade.
I am an engineer but this is the first time for me delving into the specifics of video stream decoding and encoding.
I'm not questioning GBPVR's right to exist, but I'm rather curious to get a brief GBPVR history. When did the project start, and why? I was thinking that most people would have settled for the then (I think) already existing mythtv, and implement any "missing" functionality.
But no, sub had to go about and do it all by himself I'm really glad you did, but what where you thinking? Did you in any way envision the impact GBPVR would get? Or the amount of time you'd put into it?
Anyhow... I'm just a bit curious, that's it. And really, really thankful for all the work you've put into this for us. This far
I almost exclusively restart the GBPVR service with the config, starting that up and clicking OK. I do it this way otherwise the little MVPTrayIcon (the simple little utility) doesn't show up in the tray.
Quite often, the secondary "Information" window that pops up after you click OK on the config will turn white and hang with a "Not responding" after which the config window does the same. I then have to manually close it and click "End Now". It doesn't do it all the time and if I go through the process again immediately after, GBPVR then restarts perfectly normally (every time) and works just fine after it occurs.
I attach the logs from just after aborting with End Now, and before a successful restart.
Very occasionally, I also get the error below, which occurred after I turned off the service and dropped in your GBPVR.exe fix for my scrolling problem (in the gbpvr directory). I don't know if they are related.
I'm having a weird issue with .9808. Recently, my recordings have started by creating a file of 0KB in size that shows up as a recording in GBPVR, once or twice, until the real recording kicks in and the show is fully recorded. Sometimes it does create a file of some length (very small) and records a very short clip at the start, before closing and starting again.
I've searched this forum for a while before posting this question. I must say, Sub must never sleep, I applaud the dedication.
I've recently upgraded to GB-PVR v0.98.8b from GB-PVR v0.92.11. I had a teething problem with logging in to the Access DB, but a config file change fixed that (a user/password setting issue). v0.92 has worked for many months without any issue. I already had .Net 2.0 on my PC, so I don't suspect that it contributes to my issue (as other users have suspected).
Anyway, on with my issue. When in overlay mode, I cannot watch a widescreen AVI (576x336, non-interlaced) in fullscreen. It's always small and has black borders. Although I do have a widescreen TV I have the TV Shape setting in GBPVR set to 4:3, mainly because my PVR250 outputs a 800x600 picture. Plus I get no picture at all if I use a 16:9 TV Shape (only for AVIs, MPG is okay). The previous version just maximized the picture and everything was perfect.
Am I missing a setting or has something changed? I suspect GBPVR is doing something clever (hence the TVShape setting). I don't know. I'm stuck. There doesn't appear to be many settings that control the Overlay mode. I can use VMR9, but it's not very smooth. But that's because I'm using a VIA Epia 10000. I really need the performance of the overlay mode.