Hadu, CCCam client plugin voor Windows

[Gast zzzzzzz]

In de handleiding staat dat je maar één keer naar een server kunt connecteren.

Dat vind ik nu heel spijtig, want Hadu werkt bij mij voortreffelijk.

Voor een goede PVR moet je toch op zijn minst 4 keer naar een server kunnen connecteren, desnoods met een andere login.

 

Kent er iemand een manier om die ingebouwde beperking te omzeilen ?

De enige die ik kan bedenken is via een andere CCcam server die dan met de mijne gelinkt is.

[the_knarf]

@ZZZZZZZ,

 

je mag maar 1 keer met het zelfde account connecteren op de server, maar je kunt wel meerdere connecties maken.

Ik heb aan de server kant 12 F regels toegevoegd.

Het ligt aan de PVR software die je gebruikt hoe je dit aan de client kant moet inrichten.

[Gast zzzzzzz]

Ok, zal dat eens testen, vond het al vreemd dat je maar één keer zou kunnen connecteren naar een server.

 

[Tonskidutch]

zo nu even van de ene naar de andere overgestapt...

met hadu werkt het na een enkele herstart nu prima

 

progdvb 6.20.3

hadu 0.105 (die andere moet ik ook nog eens zoeken en testen)

 

(vind dat het wel heel simpel en eenvoudig werkt 20 minuten op XP met skystar2 en BDA drivers)

 

ben enkel nog op zoek naar een manier om favorieten aan te maken in de channellist

 

ciao

[Tonskidutch]

o ja voor de hadu CCcam

de ini aanpassen

 

Code:

[General]PluginActive=1KeyPath2=[Options]UsePSITables=1SurveyPMT=1UsePATforPMT=0DontUpdViewer=0UseDVBTime=1MaxECMPIDs=2MaxConnections=4DisplayIPorURL=1ECMTimeOut=3LogMessages=0LogMessLevel=1[specific]DVBViewerAPI=0DVBViewerAllAudio=1DVBViewerCSAStat=0[Device]MDRoot=0DescrCommand=XorEven=XorOdd=UseTT=0;;   Sample for a CCCam server;   -------------------------;; Server declaration (mandatory) :;         [serv_whateveryouwishforyourservername]; Mandatory parameter : ;         Server=Protocol:Server:Port:(unused):Username:Password;               Sample: Server=CCCam:MyServer.com:12000:0:MyUsername:MyPassword; Optional parameters :;         Active=        ; ([1] or 0);         TimeOut=       ; (0=None, or 3-7 seconds. Default is [5] seconds);         PadTime=       ; ([0=None], or (TimeOut+2)-N seconds);         WantEmus=      ; (0=No or [1=Yes]);         MaxHop=        ; ([0=None], or 1-N);         CAIDProv=      ; [None] or 32 max entries of CAID/Providers;         NoCAIDProv=    ; [None] or 32 max entries of CAID/Providers;[serv_aa]Server=CCCam:192.168.179.110:12000:0:ton:skystarActive=1-----------------------------------------------------[serv_bb]Server=CCCam:192.168.179.111:12000:0:tonski:badkamerActive=1-----------------------------------------------------[serv_cc]Server=CCCam:192.168.179.112:12000:0:tonskidutch:slaapkamerActive=1

 

mooi en opnemen gaat ook

 

ciao

[Tonskidutch]

och heden er is al een die veel veel nieuwer is 0.116 (4 augustus 2009)

en wellicht heb ik nog niet lang genoeg gezocht

 

Code:

Hadu CCCam client Plugin for windowsAugust 4, 2009 – 23:28While I’m testing my new satellite setup for a HTPC that has yet to be build I found a really usefull DVB plugin everybody should hear about. Finally a CCCam client for windows is available. First tests were very succesfull for me. Version Beta 0.1.0.0 was released June 23, 2009 this was a initial Beta Test release. The current version is 0.116. Find latest release and changelogs here.Download Hadu 0.116Hadu 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 subdirectoryCaution: 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 wordSample: 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.

 

dat werkt wel goed zeg... naar mijn dreambox connecten en hoppa beeld

 

ciao

[Tonskidutch]

u is weer bedankt,

[andre123]

Deze is van 25-10 0119

 

http://fs04n4.sendspace.com/dl/d7645af7c...eta%200.119.zip

 

_________________________

HTPC met DvbViewer en flycccam op windows vista ultimate 64bit

Visiosat Big BiSat - vantage 8/1 - 8 x Alps lnb

[Tonskidutch]

Releases:

---------

 

-Version Beta 0.1.1.9 : October 25, 2009 Beta Test release.

 

 

Changelog:

----------

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 1,

-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.

 

stond in de bijlage text...

 

wil men misschien weten voorafgaand aan downloaden..

 

ciao

[Tonskidutch]

misschien even een update van het knutselen

zoals boven vermeld werk ik dus met progdvb

 

stom stom stom... door de (aangeboden 20 dagen elecard) mpegviewer mee te installeren in progdvb, is mijn elecard registry verkloot

met betrekking tot mijn legale elecard die ik al had lopen is nu ook daar de licentie afgelopen

(ik had dat in het verleden ook al eens, @damned)

 

lastig daar de support van elecard wel wat gammel is.

 

maar goed we stoeien en knutselen verder.

 

ciao

 

 

[Ou-Tannu]

ah weer een nieuwe

 

[gielvandiek]

hoi allemaal ik begrijp er niks van.

Gisteren een SkyStar hd2 binnen gekregen, voor de HD kanalen dacht ik. Computer opnieuw geinstalleerd kaart erin drivers geintalleerd DVB vieuwer er opgezet Hadu ini hadu dll in de dir

C:ProgramFiles\DVBViewer\plugins gezet.En heb dit in de hadu ini gezet

server=cccam:192.168.1.150:12000:0:comp kamer

comp kamer is de fline in de server

Ik hoop dat iemand mijn kan helpen zou wel iets stoms hebben gedaan. { kan natuurlijk wel gewwon fta kanalen ontvangen }

bij voorbaat dank

 

Groeten Giel

[the_knarf]

Ik doe het even uit mijn hoofd, omdat ik zelf HADU niet meer gebruik.

 

volgens mij moet je regel zijn:

server=cccam:SERV_192.168.1.150:12000:0:comp kamer

 

en ik vermoed dat je de naam in moet vullen i.p.v. ipadres,

Test het even.

 

gr, Frank

 

[Tonskidutch]

neen die regel was bijna goed...

Citaat:

server=cccam:SERV_192.168.1.150:12000:0:comp kamer

wordt

server=cccam:SERV_192.168.1.150:12000:0:comp:kamer

 

der moet enkel dit boven staan

[serv_dreambox] tussen haakies en een naam achter _

iedere naam die je wenst

 

maar let op de nieuwste hadu moet je even die rooie aanpassen

 

[specific]

DVBViewerAPI=0

DVBViewerAllAudio=1

DVBViewerCSAStat=0

DVBViewerRecServ=2

DVBViewerIdleServ=0

 

ciao

[gielvandiek]

Hoi bedankt voor jullie snele reactie, maar het werkt nog steed niet. Ik hoop dat ik dit zo mag doen, want misschien zie ik iets over het hoofd. Dit is toch het enige wat je moet doen? Ik heb trouwens een debian server

[General]

PluginActive=1

KeyPath2=

 

[Options]

UsePSITables=1

SurveyPMT=1

UsePATforPMT=0

DontUpdViewer=0

UseDVBTime=1

MaxECMPIDs=4

MaxConnections=4

DisplayIPorURL=1

ECMTimeout=3

MaxCAIDLoops=4

LogMessages=0

LogMessLevel=1

Systray=0

 

[specific]

DVBViewerAPI=0

DVBViewerAllAudio=1

DVBViewerCSAStat=0

DVBViewerRecServ=2

DVBViewerIdleServ=0

 

[Device]

MDRoot=0

DescrCommand=

XorEven=

XorOdd=

UseTT=0

 

;

; Sample for a CCCam server

; -------------------------

;

; Server declaration (mandatory) :

; [serv_whateveryouwishforyourservername]

; Mandatory parameter :

; Server=Protocol:Server:Port:(unused):Username:Password

; Sample: Server=CCCam:MyServer.com:12000:0:MyUsername:MyPassword

; Optional parameters :

; Active= ; [1] or 0

; Timeout= ; 0=None, or 3-7 seconds. Default is [5] seconds

; PadTime= ; [0=None], or (Timeout+2)-N seconds

; TimeRecon= ; [0=Automatic], or 1-32 seconds

; WantEmus= ; 0=No or [1=Yes]

; MaxHop= ; [0=None], or 1-N

; CAIDProv= ; [None] or 32 max entries of CAID/Providers

; NoCAIDProv= ; [None] or 32 max entries of CAID/Providers

; NoNodeCAID= ; [None] or 32 max entries of Node/CAIDs

; CAIDTunnel= ; [None] or 32 max entries of CAID/CAID/Provider/SIDs

; NoSID= ; [None] or 64 max entries of SIDs

; PrioGenRules= ; 1 or several general rules for priority. Default is [HOP]

; PrioCAIDProv= ; [None] or 32 max entries of CAID/Providers for priority

;

[serv_debian]

server=cccam:SERV_192.168.1.150:12000:0:comp:kamer

 

Groeten Giel