INTERACT FORUM
Windows => Television => Topic started by: tunes0710 on April 15, 2019, 09:15:08 am
-
Hi all.
I've read through the manage channel guide, but I can't figure out what I need to do.
My tuner has found lots of channels, and I've set up EPG Collector to get EPG data, but in the manage channels section there is no channel number next to the channel name.
Is there any way of getting data from somewhere to automatically match up the channel against say the UK freeview channel numbers, or even the sky channel numbers?
Is this something I need to do through EPG Collector? if so, is there a guide on how I can set channel numbers there?
Lastly, I'd like to remove duplicated channels, I'm assuming this is what autogroup is for, but when selecting it, I've ordered it for dvb-s to be at the top, but it doesn't appear to group anything?
I realise I could manually group it, but I was hoping there was a way of automatically grouping with me just manually verifying it was all ok?
My aim is so that the Guide only shows channels that have a channel number (which will hopefully have EPG data for them).
Thanks in advance!
-
1. Channel Number:
There is a checkbox before scanning starts, "Include channel number in channel name". Make sure you check the box before proceeding.
However, judging by the fact the Channel Number column is not filled, the UK Channel Number is not available during scan. The service provider must broadcast the descriptors that contain such data in order for MC to pick them up.
Unfortunately there is no good way of fixing this except manually changing them.
2. Removing duplicates:
Channel Grouping is for grouping different types of channels (such as DVB-S vs DVB-T) that carry identical programming. Automatic grouping can happen only under some strict conditions - such as identical channel name. If automatic grouping did not work, the only way is to manually group selected channels.
Your screenshot only shows dvb-s channels. If you want to remove duplicate channels that are all DVB-S channels, you can select the redundant channels and choose "Hide".
-
What would the tag have to read in the XMLTV file for JRiver to pick it up as a channel? I'm wondering if I can post-process something for after EPG Collector has run, if I can compare channels to a freeview list etc and manually add it in to the XML.
So removing the duplicate channels would need to be a manual thing in JRiver? Absolutely fine - just wanted to make sure there wasn't a feature/function I was missing.
-
Normally XMLTV files are used for EPG updating only. They are used for setting up channels only in case of CableCARD channels (in USA) or STB channels . Once a set of channels are already setup using transport stream scanning, we can no longer change them except manual editing.
This is the first time I learned that DVB-S channel scanning did not produce "UK Channel number" data.
Here is a part of an xmltv file, related to a channel:
<channel id="I6.28457452.microsoft.com">
<display-name>6 WGBO</display-name>
<display-name>6</display-name>
<display-name>WGBO</display-name>
<display-name>WGBO Univision 66</display-name>
<display-name>UNI</display-name>
</channel>
As I said above, currently we are not using all of the data in the file.
So removing the duplicate channels would need to be a manual thing in JRiver? Absolutely fine - just wanted to make sure there wasn't a feature/function I was missing.
Yes, if by "removing duplicate channels" you mean removing duplicates found in the same channel type (for example DVB-S). Usually we advice people to use "Hide" instead of out-right deleting the unwanted channels because you may end up re-do scanning in the future and those channels will be picked up again. Tagging them as "Hidden" means you keep them but MC will ignore them and will not display them in normal GUI.
-
1. Channel Number:
There is a checkbox before scanning starts, "Include channel number in channel name". Make sure you check the box before proceeding.
However, judging by the fact the Channel Number column is not filled, the UK Channel Number is not available during scan. The service provider must broadcast the descriptors that contain such data in order for MC to pick them up.
Unfortunately there is no good way of fixing this except manually changing them.
There is a section in EPG Collector that allows the xml file to include an LCN tag which has the user defined channel (which on the scan I do, is equivalent to sky channels), i.e. BBC One London = 101 (XMLTV Identifier is 6301).
Could you not add a button, maybe "Map Channels" that allows you to select an EPG Guide and then scan for either XMLTV Identifier, or Service ID, and map them against the LCN Tag in the XML where <Channel ID> matches XMLTVid?
Or I'm assuming this info is kept in JRiver in a mysql/sqlite type database? Are we able to get access to the database so I can run a script to update it myself?
-
There is a setting or settings in EPG Collector for this. Something like set the User Channel to LCN or similar. I haven't looked at my EPG Collector setup in ages, so don't remember the details.
I'll have a look and see if I can work out what I did.
There ain't no MySQL or SQLite in MC! It wouldn't be a good idea to directly edit the database either.
-
Well, I was sort of right, and it seems like you have already found what I am doing.
Note that I am using EPG Collector with DVB-T channels and collecting from the OTA EIT data.
The first image shows the definition of "Channel No.", which is also known as "User Channel Number". I think the column was automatically populated with the XMLTV ID by an EPG Collector scan. I'm not entirely sure, as I may have entered the values. See the first image, with the important column highlighted by the red arrow.
Then on the Output tab, set the "Format of channel ID" to "User Channel number", and tick the "Create an LCN tag containing User channel number". See arrows, second image.
As I use the XMLTV ID as my User Channel Number, MC matches up most channels no problem, whenever I do a new channel scan in MC, or in both EPGC and MC. The only exceptions are when there are duplicate channels, one HD the other SD, and only one EPG data stream. Or when there is no EPG data for a channel.
The resulting XMLTV file, "TVGuide.xml" header information looks like this:
<channel id="1">
<display-name>10 BOLD</display-name>
<lcn>1</lcn>
</channel>
<channel id="2">
<display-name>ABC</display-name>
<lcn>2</lcn>
</channel>
<channel id="3">
<display-name>SBS ONE</display-name>
<lcn>3</lcn>
</channel>
<channel id="7">
<display-name>7 Melbourne</display-name>
<lcn>7</lcn>
</channel>
<channel id="9">
<display-name>Channel 9 Melbourne</display-name>
<lcn>9</lcn>
</channel>
<channel id="10">
<display-name>10</display-name>
<lcn>10</lcn>
</channel>
You will see that the "Channel id" (XMLTV ID) matches the LCN in each case, which is the User Channel number in EPGC.
The matching happens in MC at the end of a manual EPG setup, from memory. It mostly gets it right, and allows you to change or add any mapping required.
Then "Options > Television > Manage Channels" allows you to see and change the mapping from Channel # to XMLTV ID as well.
That has worked for me for a long time. I haven't made many changes expect when channels have changed, and when the broadcast EPG data was downgraded.
I'm not sure all the above added much to what you already know. Also, my channel situation, except for the many, many changes we had a while back, is much simpler than yours. Particularly if you want to keep using the standard of, for example, BBC One London = Channel 101 (XMLTV Identifier is 6301), where your channel number is different to the XMLTV ID.
-
Hi RoderickGI,
Thanks for your message. As you mentioned, I've already done this, the only difference is I didn't have user channel number in the output of EPG Collector - although I did have it set to that in the past.
Unfortunately, even with the matching set up.. it just puts the channel number in XMLTV ID column under JRiver, it doesn't populate the Channel # column, which is what I am trying to achieve.
I've done some of the manual grouping and hiding channels, but I was hoping I could avoid having to type the channel number in to each entry?
Is there a button/feature I'm being really daft and overlooking that will copy the channel number from XMLTVID to Channel #?
-
It has been a long time since I ran the TV setup on my HTPC, and even longer since I ran it on a new clean Library.
But I know I didn't manually set the [Channel #] field in MC. It would have been populated from a channel scan, because as Yaobing says, MC doesn't use the EPG to set up channels. Once it has the LCN, it can match channels up to the LCN, and pick up a different XMLTV ID if required, in the XMLTV data.
I have a vague memory of having to select using the scanned channel number, which is just the LCN, during a scan. It must be mentioned in the TV setup Wiki articles or threads somewhere. I did document my EPGC setup to some degree way back...
Maybe Yaobing can provide a quick answer.
-
It has been a long time since I ran the TV setup on my HTPC, and even longer since I ran it on a new clean Library.
But I know I didn't manually set the [Channel #] field in MC. It would have been populated from a channel scan, because as Yaobing says, MC doesn't use the EPG to set up channels. Once it has the LCN, it can match channels up to the LCN, and pick up a different XMLTV ID if required, in the XMLTV data.
I have a vague memory of having to select using the scanned channel number, which is just the LCN, during a scan. It must be mentioned in the TV setup Wiki articles or threads somewhere. I did document my EPGC setup to some degree way back...
Maybe Yaobing can provide a quick answer.
I think it's because the load program guide/scan has changed over the revisions.
From the wiki it shows
(https://wiki.jriver.com/images/4/4f/TV_Setup_EPG_loading.png)
and
(https://wiki.jriver.com/images/e/ea/TV_Setup_Manage_Channels.png)
And if you look in there it appears to have populated the channel number from the scan.
I've included a screengrab from my "load program guide", but when it moves to the manage channels, it hasn't populated the list.
That is why I was asking if there was a button that could be pressed that would populate the channel number from the XMLTVID box (if using channel number in EPG Collector output), or a way (if using XMLTVID in output) of parsing the channel numbers against an XMLTV file to match the xmltvid in the channel list with the file, and populating the channel # with the details in the LCN tag.
I realise this is only a small issue in the grand scheme of things.. but for new users to JRiver, or as in my case, people who are just starting to use it for the TV capability, it would definitely make things easier (and quicker) in our setup.
-
For the difference shown in the images you posted, I think the checkbox Yaobing mentioned earlier is the answer. The missing part appears to be, as you say, populating the Channel # field.
There is a checkbox before scanning starts, "Include channel number in channel name". Make sure you check the box before proceeding.
If you had that checkbox ticked, and still no numbers showed, something is missing from the OTA scan. As the channel # can, and usually is, different to the XMLTVID (despite my example), then it wouldn't be normal to copy the number over. Hence, no button to do so.
However, I can't imagine that the required data is actually supposed to be missing from the OTA scan. Maybe search the forum for users from your area (UK, right?), and what they have done. There are quite a few of them. Maybe your source has mucked up their broadcasts!
Another avenue would be looking at what the EPGC scan itself finds. IF EPGC fills in its Channel No. column, and the numbers are LCNs, then the data is in the scan. Based on your earlier image of the XMLTV xml file created, EPGC does have the LCNs, unless you keyed in the numbers.
You could also try something like DVBLink (you can still get the free version, although it is EOL) to see if it finds the channel numbers in its scan. MC basically does the same thing.
-
Hiya,
I can confirm that I have the button ticked about including channel number, but nothing is being populated from my OTA scan.
Depending on the option selected, I can get EPG Collector to output the channel number as either SID (as shown on here https://en.kingofsat.net/freqs.php?&pos=28.2E&standard=All&ordre=freq&filtre=no&aff=list - i.e. BBC One HD is 6961), or it can set the channel number to the same number as the LCN.
EPG Collector is setting the LCN from an OTA scan (I'm not populating anything in there), so it shows that it must be broadcasting the channel numbers, unless EPG collector is doing some sort of lookup and adding in the LCN numbers, but I'd doubt they would be doing that.
It seems that during the scan JRiver isn't picking them up. Is it possible to get a small EXE that contains the section of JRiver which does the scanning and can output data to a text file so it can be debugged? or is there any way of getting JRiver to natively output the scan data in to a text file?
I'm not so worried about having to set them manually.. I'm just trying to help get to the bottom of why JRiver isn't doing this, so it can be fixed, to help others moving forward :-)
-
You can turn on logging in MC. Please read this wiki on logging. (https://wiki.jriver.com/index.php/Logging)
1. Go to Help > Logging, and turn it on.
2. Run TV channel scanning and wait for it to finish.
3. Go back to Help > Logging to collect the log file.
4. Post it here if the file is not too large. If it is large, email it to me. I am yaobing _at_ jriver _dot_ _com_
-
Log file was 18mb.
Have zipped it up and included in here.
-
I am UK based, and can confirm that OTA scans work as expected for me. Channel numbers are populated and match the UK Freeview channel numbers.
-
Hi Fangio,
Are you using DVB-T or DVB-S?
-
Hi,
I am using Freeview DVB-T/DVB-T2. Sorry, I should have read the thread properly before butting in!
-
Not at all - I appreciate the feedback... I'm thinking more and more that it may be something to do with the fact I'm on DVB-S
-
Not at all - I appreciate the feedback... I'm thinking more and more that it may be something to do with the fact I'm on DVB-S
It appears that ASTRA does not send channel info descriptors in NIT. Maybe it does in another place, such as Bouquet Association Table, which we currently do not parse.
-
It appears that ASTRA does not send channel info descriptors in NIT. Maybe it does in another place, such as Bouquet Association Table, which we currently do not parse.
Is it worth me raising a ticket on the EPG Collector forum to ask them? As I say, doing a scan with their software, unless they parse against a 3rd party list, they must get channel info OTA, as they populate the LCN tag with the channel number.
-
Unfortunately, Channel Info descriptor is not specified in DVB specification. The descriptor in NIT is a "privately defined" one. I would guess that if some network decide to deliver the info in another place it will be a private descriptor too. I would like to find out normally where such info is delivered in DVB-S networks. My guess is they are in Bouquet Association Table.
-
Unfortunately, Channel Info descriptor is not specified in DVB specification. The descriptor in NIT is a "privately defined" one. I would guess that if some network decide to deliver the info in another place it will be a private descriptor too. I would like to find out normally where such info is delivered in DVB-S networks. My guess is they are in Bouquet Association Table.
I had a question to ask in the EPG Collector forum, so I also bolted that question on to the bottom.. but looking at the logs (sadly not the actual output) of it's processing, it did mention the Bouquet Association Table, so there is a very good chance you are right, but hopefully Steve will come back and confirm.
-
I added some exploratory code so I can see how Bouquet Association Table is structured and where the logical channel numbers might be.
Please help me do some testing.
Install the latest MC25 (build 25.0.27) first, then download and copy the DLL "JRTelevision.dll" (linked below) into MC25 installation folder.
32-bit JRTelevision DLL for testing (https://www.dropbox.com/s/nwvwsujpiksyb1e/JRTelevision%2032-bit.zip?dl=0)
Turn on logging and run channel scanning. Then collect the log files. Since this is only for discovery, the logical channel numbers will not be added to scanned channels after the scan, but I hope traces of them might be found in the log files.
-
Sorry, have been away - just running a new channel scan now and will post the log file up shortly.
-
New Log
-
Taking from https://en.kingofsat.net/freqs.php?&pos=28.2E&standard=All&ordre=freq&filtre=Clear&aff=list - BBC ONE London is in TSID 2045
So I am assuming that the channel number was broadcast as Sky or Freeview (Either 101 or 1), it would be somewhere in here?
0815485: 7160: TV: TransportStream::OutputDebugInfo: TSID 2045, ONID 2. Length of all descriptors 289
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Start
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Desc Tag: 0x5f
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Desc Length: 4
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x00 0x00 0x00 0x02
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Finish (0 ms)
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Start
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Desc Tag: 0xb1
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Desc Length: 74
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x00 0x20 0x18 0x9d 0x01 0x07 0xd2 0x03
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0xba 0x3b 0xaf 0x18 0x9e 0x01 0x07 0xd6
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x03 0xc9 0x3c 0x9f 0x18 0xac 0x01 0x07
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0xe2 0x00 0x74 0x07 0x4f 0x18 0xae 0x01
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x07 0xe3 0x02 0x66 0x26 0x6f 0x18 0xc5
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x01 0x08 0x67 0x03 0xc6 0x3c 0x6f 0x18
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0xcf 0x01 0x08 0x19 0x03 0xc2 0x3c 0x2f
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x18 0xd9 0x01 0x08 0x1a 0x03 0xc8 0x3c
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x8f 0x18 0xf6 0x01 0x08 0x03 0x03 0xd5
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x3d 0x5f
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Finish (0 ms)
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Start
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Desc Tag: 0xb1
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Desc Length: 74
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x00 0x21 0x18 0x9d 0x01 0x07 0xd2 0x03
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0xba 0x3b 0xaf 0x18 0x9e 0x01 0x07 0xd6
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x03 0xc9 0x3c 0x9f 0x18 0xac 0x01 0x07
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0xe2 0x00 0x74 0x07 0x4f 0x18 0xae 0x01
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x07 0xe3 0x02 0x66 0x26 0x6f 0x18 0xc5
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x01 0x08 0x67 0x03 0xc6 0x3c 0x6f 0x18
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0xcf 0x01 0x08 0x19 0x03 0xc2 0x3c 0x2f
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x18 0xd9 0x01 0x08 0x1a 0x03 0xc8 0x3c
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x8f 0x18 0xf6 0x01 0x08 0x03 0x03 0xd5
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x3d 0x5f
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Finish (0 ms)
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Start
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Desc Tag: 0xb1
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Desc Length: 74
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x00 0x22 0x18 0x9d 0x01 0x07 0xd2 0x03
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0xba 0x3b 0xaf 0x18 0x9e 0x01 0x07 0xd6
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x00 0x66 0x06 0x6f 0x18 0xac 0x01 0x07
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0xe2 0x00 0x74 0x07 0x4f 0x18 0xae 0x01
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x07 0xe3 0x02 0x66 0x26 0x6f 0x18 0xc5
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x01 0x08 0x67 0x03 0xc6 0x3c 0x6f 0x18
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0xcf 0x01 0x08 0x19 0x03 0xc2 0x3c 0x2f
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x18 0xd9 0x01 0x08 0x1a 0x00 0x65 0x06
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x5f 0x18 0xf6 0x01 0x08 0x03 0x03 0xd5
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x3d 0x5f
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Finish (0 ms)
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Start
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Desc Tag: 0xb1
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Desc Length: 38
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x00 0x32 0x18 0xb1 0x01 0x04 0x23 0x03
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0xba 0x3b 0xaf 0x18 0xb2 0x01 0x04 0x24
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x03 0xc9 0x3c 0x9f 0x18 0xc0 0x01 0x04
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x44 0x00 0x8f 0x08 0xff 0x18 0xc2 0x01
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0x04 0x45 0x02 0x66 0x26 0x6f
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Finish (0 ms)
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Start
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Desc Tag: 0xb1
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Desc Length: 11
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0xff 0xff 0x18 0xf7 0x01 0x08 0x04 0xff
0815485: 7160: TV: CDescriptor::OutputDebugInfo: 0xff 0xff 0xf1
0815485: 7160: TV: CDescriptor::OutputDebugInfo: Finish (0 ms)
0815485: 7160: TV: CMPEG2SectionsAndTablesParser::ParseSection: Finish (0 ms)
-
Unfortunately descriptor tag 0xb1 is a “user defined” tag. I do not know how to interpret it. Thus I don’t know if they carry logical channel number, and if they do, how to extract the data. I can not find in the log any other “user defined” tags that are known to carry logical channel number. So we are kind of stuck here
-
Would it help if I ran something like dvbsnoop (http://dvbsnoop.sourceforge.net/) whilst watching specific channels and put the log in here?
-
I don't know if it will help, but it would not hurt. I took a look at their website that you linked, and looked around their sample outputs, but could not find anything related to logical channel number. Maybe the actual scan might produce something.
Yes, go ahead with running it. Thanks.
-
So it seems that DVB Snoop doesn't work on Windows 10, which is a nuisance... just kept locking up the machine...
I had a reply on my EPG Collector thread where I asked about how they get the freeview channel numbers OTA and this was his reply.
The easy bit first. EPGC does get the channel numbers OTA from the Bouquet Association Table where FreeSat uses a custom descriptor ID 0xd3. This is not part of the EIT standard but is not unusual. Various Freeview implementations do the same thing with a descriptor ID of 0x83.
Now obviously with the log, there was 0x83's in there, but because I don't know what I'm looking at, I don't know how to interpret it - but I'm hoping that it may provide some assistance?
-
So it seems that DVB Snoop doesn't work on Windows 10, which is a nuisance... just kept locking up the machine...
I had a reply on my EPG Collector thread where I asked about how they get the freeview channel numbers OTA and this was his reply.
Now obviously with the log, there was 0x83's in there, but because I don't know what I'm looking at, I don't know how to interpret it - but I'm hoping that it may provide some assistance?
Thanks for the details.
-
Additional message in case it is of any use....
FreeSat uses non-standard pids for all the tables, probably because Sky got in first and used all the standard pids.
So the BAT is on pid 0xbba (not the standard pid 0x11) and you should find a descriptor with id 0xd3 which has the lcn info.
-
Additional message in case it is of any use....
FreeSat uses non-standard pids for all the tables, probably because Sky got in first and used all the standard pids.
So the BAT is on pid 0xbba (not the standard pid 0x11) and you should find a descriptor with id 0xd3 which has the lcn info.
This is interesting. We did get pid 0x11 packages for BAT but they just do not contain useful information (like descriptor 0xd3 or 0x83). I will try getting 0xbba packages.
-
Let me know if you want me to try a new version to log a scan
-
Please test this DLL. (https://www.dropbox.com/s/ftnxmweu0dk1u07/JRTelevision%2064%20bit.zip?dl=0)
Install build 40 (latest build on MC25 board) first, then copy the DLL. Please get a log file.
Note that this DLL likely still will not get the correct channel number for each channel. It is more of an "exploration" build. I am checking what the custom PID 0xbba for Bouquet Association Table will produce, and whether FreeSat channel info descriptors and / or OpenTV channel info descriptors will produce anything.
The fact that channel info descriptors in DVB-S contain data for multiple regions is new to me and I am still trying to figure out what to do with different regions.
-
Would the 64 bit DLL work with a 32 bit install?
I've grabbed .40 from the forum, backed up the old dll and replaced it with the one in the dropbox link.
The issue is, when I start logging and go in to options/manage channels and select rescan - when it comes to the window "scan for new channels" and I click "perform a more thorough but slower scan", it doesn't do anything.
Usually I get the popup asking me to select a frequency, so it can then check for other NITs etc.. but that window isn't coming and it doesn't appear to be scanning anything.
I've left it 30 minutes and then cancelled it and included the log file in here.
Do I need a 32 bit DLL, or has something broken in the latest update?
EDIT: I think it must be the DLL... if I restore the original .dll with .40, I get the "choose scan mode" window pop up.
Have you got a 32 bit DLL? available?
-
Can you install the 64 bit version of MC?
-
I forgot you run 32-bit version.
Here is the 32-bit version DLL. (https://www.dropbox.com/s/yewv4vy36xwht70/JRTelevision%2032-bit.zip?dl=0)
-
Thanks, will give it a go now.
Just out of curiosity, is there any benefit of running the x64 over the x86 version?
-
It started scanning... last I saw it was scanning 4/75 and next it had crashed/closed
Have included log.txt and crash.dmp in this zip
-
It did the same again, but this time deleted log.txt and just left crash.dmp. Gets up to 5/75
I'm going to try different permutations (not selecting slower scan, and then both using original .40 dll)
Will post results
-
Second time round, scanning without selecting "perform a more thorough but slower scan" worked, but it's almost like it only scanned 1 frequency (I'd chosen to scan NIT) as it took a minute or so, instead of over half hour as normal.
In the same log, I am rescanning, not selecting slower scan, but using Legacy mode instead of scanning NIT. It's now scanning 150 channels
It got up to about 12/150 and crashed again...
Crash.dmp enclosed
-
Tried a new scan, using original .dll.. selected slower scan but it only appeared to scan one frequency again and finished.
Have added this log file, perhaps an error with the new DLL that's causing it to crash?
-
Sorry, a new bug had escaped detection.
Please try this new 32-bit DLL. (https://www.dropbox.com/s/9xzxdrak11kyuv9/JRTelevision%2032-bit.zip?dl=0)
-
Stepped out the room for 2 minutes, came back in and it had crashed again.
crash.dmp and log.txt in zip file
This was with new dll doing a slower scan.
-
Tried again without selecting slower scan.
It got up to about 25/75 before crashing, but removed log.txt and just left crash.dmp
-
Tried it again using legacy scanning instead of NIT.. it got up to about 17/150 (from last check), but this time left log.txt (over 100mb) as well as crash.dmp
I've had to email as the .zip is 2.5mb and over the 1200k limit
-
Thanks for testing. I will get to it on Tuesday.
-
No problem.
Am currently doing another scan... legacy search using slower scan.
It's up to 43/150 at the moment. will post logs once it finishes/crashes.
-
Crashed again doing the above.
Larger log file so will email again
-
Thanks. All crashes point to the same place, where I had some bug in BAT scanning. I will figure out a fix tomorrow.
-
Please test this new DLL. (https://www.dropbox.com/s/vsgtqe4l5ln0hi0/JRTelevision%2032-bit.zip?dl=0) A bug that caused program to crash was fixed.
-
I left it scanning and popped out, but came in and it had crashed again.
This was using NIT and slow scan. Will try NIT and normal scan.
crash.dmp enclosed
-
It got up to 51/75 and crashed again, not selecting slow scan and choosing NIT.
Log enclosed.
-
Thanks for the logs. Unfortunately you were only able to capture dump files, but not the logs. For some reason the crash was so bad that the log files disappeared. Something I only experienced since the last batch of logs you posted.
If you are not able to capture the log files, let's wait for the next public build and try again then.
-
I'll try other permutations to see if I can get it to crash but keep the log file
-
Build 45 is out on MC25 board (https://yabb.jriver.com/interact/index.php/topic,120874.msg0.html#new). Please just use that one.
-
Will give that a go - Do I need to re-download the other DLL from your post above, or just use the one that comes with .45?
-
Build 45 should do it.
-
Updating now... Have found out that if I run a scan and it crashes/removes the log, and I open it up straight away and do the same.. it keeps the log on the 2nd crash.
Will run a scan on the new version and upload a log from that too.
Log and dump come to over 1200KB, so emailing this.
-
It's crashed again, similar place using .45
Deleted log file, so re-opened and ran again - crashed in same place and left log file.
Again too big to upload, so have emailed to yaobing
-
Thanks. I got it. The NIT scan picked up transponders that do not carry any service, but are sending sections and tables. We did not handle such cases properly.
Please try this DLL. (https://www.dropbox.com/s/k66ckduncrcd66p/JRTelevision%2032-bit.zip?dl=0)
-
A good thing I see from your latest emailed logs is that we seem to get channel numbers in BAT, OpenTV channel info descriptors:
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Region 45350
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65535 has channel number 4096, channel ID 55557, type 14, flags 0xff 0xff
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65521 has channel number 4047, channel ID 49177, type 15, flags 0x3 0x77
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 14207 has channel number 9000, channel ID 10271, type 35, flags 0xff 0xff
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65521 has channel number 9001, channel ID 23327, type 35, flags 0xff 0xff
1345938: 8460: TV: TransportStream::OutputDebugInfo: TSID 2004, ONID 2. Length of all descriptors 75
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Start
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Desc Tag: 0x5f
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Desc Length: 4
1345938: 8460: TV: CDescriptor::OutputDebugInfo: 0x00 0x00 0x00 0x02
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Finish (0 ms)
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Region 45377
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65535 has channel number 1050, channel ID 6854, type 4, flags 0xff 0xff
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65521 has channel number 1051, channel ID 7093, type 4, flags 0xff 0xff
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65521 has channel number 1052, channel ID 7348, type 4, flags 0xff 0xff
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65521 has channel number 1053, channel ID 7569, type 4, flags 0xff 0xff
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65521 has channel number 1151, channel ID 23939, type 16, flags 0xff 0xff
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65521 has channel number 7500, channel ID 19904, type 29, flags 0xff 0xff
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65521 has channel number 1171, channel ID 10645, type 35, flags 0xff 0xff
1345938: 8460: TV: TransportStream::OutputDebugInfo: TSID 2007, ONID 2. Length of all descriptors 165
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Start
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Desc Tag: 0x5f
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Desc Length: 4
1345938: 8460: TV: CDescriptor::OutputDebugInfo: 0x00 0x00 0x00 0x02
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Finish (0 ms)
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Region 45467
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65535 has channel number 1827, channel ID 64257, type 19, flags 0x0 0xb7
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 2943 has channel number 1875, channel ID 44289, type 21, flags 0x0 0x82
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 2095 has channel number 1891, channel ID 44545, type 21, flags 0x0 0xe6
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 3695 has channel number 1879, channel ID 44801, type 21, flags 0x0 0xa3
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 2623 has channel number 1806, channel ID 45057, type 21, flags 0x0 0x81
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 2079 has channel number 1822, channel ID 45313, type 21, flags 0x0 0xe5
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 3679 has channel number 1448, channel ID 45569, type 21, flags 0x0 0x9c
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 2511 has channel number 1847, channel ID 45825, type 21, flags 0x0 0xa5
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 2655 has channel number 2602, channel ID 46593, type 21, flags 0x2 0xf2
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 12079 has channel number 2608, channel ID 46849, type 21, flags 0x2 0xc7
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 11391 has channel number 1834, channel ID 47105, type 21, flags 0x1 0xa2
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 6703 has channel number 2606, channel ID 47361, type 21, flags 0x2 0xc6
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 11375 has channel number 3620, channel ID 31489, type 23, flags 0x1 0x0
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 4111 has channel number 4330, channel ID 35073, type 23, flags 0x1 0xe
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 4335 has channel number 4332, channel ID 35329, type 23, flags 0x0 0xf5
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 3935 has channel number 2202, channel ID 36609, type 23, flags 0x0 0x91
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 2335 has channel number 5415, channel ID 37121, type 23, flags 0x0 0xb5
1345938: 8460: TV: TransportStream::OutputDebugInfo: TSID 2008, ONID 2. Length of all descriptors 48
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Start
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Desc Tag: 0x5f
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Desc Length: 4
1345938: 8460: TV: CDescriptor::OutputDebugInfo: 0x00 0x00 0x00 0x02
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Finish (0 ms)
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Region 45350
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65535 has channel number 4004, channel ID 56345, type 14, flags 0x3 0x60
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 13839 has channel number 3858, channel ID 4633, type 15, flags 0x3 0x5e
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 13807 has channel number 4076, channel ID 9241, type 15, flags 0x3 0x3d
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 13279 has channel number 4009, channel ID 19993, type 15, flags 0x3 0x61
1345938: 8460: TV: TransportStream::OutputDebugInfo: TSID 2010, ONID 2. Length of all descriptors 111
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Start
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Desc Tag: 0x5f
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Desc Length: 4
1345938: 8460: TV: CDescriptor::OutputDebugInfo: 0x00 0x00 0x00 0x02
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Finish (0 ms)
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Region 45413
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65535 has channel number 2501, channel ID 22785, type 27, flags 0x0 0x7e
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 2031 has channel number 2502, channel ID 23041, type 27, flags 0x0 0xa0
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 2575 has channel number 2503, channel ID 23297, type 27, flags 0x1 0x65
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 5727 has channel number 2515, channel ID 23809, type 27, flags 0x0 0xe2
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 3631 has channel number 2506, channel ID 24065, type 27, flags 0x1 0x5f
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 5631 has channel number 2508, channel ID 24321, type 27, flags 0x1 0x61
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 5663 has channel number 2509, channel ID 24577, type 27, flags 0x1 0x63
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 5695 has channel number 2511, channel ID 24833, type 27, flags 0x1 0x60
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 5647 has channel number 2512, channel ID 25601, type 27, flags 0x1 0x5e
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 5615 has channel number 3508, channel ID 25857, type 27, flags 0x1 0x64
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 5711 has channel number 2507, channel ID 26113, type 27, flags 0x1 0x62
1345938: 8460: TV: TransportStream::OutputDebugInfo: TSID 2011, ONID 2. Length of all descriptors 111
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Start
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Desc Tag: 0x5f
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Desc Length: 4
1345938: 8460: TV: CDescriptor::OutputDebugInfo: 0x00 0x00 0x00 0x02
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Finish (0 ms)
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Region 45413
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65535 has channel number 1261, channel ID 43010, type 21, flags 0xc 0x58
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 50575 has channel number 1262, channel ID 43266, type 21, flags 0xc 0x5c
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 50639 has channel number 1264, channel ID 43522, type 21, flags 0xc 0x5d
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 50655 has channel number 1263, channel ID 43778, type 21, flags 0xc 0x5e
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 50671 has channel number 3645, channel ID 55297, type 23, flags 0x2 0x6e
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 9967 has channel number 1843, channel ID 36097, type 35, flags 0x2 0x63
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 9791 has channel number 1881, channel ID 36353, type 35, flags 0x2 0x61
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 9759 has channel number 1884, channel ID 36609, type 35, flags 0x2 0x5f
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 9727 has channel number 1844, channel ID 36865, type 35, flags 0x2 0x64
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 9807 has channel number 1882, channel ID 37121, type 35, flags 0x2 0x62
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 9775 has channel number 1890, channel ID 37377, type 35, flags 0x2 0x60
1345938: 8460: TV: TransportStream::OutputDebugInfo: TSID 2012, ONID 2. Length of all descriptors 201
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Start
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Desc Tag: 0x5f
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Desc Length: 4
1345938: 8460: TV: CDescriptor::OutputDebugInfo: 0x00 0x00 0x00 0x02
1345938: 8460: TV: CDescriptor::OutputDebugInfo: Finish (0 ms)
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Region 45503
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65535 has channel number 1054, channel ID 7824, type 4, flags 0xff 0xff
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65521 has channel number 4095, channel ID 14085, type 15, flags 0xff 0xff
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65521 has channel number 1140, channel ID 13316, type 16, flags 0xff 0xff
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 65521 has channel number 1001, channel ID 52737, type 16, flags 0x1 0x32
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 4911 has channel number 1002, channel ID 52993, type 16, flags 0x1 0x33
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 4927 has channel number 1807, channel ID 53249, type 16, flags 0x1 0x36
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 4975 has channel number 1811, channel ID 53761, type 16, flags 0x1 0x37
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 4991 has channel number 1838, channel ID 54273, type 16, flags 0x1 0x30
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 4879 has channel number 1808, channel ID 13057, type 17, flags 0x1 0x31
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 4895 has channel number 1409, channel ID 13313, type 17, flags 0x1 0x2d
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 4831 has channel number 1823, channel ID 13569, type 17, flags 0x1 0x38
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 5007 has channel number 1818, channel ID 13825, type 17, flags 0x1 0x34
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 4943 has channel number 1810, channel ID 39169, type 17, flags 0x3 0xe7
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 15999 has channel number 1852, channel ID 41729, type 17, flags 0x3 0xb6
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 15215 has channel number 1851, channel ID 44289, type 17, flags 0x3 0xe6
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 15983 has channel number 1819, channel ID 35841, type 19, flags 0x3 0x83
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 14399 has channel number 1850, channel ID 36610, type 19, flags 0x3 0xe4
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 15951 has channel number 1816, channel ID 32257, type 21, flags 0x1 0x35
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 4959 has channel number 2207, channel ID 46081, type 21, flags 0x0 0xaa
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 2735 has channel number 1815, channel ID 4609, type 22, flags 0x1 0x2f
1345938: 8460: TV: OpenTVChannelInfoDescriptor::OutputDebugInfo: Service ID 4863 has channel number 1830, channel ID 59905, type 23, flags 0x1 0xb1
The above are just snippets of a large number of entries. We get BAT sections only on one frequency, 11112000 kHz, transport stream ID 2067.
-
Brilliant news :-)
Have just done a scan using the new DLL and it completed successfully, no crashes.
Using NIT and slow scan.
Have emailed the logfile.
Let me know if you need me to do any other testing.
-
Thanks for your patience and help.
-
Great! Thanks!
Now we got those nasty crashes out of the way, I will be able to concentrate on getting the channel numbers from BAT. It will be a bit of complicated if BAT is only available on only one or some of the transport.
-
The BAT tables that we were able to scan so far do not help. Not only they are not available on all transport, the data present in these tables do not correspond to anything in actual channels.
We got these tables using the standard DVB PID for BAT, i.e. 0x11. Maybe this is the problem. We have not been able to get the non-standard packets with PID 0xbba.
So I added some code to try a different method of getting these tables. Please first install the latest (MC25.0.48) then copy the DLL (https://www.dropbox.com/s/sytdf7j35wsx6s8/JRTelevision%2032-bit.zip?dl=0).
-
Updated to the new version, replaced DLL and scanned using slow scan and NIT... it picked up an extra transponder somehow?! there are usually 75, but it picked up 76 this time.
Emailed logs
-
Thanks for testing.
it picked up an extra transponder somehow?! there are usually 75, but it picked up 76 this time.
Yes, there is a new transponder that was not there previously. I don't think it is my change that caused it. It probably is a new transponder. It is transmitted with transport stream ID 2037, on frequency 12421500 kHz.
The following channels were found:
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels(1): Start
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: Start
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: Network Name: ASTRA, Freq: 12421500, Bandwidth: 0
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: NID: 32, TSID: 2037, ONID: 2, # of services: 6
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: A channel of type DVB-S is created
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: Service 00:
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: Service Name: 6811, Service ID: 6811, Video PID: 5800, Audio PID: 5801, PMT PID: 263, (Channel: -1)
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: Channel string: DTV 2037 (32-6811)12421500, 0, 2, 5801, 5, 1, 5800, 263, 0, 2, eng, 5800, 1, 27500, 11700, 0, 0, 20, 2, -1, -1
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: A channel of type DVB-S is created
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: Service 02:
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: Service Name: 6805, Service ID: 6805, Video PID: 5400, Audio PID: 5401, PMT PID: 259, (Channel: -1)
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: Channel string: DTV 2037 (32-6805)12421500, 0, 2, 5401, 5, 0, 5400, 259, 0, 0, eng, 5400, 1, 27500, 11700, 0, 0, 20, 2, -1, -1
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: A channel of type DVB-S is created
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: Service 04:
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: Service Name: 6803, Service ID: 6803, Video PID: 5200, Audio PID: 5201, PMT PID: 258, (Channel: -1)
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: Channel string: DTV 2037 (32-6803)12421500, 0, 2, 5201, 5, 0, 5200, 258, 0, 0, eng, 5200, 1, 27500, 11700, 0, 0, 20, 2, -1, -1
1586422: 4116: TV: CMPEG2SectionsAndTablesParser::GetChannels: Finish (0 ms)
Notice that these channels don't even have channel names. They just use "Service ID" for their names.
Now back to more important stuff. We still can not get valid BAT data. The alternative method that I added today did not produce any thing.
Are you sure FreeSat sends Bouquet Association Tables on PID 0xbba? Nothing came up when we request packets with PID 0xbba, and TID (table ID) 0x4A.
-
Looks like a new transponder went live yesterday - it's mainly data apart from 1 BBC channel (so far).
With regards to the PID etc... this was the message from last month that the developer replied with.
You are probably looking at the wrong pid for the BAT data.
FreeSat uses non-standard pids for all the tables, probably because Sky got in first and used all the standard pids.
So the BAT is on pid 0xbba (not the standard pid 0x11) and you should find a descriptor with id 0xd3 which has the lcn info.
Looking at the log from EPG Collector, it say about getting network information data from 0xBB9 and station data from 0xBBA, so I'm assuming it's right?
I've also enclosed the log from EPG Collector in here as well if it helps?
-
Here is another modified DLL for testing. (https://www.dropbox.com/s/adi0qh8fk8kl447/JRTelevision%2032-bit.zip?dl=0)
I enabled some extra logging. I am really puzzled. EPGCollector indeed uses 0xbba for FreeSat PID. For some reason those packets were not captured in MC.
Due to extra logging, the log file can be very large. Do not use slow scan.
-
Just emailed latest log, using NIT without a slow scan.
-
Thanks for the log.
I am quite sure now we are not getting any packets with PID 0xbba. Somewhere they are filtered out. >:( >:( >:( :( :( :(
-
Steve Kindly replied with me asking him if the PID and Table was correct
Checking my code pid 0xbba table 0x4a should be correct.
The source code is available on here. The module is FreeSatController.cs in EPG Collector\DVBServices\FreeSat.
I've uploaded the file.. as it references various dictionaries, I don't know if you'd need them as well, however the .cfg files are all available in his source code.
Hopefully this may help you?
-
Thanks for the info. I have seen that file previously. It shows that EPGCollector uses special PIDs. But my problem is when I try to get those packets I find nothing. I even wonder whether we really are tuned to FreeSat channels.
-
I think you must be, as for the actual viewing... it's freesat I'm getting....
If there is any other testing I can do, I'm happy to do so.. or if there are logs from any other software that would help.. happy to do that too....
-
I think you must be, as for the actual viewing... it's freesat I'm getting....
If there is any other testing I can do, I'm happy to do so.. or if there are logs from any other software that would help.. happy to do that too....
You are sure the channels we found are FreeSat? You may or may not be aware, we have not implemented DiSEqC inside MC. It is on my list and I recently tried to restart the project, but have not gotten anywhere yet. For now, you need to make sure the antenna is pointing to the correct satellite before you start using MC to scan. The way to do it is to run another software that does have DiSEqC implemented. If you don't ever switch to different satellite, then this is unlikely an issue. Also judging by the fact you are able to run DVBCollector and get correct info, this is unlikely the issue. But I thought I'd just throw it out there.
-
Oh god.. shoot me.
Talk about mixing my metaphors... The channels are actually Sky Digital... but Free to Air ones.
It is in EPG Collector that I specify Freesat, as the EPG is the same...
If you look on https://en.kingofsat.net/freqs.php?&pos=28.2E&standard=All&ordre=freq&filtre=Clear it shows that the channels are Sky Digital (with some also being classed as freesat).
However, it is the channel numbering from Freesat that I am after (i.e. BBC one being 101 etc)
I've included a couple of screen grabs from EPG Collector settings in case that helps? And also one from dvb dream.
Sorry! :-(
-
Have included a couple more grabs from DVB Dream regarding Diseqc settings...
I'm assuming it must be ok, as I'm able to watch TV via JRiver?
-
The channels appear to be the same, at least the one with details in a screenshot matches on in MC's scan identically.
So, if we are tuning to the same transport stream, why are the FreeSat packets not appearing?
Anyway, as a desperate attempt, I made a DLL that would look for FreeSat packets directly, without first looking for standard packets. I do not see why it would matter, but I want to try anything.
Here is the DLL. (https://www.dropbox.com/s/3szfpergpywmkrc/JRTelevision%2032-bit.zip?dl=0)
-
Ran it with the new DLL... it didn't find any channels, but I'm assuming from what you said, this was expected?
Have included the log that it produced.
Let me know if you need me to run it again?
-
I will keep looking for a way to get FreeSat BAT data. In the mean time I added the following new feature (which you originally requested) to get around the problem:
NEW: Added an option during manual on-line EPG loading to fill empty "Channel Number" field with LCN value found in xmltv data. Not applicable to ATSC channels.
This will be available in build 70 (not out yet) or later.
-
Brilliant :-)
Many thanks for that.
Will keep checking the thread, so if you make any progress with the BAT scanning, I'll test it out.
-
Brilliant :-)
Many thanks for that.
Will keep checking the thread, so if you make any progress with the BAT scanning, I'll test it out.
Looks like there may be a small glitch, in that the channel number overwriting the name of the channel.
For example "5 USA", gets matched with "5 USA" in the tvguide.xml, but where the LCN is 129 it's showing as "129 USA" on the right hand column
Same with "5Spike" becoming "141 Spike" and "5SELECT" turning in to "133 SELECT"
It works fine if the channel name doesn't start with a number
i.e. "BBC 6 Music" is (manually) matched with "707 BBC 6Music"
Also, the first time I did a channel scan and matched additional channels.. when I clicked next, it didn't import any of the channel numbers of the XMLTV ID numbers.
But after I went to load program guide and did it again, and it populated the details absolutely fine.
Happy to provide logs, but let me know how far you want me to go through the process before submitting the logs..
i.e. shall I recreate all of the above steps... or just do the initial scan and match (where it didn't show XMLTV IDs' etc)..
-
I just tried running it all again and not ticking add channel number to name.
But it's still stripping the number from the start of the channel name.
So for example, if I manually try to match 5 USA (which did auto match when I included adding channel number to name), it now just shows "USA" or "USA+1" in the dropdown, even though it is showing as 5USA in the TvGuide.xml
-
I see. I had added code to prevent this from happening, but it does not cover the situation in which channel scan does not produce channel number. For example if you had channel number to start with, your "5Spike" might be "141 5Spike", and stripping channel number would make it "5Spike". But the program does not know the first part is already missing and ended up stripping the number in the second part.
I will think about it.
-
Hiya,
Just thought I'd check in to see if there was any update on BAT scanning, or the issue with stripping numbers from the start of a channel name?
Cheers :-)
-
Hiya,
Just thought I'd check in to see if there was any update on BAT scanning, or the issue with stripping numbers from the start of a channel name?
Cheers :-)
No progress in getting info from BAT.
Regarding channel numbers, I did this:
25.0.84 (7/29/2019)
1. Changed: Re-implemented TV channel to xmltv ID matching routine for DVB channels as well as OpenCABLE and STB channels. The more elaborate methods hopefully will improve matching accuracy, especially for DVB channels.
-
Hi guys,
Have only just noticed this conversation.
I too use Freesat, having dropped Sky a few years ago, but how these clowns get a license to broadcast sometimes is beyond me.
On at least a weekly basis and very often more frequently than this, they move channels around transponders and you only notice when a channel stops working and perform a rescan.
As tunes0710 has said, Freesat and Sky are both broadcast from Astra 28.2 - the only real difference is that any channel carrying any form of encryption will not be available to you if using Freeview.
@yaobing - For this provider at least (the only UK satellite one we have) it would be a godsend if there was an option to automatically identify encrypted channels in manage channels, then we could hide all of them at once.
As it is, I am so used to rescanning an reordering my lineup that I know which ones are encrypted, although over the past few months, they have been moving many previously FTA channels from Freesat over to Sky, meaning that they get encrypted so become unavailable to those of us using Freesat.
@tunes0710 - I tend to use the following transponder when rescanning, as it seems to the most reliable for me generally - 10714000 Horizontal, SR 22000, FEC 5/6, Modulation QPSK.
For checking listings, I would recommend Lyngsat and this has long been a firm favourite of mine. The listings available to Sky/Freesat can be found here - https://www.lyngsat.com/packages/Sky-UK.html
The site clearly shows encryption and other features with a colour code in the grid/table.
Due to the way that many of our channels work, there will be many examples that are duplicates destined for different regions and territories. An example of this is in the attached screenshot.
When scanning, the channel Really will appear twice, and MC will list these channels as Really and Really (1). From the Lyngsat listing, it is clear which version of the channel is for the UK and which is for Ireland, and then you can hide or remove the duplicate entry in MC by matching on the SID number.
For other channels such as Channel 4, this will appear multiple times for different regions, SD and HD and these will all just be labelled Channel 4 followed by sequential numbers.
It's the way they do it here I guess, but it is infuriating.
As for hiding vs deleting channels, I always just delete all the channels now and when re-scanning, I scroll down the list of new channels that populates the bottom of the manage channels list and can easily see which have changed or are new as am so used to doing it - again this is not due to an MC issue but due to the frequency that they are re-organised by Sky/Freesat.
I have previously tried to hide channels, but what I tend to find happens is that this also hides many of my existing channels that I want to keep, presumably because the name is the same.
Using Really as an example again, almost without exception, when scanning has completed and channels are listed in the manage channels grid, the Irish variant will be listed first as Really or ChannelName and the second variant (the UK one that I want) will be Really (1) or ChannelName (1).
I rename the channels so that the UK channel is changed from ChannelName (1) to ChannelName and for the Irish variant just add any random text to the end of the name to differentiate it and then hide it.
The issue I then have is that when I rescan channels again, all of the Irish variants appear again with no number after them as they get listed first. If I hide those channels that populate the bottom of the grid after a rescan, this also seems to hide the UK versions of the channels I edited previously to remove the number. I assume this is because both channels have the same name (the edited UK version that I called ChannelName now has the same name as the Irish version called ChannelName, and the UK version will appear again as ChannelName (1)).
If the channels do not get hidden because the names are the same then I must have some other problem, but every method I have tried seems to hide all versions of the channel that show the same display name, even though they are different channels as far as the SID is concerned.
Due to this, I just find it it quicker overall to shift select all of the channels, pick out the 3 or 4 I need to keep and delete the rest, then edit the remaining new channels and drag them to the correct place in the grid. I stopped bothering trying to number channels quite some time ago as Sky's system drove me mad.
Anyway, I hope some of this makes sense and/or is of use. Let me know if you need any further information or examples, screenshots etc.