c'è una sezione apposita in hadu.ini
[Specific]
DVBViewerAPI=0
DVBViewerAllAudio=1
DVBViewerCSAStat=0
DVBViewerRecServ=0
DVBViewerIdleServ=0
DVBViewerEncrServ=0
Purtroppo avevo letto un msg in merito su DVBN ma al momento non è raggiungibile
cmq in rete si trova la spiegazione delle opzioni
[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).
-DVBViewerEncrServ (1,2=Yes or [0=No]): Flag to start the server session(s) when the service becomes active (see DVBViewerIdleServ option), and only when the recorded channel is encrypted. If DVBViewerEncrServ=2, it also stops the server session(s) if the channel becomes no more encrypted. The former comment concerning the needed extra-time before being able to decrypt the channel still applies here (it will even be a bit longer).
Inviato: mer feb 22, 2012 1:41 pm