Jump to content

Unicast still problem switching channels


spaltzer

Recommended Posts

Hi,

 

The release version (3.5) has the same problem that I wrote about in the beta-forum here:

 

http://www.DVBViewer.com/forum/index.php?showtopic=13097

 

This is a real issue for me since I live in sweden where we on DVB-T have 4 FTA channels and on DVB-C which I use we only have scrambled channels. So if you live in sweden you basically need to watch encrypted channels. It sucks I know, but that's the way it is.

 

Again, the bug is that with a remote client it is not possible to change between encrypted channels within the same transpoder. This means that if I want to switch between channels within the same transponder I first need to switch to a channel in a different transponder and then switch back to the channel I wanted.

 

I just want to know if you are looking into this?

 

In Regards,

Magnus

Edited by spaltzer
Link to comment
  • 1 month later...
  • 4 weeks later...
  • 4 weeks later...
  • 1 month later...

Maybe the thread should be closed. Many new versions of the DVBViewer have been released since. I've just tested the latest server and had no problems to switch at the client between encrypted channels.

 

server 3.5.0.4 (06.10.2006) connected to a firedtv-s, premiere S01/ freecam

 

:):):)

Link to comment

Thanks for replying Derrick!

 

Very hopefully I just downloaded 3.5.0.5 and tested it but unfortuanly it doesn't work for me. I have previosly tried 3.5.0.2 and 3.5 with the same results.

 

Just to clarify: are you switching between encrypted channels within the same transponder? Switching between encrypted channels that are in different transponders work fine for me but not when the channels are in the same transponder.

 

The key thing seem to be that when DVBServer in the log says "Add Tuner" it works, if it does not add the tuner (as in the from- and to-channels are in the same transponder) and just does the delpid and addpid i get no picture and no sound and i get the * after the channel name in the lower left of the application window.

 

Below are some excerpts from the debug tab of dvbserver 3.5.0.5 for a succesfull switch and an unsuccesfull switch.

 

This is a switch from one encrypted channel in one transponder to another encrypted channel in another transponder (succesfull switch):

 

2006-10-20 23:36:33 Add Tuner

2006-10-20 23:36:33 Frequency:378000

2006-10-20 23:36:33 Symbolrate:6875

2006-10-20 23:36:33 LNB:0

2006-10-20 23:36:33 Selection:0

2006-10-20 23:36:33 Polarity:3

2006-10-20 23:36:34 SO_SNDBUF: 4294967295

2006-10-20 23:36:34 Addpid: 0

2006-10-20 23:36:34 Addpid: 18

2006-10-20 23:36:34 Addpid: 4103

2006-10-20 23:36:34 Addpid: 4359

2006-10-20 23:36:34 Addpid: 263

 

This is a switch from one encrypted channel (the channel tuned in the log above) to another encrypted channel in the same transponder (unsuccesfull switch):

 

2006-10-20 23:40:13 DelPid: 0

2006-10-20 23:40:13 DelPid: 18

2006-10-20 23:40:13 DelPid: 4103

2006-10-20 23:40:13 DelPid: 4359

2006-10-20 23:40:13 DelPid: 263

2006-10-20 23:40:13 Addpid: 0

2006-10-20 23:40:13 Addpid: 18

2006-10-20 23:40:13 Addpid: 4105

2006-10-20 23:40:13 Addpid: 4361

2006-10-20 23:40:13 Addpid: 265

2006-10-20 23:40:13 Addpid: 7945

 

I'm using a FireDTV-C with Conax coding.

 

Any help on resolving this matter would be greatly appreciated.

 

Thanks, Mussla

Edited by spaltzer
Link to comment

dunno if I can help you.. could you start transedit -> analyze -> transponder -> save as xml and then attach this file?

 

ps.

my excuses, I have the same problem. Switching between channels from the same mux doesn't work. But there are more weird things.. ..pids are added and deleted at very high speed. These pids are ecms but they are in my case the wrong pids for a different ca_id. Sorry m8, the CI part still seems rather buggy.. :)

 

 

Link to comment

I'm attaching the transponder xml-dump. It's rather large so FireFox might pause to "think" for a while while it opens it. The interesting things should be right at the top, i.e. the channels involved that I showed in the log.

 

If there's anything more that could be of use to track this down I'm happy to collect it.

 

In a way I'm glad to hear that we are at least two having this problem since it increases the chances that it's nothing weird potentially hard-to-track going on in our respective setups :)

 

EDIT: The attachment is 265kb in size and my maximum is 256kb. Need to find some place to host it.

Edited by spaltzer
Link to comment

@Lars, you're right :) ..the adds/dels are not caused by the server. But still no zapping within the same transponder. The CI keeps the data from the 1st channel. Switching to other encrypted channels of the same type in the same mux results in no data. Switching back to the initial service brings back the colour :) This loop only can be broken after switching to another mux which results in a tuning command. @spaltzer's description of the problem was absolutely right.

 

@spaltzer, probably we don't need the xml anymore because the problem ist not related to cable or to a certain CAS. Conax, BC/Aladin, Seca2 all show the same behaviour. Though I´d like to check your xml, because I can't receive this. Most of the data of the xml come from epg. If you uncheck the EIT in the settings of the analyzer part of transedit, the file will be much smaller :)

Link to comment

I removed the EPG-data but for some reason this stream is too large anyway so I'm hosting it Here.

 

Thanks for looking into this and please don't hesitate to ask me for more information should it be needed.

 

Spaltzer :)

 

EDIT: I'm attaching a support.zip as well.

support.zip

Edited by spaltzer
Link to comment

I'm very sorry to have to say this... but I downloaded version 3.0.5.0 with the fix for this problem and it doesn't work for me. :) It looks like the same thing is happening with this version as the previous ones.

 

Yes, I did check the "Have CI" option. (If I don't I get no picture at all).

 

Im attaching a support for the client and a support for the server and the server log.

 

Hopefully someone can figure out if I'm doing something wrong, or if something needs to be fixed.

 

The logs should show a client connecting, tuning a channel and recieveing picture:

 

2006-10-25 20:16:17 SO_SNDBUF: 4294967295

2006-10-25 20:16:17 Add Tuner

2006-10-25 20:16:17 Frequency:290000

2006-10-25 20:16:17 Symbolrate:6875

2006-10-25 20:16:17 LNB:0

2006-10-25 20:16:17 Selection:0

2006-10-25 20:16:17 Polarity:3

2006-10-25 20:16:17 Addpid: 18

2006-10-25 20:16:17 SO_SNDBUF: 4294967295

2006-10-25 20:16:18 Addpid: 0

2006-10-25 20:16:18 Addpid: 4103

2006-10-25 20:16:18 Addpid: 4615

2006-10-25 20:16:18 Addpid: 263

2006-10-25 20:16:18 Addpid: 7943

 

Then tuning another channel on the same transponder and getting 'no data':

 

2006-10-25 20:16:25 DelPid: 0

2006-10-25 20:16:25 DelPid: 4103

2006-10-25 20:16:25 DelPid: 4615

2006-10-25 20:16:25 DelPid: 263

2006-10-25 20:16:25 DelPid: 7943

2006-10-25 20:16:25 Addpid: 0

2006-10-25 20:16:25 Addpid: 4102

2006-10-25 20:16:25 Addpid: 4614

2006-10-25 20:16:25 Addpid: 262

2006-10-25 20:16:25 Addpid: 7942

 

Then tuning another channel in a different transponder and recieveing picture:

 

2006-10-25 20:16:36 DelPid: 0

2006-10-25 20:16:36 DelPid: 4102

2006-10-25 20:16:36 DelPid: 4614

2006-10-25 20:16:36 DelPid: 262

2006-10-25 20:16:36 DelPid: 7942

2006-10-25 20:16:36 Add Tuner

2006-10-25 20:16:36 Frequency:298000

2006-10-25 20:16:36 Symbolrate:6875

2006-10-25 20:16:36 LNB:0

2006-10-25 20:16:36 Selection:0

2006-10-25 20:16:36 Polarity:3

2006-10-25 20:16:36 SO_SNDBUF: 4294967295

2006-10-25 20:16:37 Addpid: 0

2006-10-25 20:16:37 Addpid: 4104

2006-10-25 20:16:37 Addpid: 4360

2006-10-25 20:16:37 Addpid: 264

2006-10-25 20:16:37 Addpid: 7944

 

Let me know if you need more information.

 

In Regards,

Spaltzer

ServerSupport.zip

server.log

ClientSupport.zip

Link to comment

@spaltzer, you're absolutely right. The latest beta version from the member's area does not contain the fix or something else is wrong. I had a test version which worked with channels from the same mux. I've just checked the official beta and it sucked again. Poor quality control :)

Link to comment

Thanks for testing this and for letting me know your findings Derrick! Much appreciated!

 

I was tearing my hair off trying to understand why it didn't work for me so I can stop that now while I have some left! :)

 

And thanks to the developers for making a fix for the bug! Much appreciated!

 

I have my hopes the fix will make it into the next beta version :disgust:

Edited by spaltzer
Link to comment
The problem is hardware-related. You have do update yours firedtv firmware to the newest version.

nonsense, otherwise switching between channels from the same mux wouldn't work in direct mode either. Just wait for the fix..

Link to comment
  • 3 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...