[createcoms]

DVBViewer is not working, on either 4 non-beta or this latest beta.

log shows it cannot open tv card. I completely uninstalled the drivers and reinstalled, with no change.

[Lars_MQ]

Start -> programs -> dvbviewer program group -> userdata folder. In the explorer window delete or rename the file hardware.xml.

If this doesn't work try setting the direct tuning option in options -> hardware

[jhrdlicka]

I have plea for modification function "popup channel list" in "Preferences | tv+radio".
DVBViewer switch on "popup channel list" if i do not want , example when I switch on/off full screen and mouse cursor is on right.
For example: add delay ms as have "control bar" or treat another. If is it possilble.
Josef

[createcoms]

I nuked the xml file and that did not work, so I tried direct tuning with no success either!

[lighttear]

Forgive me but also with this 4.0.1.11 beta my "personal" bug is still here !!

My hw configuration is the following:

- MB Asus P5Q3 Deluxe
- 2GB DDR3 1006 MHz RAM
- Intel Quadcore 9550
- Asus ATI Radeon HD 3650 fanless
- Haupage Nova DVB-T PCI card
- Skystar HD (aka Technotend S2-3200) PCI card

I have 2 primary partition with:
- Vista Business SP1
- Windows XP SP2

and with BOTH O.S. I experience this annoying bug since coming of Dvbviewer 4.0:

when, IN WINDOWED MODE, Dvbviewer IS TUNED on a terrestrial OR on a satellite channel,
despite audio and video are correctly reproduced on my LCD or Plasma TV, Dvbviewer suffers from periodic stalls (locks) every about 1.5 secs for some tens of second:
i.e.
1. menu's activation does not respond immediately every about 1.5 seconds
2. changing sound volume using the mouse wheel does not respond immediately when locks occur
3. moving the sliding bar in timeshifting mode does not respond immediately when locks occur
4. moving Dvbviewer window around desktop locks every about 1.5 seconds

THIS BUG DOES NOT OCCUR in file mode, only in live TV !

THIS BUG DOES NOT OCCUR IN FULL SCREEN, so symptoms #2 and # 3 DO NOT OCCUR ANYMORE in live TV

THE LOCKS DURATION is slightly different between terrestrial and satellite channels (that is between the 2 different PCI DVB cards)

The strange thing is the following:

- if I replace the BDA Technisat driver , with latest BDA drivers from Technotrend, the BUG DISAPPEARS with satellite channel ONLY, this means that terrestrial channel (the other PCI card with latest Hauppage
BDA drivers) CONTINUE TO BE AFFECTED

On my personal opinion, something wrong was introduced since Dvbviewer 4.0 related to BDA AND graphic card drivers because:

1. even keeping latest dvbsource.ax filter (in bundle with dvbviewer 4.0), OLDER release 3.9.4.0 AND "arcaic" 3.5.0 DO NOT SHOW THIS BUG AT ALL
2. IDENTICAL bug under both O.S. ONLY since Dvbviewer 4.0 onward
3. my htcp is quite new and I have nothing attached (both 2 PCI slots are taken by Nova-T and Skystar HD, other pci-express slots are free)
4. a friend of mine reports the same bug under Windows XP SP2, Dvbviewer 4.0, Skystar HD AND Technisat BDA drivers

I hope developers will take into account my help request in next betas of dvbviewer (I don't believe that Hauppage will develop a new "dvbviewer 4.0 compliant" BDA driver for Nova DVB-T PCI card ...)


many thanks for Your effort

Lorenzo

Attached File(s)

•  support.zip (6.94K)
  Number of downloads: 10

[Lars_MQ]

Handling of fullscreen and windowed mode is no difference, so it is most likely a problem of your settings/decoder/graphicscard/driver.

[remlap]

Hi can you tell me what you mean by partially Blu-Ray playback?

[lighttear]

Lars_MQ, on Feb 15 2009, 20:21, said:

Handling of fullscreen and windowed mode is no difference, so it is most likely a problem of your settings/decoder/graphicscard/driver.

Hi,
I wish it was like you said: I tried lots of combinations of directx mpeg codec, audio and video render, even latest driver from Ati but with no luck.
Sure, is something related to BDA drivers AND how application handles dvb data from live tv:

1. I noted that if I schedule a recording, that is when dvbviewer starts WITHOUT building the graph (new behaviour since beta 4.0.1.0) the periodic locks do NOT occur anymore
2. if I tune a channel, dvbviewer builds the graph AND I tick "disable A/V" , audio and video are not rendered (obvious) but locks still there (the graph is still built I think).

You say that there is no difference between fullscreen and windowed mode, but what can I conclude if "under my eyes" older 3.9.40 and 3.5.0 dvbviewer installations DO NOT show this "bug" in windowed mode ?
And what about the fact that I get exactly the same behaviour under a new fresh installed Vista SP1 partition with only dvbviewer 4.0 and cyberlink 8 installed ?

p.s. plugins directory of dvbviewer completely empty

I don't think my hw is faulty, probably I have a rare, unlucky hw/BDA driver/"dvbviewer built" combination installed ...

With BDA drivers from Technotrend I solved the problem with satellite channels, but still I can't easily use dvbviewer 4.0.x with terrestrial channel
in windowed mode since "newer" BDA driver from hauppage are not available.

Thanks anyway for your interest in my problem

Cheeers

L.

[Tjod]

lighttear, on Feb 16 2009, 10:45, said:

Sure, is something related to BDA drivers AND how application handles dvb data from live tv

I think more that the problem is related to the Graphiccard/driver.

[gaptag]

I've only recently started using DVB Viewer with my two Hauppauge "Nova-T" DVB-T PCI cards and had quite a hassle trying to get them to tune.

To cut a long story short, I found that the provided presets (Terrestrial (Europe)) use the standard channel 21-69 frequencies, however, here in the UK, as far as DVB-T transmissions are concerned, there are a large number of transmitters that appear to use offsets of +/- 166.67 KHz. This is enough it appears to stop DVB Viewer Pro (or the card?) from latching onto the MUX and picking up the channel information, making for one very frustrated end user! :-S

A quick google has actually picked up some old postings on the DVB Viewer forums dated back to 2005/6 also indicating that France for example is also affected by this issue with some tuner cards?

I'm probably going to try and work around the problem for myself by creating my own .ini file with suitable presets from this site ( Mendip Multiplexes (tick the box for Extended MUX Info)) which covers my local transmitter.

I was wondering if there is a case for a UK and France specific presets option so that new users will more likely have success in tuning? Or, is there a case for this problem to be resolved by an extra check-box in the channel scan dialogue box which when checked causes the +/- 166.67Hz frequencies to be scanned automatically?

This post has been edited by Griga: 20 March 2009 - 08:01

[Moses]

You should have a look at Transedit (from the Membersection). Here is the manual to it: http://www.dvbviewer...0E/Content.html

Maybe the "Update" functionality works for DVB-T, too, so you'd need just one working mux (and your provider must have transmit "good" NIT). Even if that's not the case, it should be much easier to edit the transponder.ini. It's even possible to do a blind scan (but that could last very long). In every case: transedit is the tool of choice for such a case.
If you succeed you should think about posting your ini file somewhere in the forum. That can help other users with the same issue and most probably the dvbviewer developers will include your file with the next release.

This post has been edited by Moses: 16 February 2009 - 22:53

[Griga]

Quote

Maybe the "Update" functionality works for DVB-T

Most likely it won't. However, a Blind Scan with TransEdit (see members area) considering the DVB-T frequency shift will automatically create a transponder list:

1) Create an empty transponder list (File -> New List -> Terrestrial).

2) Click Blind Scan. Enter the frequency range according to the example for French DVB-T given at the end of this manual section.

3) After the Blind Scan the transponder list will contain all successfully scanned transponders. Save it.

[lighttear]

Tjod, on Feb 16 2009, 18:14, said:

I think more that the problem is related to the Graphiccard/driver.

If was like that, what about the fact that UNISTALLING all ATI driver stuff under Vista and using internal SVGA driver from Microsoft the bug is still there ?
And most important, why older dvbviewer (<= 3.9.4) in exactly the same environment does not suffer from this ?

Something must be changed since dvbv 4.0 in handling dvb data from bda devices ...
some drivers (technotrend for S2-3200 PCI card) seem to bypass the problem , other BDA drivers (Technisat and hauppage) don't do it...


Thanks anyway


Cheers


L.

[gaptag]

Moses, on Feb 16 2009, 23:52, said:

You should have a look at Transedit...

Thanks Moses/Griga. I will have to have a look at this TransEdit. I'm quite set with my channels once they're set up so I didn't think of installing this.

I'm not sure that this will ultimately fix the problem for all UK/French users though, not unless they all use it in the same way to get their own custom frequency list.

The reason I say this is that the frequencies used in the UK vary from transmitter to transmitter, and so does the case of having +/- 166.67Hz or not having it at all. In fact, with digital switch-over happening, the transmitters are all changing anyway, and may change again in the future at the drop of a hat. While I can scan for my local transmitter, I couldn't ask for that to be added to the installation files for DVB Viewer as that wouldn't help anyone else outwith a 60 mile or so radius of the transmitter I'm on! :-(

This is why I was wondering about a check-box option on the built in channel scan dialogue to enable checking of the +/- 166.67Hz as well as the 0Hz offsets.

Only other way I can see is a complete freqency list which not only has the current channel 21-69 frequencies with 0Hz offset as is already included, but also including all +/-166.67Hz offsets. This would make for a slow scan, but is unfortunately necessary for us UK users it seems otherwise we simply just don't get a successful scan. :-(

Despite the numerous sites available with technical information, I actually found it extremely hard to find out which of my frequencies required the offset. It turns out that only five out of the six MUXes have the offset. I only found this out by finding someone's posting of a results file for a linux dvbscanner that just happened to be for my local transmitter. I struck lucky with this and managed to put the exact six frequencies in manually and get it to scan.

[Tjod]

lighttear, on Feb 17 2009, 09:24, said:

Something must be changed since dvbv 4.0 in handling dvb data from bda devices ...

I think you are looking on the wrong site. If ther is a poblem in conection with the BDA driver you should make all tests without playback (only recording) and reprodus the problem than. But as I understand without playback ther is no problem.

So im quite shour the problem is at the DirectShow site (DVBSource -> Decoder - > Renderer).

Quote

And most important, why older dvbviewer (<= 3.9.4) in exactly the same environment does not suffer from this ?

May be you have only tryed the EVR renderer. Because there was a change who this renderer is handled.