neumoDVB

Your compile report is not helpful as all the interesting parts have been omitted.
Did you follow the compilation instructions?
 
I have just released version 1.9 of neumodvb. The main novelty is that it better exploits the newest
driver facilities for stid135 based cards and for embedded t2mi streams.
This has only been tested well with the newest drivers (release-1.8 which will be available later today).

Improvements​

  • Allow sharing of mux tuned in positioner_dialog.
  • positioner_dialog: do not add requested isi to isi list when it does not exist in stream.
  • Avoid showing fake stream_id -1 in positioner_dialog when user requests non-existing ISI.
  • Improved handling of unrelated muxes with same mux_id.
  • Distinguish between peak and mux scan in frontendlist.
  • New si code to handle multiple ISI streams on the same tuned frontend.
  • Remove driver_supports_t2mi argument.
  • Use driver support for embedded t2mi streams when available.
  • Allow illegal rbsp fields in video streams, which prevent proper time stamping of Ambience TV on 1.9E.
  • Silence some log messages.
  • Improved debug messages.
  • Updated neumodmx.h.
  • Silence some gdb warnings (.gdbinit).

Bug fixes​

  • Incorrect naming of backup dbs.
  • Do not share subscriptions between two template muxes.
  • Incorrect assertions on transport streams without content.
  • When tuning to good multi-stream, the current mux is not saved if the mux is a template.
  • When tuning to a single stream which is really a multistream, si code never times out.
  • Polarisation ignored when reserving mux.
  • Unneeded tuning in some cases, causing a failure due to an unknown lnb.
  • When user requests non-existing ISI, a mux is created in the database.
  • Incorrect SI processing when requested ISI does not exist.
  • Incorrect active_adapter_t::mux_for_key.
  • Information from other mux shown in spectrum dialog when mux does not lock.
  • Accidental reuse of mux_id on template muxes.
  • Make get_positioner_move_stats return pol as well.
  • Nit processing started before pat has been received, resulting incorrect flagging nit as invalid in positioner_dialog.
  • Incorrect ts_id and network_id passed to driver and then to positioner_dialog.
  • Number of services accidentally cleared in mux records in database.
  • Infinite waiting for last_signal_info.
  • Incorrect assertions.
  • Request_tune can return without yet tuning when positioner is moving. In that case active_adapter concludes erroneously that tune failed.
  • Handle races in task_queue_t::stop_running.
  • Deadlock in receiver_t::stop.
  • Matches_physical_fuzzy: make symmetric.
  • Restrict calling active_adapter_t::on_stream_mux_change.
  • Clean_overlapping_muxes: detect change from multistream to single stream and vice versa.
  • Incorrectly set requested_stream_id.
  • PAT_TUNED overwritten.
  • Updated_new_dbfe not correctly set when reusing subscription.
  • Show error message when starting blindscan without selected spectra, instead of silently failing.
  • Improved chdb::matches_physical_fuzzy.
  • Null pointer dereference on closing mpv window.
  • Incorrect argument order in call leads to incorrect subscription.
  • Suppress warning for MHP_IPv4RoutingDescriptorTag
  • Assertions to ensure set_rf_input is called.
  • Incorrect propagation of scanning when detecting new ISIs.
  • scans_in_progress cleared immediately after being filled.
  • Do not allow mux reuse if bbframes are not on.
  • Fix Python assertion in frontend list.
  • Improved removal of fibers when active_service is ending.
  • Remove newlines in debug messages.
  • Bug in deciding to request bbframes or not.
  • Incorrect creation of service_name for pat-only service.
  • Make lmdb_hint work again.
  • No longer update stream_id from driver mux while processing si.
  • T2MI mux causes update_stream_mux_tune_confirmation to be called.
  • Allow sorting of lnb network and connection lists.
  • Remove unused cable_no fields.
  • Incorrectly adding sats to wrong database when user agrees to add them.
  • Incorrect highlight colour in cable list
 
deeptho said:
I have just released version 1.9 of neumodvb. The main novelty is that it better exploits the newest
driver facilities for stid135 based cards and for embedded t2mi streams.
This has only been tested well with the newest drivers (release-1.8 which will be available later today).
Click to expand...


Thank you for this.
I have a question if you can please help?

Would it be possible to update the instructions for compilation/instalation from github for more recent versions of ubuntu (not MATE) such as 24.04.02 LTS?
 
moonbase said:
Thank you for this.
I have a question if you can please help?

Would it be possible to update the instructions for compilation/instalation from github for more recent versions of ubuntu (not MATE) such as 24.04.02 LTS?
Click to expand...
Sure, of someone sends me the changed instructions.
 
Hi

Deeptho, do you know when the new blindscan driver will be available ?

In the mean time, I saw that you have updated the blindscan tools and documentation.
I think there's a typo as you mention NRK GSE radio mux is on 5W but it should be 0.8W instead ?

If I understand correctly, I could use neumo-dmx instead of dvbstream or dvbsnoop as it provides an advanced handling of streams ?
 
RyLe said:
Hi

Deeptho, do you know when the new blindscan driver will be available ?

In the mean time, I saw that you have updated the blindscan tools and documentation.
I think there's a typo as you mention NRK GSE radio mux is on 5W but it should be 0.8W instead ?

If I understand correctly, I could use neumo-dmx instead of dvbstream or dvbsnoop as it provides an advanced handling of streams ?
Click to expand...
Thanks for pointing out the errors, but I already corrected this yesterday. The drivers are on github as well.

I would use neumo-dmx. Yes.
 
I am a bit annoyed that although I have updated neumoDVB, when I test with "cat /sys/module/dvb_core/info/version", I get v.1.7 and not v.1.9.
What am I doing wrong, if?
 

Attachments

  • neumoDVB v.1.7_2025-06-13_10-48.webp
    neumoDVB v.1.7_2025-06-13_10-48.webp
    14 KB · Views: 31
satesco said:
I am a bit annoyed that although I have updated neumoDVB, when I test with "cat /sys/module/dvb_core/info/version", I get v.1.7 and not v.1.9.
What am I doing wrong, if?
Click to expand...


Same version 1.7 here from installation done on 7th May 2025.

I checked the changelog but could not see the version release dates.
Just a guess but as we are now on version 1.9 I think I should have been on version 1.8.
 
satesco said:
I am a bit annoyed that although I have updated neumoDVB, when I test with "cat /sys/module/dvb_core/info/version", I get v.1.7 and not v.1.9.
What am I doing wrong, if?
Click to expand...
Yes, I had a similar experience once: I went to check the washing machine and I was a bit annoyed that it did not contain my dinner.
:->
You are confusing a driver interface version with something completely unrelated.
 
deeptho said:
Yes, I had a similar experience once: I went to check the washing machine and I was a bit annoyed that it did not contain my dinner.
:->
You are confusing a driver interface version with something completely unrelated.
Click to expand...


Was the washing machine a dish washer, it might have contained the dirty plate from a previous version of your dinner ?

So if we are confusing the driver interface version with something unrelated, where do we find out the version of neumoDVB ?
 
moonbase said:
where do we find out the version of neumoDVB ?
Click to expand...
What version do you have in neumodvb/build/src/util?

I'm still on 1.8, despite current update.

neumodvb version.webp
 
About to embark on a neumodvb install later. The somewhat unhelpful replies here fill me with confidence. Fingers crossed I don't run into any issues.
 
deeptho said:
Yes, I had a similar experience once: I went to check the washing machine and I was a bit annoyed that it did not contain my dinner.
:->
You are confusing a driver interface version with something completely unrelated.
Click to expand...
I would have preferred that you provide me with an answer to my question rather than receiving what I now see as gratuitous irony.
This isn't a master chef competition; after all, we're using your tools, and if we have difficulty using them, we hope for help, regardless of where it comes from.

I understand that it's hard to answer our ignorant questions, as you have other projects and don't have time for everyone.
In over 70 pages on this thread and with many followers, only @Llew jumped in from time to time to help those who were having problems using neumoDVB.

Many Linux experts are reading this thread, and I would have expected one of them to provide a helpful answer to those seeking assistance. Unfortunately, their silence forces us to turn to you.

For this reason, I am sorry to have to ask for your help, which you have generously offered me up to this point. It seems that this “reservoir” is running dry. This will force me to put my hand on the book, pardon me, on Linux. :(:)
 
satesco said:
For this reason, I am sorry to have to ask for your help, which you have generously offered me up to this point. It seems that this “reservoir” is running dry. This will force me to put my hand on the book, pardon me, on Linux. :(:)
Click to expand...


@satesco

The neumoDVB author will be busy looking for his dinner in the dish washer and probably too busy to reply. Perhaps if you tell him his dinner is in the oven it will speed things up and you might get reply. The dinner could of course be in the dog....

.
Untitled.webp
 
Clean installation of latest debian13 with kernel 6.12.30. Blindscan drivers installed fine following directions from github. Unfortunately, I'm not able to build neumodvb. I just couldn't go beyond 11% of building. Console output is attached and the error at line 109 is visible:
logger.cc:78:3: error: call to 'configureAndWatch' is ambiguous
78 | DOMConfigurator::configureAndWatch(logconfig, 1000);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Note that this is not full log, just the last part of it.
So far I've tried reinstalling gcc, g++ (default version is 14 but also tried 13 with required dependencies).
Further, directions says it needs clang-16 version so I had to manually install with all needed dependencies. Later I treid default version (19 on debian)but outcome is always the same.
Could someone with better linux knowledge point me in the right direction with this "ambiguous" error as I ran out of the options.
 

Attachments

satesco said:
I would have preferred that you provide me with an answer to my question rather than receiving what I now see as gratuitous irony.
This isn't a master chef competition; after all, we're using your tools, and if we have difficulty using them, we hope for help, regardless of where it comes from.

I understand that it's hard to answer our ignorant questions, as you have other projects and don't have time for everyone.
In over 70 pages on this thread and with many followers, only @Llew jumped in from time to time to help those who were having problems using neumoDVB.

Many Linux experts are reading this thread, and I would have expected one of them to provide a helpful answer to those seeking assistance. Unfortunately, their silence forces us to turn to you.

For this reason, I am sorry to have to ask for your help, which you have generously offered me up to this point. It seems that this “reservoir” is running dry. This will force me to put my hand on the book, pardon me, on Linux. :(:)
Click to expand...
Satesco,
calm down. The answer was in my reply after the joke:

"You are confusing a driver interface version with something completely unrelated."

The versions of the kernel drivers (which is what you checked). Have nothing to do with the
version of neumodvb.

The way Llew is checking is better, but he has not yet updated properly. The best way is to check neumo.log, because people
make many other mistakes like not recompiling.


2025-06-15 17:04:38,572 INFO: [ ] BUILD=4129a53+ TAG= BRANCH=master il/identification.cc:35

-> BUILD=4129a53

I am running a more recent version than on github. github also had the tag neumodvb-1.9 missing, but this only affects
what is printed in the log file. the code is/was there!
 
nighthawk77 said:
Clean installation of latest debian13 with kernel 6.12.30. Blindscan drivers installed fine following directions from github. Unfortunately, I'm not able to build neumodvb. I just couldn't go beyond 11% of building. Console output is attached and the error at line 109 is visible:
logger.cc:78:3: error: call to 'configureAndWatch' is ambiguous
78 | DOMConfigurator::configureAndWatch(logconfig, 1000);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Note that this is not full log, just the last part of it.
So far I've tried reinstalling gcc, g++ (default version is 14 but also tried 13 with required dependencies).
Further, directions says it needs clang-16 version so I had to manually install with all needed dependencies. Later I treid default version (19 on debian)but outcome is always the same.
Could someone with better linux knowledge point me in the right direction with this "ambiguous" error as I ran out of the options.
Click to expand...
This is due to some recent changes in an external library. Will be fixed in the new version (soon).
 
@deeptho,

Thanks for your reply. I knew I was doing something wrong, but didn't know what it was. That's why I asked you.
I checked again, and the driver version doesn't show up even though I recently (re)installed it. It just shows the installation source.
What is the correct command to check the version of the installed driver?

"const char* GIT_REV="de1b0d2";
const char* GIT_TAG="";
const char* GIT_BRANCH="master";"

I want to think that my questions are probably those of other Linux newbies.
On this occasion, I would like to ask those who use neumoDVB and are knowledgeable in Linux to answer when users ask about a particular problem or issue with this system.
I thank them in advance. :)
 
Back
Top