Feature request for TransEdit

[Retrofan]

Hi,

 

I have a feature request for TransEdit:

If you could export the LCN number in the M3U files (SAT>IP) as well using the tvg-chno parameter, that would be great.

 

This could be handy when using other applications like Simple IPTV client in KODI but for other programs as well.

https://kodi.wiki/view/Add-on:PVR_IPTV_Simple_Client

 

I use TransEdit mainly for scanning DVB-C channels which does a great job. but I also would like to have the LCN in the channellist when using M3U file.

When there's no LCN detected by TransEdit, the tvg-chno parameter can be skipped.

[Griga]

vor 16 Stunden schrieb Retrofan:

If you could export the LCN number in the M3U files (SAT>IP) as well using the tvg-chno parameter, that would be great.

This could be handy when using other applications like Simple IPTV client in KODI but for other programs as well.

 

I've tried, but Kodi 19 (Matrix) doesn't support Sat>IP (RTSP) URLs. The Simple IPTV Add-On reads the M3U quite happily, but I got a "Cannot be played" message.

 

The RTSP M3U output in TransEdit is tailored for the VLC, that doesn't support tvg tags, but understands the

 

#EXTINF:-1, category, channel name

 

scheme.

 

[Retrofan]

Hi Griga. Thanks for trying.

 

It does work over here with KODI 19. Just tried again. I added the tvg-chno parameter myself and it works fine.

However, the option "use channel number from backend" has to be turned on in PVR Live & TV settings.

 

Because of a RTSP bug in KODI 19 you have to add the KODIPROP tag as well for each channel, but this is not needed anymore when KODI 19.1 is released,

see over here: https://github.com/kodi-pvr/pvr.iptvsimple/issues/501

 

This is my M3U with RTSP URLs from TransEdit. I'm using the Fritz!WLAN Repeater DVB-C as SAT>IP server, a well-known device in Germany.

 

#EXTM3U
#EXTINF:-1,tvg-chno="1",ARD
#EXTVLCOPT:program=19401
#KODIPROP:inputstream=inputstream.ffmpegdirect
#KODIPROP:inputstream.ffmpegdirect.open_mode=ffmpeg
#KODIPROP:inputstream.ffmpegdirect.is_realtime_stream=true
rtsp://192.168.0.4:554?freq=386&msys=dvbc&sr=6900&mtype=256qam&pids=0,16,17,20,2000,2001,2101,2011
#EXTINF:-1,tvg-chno="613",ZDF
#EXTVLCOPT:program=20044
#KODIPROP:inputstream=inputstream.ffmpegdirect
#KODIPROP:inputstream.ffmpegdirect.open_mode=ffmpeg
#KODIPROP:inputstream.ffmpegdirect.is_realtime_stream=true
rtsp://192.168.0.4:554?freq=490&msys=dvbc&sr=6900&mtype=256qam&pids=0,16,17,20,2900,2901,2911
 

Maybe you can try again? Thanks!

Edited May 4, 2021 by Retrofan

[Retrofan]

On 4/26/2021 at 9:35 AM, Griga said:

 

I've tried, but Kodi 19 (Matrix) doesn't support Sat>IP (RTSP) URLs. The Simple IPTV Add-On reads the M3U quite happily, but I got a "Cannot be played" message.

 

The RTSP M3U output in TransEdit is tailored for the VLC, that doesn't support tvg tags, but understands the

 

#EXTINF:-1, category, channel name

 

scheme.

 

Hi, please try again. KODI 19.1 is out and has a RTSP bugfix as well.

[Retrofan]

On 4/26/2021 at 9:35 AM, Griga said:

 

I've tried, but Kodi 19 (Matrix) doesn't support Sat>IP (RTSP) URLs. The Simple IPTV Add-On reads the M3U quite happily, but I got a "Cannot be played" message.

 

The RTSP M3U output in TransEdit is tailored for the VLC, that doesn't support tvg tags, but understands the

 

#EXTINF:-1, category, channel name

 

scheme.

 

 

Since version 7.2.3.0 DVBViewer also supports the tvg-chno parameter. Maybe a nice moment to add for this parameter in TransEdit as well when exporting the SAT>IP urls to M3U file? Thank you!

 

Added: Channel Editor: On M3U (IPTV) channel list import the Channel Editor now adopts channel numbers from tvg-chno tags, if present. Using them for channel selection by number input requires Options → TV/Radio → Use custom channel numbers to be switched on.

[Griga]

vor 12 Stunden schrieb Retrofan:

Since version 7.2.3.0 DVBViewer also supports the tvg-chno parameter. Maybe a nice moment to add for this parameter in TransEdit as well when exporting the SAT>IP urls to M3U file?

 

TransEdit doesn't deal with channel numbers at all, except if the broadcaster provides LCN (Logical Channel Numbers) and they are retrieved on scanning (see Settings -> Scanner). Is this what you want?

 

[Retrofan]

Hi, yes, that's indeed what I prefer. When exporting to INI the LCN is exported as well but when exporting to SAT>IP format the LCN isn't exported, which is now also possible with the use of the tvg-chno parameter which DVBViewer also supports.

[Retrofan]

I also have an issue regarding LCN. With TransEdit version 4.2.4.1 all LCN of my cable operator are visible after a channelscan.

However, with TransEdit 4.3.3 the Network ID of my region isn't viewed anymore.

Is something changed? Maybe it's possible to have an option to activate the behaviour of 4.2.4.1 again in cases when it's needed?

 

 

 

 

 

 

 

[Griga]

vor 2 Stunden schrieb Retrofan:

I also have an issue regarding LCN. With TransEdit version 4.2.4.1 all LCN of my cable operator are visible after a channelscan.

However, with TransEdit 4.3.3 the Network ID of my region isn't viewed anymore. Is something changed?

 

I don't know. I can't find a code change that could explain the difference.

 

For checking it I would need a transponder dump from a frequency on which a LCN descriptor is broadcasted. You can check in the TransEdit Analyzer if it is present by entering Logical Channel Number in the search field and clicking Find.

 

Then you can record it with the TransEdit Analyzer. Right-click the PID list on the right -> Select All -> click Start Recording -> let it record about 1 minute -> click Stop Recording. Settings -> Analyzer tells you where the recording is stored. You can upload it to WeTransfer, if you have no other web space, and send me the link via PM.

 

[deWolf]

In the hardcopies it can be seen that a second option ′Update chanel names in the DVBViewer channel list′ is active in version 4.2.4.1 compared to 4.3.3.0. Could this be the reason that the ′LCN′ field is filled here?

[Griga]

vor 22 Minuten schrieb deWolf:

Could this be the reason that the ′LCN′ field is filled here?

 

No. The issue has to be checked with a transponder dump under debugger control. Everything else is blind guessing.

 

[Retrofan]

21 hours ago, Griga said:

 

I don't know. I can't find a code change that could explain the difference.

 

For checking it I would need a transponder dump from a frequency on which a LCN descriptor is broadcasted. You can check in the TransEdit Analyzer if it is present by entering Logical Channel Number in the search field and clicking Find.

 

Then you can record it with the TransEdit Analyzer. Right-click the PID list on the right -> Select All -> click Start Recording -> let it record about 1 minute -> click Stop Recording. Settings -> Analyzer tells you where the recording is stored. You can upload it to WeTransfer, if you have no other web space, and send me the link via PM.

 

 

Thanks Griga! Done!

[Griga]

Thanks. Now I can reproduce the issue. It is caused by the following change in TransEdit 4.3.0:

 

Am 22.2.2022 um 10:04 schrieb Griga:

Added: Scanner: Needless (redundant) LCN sets, that are a subset of another numbering set, are removed automatically, so that they don’t appear in the “Channel Numbering Selection” dialog anymore (see here).

 

Is was implemented due to LCN results in an Austrian cable network, in order to facilitate the selection for users.

 

Here are the LCN numbering sets that are offered by the Channel Numbering Selection window (see scanner context menu or Ctrl + L) after scanning your transponder dump:

 

 

The numbering set with LCN ID = 4444 that you want is present in your file, but presumably dropped by TransEdit because it is already completely covered by one of the sets above, maybe 3333. Please try if it is usable for you.

 

[Retrofan]

Thanks, but it's not usable. In my region I have to use 4444 for free to air or 5555 for both free to air and encrypted channels. Both IDs are disabled now.

Maybe you can add an option to get the behaviour of 4.2.4.1 back again?

Thanks!

[Griga]

vor 10 Stunden schrieb Retrofan:

Thanks, but it's not usable. In my region I have to use 4444 for free to air or 5555 for both free to air and encrypted channels.

 

What is actually missing?

 

Each entry in the LCN list for a certain LCN set (identified by its ID) is a channel/LCN pair. I've checked it under debugger control and got the following results:

• Set 3333 (HE Heerenveen B2B FTA) contains all entries of set 4444 (HE Heerenveen FTA) plus 8 additional entries (total 157).
• Set 6666 (HE Heerenveen B2B) contains all entries of set  5555 (HE Heerenveen) plus 9 additional entries (total 304). It also covers set 43140 (HE Heerenveen, same name)

That's why 4444, 5555 and 43140 are dropped.

 

vor 10 Stunden schrieb Retrofan:

Maybe you can add an option to get the behaviour of 4.2.4.1 back again?

 

Up to now I can see no reason for it. All channel/LCN pairs for Heerenveen are provided by the "HE Heerenveen B2B FTA" and "HE Heerenveen B2B" sets. What does B2B mean?

 

[Retrofan]

Hi,

 

I think B2B is meaning Business 2 Business, the Business department of my cable operator.

 

Although the LCN is provided by the other network ID's, it's not the one we official use in my region, but ofcourse I can still (mis)use it.

Maybe it's because Ziggo uses NIT other instead of Actual NIT or something? Maybe then we can add an option to use LCN from Other NIT instead of Actual NIT?

 

But more important: are you willing to add support for the LCN in SAT>IP M3U export in TransEdit? Then I'm very happy 🙂

 

Thanks for your help until now.

Edited August 12, 2024 by Retrofan

[Griga]

vor 3 Stunden schrieb Retrofan:

Maybe it's because Ziggo uses NIT other instead of Actual NIT or something?

 

You can look it up in the Analyzer tree view on the left. All LCN information is located in the NIT (Network Information Table) for other networks. Just search for Logical Channel, then you will see where this information is stored. By clicking the plus sign on the left of the nodes you can expand them and inspect details within the data structures, e.g. which number is assigned to which channel.

 

The NIT for the actual network only enumerates the Heerenveen frequencies and for each a list of services (= channels) that are broadcasted on this frequency.

 

[Retrofan]

In my opinion an option like "Don't show redundant LCN sets" in the scanner area is nicer instead of TransEdit making the decision for me and filtering data away even though it's there. 🙂 With this option both the guy in Austria and me are helped.

And otherwise I still can use 4.2.4.1 if I really want to use the Network ID of my region.

Also the LCN is luckily exported when using the INI format for DVBViewer.

Have a nice day!

 

Edited August 13, 2024 by Retrofan

[Retrofan]

@Griga Maybe this technical document of Ziggo is interesting for you?

https://ziggo-main.aem.aws.ziggo.io/content/dam/ziggo/klantenservice/apparaten/modems/eigen-modem/pdf's/VZ E-NWS_DDV-SPC PSI_SI Overview v2.1_final_63.pdf

 

4.8.2 SDT Descriptors?

Edited August 13, 2024 by Retrofan

[Griga]

vor 4 Stunden schrieb Retrofan:

 With this option both the guy in Austria and me are helped.

 

In the Austrian case there were only two LCN sets, a large and a reduced one. After dropping the reduced one, that was completely covered by the large one, the Channel Numbering Selection dialog didn't appear anymore after scanning, because there was nothing left to decide, and the user just got his LCNs without having to think about which set would be suitable for him, and without having to configure a LCN ID for future scans.

 

In your case the filtering is not that favourable, but IMO providing an option for switching it off isn't necessary either, because users from Heerenveen can still find their region in the Channel Numbering Selection dialog. Due to the filtering they don't have to decide which one of 5 Heerenveen sets is best for them, without knowledge about the details. TransEdit already performs a pre-selection. In a technical sense the appended "B2B" doesn't make a difference. Im sure that users from Heerenveen will select it, because there is no other choice that looks suitable for their region.

 

However, I can imagine potential cases where the filtering would make it more difficult for users, for example, if the LCN set for Amsterdam (just as an example) would completely cover the Heerenveen set, so that the name "Heerenveen" wouldn't appear anymore in the Channel Numbering Selection dialog, leaving users from Heerenveen quite clueless what they should select. This would be a good reason not for an option, but for removing the filtering again, or even better for displaying the names of all (other) sets that are covered by a certain set, so that the user sees something like 3333 Amsterdam, Heerenveen, Heerenveen B2B...

 

Providing options for every single usage scenario is a sure way of spoiling applications. In the long term it makes them unmaintainable and unusable. Options only help users if they know them and there meaning and whether they apply to certain situations or not. So providing another option should be the last resort.

 

The basic problem is that TransEdit isn't like a receiver that is made suitable for a certain region by firmware, but it is used world-wide, and I can't afford adapting it to 100 different special requirements. It must work in a general way.

 

vor 3 Stunden schrieb Retrofan:

Maybe this technical document of Ziggo is interesting for you?

 

Most of it is already covered by the DVB specifications. The interesting part is 5.2.7 EACEM logical channel descriptor (NIT), indicatiing that Ziggo is following the EACEM LCN specifications (European Association of Consumer Electronics Manufacturers), which I already have in another PDF on my PC. LCNs are not part of the general DVB specifications and are handled differently in different countries, which makes it difficult to integrate them in PC software.

 

Anyway, thanks for the link. I'll store the PDF on my PC. One never knows if it will become necessary in future to look up something Ziggo-specific.

 

[Griga]

Your transponder dumps helped to spot a bug that I wasn't aware of before. Under certain circumstances no network name was assigned to a LCN set. This happened if the network name was transmitted in a separate NIT section that contained no LCN definitions.

 

I've encountered the bug when I tried to add the names of dropped LCN sets in the Channel Numbering Selection dialog to the sets that cover them. But the names for set 5555 and 43140 (both "HE Heerenveen") remained empty. However, it is fixed now, and the result looks like this

 

 

Maybe a column showing the number of contained LCNs for each set could also be useful?

 

Am 25.4.2021 um 17:09 schrieb Retrofan:

If you could export the LCN number in the M3U files (SAT>IP) as well using the tvg-chno parameter, that would be great.

 

I've found a solution for the conflicting VLC and Kodi M3U formats. The VLC also reads M3U files quite happily, if the filename extension is .vlc. So TransEdit now allows to export a Sat>IP M3U either tailored for the VLC with the filename extension .vlc or for Kodi (including tvg-chno and group-title tags) with the filename extension .m3u.

 

Furthermore I've added DVB subtitle PIDs to the pids=... list in the RTSP URLs, that were not included before.

 

Am 4.5.2021 um 18:20 schrieb Retrofan:

This is my M3U with RTSP URLs from TransEdit.

#EXTINF:-1,tvg-chno="1",ARD

 

Not quite correct. There should be a blank after -1, not a comma. Rather do it this way:

 

#EXTINF:-1 tvg-chno="1",ARD

 

Anyway, if you want a TransEdit test version, please let me know...

 

[Retrofan]

@Griga O, great that you fixed a bug in TransEdit, my favourite tool 🙂

 

And, yes please, I want the TransEdit test version, thanks! Just send me a link via PM.

 

And is it also possible for you to add an option to include or exclude pid 18 (EPG) in the RTSP URLs in case someone wants this when exporting to M3U?

Edited August 16, 2024 by Retrofan

[Griga]

I've sent you a PM.

 

vor 13 Stunden schrieb Retrofan:

And is it also possible for you to add an option to include or exclude pid 18 (EPG)

 

I've added a possibility to add any PID and even more than one. Simply append to the filename what shall be appended to the &pids=... string, beginning with a comma, e.g. MyExport,18.m3u or MyExport,1,18.m3u. The part after the leading comma must only contain digits and additional commas.

 

Please note that EPG (EIT) streams may occupy some bandwidth in your network. You can look it up in the Analyzer. The one in your files is already close to 1 MBit/s. On Astra 19.2° East there are transponders with a 3 MBit/s EPG stream.

 

[Retrofan]

Thanks Griga, much appreciated, I will check it out 🙂

[Retrofan]

Hi Griga, I did some tests and it works great, thank you very much!

 

For LCN I let TransEdit remember ID 3333, so I don't see it anymore as I normally expect 4444 🙂

The output is luckily the same as before.

 

Also the export of tvg-chno and possibility to add pids to the M3U is cool.

 

Is the #EXTVLCOPT:program=x parameter needed for exported M3U as VLC has now it's own format? (.vlc) Just checking.

 

The appended pid, 18 in my case, now stands at the end of the URL line. No problem ofcourse, but maybe it can be put between 0,16,17,20?

Other pids can be appended at the end of the line. It's more cosmetic, but if you don't agree I understand as well🙂

 

If I find more I will let you know over here. This version is now very useable!

Edited August 17, 2024 by Retrofan

[Griga]

vor 37 Minuten schrieb Retrofan:

Is the #EXTVLCOPT:program=x parameter needed for exported M3U

 

Yes. It specifies the Service ID of the channel that shall be played. Without it sending EPG data would be pretty useless, because the client needs the Service ID for finding out which EPG data in the EIT stream is appropriate for the played stream.

 

Clients could also try to retrieve the Service ID by checking if one of the PIDs in the URL matches one of the PMT PIDs listed in the Program Association Table (PAT on PID 0, read more about it here), but this is complicated, and the result may be ambiguous.

 

It is a design fault of Sat>IP URLs that they provide no official way to specify the Service ID. That's why several proprietary methods have been introduced. The VLC method is the most popular one and widely spread. Many clients are able to understand it, e.g. the IPTV Simple PVR Add-On for Kodi (see here).

 

[Retrofan]

OK, I understand, thanks!

[EnoSat]

What is the correct setting TBS6909X to be able to select satellites connected to individual tuners?

[Griga]

9 hours ago, EnoSat said:

What is the correct setting TBS6909X to be able to select satellites connected to individual tuners?

 

In TransEdit: Right-click the satellite on the left side of the main window -> Set Group in combination with Settings -> Hardware -> Groups for the tuners in question. 

For example, if a satellite belongs to group C, TransEdit only uses tuners with enabled group C for it, but no tuners with disabled group C.

 

In DVBViewer: Go to the channel editor -> select a category or channel -> select the group on the right side -> click Apply in combination with Settings -> Options -> Hardware -> Groups for the tuners in question.