neumoDVB

[deeptho]

Thanks for wanting to help me. I tried to do what it says on the link you gave me. It didn't work. I also tried the Recover Deleted Files app, but without success. I'm not sure if it's still possible to recover the working app.
To cleanly install the app, I also tried to delete any files left in neumoDVB from the previous installation. Unfortunately, the same errors are still occurring as before(u32 and u8).
I hope I'm not wrong, but the structure you're talking about has to do with how the frontends are registered in the previous installation. These adapters cannot be ordered otherwise by a new building. Although it shouldn't be a problem, I think I did the driver installation after neumoDVB(?). Because of this, the application didn't know how to choose the correct adapter. Plus, only some of my tuners had the driver that Deeptho designed.
There must be another method of installation despite the persistence of these errors. I hope Deeptho will step in with a solution.
I hope I don't start all over again, with installing blindscan drivers and then neumodvb

I do not know if all of this is correct, but there seems to be confusion. I do not think satesco actually INSTALLED the programs, Instead he compiled it and ran it from the source directory (as recommended). It seems to have run properly, but then he deleted it and in the mean time, for some reason some other changes to his setup prevent recompilation.

I performed an installation from scratch of the drivers and the application on a clean (new ) ubuntu system and
-except for the incorrect/incomplete dependency list - the instructions I provided on github lead to a fully working system.
No compilation errors, no screen resolution problems. etc. Of course all bets are off if you start mixing older and newer versions of python, libraries ... or if some other required software is not installed.

In the mean time I also did some test like that for fedora36. There have been a few changes in fedora since fedora34, so
again the dependency list needs to be updates, a small change to the source code was needed and some FALSE compiler warning is emitted, but apart from that, I also ended up with a working system.

Soon I will upload a new version, which has some other bugs fixed as well.

Hopefully soon I can also provide a "direct download' I am considering "AppImage" for that. The main downside is that
such downloads are huge. Theoretically they should work on all linux systems. That still leaves the problem of driver
installation, which is sometimes difficult (but I repeat: the instructions on github at deeptho/linux_media simply work
on both ubuntu and fedora - at least on a clean system).

 

[satesco]

I'm sorry, @deeptho, to say that I can't use your app anymore. I deleted it because I couldn't do blindscan and spectra. I couldn't get it back. I tried to reinstall it but the errors appeared that I wrote about previously. So I can no longer use your app.
I add that I have installed all the dependencies you mention. I haven't forgotten any of them. And believe me, I followed all the instructions.
I'm sorry to put you through this ordeal again, but please take a look at the module errors (it seems) that your application generates in the installation process. They didn't appear in the previous installation, but only now.
You could also see that no dependencies were missing during the installation.
I don't know what else to say, but if I can no longer install your application, then I have to start from scratch, i.e. install the blindscan drivers and install neumodvb.
Please have a look at the files in the attachment and then tell me if it is still possible to install neumodvb without errors.
Thank you very much for your patience and kindness.

 

[deeptho]

I'm sorry, @deeptho, to say that I can't use your app anymore. I deleted it because I couldn't do blindscan and spectra. I couldn't get it back. I tried to reinstall it but the errors appeared that I wrote about previously. So I can no longer use your app.
I add that I have installed all the dependencies you mention. I haven't forgotten any of them. And believe me, I followed all the instructions.
I'm sorry to put you through this ordeal again, but please take a look at the module errors (it seems) that your application generates in the installation process. They didn't appear in the previous installation, but only now.
You could also see that no dependencies were missing during the installation.
I don't know what else to say, but if I can no longer install your application, then I have to start from scratch, i.e. install the blindscan drivers and install neumodvb.
Please have a look at the files in the attachment and then tell me if it is still possible to install neumodvb without errors.
Thank you very much for your patience and kindness.

Your log files show that clang-format is missing. So check the dependencies (all of them!) once more.
You probably have not installed clang either because it is not used according to your log files.

What would be the point of reinstalling the driver? The things that work work and should not be removed....

 

[Satspot]

Your log files show that clang-format is missing. So check the dependencies (all of them!) once more.
You probably have not installed clang either because it is not used according to your log files.

What would be the point of reinstalling the driver? The things that work work and should not be removed....

Not directly related to your project but something I was working on a while back. You can see how the author handled the constant breaks with every new kernel update. I wonder could you create one install script to execute all those install instructions GitHub - b-rad-NDi/Ubuntu-media-tree-kernel-builder: Slip stream the latest LinuxTV.org media drivers into an installable Ubuntu kernel package

 

[satesco]

@deeptho,

I managed to solve the problem much easier than I thought, in an "unorthodox" way Those "unknown type name 'u32' and 'u8' errors" were in the frontend.h file in /usr/include/linux/dvb/, which probably memorized the previous configuration of the adapters. I replaced this file with a similar one from another kernel package. Then I proceeded to install neumodvb following the installation instructions from Github. Fortunately, no more errors appeared and I finished with the installation of the application.
So everything went normal. I started the application and checked the frontends. Everything was ok as if I had not uninstalled neumodvb before.
I chose to do the first test on Astra at 19.2E with the 6903x card. I carefully followed the setup and use of the frontend. Of course, I started what I was most interested in with neumodvb, the spectrum and blindscan.The Astra transponder signal also appeared on the top of the Spectrum.I did some manual scans and memorized some channels from this satellite.
Then I manually scanned the cable frequencies with the 6504 card. I manually found all the programs in my cable provider's package.
But I was most interested to see how neumodvb works on Eutelsat 10A to 10.0E, which as we know, the signal and parameters are different from one transponder to another. Then I was curious how the 6903x card reads transponders with low symbol rate in the upper part of the band, where we have more Radio Maria programs.
I wanted the application to scan only a part of the band, between 12500-12750 HV, but the application showed me the whole band of the satellite, from 10700-12750 MHz,on both polarities.I chose the blindscan to scan the whole satellite on both polarities. Everything went normal. I found that the Data transponders, although they had signals were not memorized. Instead, the feeds were memorized. Unfortunately, neumodvb did not close any low symbol rate on the Radio Maria transponders even if it detected the signal level, the SNR was not on the signal bar.
So far that's all I can say after the first contact with neumodvb.
I tried to change the volume on sound,= and -, but I didn't succeed. How can I use it? Or is it a bug?
Thanks a lot, Deeptho, for the effort you put into creating this program. You've taken a tremendous step, I'd say a leap, from some of the attempts by some exceptional developers in the Linux world to give reception enthusiasts a working tool but, it seems, have abandoned them or are in abeyance.
Fortunately, you provide us with the full working equipment.
To be excused for the rather long text on your topic. But I was glad I could install and work with your tool
Kind regards

 

[Llew]

Excellent @satesco you've cracked it

At last someone I can compare notes with

 

[Llew]

I see you're showing the whole spectrum range in the From/To box in your 10E screen grab. You have to put your needed spectrum range in there.

 

[satesco]

I see you're showing the whole spectrum range in the From/To box in your 10E screen grab. You have to put your needed spectrum range in there.

I envied you, collegiately, when you first used neumodvb. To my knowledge, you are the first user to use the app. But now I'm glad that when it is the case at some satellites/positions, we can check the app and make comparisons.
For now, I have to familiarize myself with the app. While working with neumodvb I wondered how one could generate lists of scanned satellites, like utilities in Windows? Or how to set the scanning steps, etc.
Anyway, the questions will come as we use the application. We are just at the beginning, both Deeptho, who wants to improve it, and us, users, who still need guidance from him.

 

[Llew]

While working with neumodvb I wondered how one could generate lists of scanned satellites, like utilities in Windows? Or how to set the scanning steps, etc.

I don't have neumoDVB on my present PC to check, but isn't the Bouquet list in the app used for storing the scanned sats? Deeptho should be able to advise.

 

[satesco]

Yes, the app does store satellites and channels, but I wish I could have separate lists.
I'm still at the beginning and I admit that I still don't know the app in all its details as Deeptho thought. I hope to learn more as I go along.

 

[deeptho]

Satesco,
that is a nice result.

ER=215446]@deeptho[/USER],

I managed to solve the problem much easier than I thought, in an "unorthodox" way Those "unknown type name 'u32' and 'u8' errors" were in the frontend.h file in /usr/include/linux/dvb/, which probably memorized the previous configuration of the adapters. I replaced this file with a similar one from another kernel package. Then I proceeded to install neumodvb following the installation instructions from Github. Fortunately, no more errors appeared and I finished with the installation of the application.

But that does not make any sense, as these files are all the same. Changes to that file are very rare. Anyway, the trick now is to not delete it.

But I was most interested to see how neumodvb works on Eutelsat 10A to 10.0E, which as we know, the signal and parameters are different from one transponder to another. Then I was curious how the 6903x card reads transponders with low symbol rate in the upper part of the band, where we have more Radio Maria programs.

Yes, 10.0E is interesting, but I cannot find any info on Radio Maria with low symbol rate on that sat. What frequency, polarisation and symbolrate?

Locking small symbolrates is tricky and depends on mysterious choices of te people who developed the chips. What always helps is to enter a low symbol rate, even when doing blindscan. Does the "get spectrum" detect a peak close to the correct frequency or not? That too can go wrong. Nothing is perfect

I wanted the application to scan only a part of the band, between 12500-12750 HV, but the application showed me the whole band of the satellite, from 10700-12750 MHz,on both polarities.I chose the blindscan to scan the whole satellite on both polarities. Everything went normal. I found that the Data transponders, although they had signals were not memorized. Instead, the feeds were memorized.

That is a design choice. Only DVB muxes are remembered.

Unfortunately, neumodvb did not close any low symbol rate on the Radio Maria transponders even if it detected the signal level, the SNR was not on the signal bar.

That means it cannot lock. Various possible reasons. If you tell me the frequency, and if I can receive it, I could try
myself. I had successes on 5.0W with Alouette and such (Symbolrate 687?), but I think they have gone. The cards officially do not support this (1000 Ms/s is the official limit)

So far that's all I can say after the first contact with neumodvb.

One step at a time.

I tried to change the volume on sound,= and -, but I didn't succeed. How can I use it? Or is it a bug?

It should work, or it is a bug. ou can always control the volume with the standard ubuntu sound control

Thanks a lot, Deeptho, for the effort you put into creating this program. You've taken a tremendous step, I'd say a leap, from some of the attempts by some exceptional developers in the Linux world to give reception enthusiasts a working tool but, it seems, have abandoned them or are in abeyance.
Fortunately, you provide us with the full working equipment.
To be excused for the rather long text on your topic. But I was glad I could install and work with your tool
Kind regards

Well, enjoy it. There are plenty of bugs, and there are a few satellites whcih make it extra difficult to not crash
(they report incorrect polarisation, or contradcitory information, or iimpossible frequencies) but it should be usable.

 

[deeptho]

I don't have neumoDVB on my present PC to check, but isn't the Bouquet list in the app used for storing the scanned sats? Deeptho should be able to advise.

Check the documentation....

Currently there is no data export, but all data can be accessed from python and then exported. That is not documented, and not implemented

 

[Llew]

So the data are in some form somewhere, but not easily accessible and/or converted easily into a comprehendible list?

 

[Llew]

If you tell me the frequency, and if I can receive it, I could try
myself.

There are some international Radio Maria TPs 0n 10E at 12.588V and 12.606V, 07V and 08V, but I have failed to lock them in the spectrum scanner.

 

[satesco]

1. I thought about putting that frontend.h file back in the DVB folder, but I figured there's no point in making trouble for myself since your application works,
2. There are six transponders now Radio Maria that I discovered in 2015. They are active and can be locked manually and auto, depending on the signal, with Crazyscan, EBSpro, and IQmonitor. You can find them on FlySat.
3. The tbs6983,6903 and USB5927 cards are the most reliable devices that lock this low symbol rate at 10.0E, but also others. My opinion is that these are the best performing DVB-s2 cards for the reception.
I'll try using the 6983 or 5927 cards at 10.0E and we'll know what neumodvb can do about it.
With the 6903x card I managed to lock the symbol rate and 281 Ks. But with others, you can't be sure you succeed every time.
If I have to confess one thing, then you should know that I am committed to installing your application to see to what extent on Linux the DVB cards(6903x/6909x) can perform at reception although I know they are designed mostly for streams, IPTV, and the like.

 

[deeptho]

No radio Maria to be received here: I see one peak in the spectrum. It does not lock. I general the spectrum looks
very different here in that frequency range, probably this is on a beam I cannot receive (1.2m dish)

 

[satesco]

Here are those low symbol rate transponders lock with Crazyscan, EBSpro and IQmonitor.
If you can include drivers for 6983/6903 in blindscan, then I can say that your application will outperform all others in Lynux.
I'll do a 5927 test with your app if you say you included the driver in your package.

 

[deeptho]

Here are those low symbol rate transponders lock with Crazyscan, EBSpro and IQmonitor.
If you can include drivers for 6983/6903 in blindscan, then I can say that your application will outperform all others in Lynux.
I'll do a 5927 test with your app if you say you included the driver in your package.

I have no 6983 or 6903 cards. stv091x cards are already supported, so they may work anyway (but there culd be problems if they use diffferent tuners) and you will not get high resolution spectra.

 

[satesco]

I think the best test you can do with DVB applications is on satellites with more spots, those without dth signal in the area. That's why I wanted to try the 6903x card with neumodvb at 90.0E, Yamal 401.
For this satellite, I had to edit the list of satellites of the application, which stops at 75.0E. I have added those in orbit up to 100.5E, the eastern limit where I can receive AsiaSat 5.
I'm still at the beginning of using neumodvb, maybe I'll find out later how I can set the limits between which I can scan the band. For now, the application setting is on the whole Ku band,i.e. from 10700-127500 MHz.
I'm a bit annoyed that the symbol rates on some transponders don't correspond to those, say, found by Crazyscan. I'll post the spectrum obtained by neumodvb and Crazyscan to compare some parameters. For example, at 11384 H, the symbol rate is 24500 on neumodvb, and on Crazyscan, 30000. There are other transponders with different parameters.
Another example, 11435 H uses the S2X extension, but on neumodvb it shows a symbol rate of 11800, while on Crazyscan it is 13500.
I also tested this satellite if neumodvb lock low symbol rate. Unfortunately at 90.0E, it didn't find any such low symbol rate. While Crazyscan was found and locked at auto search symbol rate of 492 at 12606 H, and at manual search also the one of 281 at 12556 H.
Can you get more out of neumodvb?

 

[Llew]

I'm still at the beginning of using neumodvb, maybe I'll find out later how I can set the limits between which I can scan the band. For now, the application setting is on the whole Ku band,i.e. from 10700-127500 MHz.

satesco,do you still have a problem setting a scan range? Can't you change the range in the From/To box, as in my range setting?


-