With neumoDVB (and Crazyscan) on satellites

[satesco]

I have taken Deeptho's suggestion( #754) to post separately on another thread my experience with neumoDVB on the satellites I receive. Loading a topic with dozens or hundreds of interventions only discourages many users who want to install and work with neumoDVB, especially those who have not ventured to work on Linux and who, for this very reason, have problems installing the application (or drivers for dvb cards). It is also expected, given that the technical issues that some users have with neumoDVB can be more easily tracked by them.
I found myself and still have apprehension when I have to change something in neumoDVB
That's why I'm opening this topic in the hope that there will be users who will try to use the stid135(tbs6903x/6909x) chip cards, which I would say stimulated (maybe I'm wrong) Deeptho to develop this application on Linux. And I must admit that, in some ways, neumoDVB is a new experience for those who have used these cards under Windows.
To a certain extent, we are each a kind of beta-tester when using neumoDVB, the more so as each release brings something new or improves certain things. But beyond the experience one has with the app is whether and to what extent it can convince him that it is worth using it as an enthusiast.
I have a vague conviction that those who try to use neumoDVB hope they will receive more muxes, and the results will be better on Linux than on Windows. If there is such a delusion among some users, I should point out that neumoDVB does no more than Crazyscan. The app does nothing more than better manage hardware usage resources, using a different algorithm to exploit the stid135 chip.
But I'll stop here because I don't want to do more wrong than I have done(?).
As I said, I will go on this adventure on satellites with neumoDVB(Linux) and Crazyscan(Windows).
(Those who want to see what I got at 62.0E, look at #753.

Amos 4 @ 65° E

At 65.0E, we have an example where the result depends on the card used, as Deeptho warns, capable of detecting and displaying a signal without locking it. Crazyscan has been designed so that weak signals that cannot be locked are still displayed on the spectrum. This is only valid for STV091X-based cards (6983/6903/USB5927). Other cards cannot display the nolock signal on the spectrum like the 6903x.
Whereas neumoDVB shows a weak signal subliminally without locking it-11360 V,45000,2/3. This is what IQmonitor does with the 6983 cards, and it can indicate the parameters of a mux that cannot be visualized with the image.
I will post the results at 65.0E with 6903x cards with neumoDVB and Crazyscan, and 6983.

 

[satesco]

Intelsat 17 @ 66° E
tbs6903x card with neumoDVB and Crazyscan:
neumoDVB:10945-11700 H, 10945-11700 V, 12500-12750; Muxes found, Services,
Crazyscan: 10945-11700 HV, 12500-12750 HV.

 

[satesco]

Intelsat 20 @ 68.5° E

Intelsat 20 reception with 6903x card and neumoDVB and Crazyscan apps, 10950-11700 HV and 12500-12750 HV.

 

[satesco]

Continued at 68.5E with neumoDVB and Crazyscan, using the tbs6903x card.

 

[satesco]

Eutelsat 70B @ 70.5° E

Test with neumoDVB at 70.5E, in which I notice on the spectrum that 11215 V/11230 V,51421, and 11277 V/11292 V,45000 appear on other muxes but are correctly listed on the Muxes. They are indeed displayed with the correct parameters after manual scanning.
I should also add that the auto scan with 6903x is faster with neumoDVB than Crazyscan, as is natural and has happened on every satellite I have scanned so far.

 

[satesco]

continued from 70.5E

Another advantage that neumoDVB has when using the 6903X card is that it discovers or locks muxes that cannot be found with Crazyscan, such as 11107 H,416,2/3,8PSK. I had to use the 6983 cards to lock this mux with Crazyscan, not the 6903x.

-I would ask too much of the moderators to post more pictures than 10. Thanks.

 

[deeptho]

continued from 70.5E

Another advantage that neumoDVB has when using the 6903X card is that it discovers or locks muxes that cannot be found with Crazyscan, such as 11107 H,416,2/3,8PSK. I had to use the 6983 cards to lock this mux with Crazyscan, not the 6903x.

-I would ask too much of the moderators to post more pictures than 10. Thanks.

As always: there are pros and cons. crazyscan uses a different peak finding algorithm. Sometimes one is better than the other. You need some luck.

The peaks in the spectrum (frequency and bandwith) are used as an initial guess. The guess 11277H is clearly incorrect, which is due tothe non-flat spectrum which seems to happen with advanced high symbol rate modulation schemes.

 

[CrazyCat]

BLscan2() not implemented for STiD135, used only step-by-step BLScan() without peak detection.

 

[satesco]

Intelsat 22 @ 72.1° E

Testes with neumoDVB and Crazyscan on 72.1E with 1.50 ant, IBU lnb: 11400-11700 HV and 12500-12750 HV.
Between 11400-11700 HV, at 72.1E, neumoDVB and Crazyscan applications find no active mux. In my area, in this part of the band, I have a lot of interference in the Ku band because the useful signal is often attenuated or even disappears. And yet, I would say that what the neumoDVB spectrum shows, compared to Crazyscan, also indicates how the neumoDVB driver has been designed. It displays any signal/noise as an information carrier. When you see so many muxes on the spectrum, you would think one could be an active mux out of many signals. But it isn't; ultimately, both utilities achieve the same result.

 

[deeptho]

Intelsat 22 @ 72.1° E
also indicates how the neumoDVB driver has been designed. It displays any signal/noise as an information carrier. When you see so many muxes on the spectrum, you would think one could be an active mux out of many signals. But it isn't; ultimately, both utilities achieve the same result.

Well, it doesn't. It is a candidate peak to scan. Not a mux.

 

[satesco]

Indeed.

 

[satesco]

ABS-2 / ABS-2A @ 74.9° E

6903x card with neumoDVB and Crazyscan on 74.9E: 10950-11700 HV and 11700-12750 HV.

 

[satesco]

Apstar-7 @ 76.5° E

6903x card with neumoDVB and Crazyscan on 76.5E: 11450-11700 HV and 11700-12750 HV:

 

[satesco]

Express-80 @ 80° E

tbs6903x card with neumoDVB and Crazyscan on 80.0E: 10950-11700 H/V:
I thought the Muxes problem was solved with generic multi-streaming(?) that generates dozens or hundreds of streams appearing on the Muxes list that currently has no practical or other value. We have such a mux at 10974 H, which, as you can see on the list, fills the list without any purpose for us, simple users. It would be a different story if we had such an app for such (multi) streams.
On Windows, with Crazscan, this mux is single and encapsulated.
It looks like neumoDVB; such a stream is not encapsulated(?), so it populates the list with everything it finds on this stream. But whatever the nature of this stream, it would be more useful if such muxes were not repeated tens or hundreds of times.

 

[Llew]

Express-80 @ 80° E

tbs6903x card with neumoDVB and Crazyscan on 80.0E: 10950-11700 H/V:
I thought the Muxes problem was solved with generic multi-streaming(?) that generates dozens or hundreds of streams appearing on the Muxes list that currently has no practical or other value. We have such a mux at 10974 H, which, as you can see on the list, fills the list without any purpose for us, simple users. It would be a different story if we had such an app for such (multi) streams.
On Windows, with Crazscan, this mux is single and encapsulated.
It looks like neumoDVB; such a stream is not encapsulated(?), so it populates the list with everything it finds on this stream. But whatever the nature of this stream, it would be more useful if such muxes were not repeated tens or hundreds of times.

Very interesting satesco, so many streams with no obvious way of parsing them with our programs and cards (unless somebody knows otherwise).

Unfortunately none of the satellites east of 58E are visible to me, so I can't check myself. Maybe similar streams are able to be seen within my arc reach, I'll check when I have time.

 

[satesco]

I have also raised this issue on 53.0E/52.0E, with multistream (#411) on 11244 H,2000,2/3,8PSK, which neumoDVB found on a mux that repeats over and over again. If then, the Crazyscan window showed me these multiple streams; this time, on 10974 H, the same app shows me that the mux has only a single stream.
The same problem manifests itself, for example, on 30.0W, 11676,1766,5/6,8PSK, which has 250 streams(see picture). I have exemplified this only with Crazyscan. At least on the Windows app, they are not displayed, being considered (maybe) useless as long as we don't have an app to show the content.
The annoying thing is not that these streams are unnecessarily listed, but when you have to search for a specific mux, you must search a lot to find it. It's a matter of time.
I must point out one thing, the observations I make above, or elsewhere, are those of a simple user and not of a specialist. Any clarification in this regard is welcome.

 

[satesco]

G-Sat 30 @ 83° E

Here is a satellite, G-Sat 30, at 83.0E, which has no useful signal in the Ku band with my antenna. Because of this, the 6903x card does not see any signal with Crazyscan. Instead,neumoDVB manages to identify signals and parameters, the same as the 6983 cards. That's why I'm posting its spectrum.
This is also a test that the 6903x card with neumoDVB might be at the same level as the 6983/6903.5927 cards when identifying a position on the arc.

 

[EnoSat]

The same problem manifests itself, for example, on 30.0W, 11676,1766,5/6,8PSK, which has 250 streams(see picture). I have exemplified this only with Crazyscan. At least on the Windows app, they are not displayed, being considered (maybe) useless as long as we don't have an app to show the content.

And you can see that the diagram is QPSK, so the whole detection is bad

 

[deeptho]

Express-80 @ 80° E

tbs6903x card with neumoDVB and Crazyscan on 80.0E: 10950-11700 H/V:
I thought the Muxes problem was solved with generic multi-streaming(?) that generates dozens or hundreds of streams appearing on the Muxes list that currently has no practical or other value. We have such a mux at 10974 H, which, as you can see on the list, fills the list without any purpose for us, simple users. It would be a different story if we had such an app for such (multi) streams.
On Windows, with Crazscan, this mux is single and encapsulated.
It looks like neumoDVB; such a stream is not encapsulated(?), so it populates the list with everything it finds on this stream. But whatever the nature of this stream, it would be more useful if such muxes were not repeated tens or hundreds of times.

That is just the way it is designed, not only for simple users... And these streams are not useless. Some of them contain interesting data. I found the operating system for an in flight entertainmens system once.

So it is NOT a problem. The only thing that changed is that scanning such muxes is now much faster,

 

[satesco]

That is just the way it is designed, not only for simple users... And these streams are not useless. Some of them contain interesting data. I found the operating system for an in flight entertainmens system once.

So it is NOT a problem. The only thing that changed is that scanning such muxes is now much faster,

Thanks for the info, but until we can access such a stream (it will be a long time), it would be good if you could find a solution that does not generate so many muxes.
Such streams are intended for professionals with dedicated devices/software. I don't see how we (yes, simple users) can see this content. I'm skeptical about this in the short term in this regard, but that doesn't mean that we/I won't look for muxes that offer us a chance to see what is...forbidden if we find such muxes among the first ones