freezing picture on c/s

[gavw1]

My TM9100 Linux freezes constantly. I have been told this is because my broadband ping is too high. Is this true? if so can the settings on the TM9100 be altered to solve this problem

 

[Analoguesat]

Explain better please - your post doesnt make much sense. Which channels - free to air, or are you on a card share.

 

[gavw1]

sorry meant to say cardshare.

 

[Analoguesat]

Find a better card share. Theres a slow link in the chain somewhere - remember the card you are reading the keys from could be three or four hops down the chain, and the box isnt updating fast enough when the keys change.

 

[gavw1]

Changed my image and it seems a bit better. Was wondering if i use CCcam +news will this make any difference

 

[Analoguesat]

Try it and see. Personally I doubt it.....

 

[dasteelman]

1) which encryption are you having the 'freezing' issues with? if its ND$, this is a common problem, cccam emu helps and the card can be overclocked.

2) like analoguesat said...high ping from the server is a problem.

3) anything after 1 hop is an issue.

also tell us what EMU you are using.

 

[gavw1]

Runnng UR14 with CCcam 2.0.9. Considering changing to edg nemisis 4.4. Anything other that FTA freezes.

 

[compufunk]

Runnng UR14 with CCcam 2.0.9. Considering changing to edg nemisis 4.4. Anything other that FTA freezes.

Changing image wont help because thats not where the problem lies. The problem is with the hop distance and/or the speed of your connection to your peers.

It doesn't matter if you have a 50mg broadband connection, if your peers only have a 256K upload speed. Then you are limited to a 256k connection to those peers.

 

[Analoguesat]

I told you what the likely answer was back in post #4.

Find a better card share. Theres a slow link in the chain somewhere - remember the card you are reading the keys from could be three or four hops down the chain, and the box isnt updating fast enough when the keys change.

 

[A nonymous]

You need to get the person you are sharing from to set your lines so you don't receive anything above hop2, Anything after hop2 is too problematic after that.

Try loading cccaminfo.php onto your pc which will allow you to monitor what is happening on your box, it was also allow you see how fast the ping of the client you are taking the card from.

Exactly which provider are you having problems with? I'm guessing its Sky Italia as thats usually found to be the most problematic one out there.

:-beer

Nano

 

[compufunk]

You need to get the person you are sharing from to set your lines so you don't receive anything above hop2,

Have I missed something?

There is no need to bother your peers and ask them to block cards beyond hopWhatever. You can set those preferences yourself. You can ignore cards beyond any hops you like as follows.

C: server.com 12000 username password {0:0:[B]2[/B]}

The above ignores any cards past hop 2 from server.com.

Just change the number in bold to whatever you like.

 

[A nonymous]

I know how to set lines up on cccam, gbox, mbox, mgcamd, camd3, newcs where would you like me to stop

In past experience setting the last figure to 2 on cccam makes no difference at all, you still receive hop3 cards if thats what your share has set for you.

I now what your saying should work but i've found previously that it doesn't

Asking your peers to set your permissions lower is the only way to guarantee it :toke:

:-beer

Nano

 

[compufunk]

In past experience setting the last figure to 2 on cccam makes no difference at all, you still receive hop3 cards if thats what your share has set for you.

How could you tell? I',m always interested in improving things any way I can.

 

[compufunk]

In past experience setting the last figure to 2 on cccam makes no difference at all, you still receive hop3 cards if thats what your share has set for you.

Having 2 Dreamboxes to play with at the minute, I thought I'd test this out.

I set the server to share up to hop3 and the client to only request hop1.

Anything past hop1 was not available to the client.

The server was running CCcam 2.11, the client was running CCcam 2.2.

If what you describe was a problem with older versions of CCcam, then it seems to have been rectified now.

C

PS: CCcam 2.2 is now available to Darkstar2 users via the yellow button.

 

[tomthebomb1968]

hope this clearsthings up
C: server.com 12000 username password { 0:0:2 } will not stop hops past 2
C: server.com 12000 username password no { 0:0:2 } will stop hops at 2
C: server.com 12000 username password yes { 0:0:2 } will stop hops at 2

The space between the { and the 0 and the 2 and the } is required as is the use of yes or no


taken from cccam.cfg #note: if {} limits are added, <wantemus> cannot be omitted. Use either yes or no.

 

[tomthebomb1968]

sorry, the post above appeared twice

 

[JTA]

that's theory, now reality - I have CCcam 2.11 with the following line :
C: server.com 12000 username password no { 961:0:1 }

this should stop all Sky UK shares which are more than 1 hop away, as this becomes unusable.
When switching channels, CCcam selects my local NDS card, or a card which is 1 hop away, sure thing. Until I get an image-freeze, which may occur a few times a day (don't know why, but it allways seem to happen on the hour). CCcam then happily uses a card 2 hops away, giving freezes every few minutes ! I have to switch channels to have Cccam select my local card again !

 

[compufunk]

I'll check again this evening, but when I tested, I did not receive any sky cards from past hop1. (I didnt check any other providers). I'll post back later.

 

[compufunk]

I have no Idea whats going on with your CCcam JTA.

I just did some testing. Here are the results

The server allows 3 hops down.

Clients Cline is.....

C: myserver.home.net 12000 user pass no {0:0:1}

I dont have a local card in my server, and about 5 cards at hop1.

I couldn't clear anything from any provider @ any hops with the above cline.

See attached images.
View attachment 20257

View attachment 20258