there seems to be a problem with probdvbservice or progdvbengine as since 6.63.* every recording is blank ie 0kb and no video but if i reinstall 6.61.1 it is all fine
i forgot to meantion it all works fine on standard edition for 6.63.* but it is only pro that doenst work
Re: bug feedback - post newly found progdvb bugs here
#798currently i am using compro s900 but it was also happening on my other machine with technotrend skystar hd 2 and blackgold bgt 3590
Re: bug feedback - post newly found progdvb bugs here
#799i should have also said it works fien doa manual record
Re: bug feedback - post newly found progdvb bugs here
#800In 6.63.10, on any SD or HD channel, after some time live-tv start to slow down, like low fps.
Try other codecs, demultiplexors, timeshift on or off, nothing work, except get back to 6.63.09.
Try other codecs, demultiplexors, timeshift on or off, nothing work, except get back to 6.63.09.
Re: bug feedback - post newly found progdvb bugs here
#801pffft I ain't paying for something that can't even do a scheduled recording properly... lame. SichboPVR doesn't freak out at signal interference like your program does either prog, check it out lol. Fix your silly engine because it is pretty sad stuff... progdvb engine error, restarting...rofl give me a breakandrewcrawford wrote:there seems to be a problem with probdvbservice or progdvbengine as since 6.63.* every recording is blank ie 0kb and no video but if i reinstall 6.61.1 it is all fine
i forgot to meantion it all works fine on standard edition for 6.63.* but it is only pro that doenst work
Re: bug feedback - post newly found progdvb bugs here
#802This is not an bug, it's an question i think:
Why ProgDVB consumption is 150mb video ram, and other dvb software is 70-100mb?
I look with gpu-z too see this high video ram usage.
How to reduce this consumption?
Why ProgDVB consumption is 150mb video ram, and other dvb software is 70-100mb?
I look with gpu-z too see this high video ram usage.
How to reduce this consumption?
Re: bug feedback - post newly found progdvb bugs here
#803I cannot confirm this. My video usage is 38MB before I start ProgDVB and between 45 and 70 MB when ProgDVB is running. So ProgDVB itself is not consuming much at all...
I use nVidia GeForce 9800GT, driver 266.58.
I use nVidia GeForce 9800GT, driver 266.58.
Re: bug feedback - post newly found progdvb bugs here
#804For SD channels, my consumption is 100mb( for progdvb) and 150mb for all windows with progdvb open.
For HD channels, my consumption is 300mb( for progdvb) and 350 mb for all windows with progdvb open.
For HD channels, my consumption is 300mb( for progdvb) and 350 mb for all windows with progdvb open.
Re: bug feedback - post newly found progdvb bugs here
#805Please send me ProgDVBEngine.logFUAll wrote:pffft I ain't paying for something that can't even do a scheduled recording properly... lame. SichboPVR doesn't freak out at signal interference like your program does either prog, check it out lol. Fix your silly engine because it is pretty sad stuff... progdvb engine error, restarting...rofl give me a breakandrewcrawford wrote:there seems to be a problem with probdvbservice or progdvbengine as since 6.63.* every recording is blank ie 0kb and no video but if i reinstall 6.61.1 it is all fine
i forgot to meantion it all works fine on standard edition for 6.63.* but it is only pro that doenst work
Re: bug feedback - post newly found progdvb bugs here
#806reeven wrote:This is not an bug, it's an question i think:
Why ProgDVB consumption is 150mb video ram, and other dvb software is 70-100mb?
I look with gpu-z too see this high video ram usage.
How to reduce this consumption?
Timeshift? I think that is not big problem. Lot of modern software request more memory.
Re: bug feedback - post newly found progdvb bugs here
#807Video RAM?
What exactly do you mean, graphics card residing RAM, or Turbo RAM (part of the mainboard located RAM, often used by budget or onboard GPU), or side port memory (like on AMD 890 chipset and similar onboard graphics), or (BIOS defined) aperture memory or what ever else?
However, video memory usage of any desktop video software mainly depends on basic settings like video resolution and color depth, in case scaling method, video buffering, in case post processing (like deinterlacing) and much more. So there are lots of adjustments effecting this, like in several of the graphic driver's controls, codec properties, possibly DirectX related settings, DirectDraw anyway, etc. pp. And possibly some adjustments may effect each other.
BTW, in contrary to main RAM, it won't make any sense, to reduce graphics RAM usage, as long as it's still below it's real size. Or do you play 3D games at the same time, needing big amounts of video RAM for textures and alike?
Generally, modern screens may use around 2 megapixels, in 32 bit colors this makes 8 MB for each frame. Triple buffering -> 24 MB. Deinterlacing ~ 48 MB and up. Plus deblocking, in case. Each extra beautifying eats even more.
Getting true hardware support from a dedicated video processing hardware stage (like available from many modern graphic cards) may but not must reduce this...
What exactly do you mean, graphics card residing RAM, or Turbo RAM (part of the mainboard located RAM, often used by budget or onboard GPU), or side port memory (like on AMD 890 chipset and similar onboard graphics), or (BIOS defined) aperture memory or what ever else?
However, video memory usage of any desktop video software mainly depends on basic settings like video resolution and color depth, in case scaling method, video buffering, in case post processing (like deinterlacing) and much more. So there are lots of adjustments effecting this, like in several of the graphic driver's controls, codec properties, possibly DirectX related settings, DirectDraw anyway, etc. pp. And possibly some adjustments may effect each other.
BTW, in contrary to main RAM, it won't make any sense, to reduce graphics RAM usage, as long as it's still below it's real size. Or do you play 3D games at the same time, needing big amounts of video RAM for textures and alike?
Generally, modern screens may use around 2 megapixels, in 32 bit colors this makes 8 MB for each frame. Triple buffering -> 24 MB. Deinterlacing ~ 48 MB and up. Plus deblocking, in case. Each extra beautifying eats even more.
Getting true hardware support from a dedicated video processing hardware stage (like available from many modern graphic cards) may but not must reduce this...
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 >>>
Re: bug feedback - post newly found progdvb bugs here
#808More abilities needs more RAM . Like EPG in the list and more interest interface which contain many difference functions of the program and much more .reeven wrote:This is not an bug, it's an question i think:
Why ProgDVB consumption is 150mb video ram, and other dvb software is 70-100mb?
[size=50] Железо: Acer KG271C, IP Q G2020@2.9, HD7770, 8 RAM, AMD audio, Yamaha RX-V465, LG 42LA790V, Prof 7300,7301, Tevii s470, TBS 6922se. Софт: W7x64, ProgDVBx32. Настройки: prog demux, audio-AC3Filter, WASAPI, video-Custom EVR, ArcSoft 2,28,497 [/size]
Re: bug feedback - post newly found progdvb bugs here
#809my progdvb 6.63.10 start always at 9.15 every morning!!!
i cant' stop this, in scheduler nothing is scheduled!!
Please help me to stop this start every morning! thanx!
i cant' stop this, in scheduler nothing is scheduled!!
Please help me to stop this start every morning! thanx!
Re: bug feedback - post newly found progdvb bugs here
#810Please check MS scheduler about this command.