Hadu-CCcam Plugin für Windows

Hadu_-_CCCam_DVB_plugin_v_Beta_0.121

Hadu-CCCam_DVB_plugin_v_Beta_0.121

Changelog:
----------
0.1.2.1:
-bug fix for some incorrect connections in some cases.


0.1.2.0:
-bug fix for the "DVBViewerRecServ" option when set to 2 (always active),
-bug fix for incomplete server disconnections (if provoked by the server).


0.1.1.9:
-minor modifications concerning the windows resizing,
-it's now possible to load up to 64 CCCam servers within Hadu. But it's still limited to 6 active CCCam servers at the same time; you can choose which 6 active CCCam servers within -up to- the 64 possible ones,
-the maximum number of hops per node is now restricted to 8 (which is probably still too much from a reasonable point of view),
-an external -limited- tool called HaduSer has been created in order to get a few infos from Hadu and to send it a few commands, for Windows Vista/Seven and the DVBViewer recording service (and the DVBLink TVSource service). See "DVBViewerRecServ" option within the [Specific] section of Hadu.ini, and refer to the readme.txt file coming with HaduSer for more infos,
-several bug fixes concerning the Irdeto CAID and the way Hadu selects the correct ChId for a channel,
-minor bug fix within the statistic computes for a node,
-a few modifications into the ECM process and selection,
-the way Hadu starts/stops CCCam servers within the DVBViewer recording service has been modified. By default, session(s) with the concerned server(s) is/are now only active when the recording is running: see "DVBViewerIdleServ" option within the [Specific] section of Hadu.ini. But you can still return to the former way (i.e. session with the server always active) by setting this option to 2,
-workaround for non null messages 05 (Server ask) in case of CCCam server version 2.1.2. Hadu will now stop and re-start the server session, after a few ECM answers when having received this message.


0.1.1.8:
-left double-click on icon in Systray displays the Monitor window,
-workaround for Trumanshare "wrapper" application, which sends TS data with an incorrect length,
-maximum value for ECMTimeOut option has been increased to 120 seconds,
-PMT PID is displayed within the Monitor window (just before the status of the PMT),
-decrypt cyphered subtitles when used as a DVBViewer plugin (DVBViewerAllAudio=1 is required),
-bug fix concerning Irdeto ECMs with a lots of ChIDs,
-TimeRecon option added, for re-connections. It is recommended not to modify the default value for this option.

Hadu is a CardSharing Client plugin for DVB softwares on PC using DVB TV-Cards (Windows). It works as a MD plugin, a DVBCore plugin (eg. ProgDVB) or as a DVBViewer plugin. Currently, it only supports the CCCam protocol (without the AU option).

Installation:
————-
Just put Hadu.dll and Hadu.ini into the directory affected to plugins, regarding your current DVB software. It can be the directory of the software (i.e. for old versions of ProgDVB), or a given subdirectory (i.e. ./Plugins for MyTheater and Alt-DVB, …).

As it is compatible with the DVBCore API, use it as a DVBCore plugin (for DVBCore softwares) instead of using it with MDWrapper. With DVBViewer, use it as DVBViewer plugin instead of using it with SoftCSA.

Don’t use two or more CardSharing Clients and/or SoftCam Emulators at the same time (like Yankse, S2Emu or VPlug), unless you know perfectly what you are doing.

Directories of installation for the main DVB softwares:
——————————————————-
Put all the files (i.e. only Hadu.dll + Hadu.ini currently) in the same directory , as indicated hereafter:

* ProgDVB : main directory of the DVB software (or /Plugins subdirectory for version 4.38 or later of ProgDVB)
* Alt-DVB : /Plugins (or /Plugins/av0) subdirectory, and/or /Plugins/pip subdirectory for the pip, and others (/Plugins/av1 to Plugins/av2
* MyTheater, RitzDVB: /Plugins subdirectory (to use Hadu as a DVBCore plugin). Try to avoid the solution MDWrapper.dll in /Plugins subdirectory and Hadu in /MDPlugins subdirectory (MDWrapper is a workaround to make old MD plugins working with MyTheater and other DVBCore softwares)
* DVBDream 0.xx: /Modules subdirectory since version 0.85 (to use Hadu as a DVBCore plugin). /Plugins subdirectory (to use Hadu as a MD plugin) for precedent versions
-DVBDream 1.xx and above : /Plugins/pip00 and others (/Plugins/pip01 up to /Plugins/pip19) subdirectories, to use Hadu as a MD plugin
* WatchTVPro: /Plugins subdirectory (Hadu is using the TT Trick automatically if it is possible)
* HispaDVB: main directory of the DVB software for old versions, and /Plugins subdirectory since version 2. Hadu is no more using the TT Trick automatically for this software, because it is no more needed for HispaDVB version 2 and above
* MultiDec: main directory of the DVB software (Hadu supports natively the different versions of the SS1 firmware)
* DVBViewer: /Plugins subdirectory. Avoid the solution SoftCSA.dll in /Plugins subdirectory and Hadu in /MDPlugins subdirectory. Please, note that the CSA.dll (coming with the SoftCSA package coded by Pikachu) is recommended for faster unscrambling, though not absolutely mandatory. The CSA.dll must be located into the /Plugins subdirectory (or KeyPath2) or into the main directory of the DVB software. Otherwise, Hadu will use its own internal CSA algorithm (code kindly provided by courtesy of Pikachu. Thanks!). With DVBViewer version 3.4 and above, you can also use the FFDeCSA.dll (both with the CSA.dll) : depending of your DVB card, the ‘Open whole Transponder’ Hardware option in DVBViewer will have to be checked or not, to optimize the video/audio CSA unscrambling treatment.
The ‘Has CI module’ entry option into the hardware options of DVBViewer must be checked.
It is also possible to use Hadu with the recording service of DVBViewer, if you install first the Wrapper for recording service of Pikachu. Caution : currently, this option might lead to unstable behaviors of DVBViewer (especially when closing this software).
* SkyView: /MDPlugins subdirectory
* DvbTn: /Plugins subdirectory (to use Hadu as a DVBCore plugin)
* WinSTB: /MDPlugins subdirectory
* DiavloB: /Plugins subdirectory (to use Hadu as a MD plugin, though the software is based upon the DVBCore SDK)
* MajorDVB: /Plugins subdirectory
* TSReader: /MDPlugins subdirectory
* WinClip: /Plugins subdirectory

Caution: For DVB softwares based on the DVBCore SDK, don’t install Hadu as a MD plugin and as a DVBCore plugin (choose either the first or the second solution, but not both !). Same thing for DVBViewer.

Do not use the DLL TTTrick.dll: Hadu has its own TT Trick implemented.

Server Configuration (Hadu.ini):
—————–

For each server declared, the convention for its declaration is to create a section with (note the “Serv_” string at the beginning) : [Serv_whateveryouwishforyourservername].

Then comes the different parameters for the server. Only the “Server” parameter is mandatory.

Syntaxe for the “Server” parameter :
Server=Protocol:Server:Port:(unused):Username:Pass word

Sample: Server=CCCam:MyServer.com:12000:0:MyUsername:MyPas sword, where:

* CCCam: Declaration for a CCCam server (other protocols currently not available),
* MyServer.com: URL or IP address for the server,
* 12000: Port for the CCCam server (decimal value),
* 0: Caid/mask. Not used (may be empty), see “CAIDProv” and “NoCAIDProv” parameters instead,
* Myusername: Name of the user (limited to 20 characters for CCCam protocol),
* Mypassword: Password for the user.

Others parameters (each of them is optional):

* Active ([1] or 0): Server active or not active. A non active server cannot be started.
* TimeOut (0=None, or 3-7 seconds. Default is [5] seconds): Timeout value if the server is not answering,
* PadTime ([0=None], or (TimeOut+2)-N seconds): interval of time for which a “pad” command is sent to the server if no other commands has already been sent (usually must be kept to 0),
* WantEmus (0=No or [1=Yes]): similar to WantEmus option in CCCam.cfg. If set, friends emus are also used (if the server has authorized them for the user). Even if WantEmus is not set, the concerned nodes are displayed into the list of nodes, but are not available.
* MaxHop ([0=None], or 1-N): if WantEmus is set, nodes with a hop value superior to this limit are not used. A null value indicates no limits.
* CAIDProv ([None]): list of CAID/Providers ONLY used to make requests to the server(s). Each entry may concern a whole CAID, or just only one provider for this CAID. Entries are separated using a comma character. Samples:
CAIDProv=0100,1801 : only CAIDs 0100 and 1801 will be used.
CAIDProv=0604,0100:0084,0100:006A : only CAID 0604 and CAID/Providers 0100/84,0100/6A will be used.
* NoCAIDProv ([None]): list of CAID/Providers EXCLUDED. Syntax similar to the “CAIDPRov” option. Samples:
* NoCAIDProv=0604,0500 : CAIDs 0604 and 0500 won’t be used.
* NoCAIDProv=0100:6A,1810,0500:032100 : CAID 1810 and CAID/providers 0100/6A,0500/32100 won’t be used.

Limits:
——-

* Here are the main current limits applied into the plugin:
* Maximum number of CCCam servers (active or not active): 6
* Maximum number of nodes per server : 2048
* Maximum number of providers per nodes : 16
* Maximum number of hops per node : 16 (though more than 3 or 4 is probably useless)
* Maximum numbers of CAID/providers entries into to “CAIDProv” and “NoCAIDProv” options : 32
* Maximum length size for user and password: 20 for the user, 128 for the password.

um das ganze auf dem aktuellen Stand zu halten, hier die 1.22 version dazu.

So, hab mich gestern mal beigemacht und meine ersten Versuche in Sachen
Homesharing unternommen.
Meine alte SkyStar USB rausgekramt,einmal diesen Fred durchgelesen....und....lüppt.:biggrin:

Nächster Schritt wird dann das sharen auf andere Boxen (aber nur innerhalb meiner Wohnung) sein.

Danke an alle die hier alles immer sehr geduldig erklären.
Bin ich von diesem Board aber auch nicht anders gewohnt.:palamakia:

Zitat von lotzik;329940

So, hab mich gestern mal beigemacht und meine ersten Versuche in Sachen
Homesharing unternommen.
Meine alte SkyStar USB rausgekramt,einmal diesen Fred durchgelesen....und....lüppt.:biggrin:

Nächster Schritt wird dann das sharen auf andere Boxen (aber nur innerhalb meiner Wohnung) sein.

Danke an alle die hier alles immer sehr geduldig erklären.
Bin ich von diesem Board aber auch nicht anders gewohnt.:palamakia:

Mit Hadu kann man nicht sharen , da Hadu nur als CCcam client funktioniert nicht als server

neue Version beta v 0.123

Changelog:
----------
0.1.2.3:
-EMM support (still experimental),
-possibility to indicate a static Node ID added,
-ECM process largely modified. If this new version doesn't work properly for you, get back to your former version,
-controls concerning the ECM provider completed,
-default value for the "WantEmus" option is now set to [0=No],
-memory occupation for each server lowered,
-several other bug fixes and minor enhancements.

kurz und knapp: nein

Kann man auch mit Hadu 0.125 auf Oscam zugreifen?

Zitat von Hanseart;362958

Kann man auch mit Hadu 0.125 auf Oscam zugreifen?

probiers mal mit einer aktuellen oscam binary und folgenden Einträgen in den configs

oscam.conf


[cccam]
port                          = 12000
reshare                       = 0
version                       = 




oscam.user
[account]
user = user
pwd = pss
monlevel = 4
group = 1  
AU     = xx
caid = xxxx




Hadu config
[Serv_1]
Server=192.168.178.xxx:12000:0:user:pass

natürlich die IP und die xxx anpassen

Hadu CCCam DVB plugin 0.126 im ULC

Hallo zusammen,

hab mal die Hadu 0.126 ins ULC gepackt.

(Hadu ist eine cccam für Windows, welche z.B. mit dem DVBViewer genutzt werden kann)

Hadu 0.126

Viel testen konnte ich noch nicht, aber laufen tut sie.

Wenn ich mehr weiß folgt eine Info.

Hadu - CCCam DVB plugin - version Beta 0.127

Changelog:
----------
0.1.2.7:
-(partial) support for DreCrypt EMMs,
-EMM PIDs associated to ECM PIDs (based upon the CAID and provider criteria)
are now all displayed into the concerned column ("Monitor" window),
-an option has been added to display all the other EMM PIDs
(i.e. EMM PIDS not associated to ECM PIDs; see "DispAllEMMs" option);
-"EMMCAID" option has been extended, in order to include an optional EMM PID
(see "EMMCAID" option),
-bug fix for the non correct display of indexed nodes
(when the list of the nodes is sorted by user),
-Hadu is considered back as a 2.1.4 version client by default. You can of
course still modify the client version sent to the server (see "Version" option),
-minor modification into the possible levels of informations to log
(see "LogMessLevel" option),
-display of the "Server Infos" window has been optimized
(it's now a bit more reactive, while using less CPU resources),
-an option has been added when Hadu is used within
the DVBViewer recording session. It's now possible to start the
connection with the server(s) only if the channel is encrypted
(see "DVBViewerEncrServ" option),
-support for the new CCCam commands introduced
in CCCam version 2.2.0 or above
(i.e. commands 0F for the node data, and commands 0C, 0D for the new CCCam "checks")
. An option has been added to authorize
or not the Node SID assignment/rejection feature present in commands 0F
(see "UseNodeSID" option). The Node SID assignment/rejection feature will be activated
by the server, only if Hadu is also declared as a CCCam client version 2.2.0 or above
(see "Version" option). But, as there is a bug concerning the new CCCam "checks",
declaring Hadu as CCCam client version 2.2.0 may conduct to an improper channel
decoding (see the new workaround menu "Switch DCW Last Byte"),
-support for the OSCAM Partner handle, and its Node SID assignment/rejection
feature (the Extended ECM Mode is also checked but currently not used). Several
options have been added to authorize them or not (see "OSCAMPartner", "OSCAMExt"
and "OSCAMSID" options). Furthermore, when activated these features are displayed
at the bottom of the "Server Infos" window, as for the build of the OSCAM server,
-2 new features have been added: a list of ECM PIDs used (i.e. ECM PIDs cache; see
"Hadu-Cache.txt" file), and a list of manual ECM PIDs (see "Hadu-Manual.txt" file).
These features may be activated/deactivated directly from the main menu of Hadu
(see "Cache" sub-menu, and "CacheUse", "CacheUpdate", "ManualUse" options),
-an new column (title "Opt") has been added in the list of the nodes into the "
Server Infos" window (to display eventual additional infos concerning the nodes),
-all the log files (i.e. 'Hadu-Mes.log', 'Hadu-EMM.log', 'Hadu-PIDxxxx.log' and
'Hadu-Dump.txt') are now always put in the same directory as the plugin itself
(no more in path indicated by "Keypath2", if this option is used). "Keypath2"
is reserved for files possibly shared within several occurs of Hadu
(like the files for the ECM PIDs used and the manual ECM PIDs),
-support for Nagra Tiger EMMs,
-TID and SID for the current channel are displayed into the "Monitor" window,
-an option has been added when providers/ChIDs used within
CCCam messages are rejected by the server (see "DontUseProvFor" option),

Zitat

Config Hadu V 3.0.0 Beta – First Version @16/06/2011

History:

- V 3.0.0 Beta - First Version.
Feature:

1- This version using the original hadu.ini.

2- Can set\change hadu setting (more Features will add soon).

3- User can enter unlimited clines.

4- Choose server name for every cline.

5- Can fill all fields automatically (with new fixes).

5-1 You can copy and paste cline at host textbox and program will fill other parameters.

5-2 Now in this version you can copy cline with C: or with out it.

Note: it should have a space character between every part. (C: Host Port Username Password) it doesn't important copy no {0:0:3} or don’t… program will detect them automatically.

6- Program remember Hadu.ini path, use host name, show/editing mode and settings.

7- Compatible with Hadu v 0.127

Tested on Win Xp and Seven.

I recommended using original hadu.ini file that I put that in zip file.

This is the first version and it's beta so please tell me any bug or any idea here.

If any body know any way to check a cline is active or not tell me that maybe I can put that in this program…..

Alles anzeigen

Alle Versionen jetzt auch sortiert im ULC hier zu finden

History:
V 3.1.2 – New Feature and fixes:
Release date: 08/07/2011
1- Reload Hadu.ini (when you change hadu.ini with plugin its need to reload hadu.ini to program).
2- Reload Hadu list (Only ProgDVB 6.after you save all alternation while ProgDVB is run you can have new changes without rerun ProgDVB.(F5 Hadu List)).
3- Improve server name.
4- Always on top.
5- A fix in target hadu.ini
6- A fix in server list. (User can't use enter in list)
7- Fix in automatic filling
8- After click Add, server fields will be empty.
9- Remember last position of program.
10- Minimize Button!!
11- And more fixes
V 3.0.0 Beta - First Version Feature:
Release date: 16/06/2011
1- This version using the original hadu.ini.
2- Can set\change hadu setting (more Features will add soon).
3- User can enter unlimited clines.
4- Choose server name for every cline.
5- Can fill all fields automatically (with new fixes).
5-1 You can copy and paste cline at host textbox and program will fill other parameters.
5-2 Now in this version you can copy cline with C: or with out it.
Note: it should have a space character between every part. (C: Host Port Username Password) it doesn't important copy no {0:0:3} or don’t… program will detect them automatically.
6- Program remember Hadu.ini path, use host name, show/editing mode and settings.
7- Compatible with Hadu v 0.127

V 3.1.4
Change Screen of Program and Fixes.

Download