Page 1 of 1

Problem after installation of ProgDVB on Windows Home Server

Posted: Sat Jan 15, 2011 1:24 pm
by FrankP
Hallo !

I´ve made an installation of ProgDVB 6.51.02 on my Windows XP Notebook and everything worked well.

Yesterday I´ve made the same installation on my Windows Home Server. The installation was o.K. and there were no errors.

The Problem is, that I have no picture

Level and Quality of the DVB-T Signal is o.K.

This is the Error-Message: "Pin for connection not found. Stream type MPEG2. Probably one of nescessary codecs is not choosen or not installed on your computer"

I´ve received the same message for MPEG-Audio

If I check up Settings => Options => Video and Audio and chose the ELECARD MPEG2 Decoder the problem is still not fixed because I receive the same errormessage and the screen is still black

Perhaps there is some problem with installation ProgDVB on Windows Home Server ??

Best regrads

Frank

Re: Problem after installation of ProgDVB on Windows Home Se

Posted: Sat Jan 15, 2011 1:50 pm
by Prog
Try use other video codec

Re: Problem after installation of ProgDVB on Windows Home Se

Posted: Sat Jan 15, 2011 1:53 pm
by FrankP
Prog wrote:Try use other video codec
Where can I get an other video codec ?

Re: Problem after installation of ProgDVB on Windows Home Se

Posted: Sat Jan 15, 2011 2:21 pm
by Prog
One more idea, change Video render to VMR7 for example.

Re: Problem after installation of ProgDVB on Windows Home Se

Posted: Sat Jan 15, 2011 2:24 pm
by FrankP
O.K.

I will try this

So you think, this is no generally problem with the installation on windows home server ?

Re: Problem after installation of ProgDVB on Windows Home Se

Posted: Sat Jan 15, 2011 2:41 pm
by Prog
I hope no. Also you can install last directx _9_ and last .net

Re: Problem after installation of ProgDVB on Windows Home Se

Posted: Sun Feb 27, 2011 2:57 am
by chewy5000
I am having the same problem on XP

Re: Problem after installation of ProgDVB on Windows Home Se

Posted: Sun Feb 27, 2011 3:31 am
by chewy5000
Scrap that the latest update seems to have fixed it