Experts please biss key problem due to same video pids

besuperior
Registered Member
Registered Member
Posts: 61
Joined: 22 May 2016, 7:58 am
Has thanked: 2 times
Been thanked: 3 times
Contact:

Experts please biss key problem due to same video pids

#1



Post by besuperior »

india vs nz......HINDI and DD feed using same Video pids 0065....hindi and dd feed key mix now....any solutions..please help.i have vu+solo4k
sONY 4K HDR TV 43INCH
Sony 40inch Led
Sony 26inch Lcd
Vu+uno4k
Hyper 8800 Hd with 2tuner
Neoset i500p
8ft Dish with Motorized setup
95|100C+Ku|93|91|85|105|38|
besuperior
Registered Member
Registered Member
Posts: 61
Joined: 22 May 2016, 7:58 am
Has thanked: 2 times
Been thanked: 3 times
Contact:

Experts please biss key problem due to same video pids

#2



Post by besuperior »

Any one here to reply....?
sONY 4K HDR TV 43INCH
Sony 40inch Led
Sony 26inch Lcd
Vu+uno4k
Hyper 8800 Hd with 2tuner
Neoset i500p
8ft Dish with Motorized setup
95|100C+Ku|93|91|85|105|38|
User avatar
webfred
Junior Member
Junior Member
Posts: 2
Joined: 23 Mar 2018, 9:20 pm
Contact:

Experts please biss key problem due to same video pids

#3



Post by webfred »

Hello,

You can use Oscam-Emu (non official Oscam)
it is able to manage what you are looking for.
See informations below about that, (sorry i have an error message when i try to post the Github link) :mrgreen:

Code: Select all

October 2017 update (revised)
Support for BISS channels in the Emu has been greatly improved.

The old code distinguished channels only by using the service id (sid) and any one of the ecm pid (which for 99.99% of the channels is the same) or the channel's video and audio pids. As a result there were too many key clashes in the SoftCam.Key file. These formal (legacy) methods of channel identification remain in the new code as well for backwards compatibility and for those users that have a small number of keys in their SoftCam.Key and don't experience collisions. This way no editing is needed for the SoftCam.Key to work with the revised BISS code.

The revised code makes key searches based on crc32 hashes. There are two different hashes available:
The namespace hash, which is calculated by the enigma2 namespace (orbital position, frequency, polarization) and the service id of the channel. These two alone are enough to create a unique channel identifier.
There's also a universal hash, which is calculated using every pid of the channel (service id, pmt, video and audio pids). This universal hash, while not being unique as the namespace hash, is available on every box (enigma and non-enigma) and is a better alternative than oscam's constant cw protocol, since it takes audio pids into account, as well.
Using hashes to match keys, we get a distinct (unique in the case of namespace hash) identifier for each channel, which makes OSCam-Emu ideal for descrambling not only a huge amount of regular channels, but also for occasional transmitions (feeds).

December 2017 update
Support for date-coded BISS keys

Date-coded keys is a advanced feature that allows users to set an expiration date for their BISS keys.
This is extremely useful for feed hunters that want their keys to last for a specific period of time (while the feed is active). It helps avoiding key collisions and prevents serving bad keys since expired keys are no longer used by the Emu.
Date-coded keys can be enabled from the Emu's settings in the webif and are disabled by default. They can be used in the namespace hash, universal hash and "All Feeds" search methods, the three most suitable methods for feed keys. See Note 2 for more information on how to add date-coded keys in your SoftCam.Key file.

Syntax for keys in SoftCam.Key
The emulator now supports 6 different key formats in SoftCam.Key. The search for a matching key is done from the highest priority (tightest test) to the lowest priority (loosest test).

1 - Match key by namespace hash (highest priority) (enigma2 only)
F <namespace hash> 00 <key>
where

namespace hash (4 bytes) :  the namespace hash (unique id) of the channel (created automatically by the emulator)
key            (8 bytes) :  the key (Control Word - CW) with or without valid checksum bytes set
Example:

namespace hash :  CE466C4E
key            :  1122334455667788

F CE466C4E 00 1122334455667788
2 - Match key by universal hash
F <universal hash> 00 <key>
where

universal hash (4 bytes) :  the universal hash (distinct id) of the channel (created automatically by the emulator)
key            (8 bytes) :  the key (Control Word - CW) with or without valid checksum bytes set
Example:

universal hash :  A41FC067
key            :  1122334455667788

F A41FC067 00 1122334455667788
3 - Match key by tsid and onid combination (new method - December 2017)
This is a special key searching method that is very useful when there are many channels in a transponder using the same BISS key. With this method, a single key line in the SoftCam.Key file can serve all channels in that specific transponder mux.

F <tsid><onid> 00 <key>
where

tsid (2 bytes) :  the transport stream id of the channel/transponder
onid (2 bytes) :  the original network id of the channel/transponder
key  (8 bytes) :  the key (Control Word - CW) with or without the checksum bytes set
Example:

tsid    :  0123
onid    :  0987
key     :  1122334455667788

F 01230987 00 1122334455667788
4 - Match key by faulty ecm pid
F <sid><ecm pid> 00 <key>
where

sid     (2 bytes) :  the service id of the channel
ecm pid (2 bytes) :  the ecm pid of the channel only if it's different than '1FFF' (faulty, per BISS specs)
key     (8 bytes) :  the key (Control Word - CW) with or without the checksum bytes set
Example:

sid     :  0002
ecm pid :  FEFE
key     :  1122334455667788

F 0002FEFE 00 1122334455667788
5 - Match key by audio pid, or video pid, or pmt pid
F <sid><pid> 00 <key>
where

sid (2 bytes) :  the service id of the channel
pid (2 bytes) :  any other pid of the channel (except the ecm pid) like audio pids, video pid or pmt pid.
key (8 bytes) :  the key (Control Word - CW) with or without the checksum bytes set
Example:

sid :  0001
pid :  1020
key :  1122334455667788

F 00011020 00 1122334455667788
6 - Match key by service id alone
F <sid>1FFF 00 <key>
where

sid (2 bytes) :  the service id of the channel
1FFF          :  the default ecmpid for all BISS channels
key (8 bytes) :  the key (Control Word - CW) with or without the checksum bytes set
Example:

sid:  0100
key:  1122334455667788

F 01001FFF 00 1122334455667788
7 - Default "All Feeds" key (lowest priority)
If no matching key is found for a channel, the default key is used (if present). This is useful for events with many feeds that all use the same key. In this case, instead of having one key entry for each feed, you can use the default "All Feeds" key.

F A11FEED5 00 <key>
where

A11FEED5      :  Magical default key identifier for All Feeds
key (8 bytes) :  the key (Control Word - CW) with or without the checksum bytes set
Example:

key: 1122334455667788

F A11FEED5 00 1122334455667788
Note 1:
In the old BISS code, both "00" and "01" key types were used. The updated code automatically converts these keys to the new "00000000" never expiring (see Note 2), evergreen key (no action is required from the user). This is done in the Emu internally and no change is written to the SoftCam.Key file.

Note 2:
Date-coded keys allow Emu to evaluate the expiration date of a key. This feature can be enabled from the webif, in the Emu reader's settings. To set an expiration date for a BISS key, the unused "00" field in each key line is utilized. This field now represents the expiration date of the key. The date is entered in a YYMMDDhh (year, month, day, hour) format. For example, setting an expiration date of "17122510" means the key will expire December 25, 2017 at 10:00 a.m. local time. Keys with an expiration date of "00000000" will never expire and are valid forever. Same is true for the legacy "00" and "01" keys (see Note 1). When the date-coded keys are enabled, a key's expiration date is evaluated before it is loaded from the SoftCam.Key and before it is served to an ecm request. When date-coded keys are disabled, all keys, whatever their expiration date is set to, are used for serving ecm requests.

IMPORTANT: When using the date-coded keys setting a correct date and time to the receiver is crucial! Users are advised to use ntp based time instead of transponder time in their stbs.

Note 3:
OSCam-Emu informs the user about all possible key formats for a given channel.
Lines 1-2 correspond to the namespace hash. An example key (with orbital position, frequency and service id information) is printed to copy and paste in your SoftCam.Key file.
Lines 3-4 correspond to the universal hash. An example key (with audio/video pid count, pmt pid and service id information) is printed to copy and paste in your SoftCam.Key file.
Lines 5-8 correspond to the old key matching methods based on the channel pids. Notice that the pid search is done in reverse order (which usually is audio pids first, then video pid, then pmt pid) to better identifier channels where they share identical video pid but have variable counts of audio pids.
Line 9 correspond to the service id alone pid search.
Line 10 correspond to the default "All Feeds" key.

(emu) Key not found: F D325D0F7 00
(emu) Example key based on namespace hash: F D325D0F7 00 XXXXXXXXXXXXXXXX ;  10.0E 11483V sid:0001 added: 2017-10-21 @ 12:04
(emu) Key not found: F 8FFAC845 00
(emu) Example key based on universal hash: F 8FFAC845 00 XXXXXXXXXXXXXXXX ; av:3 pmt:03E9 sid:0001 added: 2017-10-21 @ 12:04
(emu) Key not found: F 00010FA1 00
(emu) Key not found: F 00010BB9 00
(emu) Key not found: F 000107D1 00
(emu) Key not found: F 000103E9 00
(emu) Key not found: F 00011FFF 00
(emu) Key not found: F A11FEED5 00
(emu) ECM failed: Key not found
Note 4:
For namespace hash, when frequency information is available, the emulator also calculates hashes that correspond to small frequency shifts (+/- 1MHz and +/-2MHz) to allow universality of the namespace hashes among users with different setups (e.g network ecms). These hashes are not shown, but if such a key is found, the user will be informed.

Note 5:
Under certain circumstances the enigma2 namespace misses the frequency and contains only the position information. If so, the tsid (transport stream id) and the onid (original network id) are used together with service id and the stripped namespace to calculate the namespace hash. This way, the namespace hash remains unique for every channel. The printed example key contains the tsid and onid (among with orbital position and service id information) instead of the frequency.

(emu) Key not found: F 2FC52124 00
(emu) Example key based on namespace hash: F 2FC52124 00 XXXXXXXXXXXXXXXX ;   3.0E  212C:0002:0028 added: 2017-10-21 @ 12:23
(emu) Key not found: F DF5D0185 00
(emu) Example key based on universal hash: F DF5D0185 00 XXXXXXXXXXXXXXXX ; av:4 pmt:0102 sid:0028 added: 2017-10-21 @ 12:23
(emu) Key not found: F 00280BBB 00
(emu) Key not found: F 002802B2 00
(emu) Key not found: F 002802A8 00
(emu) Key not found: F 0028008D 00
(emu) Key not found: F 00280102 00
(emu) Key not found: F 00281FFF 00
(emu) Key not found: F A11FEED5 00
(emu) ECM failed: Key not found
Note 6:
The tsid, onid combination (method 3) is available only when these two identifiers are deemed valid by enigma2, in other words, when the namespace is stripped off frequency (see note 4).

Note 7:
On platforms other than enigma2, the namespace variable might not be available (zeroed or filled with garbage). In this case, the emulator skips the namespace hash key matching method and tries to find keys based on the universal hash or the other legacy methods (methods 2-7).

Note 8:
The correct ecm pid for a channel is only available when using oscam dvbapi and local ecm requests. For example:

OSCam (dvbapi) <-> Emu
When using another client like cccam, the ecm pid seen by the emulator will always be '1FFF'. For example:

cccam <-> OSCam <-> Emu
Thus, for those rare cases where the channel's ecm pid is 'faulty' (other than 1FFF), the third priority search (method 4 above) will not work. Use one of the other matching patterns instead, for example matching by sid alone (method 6).

On network ecm requests (between 2 boxes connected via network protocols like cs357x or cs378x) the ecm pid will always be '0', even if dvbapi is used. For example:

OSCam (box1) <-> (network connection through cs378x) <-> OSCam (box2) <-> Emu
For this case, both the 'faulty ecm pid' and the 'All Feeds' matching patterns (methods 4 and 7) won't be available.
[ VU+ ZERO 4K, VU+ ZERO, DM800HD, VUGA SAT COMBO, ATLAS HD100 & HD200, GN-2500HD-HYBRID ]
besuperior
Registered Member
Registered Member
Posts: 61
Joined: 22 May 2016, 7:58 am
Has thanked: 2 times
Been thanked: 3 times
Contact:

Experts please biss key problem due to same video pids

#4



Post by besuperior »

thnaks man
sONY 4K HDR TV 43INCH
Sony 40inch Led
Sony 26inch Lcd
Vu+uno4k
Hyper 8800 Hd with 2tuner
Neoset i500p
8ft Dish with Motorized setup
95|100C+Ku|93|91|85|105|38|
Post Reply Previous topicNext topic

Who is online

Users browsing this forum: User avatarBing, No User AvatarDot, User avatarGoogle Adsense, User avatartiger, User avatarYandex and 226 guests