neumoDVB

[satesco]

@Llew, I hope you can see the recordings made after updating neumoDVB to v.1.2.1. This time, it was easier for me; no crashes.
I set the function easier, more uncomplicated, and straightforward, which is within reach of any user.
Recordings made can be found in Home/neumo/live/in one of the folders A0ts or recordings.

 

[JDavid22]

Yes, for the kernel you really must follow the instructions exactly because of media_build related issues.
Hopefully later some solution can be found to make this simpler. For now it means that either you stick
with the exact kernel version described in the README, and/or you experiment with multiple versions of
media_build until you find one that works.

What can also help is to disable the devices that give compilation errors, as they are almost never related to the dvb drivers.

I keep having problems when compiling the drivers, I read what was described above and now I think I have that problem. On my computer I have nvidia k5000, when I register tbsepc3 I see that it mentions the nvidia card and not the tbs6522, I am using kernel 5.8 this problem It didn't happen with kernel 5.19 but I couldn't get the checkbox OK blindscan, so I downgraded to 5.8 but I'm tempted to use the 5.13 that I see works, I just don't know if it works for my card like it did with the 6903x..
How would I proceed and disable the k5000 card?

 

[dreamsat]

Hello Deeptho,
could i install this software on a virtual machine. I don't have Linux running anywhere else.

best regeards

 

[Llew]

@Llew, I hope you can see the recordings made after updating neumoDVB to v.1.2.1. This time, it was easier for me; no crashes.
I set the function easier, more uncomplicated, and straightforward, which is within reach of any user.
Recordings made can be found in Home/neumo/live/in one of the folders A0ts or recordings.

I'm in the middle of recording something satesco. Confirmed, an update of neumodvb has placed a new A3.ts in neumo.

The main reason I wanted to check the viability of the recording process was to try it with my neumodvb in the Raspberry Pi. That still has problems showing a channel's video or audio (crashes on selecting/tuning a channel). Perhaps recording a channel instead of directly tuning it will at least prove mpv recording works. Not holding my breath though.

 

[deeptho]

I keep having problems when compiling the drivers, I read what was described above and now I think I have that problem. On my computer I have nvidia k5000, when I register tbsepc3 I see that it mentions the nvidia card and not the tbs6522, I am using kernel 5.8 this problem It didn't happen with kernel 5.19 but I couldn't get the checkbox OK blindscan, so I downgraded to 5.8 but I'm tempted to use the 5.13 that I see works, I just don't know if it works for my card like it did with the 6903x..
How would I proceed and disable the k5000 card?

You speak in riddles. What do the following mean:

• register tbsecp3? do you mean modprobe?
• "it mentions": what is "it"?

tbs6522 is not supported but may work.
I would not recommend downgrading the kernel.
Why would you want to disable the k5000 card?

 

[deeptho]

Hello Deeptho,
could i install this software on a virtual machine. I don't have Linux running anywhere else.

best regeards

That depends on what a windows virtual machine can do. Does it support pci express pass through? Then it may work.
I never use windows myself, so I don't know. I think is is better to run windows as a virtual machine under linux. That gives you
complete control over windows, like the possibility to restore windows to a known state after it installs a bad update.

 

[satesco]

I can't delete the devices/adapters in Edit Mode from the LNBs list. I wanted to remove them from the adapters list I no longer use. If I try to delete them, neumoDVB gets stuck. But actually, no adapter on the list can be deleted with this function.
Only the delete function for this operation does not respond and gets stuck. Then I used force quit. What should I do?

I have a request. I'm not sure that with your antenna, you can receive Amateur Radio at 26.0E. That's why I'm attaching the list of LNBs with the 6983 card (as an example) for the 26.0E position.
Please show me for each underlined item (red) how you set up the lnb to receive muxes from the sub-band, listing under each one what needs to be checked or changed. Thanks
(Please don't send me to documentation in this case)

 

[deeptho]

I can't delete the devices/adapters in Edit Mode from the LNBs list. I wanted to remove them from the adapters list I no longer use. If I try to delete them, neumoDVB gets stuck. But actually, no adapter on the list can be deleted with this function.
Only the delete function for this operation does not respond and gets stuck. Then I used force quit. What should I do?

This is a bug that keeps coming back. I have attempted to fix it once more in the latest version.
So, please upgrade.

I have a request. I'm not sure that with your antenna, you can receive Amateur Radio at 26.0E. That's why I'm attaching the list of LNBs with the 6983 card (as an example) for the 26.0E position.
Please show me for each underlined item (red) how you set up the lnb to receive muxes from the sub-band, listing under each one what needs to be checked or changed. Thanks
(Please don't send me to documentation in this case)

This setup is of course incorrect. You basically tell neumodvb that this is a standard universal lnb. So it will refuse to accept any value below 10.7Ghz for spectrum scan.

I don't get it: it is all explained in the documentation and there there is even an example for 26.0E. Why not simply follow that example?

 

[satesco]

....

This setup is of course incorrect. You basically tell neumodvb that this is a standard universal lnb. So it will refuse to accept any value below 10.7Ghz for spectrum scan.

I don't get it: it is all explained in the documentation and there there is even an example for 26.0E. Why not simply follow that example?

I'm sorry, but I think I misunderstood. I did not post that list because it was correct or incorrect. I wanted you to set how to fill in each item, underlined in red as if you were trying to receive these muxes yourself.
For example, what would you choose under "LNB type," "min freq," LOF low," etc., considering that I use the universal lnb (IBU)?
In other words, put yourself in the situation of an ordinary user who wants to set the lnb in neumoDVB for 10491 H,1500,4/5, and not the one who created the application.
That's what I want to know from you.
Thanks again.

 

[deeptho]

I'm sorry, but I think I misunderstood. I did not post that list because it was correct or incorrect. I wanted you to set how to fill in each item, underlined in red as if you were trying to receive these muxes yourself.
For example, what would you choose under "LNB type," "min freq," LOF low," etc., considering that I use the universal lnb (IBU)?
In other words, put yourself in the situation of an ordinary user who wants to set the lnb in neumoDVB for 10491 H,1500,4/5, and not the one who created the application.
That's what I want to know from you.
Thanks again.

Satesco,
it is for this reason that I created the documentation. All that you ask for is in there....
Here is a cut-and-paste version:

freq min. Editable This sets the lowest possible frequency the LNB can tune to. The special value -1 means that this is set to the default value for this LNB type, e.g., 10.7 GHz for a universal LNB. One reason to change the default is to receive amateur radio transmissions on 26.0E: TBS5927 supports tuning lower frequencies. E.g., change this value to 10.5GHz.


If you want to go lower than 10.5 then put a lower number. Anything but -1.

 

[satesco]

Test with neumoDVB 1.2.1 on 60.0E with the tbs6903x card.
I am getting a superb constellation of 32APSK at 10963 H,5000,3/4. Indeed, the signal is also above 20 dB.
Who wants to find and identify this position on the arc, take it as a reference.

 

[deeptho]

Yes, beatiful constellation.

 

[satesco]

It would have been better to open a topic dedicated to satellite reception with neumoDVB and Crazyscan app.
Ultimately, I thought it was better to post on this thread opened by Deeptho, because the reception tests on different satellites are related to the same issue for which neumoDVB was created.
I continue to test the 6903x card on satellites that do not have a DTH signal in my area. And I think it's essential to know to what extent neumoDVB reacts to uneven, weak signals to check how long a scan lasts and if it can lock problematic signals.
Of course, some users, who own this card and work more on Windows, are probably curious to compare what they get with this card working with Crazyscan under Windows and what results in neumoDVB achieves under Linux.
And I asked this question because I was curious to know this, so I tried to check this by traveling with the antenna to many positions on the arc, trying to post the results of this attempt.
Speaking of results, I must point out that the tests I am doing are realized with amateur receiving equipment, which apart from a dvb card, considered professional, can be more relevant in conclusions (I hope so) for all those who dare to receive satellites with neumoDVB and Crazyscan applications.
I have to add that I will not make comments. Of course, I do not claim that my results will be valid for all users under different conditions. Still, I will let the screenshots be eloquent enough to give you an idea of the possibilities of the 6903x/6909x cards exploited by the two applications that run on two different operating systems.
It is more of a personal experience that I want to share with others.
I hope that not being a Linux connoisseur, I won't have problems with neumoDVB, keeping in mind that Deeptho updates its application depending on several factors, especially bugs discovered in using it. Of course, other disruptive factors may prevent me from completing what I set out to do.
I use the 1.50m antenna, IBU lnb, card6903x.

Intelsat 39 @ 62° E

 

[deeptho]

It would have been better to open a topic dedicated to satellite reception with neumoDVB and Crazyscan app.
Ultimately, I thought it was better to post on this thread opened by Deeptho, because the reception tests on different satellites are related to the same issue for which neumoDVB was created.

Either way is possible. It might be easier for users looking for technical support to have a separate thread, but that is a detail.

I continue to test the 6903x card on satellites that do not have a DTH signal in my area. And I think it's essential to know to what extent neumoDVB reacts to uneven, weak signals to check how long a scan lasts and if it can lock problematic signals.

That depends mostly on the card (can it lock?), and a little bit on the drivers (how easy is it to lock?).
Also take into account that the definition of "lock" can be different. neumo only logs results if something useful can be
found in the stream, or if it is an old stream that cannot be locked any more. And the definition has changed over time, and
can vary between cards because of driver differences and even hardware differences.

Of course, some users, who own this card and work more on Windows, are probably curious to compare what they get with this card working with Crazyscan under Windows and what results in neumoDVB achieves under Linux.
And I asked this question because I was curious to know this, so I tried to check this by traveling with the antenna to many positions on the arc, trying to post the results of this attempt.

Any differences will be due to the drivers or sometimes due to luck. Like when the weather changes suddenly.
If something works better on windows, I would like to hear about it. It is not sure something can be done about it,
because sometimes a compromise is needed between one type of problem and another.

Speaking of results, I must point out that the tests I am doing are realized with amateur receiving equipment, which apart from a dvb card, considered professional, can be more relevant in conclusions (I hope so) for all those who dare to receive satellites with neumoDVB and Crazyscan applications.
I have to add that I will not make comments. Of course, I do not claim that my results will be valid for all users under different conditions. Still, I will let the screenshots be eloquent enough to give you an idea of the possibilities of the 6903x/6909x cards exploited by the two applications that run on two different operating systems.
It is more of a personal experience that I want to share with others.
I hope that not being a Linux connoisseur, I won't have problems with neumoDVB, keeping in mind that Deeptho updates its application depending on several factors, especially bugs discovered in using it. Of course, other disruptive factors may prevent me from completing what I set out to do.
I use the 1.50m antenna, IBU lnb, card6903x.

Intelsat 39 @ 62° E

 

[Llew]

In Blindscan on linux with tbs cards the TBS6522 is being discussed, so I took my card out of retirement and installed it in the PC with the 6903 tuners.

However, there's no spectrum activity or tuning with the 6522. Checking an error thrown up in neumo.log, I may be wrong, but there seems to be a problem in setting the diseqc for the port I'm using, diseqc 0 (or any other port).

I'm using the same parameters as in the TBS6903 cards, which have no problem successfully tuning the same satellite (or any other ones).

There is no problem with diseqc using the 6522 in Windows.

@deeptho, perhaps you could check the neumo.log for clues to the problem? There's nothing in the console except the usual neumo.py loading options.

 

[deeptho]

In Blindscan on linux with tbs cards the TBS6522 is being discussed, so I took my card out of retirement and installed it in the PC with the 6903 tuners.

However, there's no spectrum activity or tuning with the 6522. Checking an error thrown up in neumo.log, I may be wrong, but there seems to be a problem in setting the diseqc for the port I'm using, diseqc 0 (or any other port).

I'm using the same parameters as in the TBS6903 cards, which have no problem successfully tuning the same satellite (or any other ones).

There is no problem with diseqc using the 6522 in Windows.

@deeptho, perhaps you could check the neumo.log for clues to the problem? There's nothing in the console except the usual neumo.py loading options.

Perhaps you should first update the driver?

 

[Llew]

Perhaps you should first update the driver?

Still 1.5.

Also, No muxes are found using 6522 T/T2, so maybe it's more problematic than first thought. Other T/T2 gadgets I have OK with that.

 

[Butacas]

How do I make the TBS 5727 card show up?

I have neumodvb in Fedora 37 and the card does not appear in the frontend.

I have followed all these steps as well, but everything remains the same.

deeptho/linux_media

 

[Butacas]

TBS 5927

 

[Butacas]

I have followed all the steps, the .sh script as well.

Llew I no longer see your post.