Register

Welcome to the RDI-Board Community.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed.


Donate Now Goal amount for this month: 100 EUR, Received: 100 EUR (100%)
Donate to support this site...

Results 1 to 3 of 3
  1. #1
    Lord of Light Master
    Join Date
    May 2008
    Location
    Eden Garden
    Posts
    88
    Posts Thanks / Likes

    Default Hadu - CCCam DVB plugin - v Beta 0.121

    Introduction:
    -------------

    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 or as a DVBViewer plugin.

    Currently, it only supports the CCCam protocol (without the AU option).

    ************************************************** *******************
    * DISCLAIMER:
    *
    * It is illegal to view pay-TV channels without a valid subscription.
    *
    ************************************************** *******************





    http://www.4shared.com/file/14786233...Beta_0121.html
    Last edited by Satanicu; 9th November 2009 at 08:19.

  2. #2
    Lord of Light Master
    Join Date
    May 2008
    Location
    Eden Garden
    Posts
    88
    Posts Thanks / Likes

    Default

    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 ...... 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 ...... ECMs with a lots of ChIDs,
    -TimeRecon option added, for re-connections. It is recommended not to modify the default value for this option.

    0.1.1.7:
    -bug fix concerning the trouble for the first of the DCW in case of DVBViewer and NDS/Videoguard encrypted channels (first decoding for the channel too long in this case).

    0.1.1.6:
    -added the possibility to modify the maximum number of CAID/node loops (see "MaxCAIDLoops" option),
    -bug fix concerning the closing and re-opening of the same ECM PID in some cases,
    -bug fix for ECM PID closing requests (not correctly processed in some cases),
    -number of timeouts for ECM requests added into the nodes list,
    -minor enhancements into ECM request for the same ECM PID.

    0.1.1.5:
    -added the possibility to use an icon for Hadu in the Systray (see "Systray" menu),
    -some minor bug fixes,
    -automatic detection for Trumanshare "wrapper" application (if it's called trumanxxxxxx.exe). In this case, the command to return DCWs to the application is modified (i.e. $0410 instead of $0700). As for sssp, it's always possible to change it using the "DescrCommand" option into the "[Device]" section of Hadu.ini,
    -fix for a nasty bug concerning the node selection (still introduced into version 0.1.1.3). The start to decode a new channel should be now faster, mostly of the time (but still not faster than your server(s), of course).

    0.1.1.4:
    -added the possibility to cancel the temporarily effects of the manual ECM PID selection within the server menu (i.e. without the necessity to change or re-select the channel),
    -bug fixes inside the node priority process (introduced into version 0.1.1.3).

    0.1.1.3:
    -minor modification for the connection timeout process,
    -priority added: general rules (see "PrioGenRules" option) and CAID/provider for nodes (see "PrioCAIDProv" option),
    -modification to accept connection for CCCam servers v2.1.2.

    0.1.1.2:
    -bug fix for some CAIDs associated to emulators,
    -"NoSID" option added, to ignore one or several SIDs for a server,
    -"Enable/Disable (one CAID)" and "Enable/Disable (all CAIDs)" added into the contextual menu for a node (right-click on the node to get the corresponding menu). These menu entries correspond to the "NoNodeCAID" option into Hadu.ini; refer to this option for more details. Note that "Ignore/Use" menu entry is temporary, associated to the current session with the server, and specific to one node. While these two new menu entries are saved (i.e. not temporary), and specific to one server (all the CAIDs for a server = all the nodes belonging to this server) or to one CAID of the server (which may correspond to one or several nodes for the concerned server).

    0.1.1.1:
    -bug fix for providers associated to emulators.

    0.1.1.0:
    -several modifications for ...... ECMs (once more),
    -possibility to 'Log a PID' added (within the main menu),
    -bug fix for incorrect statistics in case of ...... ECMs,
    -"WantEmus" option is now relative to accepting or refusing emulators from server(s): default value is 1=Yes,
    -bug fixes for CAID and providers associated to emulators,
    -some fixes for improper data send by some "wrapper" applications,
    -modification into the ECM timeout process,
    -time response from server(s) added (2 new columns into the "Server Infos" window). Both for returned DCWs and for negative answers (i.e. 'No decoding' messages), there is a first latency for multiple ...... ECMs (if several ChIDs are used),
    -some fixes for nodes display in case of more than one server active.

    0.1.0.9:
    -automatic detection for sssp "wrapper" application (if it's called ssspxxxxxx.exe). In this case, the command to return DCWs to the application is modified (i.e. $0410 instead of $0700). However, you can always force it, using the "DescrCommand" option into the "[Device]" section of Hadu.ini,
    -modification to stick as tight as possible to the answer of the server(s) concerning the ECM requests. It may have some negative impacts in some rare situations. In these later cases, stop and restart the concerned server connection,
    -new modification for ...... ECMs. Only the first positive ChID (i.e. available for decoding purposes) is used, after a first test with all of them.

    0.1.0.8:
    -the way to ignore/use an available node has changed: right-click now on the node to get the corresponding menu (currently limited to this feature only),
    -because of the tremendous number or disconnections/re-connections of some nodes for most of the CCCam servers (especially, but not only, those of version 2.0.11), the restart of the CAID selection process is no more always called. Unless no nodes have been found to decode the current channel; in this last case, the restart is still automatic. In some rare cases, you may have to ask manually to retry all the ECMs,
    -...... ECMs are now sent to the CCCam server(s) one at time only (though still currently a workaround),
    -a new modification into the CAID selection process, to increase the stability of the decoding process.

    0.1.0.7:
    -bug fix for a incorrect CAID selection process. It mainly concerns all the Seca providers (but could also have a negative impact for all the others CAIDs too).

    0.1.0.6:
    -number of disconnections column added into the nodes list,
    -"NoNodeCAID" option added, to ignore all the nodes or only one node of a server,
    -CAID tunneling added for Betacrypt<--->Nagra3 CAIDs (see "CAIDTunnel" option). Do use CSa.dll and FFDeCSA.dll, if you plan to view Premiere HD channels with DVBViewer.


    0.1.0.5:
    -bug fix for Cryptoworks "long" ECMs (for Digiturk mainly).

    0.1.0.4:
    -another modification concerning the "wrapper" applications like SSSP Plug, ... Remember to set "UsePSITables=0" (or unchecking the corresponding menu entry), and "ECMTimeout=12" (for instance) for these applications.

    0.1.0.3:
    -DCWs display added into the CAID list. This display corresponds to the last DCW(s) received; which doesn't mean necessarily the current one(s),
    -all the windows of the plugin can now be minimized (and restored). The "Monitor" and "Server Infos" windows are also now resizeable (only the horizontal sizing is used; mainly to have a wider area for the lists of data),
    -choice to display IP Address or URL in the Server list has been added. The default option is still to display the IP Address (see "DisplayIPorURL" option),
    -the refresh time for the Server infos has been set to 4 seconds,
    -bug fix concerning the node disconnection treatment,
    -still another bug fix for incorrect accepting of some certain kind of nodes,
    -an ECM timeout option has been added (see "ECMTimOut" option). It's mostly to be used with "wrapper" applications like SSSP Plug, ... As I cannot test these kinds of application, I don't know if this feature is sufficient to make my plugin compliant with them,
    -node ID display added into the nodes list (last columns).

    0.1.0.2:
    -correction concerning the internal CSA support within Hadu (when used a as DVBViewer plugin). Don't use it unless absolutely necessary, especially for HD channels. Prefer the CSA.dll/FFDeCSA.dll (both of them) instead (see DVBViewer installation section),
    -bug fix for incorrect accepting of some certain kind of nodes.

    0.1.0.1:
    -new modification to process NDS/Videoguard ECM still a bit faster. Be sure to use and to configure correctly your DVB software, in order it can deliver one TS at a time to its plugins (i.e. packet size=184 bytes). And always uncheck the "Log Messages" menu in case NDS/Videoguard ECMs, if you don't want to get glitches,
    -modification to allow the "special" NDS/Videoguard ECM process, in case of DVBCore plugin,
    -several fixes concerning the multi-servers feature,
    -fixes for incorrect ECM results display and Server infos display, in different cases,
    -bug fix if no ECM stream present for a valid PID declared into PMT,
    -a few minor enhancements: explicit message when the same server ( = same IP address and same port) is already in use, Server infos window no more centered for each subsequent calls, ...
    -correction when stopping and restarting a server while being on an encrypted channel,
    -start/restart process enhanced. After 3 consecutive negative tries, the restart process is made: 1 second, then 2 seconds, then 4 seconds, ... then 32 seconds later; with a maximum of 32 seconds between each restart calls. However, a manual start is always processed immediately, regardless of the current delay between 2 restart calls,
    -various internal bug fixes and minor modifications,
    -complement of informations in some parts of the readme.txt file.

    0.1.0.1:
    -Initial public release.

  3. #3
    Lord of Light Master
    Join Date
    May 2008
    Location
    Eden Garden
    Posts
    88
    Posts Thanks / Likes

    Default 12

    Note:
    -----
    Please note that this version is a beta test release, which is not intended to end-users. This version has not been thoroughly tested and so, one can expect any kind of bugs and troubles ...

    Purpose of this version is to test this plugin by people who accept to do so. Please report bugs or successful tests with a maximum of pieces of information concerning your configuration and your troubles.


    Installation:
    -------------
    Just put Hadu.dll and Hadu.ini into the directory relative 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.
    -DVBViewer recording service: /Plugins/Plugins1 to /Plugins/Plugins31 subdirectories. Allow this recording service to interact with the Desktop, and set "Systray=1" for the concerned Hadu.ini file(s). But, as interacting with the Desktop is not allowed for services within Windows Vista or Seven, you'll have to use for them a -limited- tool called HaduSer (see "DVBViewerRecServ" option). Don't forget that it's impossible to connect to the same server twice (double login are rejected by CCCam servers).
    -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
    -DVBLink TVSource : /Plugins subdirectory. You'll also have to install the CSA.dll into this plugin directory (but this dll is used by DVBLink TVSource, not by Hadu). Concerning the display of Hadu, see as for the DVBViewer recording service.

    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.

    Each time it is possible (Alt-DVB2 and DVBDream 1.xx, for instance) set the packet size for plugins to 184 bytes, to minimize the delay for the decoding process.


    Other Files used :
    ------------------
    None currently.


    Main Menu:
    ----------
    -Active: If checked, the plugin will use the incoming ECMs to try to decode the current encrypted channel (i.e. by sending the ECMs and requesting the needed DCWs to the server(s)). Furthermore, connections with servers will only start if the plugin is active.

    -Use PSI Tables: If checked, the plugin will analyze the PMT (for the list of ECMs) and the CAT (for the list of EMMs). If not checked, it will take data obtained from the DVB software. It "costs" a little more time to begin the decoding when you change of a channel, but it is strongly advised to use this option for better results. Data given by DVB softwares are often incomplete, erroneous and are not continuously updated.

    -Monitor ...: Display the Monitor window to see the current analysis work and results.

    -Log Messages: You can log the main actions and the incoming/outgoing messages with the servers.The log files are stored, either in the KeyPath2 directory if used, or in the directory of Hadu. Note that this option may have a negative impact on the response time.

    -Log a PID...: You can log any given PID, using this submenu. Logs are made in text format. To stop the logs, just uncheck the corresponding menu. Note that by default frames of data which are transmitted are "truncated" to the usual 184 bytes size (only the payload of the TS, without the 4 bytes header). Active log is automatically closed if a channel switch occurs. The log files are stored either in the KeyPath2 directory if used, or in the directory of Hadu.

    -Systray: If checked, an icon for Hadu is displayed in Systray. Right-click on this icon shows an extract of this main menu. To stop it, uncheck the corresponding menu.

    -About...: Not much to say about it: version of the plugin and kind of DVB-API can be found here. You can also find some infos for special DVB softwares (i.e. "- TT xxxxxx" if the TT Trick is currently used, and "- MDROOT xxxxxx" for MultiDec).


    Options:
    --------
    In the Hadu.ini file (same location as the plugin), you can find the following options (values in brace [] are default values; none of these options are mandatory) :

    [General] Section

    -PluginActive ([1=Yes] or 0=No) : Same as "Active" option in the main menu.
    -KeyPath2: Files loaded and written by the plugin are stored in KeyPath2. If KeyPath2 is not used, only the directory of the plugin is used for loading and writing files.


    [Options] Section

    -UsePSITables ([1=Yes] or 0=No) : Same as "Use PSI Tables" option in the main menu. This flag is conditional for some other options.
    -SurveyPMT ([1=Yes] or 0=No) : Flag to indicate the plugin to "survey" the changes in the PMT. Only active if UsePSITables option is active. Its main use is to detect when a given channel change : non encrypted (for advertisements) to encrypted (in many pay-session channels for instance).
    -UsePATforPMT (1,2 or [0]) : Flag to indicate the plugin to obtain the PMT directly from the PAT and not from the DVB software. Only active if UsePSITables option is active. Necessary if PMT data given by the DVB software is erroneous or missing. 0=Auto, 1=Forced to Yes, 2=Forced to No. If Auto is selected, the PAT will be scanned only if the PMT data are unavailable (in case of a change for the PMT PID): but it takes several seconds more.
    -DontUpdViewer (1,2,3 or [0]) : Flag to don't update DVB software when ECM PID changes and/or Don't Send DCWs (Decoded Control Words). 0=Do both, 1=Don't update DVB software, 2=Don't send DCWs, 3=Don't update DVB software and Don't send DCWs. Note that if the TT Trick is used, the DCWs are not "really" send to the DVB software anyway but directly to the device.
    -UseDVBTime ([1=Yes] or 0=No) : Flag to use UTC time in DVB stream (currently unused). The time displayed in the Monitor window is the local time computed from the computer system time (if it's within parenthesis), or from the last UTC DVB time received (if authorized and available).
    -MaxECMPIDs (1-10. Default is [4]) : Maximum number of simultaneous ECM PIDs in use. Only one ECM PID can be active at the same time for one given server.
    -MaxConnections (1-32. Default is [4]): Maximum number of simultaneous connections (i.e. sockets). Only one connection can be active at the same time for one given server.
    -DisplayIPorURL ([1=IP Address] or 0=URL) : flag to display IP Address or URL in the Server list (Monitor window).
    -ECMTimeout (2-120 seconds. Default it [3]) : if no ECM is received during this time, Hadu will consider that a timeout has occurred, and will swith to another possible ECM PID. This option is mostly to be used with "wrapper" applications like SSSP Plug, .... In these cases, use a value higher than the ECM change frequency (12 or 14 seconds should be enough, for instance). Of course, increasing this value will slow the start decoging process, if a possible ECM PID is processed, while there is no stream for it; so use this option wisely.
    -MaxCAIDLoops (0-n. Default is [4]): Maximum number of loops for CAIDs and nodes for a channel before giving it. 0 means no limits.
    -LogMessages (1=Yes or [0=No]) : Same as "Log Messages" option in the main menu.
    -LogMessLevel (0-4. Default is [1]) : Level of informations to log into the text file called Hadu-Mes.log. The levels are cumulative: which means that level 0 stands for only level 0, level 1 stands for levels 0 and 1, and so on.
    -Systray (1=Yes or [0=No]): Same as "Systray" option in the main menu.


    [Specific] Section

    -DVBViewerAPI (1=Yes or [0=No]) : Flag to force the plugin to the DVBViewer 3.2 API Type, if DVBViewer version is 3.4 and above. 0=Auto, 1=Forced to 3.2 API Type.
    -DVBViewerAllAudio ([1=Yes] or 0=No) : Flag to decode all the Audio PIDs of the current channel, if more than one is present. 0=Only the current Audio PID, 1=All the Audio PIDs. Available only for DVBViewer version 3.4 and above, and if the "Use PSI Tables" option is active. This flag is also used to decode eventually TeleText/VideoText and Subtitles PIDs : 0=No, 1=Yes (if scrambled).
    -DVBViewerCSAStat (1=Yes or [0=No]) : Flag to display some CSA statistics in the Monitor window (below the PMT and CAT status line). 0=No statistics, 1=Display some statistics. The statistics concern the number of calls to the different CSA types, and the number of video/audio encrypted TS received into the last packet.
    -DVBViewerRecServ ([0=Auto], 1=Yes, 2=No) : Flag to communicate with HaduSer (if running). This program shows a resume of all the instances of Hadu running, with a few pieces of information. Its main purpose is to bypass the service restriction for the recent versions of Windows (i.e. Vista and Seven). For these versions of Windows, services are not allowed to interact with the Desktop; so, the Systray icon for Hadu won't be available when Hadu is used within the DVBViewer recording service. 0=Auto (only if Hadu is used within the DVBViewer recording service or DVBLink TVSource service), 1=Forced to Yes, 2=Forced to No. This option may be eventually be used for DVBViewer or any other DVB software (though the Systray option is much preferable for them).
    -DVBViewerIdleServ ([0=Auto], 1=Yes, 2=No) : Flag to start the server session(s) only when the service becomes active (i.e. when a record session is running within the DVBViewer recording service). 0=Auto (only if Hadu is used within the DVBViewer recording service), 1=Forced to Yes, 2=Forced to No. In this case, Hadu starts the server session(s) only when the recording session starts, and stops it/them when the recording session stops; note that it means you will probably miss a few seconds at the beginning of the recording session (i.e. the needed time to fully initialize the session before being able to communicate with the server).


    [Device] Section

    -MDRoot (1,2 or [0]) : Flag to analyze the root firmware in case of MultiDec, to determine automatically DescrCommand, XorEven and XordOdd (see hereafter). 0=Auto (for Multidec), 1=Forced to Yes, 2=Forced to No. This concerns only premium DVB Card "TT-compatible". Note the values for the following options prevails from the one determined by this option.
    -DescrCommand : 2 Bytes (4 hex chars)
    -XorEven : 8 Bytes (16 hex chars)
    -XorOdd : 8 Bytes (16 hex chars)
    Don't use them unless you know exactly what you are doing.
    -UseTT (1,2 or [0]) : Flag to use the TT Trick. 0=Auto (for WatchTVPro), 1=Forced to Yes, 2=Forced to No. This is only needed for DVB softwares which don't accept to send Direct DVB Commands. You need to have a premium DVB Card "TT-compatible" (like Technotrend DVB-S, Hauppauge Nexus-S, TechniSat SkyStar1) and a patched root firmware.


    Servers Sections:
    -----------------

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

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

    Syntaxe for the "Server" parameter :
    Server=Protocol:Server:Portunused):Username:Password

    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=Yes] or 0=No): 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),
    -TimeRecon ([0=Automatic], or 1-32 seconds): automatic value corresponds to the usual process for re-connections (restart each 1, then 2, then 4, then ... 32 seconds if no connection occurs). Other N values are used to always force re-connections each N seconds (this is not recommended, especially for low values).
    -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).
    -MaxHop ([0=None], or 1-N): nodes with a hop value superior to this limit are not used. A null value indicates no limits. Even if they are disabled with this rule, the concerned nodes are displayed into the list of nodes, but are not available.
    -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.
    -NoNodeCAID ([None]): list of Node/CAIDs excluded. Each entry may concern a whole server (i.e all nodes belonging to this server), or just only one CAID for this server (i.e. usually only one node of the server). Entries are separated using a comma character. Samples:
    NoNodeCAID=0102030405060708,1A1B1C1D1E1F2021 : these 2 servers won't be used.
    NoNodeCAID=0102030405060708:0100,1A1B1C1D1E1F2021: 500 : CAID 0100 won't be used for the first indicated server, and CAID 0500 won't be used for the second server.
    -CAIDTunnel ([None]): list of CAID tunneling entries, currently limited to Betacrypt<--->Nagra3 CAIDs. Each entries are separated by a comma, and data within an entry are separated with a colon character. Syntax for each entry :
    .CAID to use within ECMs stream (mandatory),
    .CAID to use when requesting the server (mandatory),
    .Provider (not used; null value),
    .SID concerned for the tunneling feature (optionnal). If this value is not filled or null, all the channels using the first CAID value are possibly concerned.
    Samples:
    CAIDTunnel=1833:1702 (all the channels)
    CAIDTunnel=1833:1702:0:81,1833:1702:0:82 (channel with SID=$0081 or $0082).
    -NoSID ([None]): list of SIDs not to processed. Entries are separated using a comma character. Sample:
    NoSID=0001,0002,0ABC
    -PrioGenRules (default is [Hop]): general rules for priority. All entries are separated by a comma. General rules always applied first, and concerned all the nodes. Currently, only the hop level and the emulator status are used. Possible values for the the first option: Hop, RHop, NHop. Possible values for the the second option: Emu, REmu, NEmu
    For all of them, xxxx means rule xxxx, Rxxxx means inversed rule for it, and Nxxxx means no rule for this option.
    .Hop: priority for nodes with lesser hop levels,
    .Emu: priority for emulator nodes (applied after the former rule).
    Here are a few samples (option values are not case sensitive):
    .PrioGenRules=NHop : no priority rule concerning hop values
    .PrioGenRules=REmu : emulator nodes used after non emulator nodes (but remember that the default value PrioGenRules=Hop is still applied for this sample)
    .PrioGenRules=Hop,NEmu: priority for nodes with lesser hop levels, and no rules for emulator nodes.
    -PrioCAIDProv ([None]): list of CAID/Providers for node priority. Syntax similar to the "CAIDPRov" option. The first CAID[/Provider] has priority over the second one, and so on; and all the CAID/Providers present into this list have priority over the other ones (i.e. those not present in the list).
    Samples:
    .PrioCAIDProv=0500,0100 : CAID 0500 has priority over CAID 0100, and above all other ones,
    .PrioCAIDProv=0100:006A : CAID 0100, provider 006A has priority over all CAID/Providers.
    Manual ECM PID selection modifies all these rules (see corresponding infos into the "Display" paragraph).

    So, for each new server to add with by default values, add these 2 lines in your .ini file, modifying the concerned data with your own ones:
    [Serv_MyServer]
    Server=CCCam:MyServer.com:12000:0:MyUsername:MyPas sword

    The above sample is corresponding to this C line for a CCCam server .cfg file:
    C MyServer.com 12000 MyUsername MyPassword


    Display:
    -------
    There are two kinds of display.


    The "Monitor" window (called from the main menu), used to display general and CAID informations for the channel, and general informations for the server(s).

    Double-clicking on an CAID row (i.e. ECM PID) will force the plugin to try to use this ECM PID entry. If it's not compatible for a given server, the following next compatible ECM PID entry will be used instead. It's important to note that node priorities are modified when this functionality is used: ECM PID selection becomes the first priority rule, and then only are applied all the other node priorities (i.e. general rules and CAID/provider for nodes). Change or re-select the corresponding channel will cancel the temporarily effects of the manual ECM PID selection; as for the "Cancel manual ECM PID selection" entry within the server menu.

    Double-clicking on an server will display the "Server Infos" window (see hereafter).

    Right-clicking on an server will display a menu to:
    -Start/Stop a server (if the server is active).
    -Activate/Deactivate a server. Same as the "Active" option in the configuration file,
    -Display the "Server Infos" window (as by double-clicking on an server),
    -Ask to retry all the possible ECMs again (if the server is started),
    -Cancel the temporarily effects of the manual ECM PID selection.

    The meanings for the main status of the servers are:
    -"Started." : connected and logged to the server; channel not encrypted,
    -"Stopped." : not connected to the server,
    -"Started. Send ECM..." : started and ECM request sent to the server,
    -"Started. Got DCWs." : started and positive result given back by the server,
    -"Started. (None)" : started, encrypted channel but no possible decoding using this server ; either because there is no corresponding CAID/provider for this channel, or because all the possible CAI/providers requested from the server have given negative results,
    "Stopped (already in use)." : not connected to the server. The same server (i.e. same IP address and same port) is already in use and connected.


    The "Server Infos" window (called from the server list in the "Monitor" window) is used to display informations for all the nodes of the server. Columns inside the nodes list:
    -S (for Status): indicates the status of the node. [Empty] = not available (because of the configuration restrictions -see "MaxHop" options-; or because it has been declared disconnected by the server). Furthermore, unavailable nodes are grayed. "....." = node available, but forced by the user to be ignored. " +" = node available. "**" = node available and currently in use.
    -Req/Got: numbers of ECM requests sent to the node, and of DCWs received from it.
    -Hop, CAID and Providers: common informations for a node.
    -DCWs (ms): last time response for DCW received from the server for the node.
    -Neg (ms): last time response for negative answer received from the server for the node (i.e. 'No decoding' messages). Both for DCWs and Negative time responses, there is a first latency for multiple ...... ECMs (if several ChIDs are used).
    -Timeout: number of timeouts for ECM requests.
    -Discon: number of disconnections (and eventual re-connections).
    -Index and Node ID: identification of the node.

    Right-clicking on an node will display a menu to:
    -toggle its state between "to use" and "to ignore" (if the node is available).
    -enable or disable the selected CAID for the selected server. This may correspond to one or several nodes for the concerned server,
    -enable or disable all the CAIDs for the selected server.
    Depending of the current status for the concerned node/CAID/server, these different entries for this menu are available or not. Enable/Disable a CAID or all CAIDs are equivalent to the "NoNodeCAID" option into Hadu.ini.

    In the nodes list, providers included in parenthesis (e.g. "(0000)") or CAIDs included in parenthesis, means that these providers or CAIDs can't be used.

    When they are included into brackets (e.g. "[0500 123450 6789A0]") or into braces (e.g. "{0604 00000}"), the corresponding node is no more connected or excluded according to various options present in the .ini file; in these 2 last cases, the node status can't be modified (by double-clicking on it).

    The meanings for the main status of the nodes are:
    -[Nothing] : node can't neither be used nor having its status modified,
    -"....." : node has been its status set to "ignore" by the user,
    -" +" : node can be used,
    -"**" : node currently in use.

    Data in the "Server Infos" window are refreshed each 4 seconds. You can force an extra refresh with the "Refresh" button.

    The clipboard button serves to copy data of the window into the clipboard (text format).

    At the bottom of the window, the total numbers of nodes and CAID/providers are displayed: the first number of both of them indicates the whole total number, will the second number indicates the total number of available items.


    Limits:
    -------
    Here are the main current limits applied into the plugin:
    -Maximum number of CCCam servers (active or not active): 64
    -Maximum number of active CCCam servers : 6
    -Maximum number of nodes per server : 2048
    -Maximum number of providers per nodes : 16
    -Maximum number of hops per node : 8 (though more than 3 or 4 is probably useless)
    -Maximum number of CAID/providers entries into to "CAIDProv" and "NoCAIDProv" options : 32
    -Maximum number of nodes/CAID entries into to "NoNodeCAID" option : 32
    -Maximum number of CAID/CAID/provider/SIDs entries into to "CAIDTunnel" option : 32
    -Maximum number of SIDs entries into to "NoSID" option : 64
    -Maximum length size for server name and URL/IP address : 128
    -Maximum length size for user and password: 20 for the user, 128 for the password
    -Maximum number of CAID/providers entries into to "PrioCAIDProv" option : 32.

    To not overload CCCam servers, it's not allowed within the plugin to have 2 active connections with the same server at the same time. Same server meaning here: same IP address and same port.



    (Many thanks to the person who has kindly provided me a CCCam server for my tests).

    Remote

 

 

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Back to Top