14 replies to this topic

[doglover]

Can somebody explain me the difference between:

 

1:0:19:578:0:0:30AC29:0:0:0:  Viasat Film Premiere Action
1:0:19:578:20:56:300000:0:0:0: Viasat Film Premiere Action

 

How are these different service refs obtained .

When I use Dreamset and read the channels from 4.8E from King-of-sat I get the second value.

 

However in the vHannibal settinglist the first value is given.

 

How come?

Or is this some clever clog who wants to do things a bit different?

 

Willy
 

Edited by doglover, 27 March 2020 - 15:32.

[WanWizard]

The vhannibal entry is missing the TSID and the ONID (both zero)  and has a rubbish namespace.

 

The namespace of a sat is the orbital position in hexadecimal, suffixed with 4 zero's. 4.8E is 0030 ( 48d = 30h ).

 

I can't imagine that this entry gives an image, unless the list comes with an equally rubbish lamedb and satellite.xml, and the tuners of the box are configured with those rubbish values.

[doglover]

That is my impression also.

But I am faced with this for inclusion in the rytec channels file.

 

Willy

[WanWizard]

Nobody can contact this vhannibal to have him (her?) explain? I think it's an italian list?

[WanWizard]

I checked the 13E file from vhannibal,

 

There is something weird in the lamedb:

0082afc2:0065:0001
	s 12226000:27500000:1:3:130:2:0

0082accf:0578:013e
	s 11471000:27500000:1:3:130:2:0

Two transponders, 12226V and 11471V, which don't have a 0 in the last 4 digits of the namespace.

 

This is causing the problem, I can only assume the creator uses some non-standard image to create the lists?

[doglover]

As I said:  A "clever" clog who wants to do things differently......

The standard way is difficult enough.

[Abu Baniaz]

With regards to the four "0" in namespace, that is not always the case. When the 0's are used, the namespace sub network is being ignored, that is the default and has always been the case. The option to not ignore it was added a few years ago. I can't remember if it was Dimitrij or Athoik. IIRC, Huevos then added function to individually select option for DVBC, DVBT or DVBS.

This change was catered for in picons, but not EPG or timers.

On ViX, the options are in Misc under tuners and scanning. PLI stil has them in Customise menu.

Sent from my Moto G (5S) using Forum Fiend v1.3.3.

[doglover]

And what was the reason for doing so....

[Abu Baniaz]

Not too sure, but think it is part of the DVB standard. It also allows more DVB-T to recognise differences when broadcasts from different masts are receivable.

[doglover]

Just scanned 11471 V with OpenPLi on a Mutant HD2400

 

Result:

#SERVICE 1:0:1:3:578:13E:82ACCF:0:0:0:
#SERVICE 1:0:1:7:578:13E:82ACCF:0:0:0:
#SERVICE 1:0:1:8:578:13E:82ACCF:0:0:0:
#SERVICE 1:0:1:B:578:13E:82ACCF:0:0:0:
#SERVICE 1:0:1:D:578:13E:82ACCF:0:0:0:
#SERVICE 1:0:1:E:578:13E:82ACCF:0:0:0:
#SERVICE 1:0:1:20:578:13E:82ACCF:0:0:0:
#SERVICE 1:0:2:1:578:13E:82ACCF:0:0:0:
#SERVICE 1:0:2:6:578:13E:82ACCF:0:0:0:

In the satellites.xml file is this given:

<transponder frequency="11471000" symbol_rate="27500000" polarization="1" fec_inner="4" system="0" modulation="1" />

Nothing unusual.

 

So I am still wondering where this comes from...

If it is part of the DVB-T system, what does it then on a satellite transponder...

 

Also on King-of-sat I cannot find anything special about this transponder.

Edited by doglover, 29 March 2020 - 08:09.

[s3n0]

DVB-T and DVB-C use specific namespaces with mask EEEE0000 (for DVB-T) and FFFF0000 (for DVB-C). The remaining 4 hexadecimal places represent the frequency of a particular channel for DVB-T or DVB-C. But why are they also used for satellite positions ? I also have no idea.

 

 

Spoiler

The remaining 4 hexadecimal places are used, I think (but I don't know for sure) in the new Dreambox image. They are used primarily because of the possible match of the entire service reference code (in the case of DVB-T or DVB-C), even though ServiceID is already defined there, there may be matches (for example, ProviderID is unfortunately missing in the service reference code specification). Therefore, it is confusing not to include the frequency of a particular channel. The Transponder-ID is included in the SRC specification but not its frequency. For these reasons, we may find the same SRC codes for different channels in some countries. The satellite position is unique, but the DVB-T and DVB-C masks like FFFFxxxx and EEEExxxx are not unique. Adding DVB-T and DVB-C frequencies to namespace in the SRC code will resolve any confusing data. The frequency for DVB-T and DVB-C represents the same meaning as the satellite position for DVB-S.

[doglover]

If this information is the frequency, How is it translated.

I tried converting it from hex to decimal, but nothing made sense

 

hex ACCF = DEC  44239

 

Willy

[Abu Baniaz]

S3n0's comment is about the service reference components, not the namespace components.

 

 

This is the commit that added this

https://github.com/O...bf316a68bf9da71

 

Followed by

https://github.com/O...13f0709317bc8d5

https://github.com/O...7d286341782424e

Edited by Abu Baniaz, 29 March 2020 - 15:43.

[s3n0]

If this information is the frequency, How is it translated.

I tried converting it from hex to decimal, but nothing made sense

 

hex ACCF = DEC  44239

 

Willy

Yes, but you write about DVB-S and I write about DVB-T/C. In the case of DVB-S namespace must be there an error (in my opinion) because the remaining 4 hexadecimal places (i.e. 2 bytes) should be equal to zero. Try to contact Vhannibal as @WanWizard advised you, hm... I wonder what Vhannibal will answer.

[Robinson]

I remember a few years ago Polish Nickelodeon also had those strange characters instead of 0's.

As far as I can remember, non-0 values are used in certain circumstances related to ONID, NID or TID perhaps. I don't know, hoerver, what the circumstances must be to produce those non-0 values.