Page 1 of 1

DisableMpeg2Decoder not work

Posted: Tue Oct 30, 2007 4:33 am
by Atlans
from command line:
ProgDVB.exe /DisableMpeg2Decoder
is not working
bda

Posted: Sun Nov 11, 2007 8:35 pm
by cycnus
/disablempeg2decoder is not working anymore for months. In 4.85.1 it was already not working any more. This command was removed from the command list in ProgDVB. What a pity !

In last versions if using multiple commands like /CH:"" /startrecord, record can't begin too.

It should be a GREAT thing if this command could be added back to ProgDVB. Because it was very useful for people who records a lot with not very big computers.
And it would be a great thing if command line with multiple commands could work too.

Prog, please, help !!!

.

Posted: Mon Nov 12, 2007 1:05 pm
by Prog
I will enable it in next version But DisableMpeg2Decoder not very safe command.

What problem with multiple commands ?

Posted: Mon Nov 12, 2007 1:15 pm
by Juergen
He is talking about more than one argument chained in a single command line, like

<path>\ProgDVB.exe /CH"ZDF" /(another_command) /(one_more_command)...

Posted: Mon Nov 12, 2007 5:13 pm
by cycnus
Thanks a lot for /disablempeg2decoder. For me it was very usefull.
Waiting a solution, I used official mainconcept filter graph and I deleted the 2 last lines :

<connect direct="yes" src="Elecard_Audio_Decoder" srcpin="Out" dest="Default_DirectSound_Device" destpin="Audio Input pin (rendered)"/>
<connect direct="yes" src="Elecard_MPEG_2_Video_Decoder" srcpin="Out" dest="Video_Renderer" destpin="VMR Input0"/>

Using this graph, I think I have the same processor usage than disabling the mpeg2decoder. Is it safe ? The recording will be the same than using official graph ?

For the other command line problem, Juergen said the thing better than me (English is not so easy for me !).

I'm talking about more than one argument chained in a single command line.
I think that when using

c:\progdvb\progdvb.exe /disablempeg2decoder /CH:"GEM" /startrecord:"myrecord.mpg"

the recording does not start.

Same thing with

c:\progdvb\progdvb.exe /stoprecord /exit

ProgDVB is not closed.

It's like only the first command line was used.

Better would be to use all commands, in the order they are given.

Other things are perfect with command line (when using more than 1 ProgDVB instance, the command line can find the good instance : that's perfect. Please, don't modify that).

I would be glad to test the new version when you will have created it.