neumoDVB

[satesco]

I finally managed to scan the circular muxes from 36.0E on the toroidal. When scanning, I had a few crashes with neumoDVB, but it ultimately worked. Below are the settings I made to the circular lnb and switch 1.1 for 36.0E.
Port 0 for Tursat in the switch does not work, although I followed the instructions in your document. Same failure as in previous days. Among all ports 0-15, only the first 0 does not work.
So only with port 0 I had and still have problems.

 

[deeptho]

Satesco,

-your log gile shows no evidence of crashes
-obviously without providing the kernel logs, nothing can be done to diagnose the 42.0E problem.
See #700, #694
-your screenshot indicates the same lnb configuration as yesterday, which does not allow tuning above 12200. But probably you have changed
something, because the spectrum shows a result above that frequency. So the screenshot is not up to date?

 

[satesco]

Here is the kern.log and screenshot with the settings for 36.0E. I hope this time I didn't miss something vital for you.

 

[deeptho]

Your 36.0E is now configured correctly, which explains why it works now.

For 42.0E the kernel log show nothing special. I suspect a problem with your setup, such
as confusing port 0 with another one. Port 0 is the default, so try it without diseqc (after powering down)

Why not meausure the voltage at various places (output of the card, input of the lnb)
during scan. The voltge should switch between 13 and 18. It should be easy to see of that happens or not.

 

[satesco]

I am working on Windows now and noticed problems with the first port at 42.0E. I need to physically check the Diseqc 1.1 switch if I have issues connecting the cable for port 0 (neumoDVB ) / 1 (Crazyscan).
I'm working with another kernel version, but I don't think that's the problem; otherwise, the switch works fine on the other ports.
On another note, I will have to test for all standards (Cable, Ka-band, etc.) after switching to neumoDVB 1.2. I seem to have problems (crashes) scanning cable programs as well. I'll come back after I'm sure the probing is not accidental.
Strangely, the cable programs I scanned with neumoDVB 1.1 can usually be watched even with v.1.2.

 

[deeptho]

If you have crashes, then you need top provide the right information. The best is to provide everything each time.
kernel log, neumo log, console messages (all for the same time period)

 

[satesco]

I hope the files help you determine why neumoDVB crashes when scanning cable muxes.

 

[deeptho]

Satesco,
you can try the new version (uploaded now) which will fix this. I hope the new fix does not break things on satellite.

 

[satesco]

I updated neumoDVB after you fixed it. This time it didn't crash, but it didn't scan either. I tried to check/scan all muxes by Ctrl+S, but when it reaches 330.000 MHz, it stops, doesn't want to scan anymore, and all other muxes are in Pending. And so it stays, and if I want to stop it, I have to exit neumoDVB just "Force Quit."
I thought about deleting all muxes and Services TV with the Delete command in Edit, but nothing happened; not only does it not delete them, but the application seems to freeze/get stuck. Only with the "Force Quit" command can I close the app.
I have attached the files you need for diagnosis.

 

[Llew]

I just did a scan on a DVB-T2 mux and it crashes after a scan. This is with the updated neumodvb.

I'll check the log files to see if there's errors after I've done some more investigation.

 

[deeptho]

I just did a scan on a DVB-T2 mux and it crashes after a scan. This is with the updated neumodvb.

I'll check the log files to see if there's errors after I've done some more investigation.

I think you forgot to recompile.

 

[Llew]

I think you forgot to recompile.

I think you're right deeptho. Silly me. Forgetful in my old age

 

[deeptho]

I updated neumoDVB after you fixed it. This time it didn't crash, but it didn't scan either. I tried to check/scan all muxes by Ctrl+S, but when it reaches 330.000 MHz, it stops, doesn't want to scan anymore, and all other muxes are in Pending. And so it stays, and if I want to stop it, I have to exit neumoDVB just "Force Quit."
I thought about deleting all muxes and Services TV with the Delete command in Edit, but nothing happened; not only does it not delete them, but the application seems to freeze/get stuck. Only with the "Force Quit" command can I close the app.
I have attached the files you need for diagnosis.

It seems that you have many copies of the 330MHz. This may be a leftover from the last bug. Try and remove all but one of them and then rescan. Same for all the other duplicate muxes.

 

[satesco]

It seems that you have many copies of the 330MHz. This may be a leftover from the last bug. Try and remove all but one of them and then rescan. Same for all the other duplicate muxes.

That's what I wanted to do; I even mentioned that, to delete all the muxes and programs scanned and saved from the previous version. Other muxes are repeated several times but are not visible in the screenshot. But I can't delete them because the application gets stuck and won't let me do anything. I tried to delete the channels and frequencies in one of neumoDVB's folders or somewhere else, but I couldn't find them.
BTW, where are they stored?

 

[deeptho]

That's what I wanted to do; I even mentioned that, to delete all the muxes and programs scanned and saved from the previous version. Other muxes are repeated several times but are not visible in the screenshot. But I can't delete them because the application gets stuck and won't let me do anything. I tried to delete the channels and frequencies in one of neumoDVB's folders or somewhere else, but I couldn't find them.

Try it again with the latest version

BTW, where are they stored?

In the database, along with all other data.

 

[Llew]

That's what I wanted to do; I even mentioned that, to delete all the muxes and programs scanned and saved from the previous version. Other muxes are repeated several times but are not visible in the screenshot. But I can't delete them because the application gets stuck and won't let me do anything. I tried to delete the channels and frequencies in one of neumoDVB's folders or somewhere else, but I couldn't find them.
BTW, where are they stored?

deeptho's updated the release in the last couple of hours satesco -

BUG: After moving positioner, lnb list updates, but row sizes are not…

Perhaps it's relevant. Can't check myself at present, I'm updating the program.

Edit: deeptho has replied.

 

[satesco]

I updated neumoDVB today, "HEAD is now at 239726a Avoid assertion on DVBC". Not only does it not scan cable muxes, but the Delete function in Edit doesn't work at all, regardless of the option in Lists: DVB-S, DVB-C, Spectra, Services, etc.
Again neumoDVB is getting stuck, and then I have to kill it, "Force Quit."
I'm unsure, but are Database db files with .mdb extension in neumo?

 

[deeptho]

I updated neumoDVB today, "HEAD is now at 239726a Avoid assertion on DVBC". Not only does it not scan cable muxes, but the Delete function in Edit doesn't work at all, regardless of the option in Lists: DVB-S, DVB-C, Spectra, Services, etc.
Again neumoDVB is getting stuck, and then I have to kill it, "Force Quit."
I'm unsure, but are Database db files with .mdb extension in neumo?

Satesco,
unfortunately when it rains it poors.

I think it is fixed now properly (the deletion of rows - don't know for sure about the scanning).
So can you try again.

The database is indeed in the mdb files, but the only way to edit it is through neumoDVB or through writing some python programs.

 

[Llew]

Satesco,
unfortunately when it rains it poors.

I think it is fixed now properly (the deletion of rows - don't know for sure about the scanning).
So can you try again.

The database is indeed in the mdb files, but the only way to edit it is through neumoDVB or through writing some python programs.

DVB-T mux deletion working fine, keeping the OK mux. I removed my DVB-T services too, so they are automatically taken out of the Channel list (were numbered "1", leaving Enex Path 1 16E as last listed channel.

 

[satesco]

With today's update (#de61b60 ), I managed to scan all the cable muxes, but before that, I deleted all of them and, simultaneously, the Services. So it worked. Thanks, @deeptho
For the terrestrial reception configuration, I admit I was annoyed, and it took me a long time to find the solution to lock the signal and scan the terrestrial services for the 6590 C/T card. Compared to my first experience with terrestrial reception with neumoDVB, last August, with this version, I had to choose 1 for priority, for the card and the standard (terrestrial) to work and show my subscription.
I don't remember than having to give priority 1 to the adapter for terrestrial.

@Llew,
Our settings differ because, in our country, they switched directly to the Dvb-T2 standard while you still keep Dvb-T.
But I'm glad we're united in trying to use neumoDVB. I hope we're not the only ones using it.