thx :respect-051:
thx :respect-051:
Hmmm, very nice, there no no more room voor dutch, because the 'D' for dutch is taken, also the 'N' for Nederlands LOL.
But my question is, is there a short manual, how to do the bridge with 1 of the EMU's and the internal cardreader...
Me, myself has the dutch seca3.
So if some1 can explain it...
please
thanx for the great job....
Arie
after testing and testing this....my conclusion is that
cccam 2.1.1 + CCC 0.2
is a better solution.
Yes, but not for those who don't want to loose one hop...
cu
KJ
For Who hasn't got Payserver cos this way not works for who has Payserver...Quote:
Originally Posted by hfmls
on the other side this First release needs some improvements for sure....
I do agree with you,Client works much better,,,
yes but this is not a day to day EMU to use. not stable, many glitches.
but congratulations to mower for this treat :)
i don't think this can be more improved, am i wrong? because BIN file is the same.
i think CCC improvements would be better. and much much more stable in azbox hd.
anyway. one thing or another. would be great :)
MBOX would be better :P with bugs fixed, update emm and nagra 3 direct.
Don't forget that some issues are Firmware related and mower is not the only player here... Opensat should also fix some stuff... Like PVR functionality (recording) and Zap speed on channel change.
Yes it can be improved if problems came from the dvbapi_module... don't forget that it is this module that link CCcam_2.1.1 with the Azbox hardware... so there is probably some improvement possibilities in this part.Quote:
Originally Posted by hfmls
Pr2
Agree with both you Guys
We must Try and see how E2 will perform on this box...
The structure of the current Fw will not allow to make more faster Zap speed hence Box working as a two part which is TV and Menu ...
you are sending command from menu part to Tv part and Tv part process your command =Zap ...Thats why zap speed is a bit slow Which I believe effect the cccam Performance...
Or
Cccam uses most of the available memory and that cause the trouble ,We may solve it with the Swap file etc...
Good Release once again but needs an update
Best regards
Please OpenSat do it. They is in advantage of all. CCcam is so much popular. most people asks about whether CCcam is working OK before they buy the box.Quote:
Originally Posted by pr2
what you want to make friend.Quote:
Originally Posted by humaxarie
DreamBox have to put the server?
newcs can put in and read the card azbox
with newcs and Radegast NewCamD will have these two options are accepted CCcam
Memory is not the problem... firmware not being released to fix stuff is...Quote:
Originally Posted by iko
Something else to try to fix issues because of bad zapping speed or time to decode... you can disable autolearning features from CCcam.
So start CCcam 2.1.1 with following line to disable autolearning "-l" this should help issues with channels not being open... let me know if it helps and we get it working nicer now.
Usage options are:Quote:
LD_PRELOAD=/EMU/lib/libdvbapi.so /EMU/lib/ld.so.1 --library-path /EMU/lib/ /EMU/lib/CCcam.mipsel -dlv -C /EMU/lib/CCcam.cfg &
Quote:
usage: CCcam [-d] [-C <configfile>]
-d run in the foreground (implies -v and -q)
-v be verbose
-q don't use syslog (use on old systems)
-C <configfile> use <configfile> instead of default (/var/etc/CCcam.cfg)
-f filter on specific demux data (saves some CPU,
but dreambox drivers might not like this too much)
-n show network packets
-s disable server
-t show timing
-l disable self-learning capabilities
So what is the best solution if I have 2 "external server" lines? This proggy here or which way to have chans "open"?
I installed this here today and I have both C-Lines connect the server. However the Chans stay dark.
What I did:
EMU was empty... I FTP'ed cccam to the root... chmod...installed as advised, edited the cfg file and chmod it 755. After a reboot the server is connected but nothing happens. In the plugin menu (on the TV) I see OpenXCAS and lib. After I tried the installation again, I dont see anything in the menu. I also tried the "-l" way mentioned above.
I used 0.2 cccam so far (only supports 1 c line) and it worked.
Any suggestions?
I'm well aware this is a great step forward and am very grateful to all who helped it happen and it really has a lot of benefits over CCCam 0.2 but at the end of the day it's not as good as it when it comes to clearing channels, question is, where do we (they) go from here?
Is there any point pursuing this version of CCcam, can The Ripper improve his 'interceptor' module (as DJBlu calls it) to improve the overall running of the program or are there certain tweaks that he may may be able to do on CCcam itself?
Or could improvements by Opensat in the firmware help the proper CCcam to run?
Or will he go back to developing CCcam 0.2 into 0.3 etc?
Just curious...
Quote:
Originally Posted by humaxarie
I've changed the menu for numbers, the dame and add new languages :coolgleamA:
The only way things are going to change is if the DVB API changes on the AZBox.Quote:
Originally Posted by gtg60
I wouldn't like to go down the route of CCC 0.3, 0.4. Because when and I mean when CCcam change the encryption it means The_Ripper has to spend x amounts of hours working out the new methods.
They can implement the Linux TV API with the Gui they have, and to be honest it would save so much time. Then they could concentrate on other items.
Just my two pence worth.
well if they could implement that, that would be cool...
but it has to have many many improvements. :) right now it's not a day to day alternative. many glitches and freezes. :)
BUT IT'S WORKING :)
go on and improve dvb api the_ripper
:)
He can't it is OpenSat that have to do this as they haven't released the drivers for the chipset or any component on the AZBox.Quote:
Originally Posted by hfmls
well they will have to do it sometime in the future! otherwise they will not evolve!!