progdvb.com

knopserl

As in my post above, I'm using the 4.0a driver verison of the Nova S-Plus. The problem is the same with any other driver version below. The drivers are from the Hauppauge homepage: www.hauppauge.de. Here is the link: http://www.hauppauge.de/pages/support/support_nova-hvr.html
BTW there are NO other ...

Forum: Hardware
Topic: NOVA S Plus (BDA)not properly initialized by ProgDVB
Replies: 7
Views: 8229
Sun Nov 18, 2007 8:05 pm
Jump to post

knopserl

now with the new 4.88 or 5.12 it's even worse! No I get no picture or tone at all even when I started WinTV before which works all the time.
The previous version 4.87.3 to 6 worked too.
I have in addition to say that not only WinTV (the original) SW works but also any other TV SW like Media Portal ...

Forum: Hardware
Topic: NOVA S Plus (BDA)not properly initialized by ProgDVB
Replies: 7
Views: 8229
Fri Nov 16, 2007 7:24 pm
Jump to post

knopserl

NOVA S Plus (BDA)not properly initialized by ProgDVB

i have found a similar thread but with other symptoms thus i create a new thread. see environment below.

when i start progdvb, i get no error message but a black screen an no tone on all channels. i have to first start the wintv sw from hauppauge which works of course. then exit and start progdvb ...

Forum: Hardware
Topic: NOVA S Plus (BDA)not properly initialized by ProgDVB
Replies: 7
Views: 8229
Sun Oct 14, 2007 11:38 am
Jump to post

knopserl

Big problems with the new timeshift naming (_0)

dear progdvb team (or Prog ;-)
first i have to thank for the great program. in my opinion still the best and most flexible one, with all the plugin support etc. please continue your very good work.

however, there are two things with which i and others have a severe problem. i'll create a seperate ...

Forum: ProgDVB support
Topic: Big problems with the new timeshift naming (_0)
Replies: 0
Views: 2284
Sun Oct 14, 2007 11:23 am
Jump to post

Search found 4 matches

Display posts from previous

Sort by

NOVA S Plus (BDA)not properly initialized by ProgDVB

Big problems with the new timeshift naming (_0)