from command line:
ProgDVB.exe /DisableMpeg2Decoder
is not working
bda
#2
/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 !!!
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 !!!
#4
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)...
<path>\ProgDVB.exe /CH"ZDF" /(another_command) /(one_more_command)...
My signature:
Please read here:
On Bug Reports And Other Complaints
and there:
BOARD RULES - READ THIS!
I don't give support by e-mail or PM.
And I will never assist on PayTV hacking.
PM ME FOR THIS AND YOUR ACCOUNT WILL BE DELETED IMMEDIATELY, WITHOUT ANY WARNING!!!
NEVER EVER DARE TO CONTACT ME FOR PRO VERSION ISSUES!
I am not responsible for that.
Check the 'Activation' section.
Please keep it in English here, or Russian in the Russian section, or German in the German section.
I don't read nor write Klingonian or any other language than English and German.
Addressing me personally in any exotic language will be treated as severe insulting! Be warned!!!
1.)AMD Phenom II x4 940, GA-MA770-UD3, 8 GB DDR2-6400. 7 Pro SP1 x64 + XP Pro SP3 x86
DVB-S2: Cynergy S2 USB HD
2.)P4 3200 i865G (F-S Scenic W600pwr) XP Pro SP3
DVB-S: hauppauge WinTV Nexus-S rev. 2.2, driver TT 2.19h, hardware mode
19.2°,13°,28.x°E,30°W, DiSEqC 1.0
Auf Deutsch:
DVB-Cube <<< Das deutsche DVB-Forum >>>
Please read here:
On Bug Reports And Other Complaints
and there:
BOARD RULES - READ THIS!
I don't give support by e-mail or PM.
And I will never assist on PayTV hacking.
PM ME FOR THIS AND YOUR ACCOUNT WILL BE DELETED IMMEDIATELY, WITHOUT ANY WARNING!!!
NEVER EVER DARE TO CONTACT ME FOR PRO VERSION ISSUES!
I am not responsible for that.
Check the 'Activation' section.
Please keep it in English here, or Russian in the Russian section, or German in the German section.
I don't read nor write Klingonian or any other language than English and German.
Addressing me personally in any exotic language will be treated as severe insulting! Be warned!!!
1.)AMD Phenom II x4 940, GA-MA770-UD3, 8 GB DDR2-6400. 7 Pro SP1 x64 + XP Pro SP3 x86
DVB-S2: Cynergy S2 USB HD
2.)P4 3200 i865G (F-S Scenic W600pwr) XP Pro SP3
DVB-S: hauppauge WinTV Nexus-S rev. 2.2, driver TT 2.19h, hardware mode
19.2°,13°,28.x°E,30°W, DiSEqC 1.0
Auf Deutsch:
DVB-Cube <<< Das deutsche DVB-Forum >>>
#5
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.
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.