incubusCamd seems very slow (sometimes more than 10sec zapping compared with 2 sec with all other emus) and some channels of my TNTsat (canal+) card are not opened (while opened with all other emus). (I had exactly the same problems with v0.99)
But maybe it is only a problem of config file (I confess that I didn't take time to read all the post concerning incubusCamd since first release
Its been running here for more then 1 hour and it is Very stable.
and yes there is still this question for me too! why incubuscamd takes sooooo long to open
a channel when other cam open it instantaneously!
I asked the question with an example here but never got any answer!
[url=http://www.denktenk.com/modules/newbb ... p?topic_id=11315&forum=63]
http://www.denktenk.com/modules/newbb ... p?topic_id=11315&forum=63[/url]
try to add a line on your incubus.prio
For example:
P: 0500:032000
OK I put this in incubusCamd.prio:
P: 0500:030B00 # TNTSAT
P: 0100:00006D #TELESAT
And indeed zapping is faster for my télésat card but no speed improvement for TNTSAT excpt that now it opens all the channels.
how do I configure incubuscamd to work with softcam.key? I tried with...
[Prov:000000:CaID:0000]
decoder_type=0
check_priority=cs,,
cs_protocol_order=newcamd,,,,,,
process_emms_on_cs_mode=0
process_emm_g=0
process_emm_s=0
process_emm_u=0
seca3_handler=0
chid=-1
...but doen't work. Do I have to specify decoder_type? In earlier versions there was this option, but now using v1.00 I don't know.
2) incubuscamd 1.00 stops when pid is changed when change between national to regional or regional to national broadcasting on swedish national channels (SVT1 and SVT2). Is this a known bug? Some settings to make?
Besides this, new incubusCamd works great on both DGS and E2 images. Fast zapping, at least in my environment.
i think you have the same bug as me with our provider when they change stream for commercials.
2) incubuscamd 1.00 stops when pid is changed when change between national to regional or regional to national broadcasting on swedish national channels (SVT1 and SVT2). Is this a known bug? Some settings to make?
If you want to use only the internal emu:
[Prov:000000:CaID:0000]
check_priority=emu
cs_protocol_order=
process_emms_on_cs_mode=0
process_emm_g=0
process_emm_s=0
process_emm_u=0
seca3_handler=0
chid=-1
max_check_uphops=5
If you want to use emu and with no valid decrypted provider to use card share protocols (for example now i will give priority to cccam and then to newcamd)
[Prov:000000:CaID:0000]
check_priority=emu,cs
cs_protocol_order=cccam, newcamd
process_emms_on_cs_mode=0
process_emm_g=0
process_emm_s=0
process_emm_u=0
seca3_handler=0
chid=-1
max_check_uphops=5
If you want to give cs priority and then emu
[Prov:000000:CaID:0000]
check_priority=cs,emu
cs_protocol_order=cccam,newcamd
process_emms_on_cs_mode=0
process_emm_g=0
process_emm_s=0
process_emm_u=0
seca3_handler=0
chid=-1
max_check_uphops=5
It's easy... you have simply to read the config file distributed with incubusCamd tar.gz
It's all explained there. You, jannek999, used old information about old config and mixed it with the new one eheheh
Bitwise i think the internal emu is not up to date to last public emus and do not forget to check how to write keys on the SoftCam.keys file. (incubusCamd uses a generic standard used also on the vdr-sc emu or it's almost the same)
Change to this
check_priority=cs,cs,emu
Also delete "decoder_type=0" it is not mentioned in the new .conf example any more.
EMM on conax is still not working. It's the same situation as before, except that it also starts the EMM-S processor now.
cam[di:1]: Initializing EMM-S processor...
cam[di:1]: Waiting for card-server to become ready...
cam[di:1]: EMM-S processor started...
Edit:
There might be one thing I have forgotten to report. This line comes before starting the EMM processors:
cam[di:1]: Error setting CA PID...
אינדקס
