neumoDVB

[satesco]

I have scanned with neumoDVB on 12606 V stream 5 PLS Root 16416 with PID 4096 T2-Mi with different cards. Stream 5 programs were found and saved, but I could not see them.
Due to the signal, which manifests differently depending on the cards used, pid 4096 for T2-Mi was picked up by stream 4, which is an error.
The ID is not found when scanning stream 5, which is probably why the programs were not displayed(?).

Now, I'm not unsure if I didn't see the Stream 5 package because of TSduck or if it's a bug/error; who knows where?

As usual, the 6909x card attenuates the signal significantly, by over 3dB, which is inconclusive for any test when the signal is not strong.

 

[deeptho]

According to the screenshots, you do not use 6909x. In any case, the difference in RF level is not important as the values
are not always computed correctly and do not affect reception

 

[ptergrand]

We are waiting for neumodvb-1.8

 

[satesco]

According to the screenshots, you do not use 6909x. In any case, the difference in RF level is not important as the values
are not always computed correctly and do not affect reception

Normal, because the 6909x does not lock the signal on 12606 V, but only with the two cards posted. That's why I posted them to see the difference in signal management.

 

[deeptho]

I have scanned with neumoDVB on 12606 V stream 5 PLS Root 16416 with PID 4096 T2-Mi with different cards. Stream 5 programs were found and saved, but I could not see them.

The screenshot shows that it is for stream 5, and this is correct. Also neumodvb decodes the channels fine on this t2mi stream, on tbs 6904se, but not on tbs6909x for some reason. There is something special about the modulation.

Due to the signal, which manifests differently depending on the cards used, pid 4096 for T2-Mi was picked up by stream 4, which is an error.
The ID is not found when scanning stream 5, which is probably why the programs were not displayed(?).

Now, I'm not unsure if I didn't see the Stream 5 package because of TSduck or if it's a bug/error; who knows where?

As usual, the 6909x card attenuates the signal significantly, by over 3dB, which is inconclusive for any test when the signal is not strong.

 

[satesco]

The screenshot shows that it is for stream 5, and this is correct. Also neumodvb decodes the channels fine on this t2mi stream, on tbs 6904se, but not on tbs6909x for some reason. There is something special about the modulation.

Of course, your opinion comes from the developer's side, but I'm trying to find an explanation from a reception point of view.
But for the moment, the 6903x/6909x cards can't lock the signal on 12606 V with my antenna, which is small for the signal it picks up.
If someone has these cards and has a big antenna, it would be good to try to lock this mux.
Although I have no proof, I'm convinced that if the signal is above the threshold, 6903x/6909x could lock and run T2-Mi.

 

[deeptho]

This has nothing to do with reception.
I think I am on the way to finding a solution: this is what I just achieved on tbs6909xV2
and currently it is raining.... Reception is not good.

Just after the screenshot below, a guy is killed by a bull :->
Followed by some adds...

 

[moonbase]

Two questions if anyone can please help?

1. How does nuemodbv define the Symbol Rate, Roll Off and Carrier Width (Bandwidth) in a blind scan?
Does it measure two of the parameters and estimate the third? For example, does it measure Carrier Width and Roll Off then estimate the Symbol Rate from those two values?

2. Which version of Linux is best to install for nuemodvb, ie, a Linux version that has the most friendly install of nuemodbv?

Thank you.

 

[deeptho]

Two questions if anyone can please help?

1. How does nuemodbv define the Symbol Rate, Roll Off and Carrier Width (Bandwidth) in a blind scan?
Does it measure two of the parameters and estimate the third? For example, does it measure Carrier Width and Roll Off then estimate the Symbol Rate from those two values?

The same way as all other programs: by asking the chip what parameters it found during tuning.
neumoDVB also inspects the NIT tables and can thus find also values for non-tuned transponders. If the satellite transmits the
wrong information (that happens), then the results can be incorrect. If this contradicts the values found by the driver, then some \
rules in the code try to make the best guess. Usually the driver values then are trusted more.

2. Which version of Linux is best to install for nuemodvb, ie, a Linux version that has the most friendly install of nuemodbv?

Thank you.

Fedora 40 or a recent ubuntu.

 

[moonbase]

The same way as all other programs: by asking the chip what parameters it found during tuning.
neumoDVB also inspects the NIT tables and can thus find also values for non-tuned transponders. If the satellite transmits the
wrong information (that happens), then the results can be incorrect. If this contradicts the values found by the driver, then some \
rules in the code try to make the best guess. Usually the driver values then are trusted more.


Fedora 40 or a recent ubuntu.

Thank you for your reply.

I think I will go with ubuntu.
The most recent LTS version is 24.04 (April 2024), will this be a suitable version to install?

 

[satesco]

Thank you for your reply.

I think I will go with ubuntu.
The most recent LTS version is 24.04 (April 2024), will this be a suitable version to install?

I'm probably not the most qualified to advise you on what and how under Linux.
But, like you, coming from a Windows environment, I was careful when I installed and compiled neumoDVB with some apprehension.

I installed neumoDVB on LTS Ubuntu 24.04. I was pleasantly surprised that Deeptho's driver and app were installed without problems.
That is, I didn't copy and paste the whole list of packages (that's for the knowledgeable), but I took each one in turn to ensure it was installed without errors. Where I was missing a file or something, I looked it up on the net.
It is a time-consuming way of working, but it is safer, and you know that you don't miss something important (in fact, they are all important).

For a beginner installing another operating system they don't know, patience at every stage is the most critical factor to success. I say this with full knowledge of the facts.

We must stand the test of time (by giving something up), not vice versa.
I hope you succeed.

 

[moonbase]

I'm probably not the most qualified to advise you on what and how under Linux.
But, like you, coming from a Windows environment, I was careful when I installed and compiled neumoDVB with some apprehension.

I installed neumoDVB on LTS Ubuntu 24.04. I was pleasantly surprised that Deeptho's driver and app were installed without problems.
That is, I didn't copy and paste the whole list of packages (that's for the knowledgeable), but I took each one in turn to ensure it was installed without errors. Where I was missing a file or something, I looked it up on the net.
It is a time-consuming way of working, but it is safer, and you know that you don't miss something important (in fact, they are all important).

For a beginner installing another operating system they don't know, patience at every stage is the most critical factor to success. I say this with full knowledge of the facts.

We must stand the test of time (by giving something up), not vice versa.
I hope you succeed.

@satesco

Thank you for your reply.

I will take it one step at a time but it might mean I am back quite a few times with questions.
The installation of the ubuntu O/S should be OK, I have done that before. Where I will get lost is with app/driver/file/kernel installations.

 

[satesco]

As I said, I'm not the best person to guide you through the installation of neumoDVB. As you know, even good intentions can lead to failures or errors, in some cases even catastrophes.
But I think I'm not wrong if I tell you what I did when I cleanly installed the driver and neumoDVB. That doesn't mean that it will ensure success.

First, I installed @deeptho's driver according to the documentation here and here.
For Ubuntu 23.04 LST, I have the following steps, according to it, namely (I copy what it says there):

"mkdir ~/blindscan_kernel
cd ~/blindscan_kernel
git clone --depth=1 GitHub - deeptho/linux_media: neumoDVB blindscan drivers media_tree ./media
git clone GitHub - deeptho/media_build_old: media_build for compiling the neumoDVB media_tree on this site
cd media_build
git checkout deepthought
git reset --hard
make dir DIR=../media
make distclean
./install.sh

Last but not least, install rsyslog so that kernel debug messages are stored in the file system in /var/log/debug:
sudo apt install -y rsyslog
sudo vi /etc/rsyslog.conf # add "kern.debug /var/log/debug" line
sudo systemctl enable rsyslog
sudo systemctl start rsyslog #to have log messages in /var/log/debug

Now install the firmware (if needed):
wget http://www.tbsdtv.com/download/document/linux/tbs-tuner-firmwares_v1.0.tar.bz2
sudo tar jxvf tbs-tuner-firmwares_v1.0.tar.bz2 -C /lib/firmware/

Now load the drivers: either reboot, or try loading the proper module for your card, e.g., tbsecp3 for many cards:
sudo modprobe tbsecp3"

I must add that I have been working with the 6.8.0-39-generic kernel since I first installed it, even if new versions have appeared, which I have accepted at installation but don't use.

For now, I think it's important to ensure that you don't encounter errors when installing @deeptho's driver.
Installing neumoDVB is another story, a bit more complicated. I have noticed that some users, myself included, have gotten stuck when they fail the first time.

I hope @deeptho or other Linuxers will correct me if I made a mistake with the driver installation command line.

 

[moonbase]

@satesco

Thank you for the detailed explanation.

I have put together an older PC (i7-2600k with 16gb of RAM and 120gb SSD) and installed ubuntu LTS 24.04
The PC motherboard is EFI bios and I got a message about /EFI/grub not found but ubuntu seemed to install OK and the PC reboots OK after displaying the message /EFI/grub not found.

As the PC is booting into ubuntu I assume I am OK to proceed ?

I have a couple of questions if anyone can please help?
1. Are all the commands typed in a terminal window, apologies if this is obvious but to a non Linux user it is all new.
2. I do not yet have a TBS card in the ubuntu PC, do I wait until I have inserted a TBS card in the machine before starting any of the installations?

 

[moonbase]

@satesco

Is this process you listed below what I need to type in the terminal window to install the driver of @deeptho ?


"mkdir ~/blindscan_kernel
cd ~/blindscan_kernel
git clone --depth=1 GitHub - deeptho/linux_media: neumoDVB blindscan drivers media_tree ./media
git clone GitHub - deeptho/media_build_old: media_build for compiling the neumoDVB media_tree on this site
cd media_build
git checkout deepthought
git reset --hard
make dir DIR=../media
make distclean
./install.sh

 

[satesco]

1. All command lines are done from the terminal to install the driver and neumoDVB.
In Linux, there is no executable for these applications.

2. I have not tried to install the application without a dvb card on the computer.

3. I installed the driver with the above command.

 

[moonbase]

2. I have not tried to install the application without a dvb card on the computer.

Was the TBS card inserted in the PC before you installed ubuntu or did you place the TBS card in the PC after the installation of ubuntu had completed?

 

[satesco]

It doesn't matter if you have a DVB card or not on your computer when you install Ubuntu or any other system.
The driver of that card is responsible for its operation.

 

[deeptho]

Was the TBS card inserted in the PC before you installed ubuntu or did you place the TBS card in the PC after the installation of ubuntu had completed?

This is not windows. Any order will work.

And if you are unfamiliar with linux, then why not read a bit about it.
For example:

https://ubuntu.com/tutorials/command-line-for-beginners#1-overview

 

[moonbase]

As I said, I'm not the best person to guide you through the installation of neumoDVB. As you know, even good intentions can lead to failures or errors, in some cases even catastrophes.
But I think I'm not wrong if I tell you what I did when I cleanly installed the driver and neumoDVB. That doesn't mean that it will ensure success.

First, I installed @deeptho's driver according to the documentation here and here.
For Ubuntu 23.04 LST, I have the following steps, according to it, namely (I copy what it says there):

"mkdir ~/blindscan_kernel
cd ~/blindscan_kernel
git clone --depth=1 GitHub - deeptho/linux_media: neumoDVB blindscan drivers media_tree ./media
git clone GitHub - deeptho/media_build_old: media_build for compiling the neumoDVB media_tree on this site
cd media_build
git checkout deepthought
git reset --hard
make dir DIR=../media
make distclean
./install.sh

Last but not least, install rsyslog so that kernel debug messages are stored in the file system in /var/log/debug:
sudo apt install -y rsyslog
sudo vi /etc/rsyslog.conf # add "kern.debug /var/log/debug" line
sudo systemctl enable rsyslog
sudo systemctl start rsyslog #to have log messages in /var/log/debug

Now install the firmware (if needed):
wget http://www.tbsdtv.com/download/document/linux/tbs-tuner-firmwares_v1.0.tar.bz2
sudo tar jxvf tbs-tuner-firmwares_v1.0.tar.bz2 -C /lib/firmware/

Now load the drivers: either reboot, or try loading the proper module for your card, e.g., tbsecp3 for many cards:
sudo modprobe tbsecp3"

I must add that I have been working with the 6.8.0-39-generic kernel since I first installed it, even if new versions have appeared, which I have accepted at installation but don't use.

For now, I think it's important to ensure that you don't encounter errors when installing @deeptho's driver.
Installing neumoDVB is another story, a bit more complicated. I have noticed that some users, myself included, have gotten stuck when they fail the first time.

I hope @deeptho or other Linuxers will correct me if I made a mistake with the driver installation command line.

I have proceeded through the first 10 lines of entry in the terminal window without generating any error messages, a screen grab is attached below.



Before I install rsylog do I need to come out of the directory structure that I have created and start with a new terminal window?
Or, do I install rsylog at the directory level I am at now (terminal is still open at the prompt in the picture above) ?

Thank you.