ProgDVB - Kein Empfang von Privatsendern (Pro7, Sat1 etc.) b

#1
Hallo zusammen,

ich nutze seid vergangener Woche eine PCI-Karte C-2300 aus dem Hause Technotrend in meinem Rechner und empfange damit anstandslos sämtliche ARD und ZDF-Programme sowie diverse andere Sender. Allerdings fehlen mir sämtliche Privatsender (bspw. Pro7, Sat1 etc.). Nun habe ich hier vom sog. DECT-Problem gelesen, welches jedoch m. E. nur bei Empfang per DVB-S auftritt, da ich jedoch DVB-C nutze fehlt mir eine passende Erklärung, zumal ich mit der mitgelieferten Technotrend-Software die o. g. Programme einwandfrei empfangen kann. Diese Software ist jedoch nicht so komfortabel wie ProgDVB, daher würde ich gerne ProgDVB nutzen.

Vielleicht hat jemand einen Lösungsansatz?

Vielen Dank vorab.


Viele Grüße,
HC-65 :?: :?:

#2
Darüber hinaus würde ich mich freuen, wenn mir jemand eine ProgDVB-Channel- und/oder Transponderlist für den Raum Köln (Kabelanbieter ist Unitymedia) zur Verfügung stellt.

#3
Sorry, but this board is in English.

Anyway, we will have to know a few details, to possibly help you on this.
First of all, do the stations mentioned use basic encryption, forcing you to use a subscriber card and CAM for them, in the TT software?
If so, you may have some CI related issues with ProgDVB. Then try at least one older version to compare.

Or do you simply get no lock on that transponders at all, no level / quality? Then compare some of that stations by channel properties. Make sure, the necessary frequencies are in the transponder list used by ProgDVB, and they are precise, on all values. If not, use your editor on it.

Even possible, you can't tune precise enough, due to whatever tolerances or deviations of frequencies.
To find out, go onto a transponder with verified data (compare again), try to adjust in tiny steps up to 2 MHz up or down. If an offset occurs, correct the transponder list entry(s).

Also find out, if the missing transponders do have anything noticeable in common, like same data rate, different from the working ones, or QAM or frequency range or whatever else.

If anything is at some limit, like low L & Q, or the frequency almost touches the limits of the AFC lock / hold range, it's possible, different software gives different results, due to e.g. timings or even non used HW functions on one.
In any case like this, it's highly recommended, to try and find out the kind of limits you're to close to, and correct the problem's source directly, if any possible. The working ones may as well be quite critical...
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 >>>