Posts by VMA

    You raised valid points.

    Haven't thought of covering an event with a huge crowd present.

    I use Starlink myself and it is amazing, but I use it in the mountains in a village with less than 40 residents. And I doubt there are further clients in my patch.

    It has been ultra stable and offers a regular bandwidth now limited to 200MBPS.

    For live feeds in news this might be ok and for delayed upload for sure. A live event (concert, sports, etc.) is probably better off with a rented bandwidth from a satellite operator.

    Meinst du meinen HTML Code oder deine Excel Datei?

    Wenn du willst schicke ich dir del Algorithmus. In einer Richtung ist es hauptsächlich Bit Schiebereien, in die andere Richtung musst du Bruteforce benutzen, also alle zweihundert tausend und irgendwas ausprobieren.

    Ich hatte mir Mal eine 1.80m Antenne gebraucht gekauft.

    Ich habe schnell begriffen dass dies für mich nicht brauchbar war. Zu groß, zu schwer. Alleine könnte ich da nichts machen und Hilfe hatte ich auch keine.

    Ich würde sagen, ab 1.50m ist man einfach auf einem anderen Niveau.

    Sieht toll aus wenn man bei jemanden im Garten eine 4m Antenne sieht, doch der Aufwand ist nicht wirklich sichtbar.

    Ich habe großen Respekt vor unseren Mitgliedern mit riesigen Antennen!

    I can perfectly understand moonbase’s position.

    Everyone — myself included — would love to own a dish like that. But people seem to ignore what is actually involved in keeping and installing a 2.8m dish.

    First, you need the space. These dishes are enormous, even at “just” 2.8 meters, and they will occupy a significant part of a property.

    Then there’s the infrastructure:

    • proper foundations;
    • roof reinforcement if mounted on a building;
    • rotor and controller;
    • suitable LNBs and feed assemblies;
    • heavy-duty mounts;
    • cables and accessories;
    • and potentially even insurance in case a storm tears the dish loose and causes damage.

    And of course there is also the most important requirement: obtaining your wife’s approval… which usually comes at a price of its own. :)

    Compared to all of that, transportation is honestly one of the smaller problems. Rent a van, take a road trip, use the Eurotunnel if necessary. Being on an island complicates things, but it was still possible for someone truly committed.

    The reality is that once you factor in all the associated costs, it barely matters whether the dish itself costs €0 or €500.

    What is genuinely sad is that these large dishes are becoming increasingly rare. Very few companies still manufacture them, and producing single units is economically unrealistic because the tooling and pressing costs are extremely high. Once these dishes disappear, they are not easily replaced.

    So I don’t think moonbase deserves criticism at all. He offered the dish — including accessories — for free. That was a generous gesture.

    In the end, nobody was willing or able to commit to the real costs and effort required to collect, transport, install and maintain it.

    And realistically speaking:

    • for Ku-band, a 1.2m dish is already more than sufficient for most people in Europe;
    • for Ka-band, smaller but extremely precise dishes are usually preferable;
    • the real purpose of these giant dishes today is mainly C-band reception.

    And C-band is not a casual hobby. It requires large, heavy, storm-resistant installations and a serious long-term commitment.

    What makes it preferable to operators to use a satellite uplink instead of using a much cheaper 4G/5G or Starlink connection to stream the video feed?

    Just asking since to me it seems much more expensive to use a satellite uplink, not to mention the required hardware.

    Stability? I get a really good connection with Starlink and even mobile internet is above 20 MBPS.

    From the replies so far, I would honestly say, that it would be better and more transparent to have one thread per satellite constellation (like 30.0W) than having separate threads for 30W-5 and 30W-6. Note that I am not complaining, but right now I am focused on feed and transponder hunting and it is often not possible to tell which specific satellite the feed/transponder originates from.

    NIT is not to be trusted and I am specifically dealing with NEW transponders, which are not listed anywhere, yet.

    For the above example (30W-5 and 30W-6), the distinction seems to be possible by frequency: when you look at existing data, it seems that transponders between Freq1 and Freq2 belong to W30-5, while transponders between Freq2 and Freq3 belong to 30W-6. But I have no further knowledge if this is a 100% certain rule or not, nor do I know if this applies to other satellites.

    Honestly, often I even "suffer" from satellite positions being too close (like 9.0E and 10.0E), causing me to receive a 9.0E transponder while the dish is optimized for 10.0E.

    The formula is simple:

    GOLD = (ROOT - 1) / 4
    ROOT = GOLD x 4 +1

    If the conversion from ROOT to GOLD does not produce an integer value, then the ROOT value is invalid for GOLD-mode conversion and no corresponding GOLD code exists.

    Expanding a bit on this: PLS (Physical Layer Scrambling) is used in DVB-S2 and DVB-S2X to pseudo-randomize the transmitted bit-stream before modulation. This avoids long repetitive bit patterns and spectral peaks that could negatively affect carrier recovery, clock recovery, synchronization and overall RF performance.

    The scrambling sequence is generated using a pseudo-random sequence generator initialized with the selected PLS code. Different PLS codes therefore produce different scrambling sequences, effectively creating “virtual” transponders on the same frequency and symbol rate combination.

    This mechanism is widely used by professional operators, feeds and contribution links to:

    • separate multiple logical streams sharing identical modulation parameters;
    • reduce accidental reception by standard consumer receivers;
    • improve spectrum organization;
    • and provide an additional operational layer beyond standard DVB parameters.

    Contrary to common belief, PLS is not encryption. A receiver only needs the correct modulation parameters and matching PLS code to demodulate the signal successfully.

    In practice, some operators use PLS as a practical access-control mechanism despite it not being an encryption system. Since many consumer receivers historically lacked proper PLS support, signals using non-default PLS codes could only be received using professional or compatible equipment.

    For instance, the Aragón TV transponder on 30.0°W appears to have no obvious technical necessity for PLS operation from a purely transmission-engineering perspective. Aragón TV is a public regional broadcaster funded through public resources, and the signal itself is officially transmitted as FTA. However, by using a non-default PLS configuration, reception is effectively limited to receivers that explicitly support DVB-S2 PLS and allow manual PLS configuration.

    It is possible that this setup exists simply because the broadcaster expects viewers and retransmission sites to use officially approved or operator-provided receivers already configured for the service. In practice, however, the use of PLS also creates a de facto reception barrier for hobbyists, DXers and users of older consumer receivers lacking proper PLS support, even though the transmission itself is not encrypted.

    I was asking due to this forum having specific sub forums for individual satellites in one constellation and I find it difficult to know to which satellite a feed/transponder belongs to.

    This might be a stupid question: when you see a new transponder in the spectrum and successfully lock it, how do you know which satellite it actually belongs? I mean when the dish is pointed to a satellite constellation.

    For example, on 30.0W, how do you know for sure if the transponder is 30W-5 or 30W-6?

    I have been fighting crashes for weeks in a new project I am developing, that puts the card under stress.

    It seems to me that streamreader.dll is not as robust as we would wish.

    With my TBS6508 the signal locks at the left side of the transponder.

    Imagine I have a transponder at 10770MHz with 8MHz bandwidth.

    BLScanEx() with 4000kHz search range will lock the signal at 10764MHz. It will return the correct center frequency at 10770MHz, but the lock happens when scanning 10764MHz. Because my software visualises the frequency being scanned, the red line will be left of the transponder.

    There is nothing I can do, since this is the behaviour of the tuner, FW, driver and/or streamreader.dll.

    It seems that different TBS tuners behave differently here.

    This becomes a problem when you have one narrow transponder close to two wide transponders. It gets difficult to tune the narrow transponder.

    It becomes obvious that these cards were not really designed for this specific and special application.

    Note that VMA Stream Reader allows to use a SMA/NWT slow cost spectrum analyser to render the spectrum and determine the transponders. It has far better resolution and gives much better results.

    Ich denke es ist das gleiche Problem wie beim DAB launcher und anderen, dass nur der erste Teil des Diseqc-Befehls ausgeführt wird, ganz unabhängig vom Kartentyp.

    I think it's the same problem as with the DAB launcher and others, that only the first part of the DiSEqC command is executed, regardless of the card type.

    /edit

    Beim Sat IQ Scanner schaltet(e) Diseqc ebenfalls nicht wie gewollt.The Sat IQ Scanner also did not switch DiSEqC as intended.

    femi
    April 17, 2026 at 8:40 PM

    I don't think that VMA Ultimate Stream Reader Pro has any problem with DiSEqC.

    And as you noticed, I dropped the idea behind VMA SAT IQ Scanner, before it was complete.

    I'm unable to determine why Ultimate didn't work the first time when scanning the circular at 36.0E. :25:
    I've now tested the 6983 card. Tomorrow I'll try the other cards as well.

    Sorry for the inconvenience.:73:

    You can use the built-in TS Analyser! No need to call VMA Transport Stream Reader.