I got an other one, still same system and progdvb version.
I have Timeshift disabled but sometimes I got this error: Timeshift buffer is overflowed
When this happends I need to shutdown progdvb and start it again.
Re: bug feedback - post newly found progdvb bugs here
#842Please try change Demux on first page of settings.
Re: bug feedback - post newly found progdvb bugs here
#843Didn't fix the problem.Prog wrote:Please try change Demux on first page of settings.
Re: bug feedback - post newly found progdvb bugs here
#844I have a Hauppauge Wintv Nova SE2 card.
The new version can't scan the transponder.
Every satellite shows signal: none.
I try "Hauppauge WinTV 88x DVB-S Tuner/Demod" with diseq 1.2
The new version can't scan the transponder.
Every satellite shows signal: none.
I try "Hauppauge WinTV 88x DVB-S Tuner/Demod" with diseq 1.2
Re: bug feedback - post newly found progdvb bugs here
#845BDA driver? Too many bad reports about support of Hauppuage in last ProgDVB. I try recheck that in next version.
ps: try select other mode in Settings->Device options.
ps: try select other mode in Settings->Device options.
Re: bug feedback - post newly found progdvb bugs here
#846Please test Hauppage problem on last prerelease (6.70.
Re: bug feedback - post newly found progdvb bugs here
#847Same Problems as mlz ,
Hauppauge dvb-s bda
No Scan possible. Signal 100% Quality 0%, no video no sound but EPG
Last working version is 6.70.03
Also the pre release (.08) is not working
Hauppauge dvb-s bda
No Scan possible. Signal 100% Quality 0%, no video no sound but EPG
Last working version is 6.70.03
Also the pre release (.08) is not working
Re: bug feedback - post newly found progdvb bugs here
#848Do you use default settings in Device options?
Re: bug feedback - post newly found progdvb bugs here
#849Hi, this is a followup to a conversation I had with CrazyCat here:
viewtopic.php?f=4&t=6980
Please see my first posting in that thread for a description of my ProgDVB switching configuration.
The problem I'm seeing is: ProgDVB does not appear to switch 22 kHZ "on" when there are two C-band LNBs (each with H and V) connected to a DiSEqC position through a multi-switch. However, when the four ports of a Universal Ku LNB are connected through a similar multi-switch, 22 kHz does switch on correctly to switch from the low range to the high range. Several STBs work correctly with this same configuration, as do other Linux and Windows software packages, including ones that run on the same box as ProgDVB does.
Using the latest Pro version, v6.70.6. Your assistance would be appreciated.
Thanks
nc-jay
viewtopic.php?f=4&t=6980
Please see my first posting in that thread for a description of my ProgDVB switching configuration.
The problem I'm seeing is: ProgDVB does not appear to switch 22 kHZ "on" when there are two C-band LNBs (each with H and V) connected to a DiSEqC position through a multi-switch. However, when the four ports of a Universal Ku LNB are connected through a similar multi-switch, 22 kHz does switch on correctly to switch from the low range to the high range. Several STBs work correctly with this same configuration, as do other Linux and Windows software packages, including ones that run on the same box as ProgDVB does.
Using the latest Pro version, v6.70.6. Your assistance would be appreciated.
Thanks
nc-jay
Re: bug feedback - post newly found progdvb bugs here
#850Regarding the above, v6.71 appears to have fixed the problem Thanks
Re: bug feedback - post newly found progdvb bugs here
#851When scanning EutelSat W3A ( 7.0E ) the scanner process always crashes at Transponder 29 ( program reports "engine error, restarting" or starts showing the last channel viewed in the background which causes the channel scan to fail/hang ).
screenshot:
screenshot:
Re: bug feedback - post newly found progdvb bugs here
#853No such file found. ( searched the whole C drive )Prog wrote:Please send me ProgDVBEngine.log
Re: bug feedback - post newly found progdvb bugs here
#855Done, making the program scan 7E again and will post the log as soon as it crashes :pProg wrote:Settings->Options->Debug->Logs