My normal pre-release tester is out of town for a couple of days. The new release is nearly ready and I'm looking a for a couple of testers to give it the quick once-over. If you can give it a go email me at support@devnz.com. In the email let me know what type of client you use (Overlay/VMR/XCard/PVR350/MVP).
PS, sorry in advance if I dont get back to everyone who emails.
Hello,
I was experimenting with recording capabilities and I wonder
1) What is the usage of High quality and standard quality profile ?
When you select a value for compression ( lets say 4500 Kbps)
is it constant bit rate or variable ?
I have noticed that in
WinTV 10 minutes recording using a profile of variable :4800 Kbps and Max:6000 Kbps gives an mpg file 400KB
in GBPVR 10 mins       -"-      high 4300 Kbps, low 4300 Kbps gives a file 433 KB
2) why higher bit rate in WinTV gives smaller mpg file than GBPVR ?...
  is it something I do wrong?...
Thanks...
Just found gbpvr from a post in the MCE newsgroups. Looks like a winner to me. Currently, I run two MCE machines and one ATI AIW 9700 pro pvr machine. I would like to give gbpvr a test run. My questions:
1. Will support for the AIW cards be coming soon?
2. If so, will it include the AIW remote?
3. SUB, do you still need an MCE remote?
4. My MCE's have Emuzed Maui's, support?
5. Any recomendations on a cheap capture card to test with?
Ideally, I would like to be a tester on the AIW series cards when, if you decide to support them! Cheers!
Hello,
 I do not know if this is a feature I have missed or a wish...
 Is it possible to be able to define multiple paths in video library?....so it would be possible to spread video files to multiple disks....
 A work-around could be to use shortcuts in Video Library base directory to point to other places in the system....
 ...I have tried creating shortcuts but they are not recognized by the program.
 So is it something you have in mind to implement ? ( I think the shortcuts work-around is simple...or not?).
Thanks,.....
P.S. Is there a next release (after 15e) comming up soon ?.........
I updated to the new xmltv that was released a couple days ago. In it they say to use tv_grab_na_dd if you live in north america. I tried it, and I cannot import the data into gb-pvr. I emailed sub with the info. Just stay with what you are already doing until he has a look
I just grabbed a new XML file, updated the guide, checked the listing for the current time. It wasn't correct. I emptied the guide and reloaded it and the show was now correct.
In general, when a show is already in the database, and the XML specifies a different show in the same slot (i.e. a program change) is the old show replaced or not? It should be!
I just started a thread in the Developers forum called GBPVR Web . It is soliciting comments. If you have a interest in this topic I suggest going there and commenting.
I am sitting here at work (and not working ) thinking about doing a web interface (service) after weather is complete and had a couple thoughts.
1) Sub, could I get info from you on the database layout and if possible some examples of the C# code you use to access the data?  If you didn't want to post that yet, email would be fine.  Actually your code that displays the guide would be extremely helpful too.  Save me development time and would make the web guide look as much like the native guide as possible.  Of course the same holds true for recording screens etc. too.  So I guess you could just give a drop of the whole app  hehe
2) I was thinking of using the Apache web server (http://www.apache.org). Â It is free, has a Windows version, is fairly well known, and (apparently) supports C# web services. Â
Basic features of guide viewing, schedule a recording, view current recording schedule, and view previous recordings would be supported at first.
My only hesitation would be that I will not have time to support people trying to get Apache running. Â And I would be worried that people who didn't know what they were doing could be completely opening up their machines or home networks. Â I would be putting a BIG disclaimer around that second concern.