Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Yaobing]

I found a dumb error I made.

Please try this DLL.  Download the zipped file, unzip it and copy the dll into MC21 installation folder.  Let's see how far this will bring us.  Please capture a set of log files regardless what the outcome is.

[beckma]

Hello Yaobing,
I will check it in the evening.

regards
Markus

[beckma]

Hello Yaobing,
still Problems.
Here is the Report the error which apeers on the Screen.
The first Report is if I use the DVBVIewer record Service as SAT>IP Server
The second Report if I directly use the Octopus Net Sat>IP server

regrads
Markus

[Yaobing]

OK, that did not go very far.  It turned out that there were more than one of my dumb errors

Please try this DLL.

[beckma]

Hello Yaobing.
tested the latest Version.
Better but still not working.
He now says starting TV in the caption.
In the onscreen Display he Displays the channel Name and "Waiting for lock"
After a while he says "no Signal".

I have atached the log

regards
Markus

[Yaobing]

We are making progress.  A couple of more bugs have been caught.

Please try again.

[beckma]

Hello Yaobing,
same behaviour.

Here the log.

regards Markus

[Yaobing]

Please try this one.

[beckma]

Hello Yaobing,
same behaviour.
Here is the log.

One question from my side.
Do you have a SAT>IP Server on your side?
And is it working with your one?

If you don't have SAT>IP Server please check this site:

http://www.dvbviewer.com/de/index.php

They have a package dvbviewer and record Service.
The recording Service has a SAT>IP Server so you could test without having a SAT>IP Hardware.

If you have a new Version please let me know I will test it.

regards
Markus

[Yaobing]

Hi Markus,

First of all, thank you for doing the tests.

I do not have a SAT>IP device.  That is why I have to rely on users like you to do the testing.

Regarding DVBViewer, does it also work with North America digital TV (ATSC)?  SAT>IP specification only mentions DVBS, DVBT and DVBC.  So I am not sure if DVBViewer will help in this situation (of me not being in a DVB country).

I noticed that there is an error in the channel that you manually created.  The frequency value needs to be entered in KHz, not in MHz.  The value 11494 appears to be the frequency in MHz.  Please re-enter the value as 11494000 or 11493750 and test again.  In the mean time I am trying to fix some small things in the program.  I will post it when I finish.


Yaobing

EDIT: I uploaded a new DLL.

[beckma]

Hello Yaobing,
I test it in the evening.
You are right the frequency was wrong.

regards
Markus

[beckma]

Hello Yaobing,
added the new dll and changed the frequency.
But still same behaviour.

Here is the log.

regards
Markus

[Yaobing]

This is getting trickier now.  There are no more "obvious bugs".  That means I have to do some trial and error type of tests.

Here are two new versions of the DLL.  Please test them one at a time.

Version 1

Version 2

[beckma]

Hello Yaobing,
tested both Versions, but still not working.
JRiver starts now and Shows Live in the caption but time is not running and onscreen menu Shows No Signal.
I have attached 3 logs.
The naming means:
DvBviwer=> I used as a tuner in JRiver the Sat>Ip Server from DVbviwer which uses the OctopusNet Sat>IP HW
OctoputsNet => I used as a tuner in JRiver directly the OctopusNet Sat>Ip Server HW

V1 => V1 of your DLL
v2 => V2 of your DLL

I also attached the channel Settings I have done in JRiver and the channel info I see in DVBViwer.
Perhaps I did some wrong Settings.

regards
Markus

[beckma]

Hello Yaobing,
any new ideas?

[Yaobing]

Hello Yaobing,
any new ideas?

I will have to dig deeper to figure out.  Here is what I found so far:

The device with IP address 192.168.0.5 (octonet) always responded with "404 Not Found" error.  It does not like the URL sent by MC, or the way a channel is specified.

The DVBViewer device (192.168.0.4) behaves better.  My second DLL behaved better than the first, so I will concentrate on its method.

[beckma]

Hello Yaobing,
Do you know how I can log the url which the dvbviewer client is sending to the sat>ip server?
So you could see where is the difference (problem ) with the url

Regards Markus

[Yaobing]

Hello Yaobing,
Do you know how I can log the url which the dvbviewer client is sending to the sat>ip server?
So you could see where is the difference (problem ) with the url

Regards Markus

You can use one of those "packet sniffers". Fiddler and Wireshark are two examples.

[beckma]

Hello Yaobing,
what pattern do I have to look for?
regards
Markus

[Yaobing]

It is probably a good idea using a filter that logs only traffic to and from the device's IP address.  Then look for messages which have URL beginning with "rtsp://".

[Yaobing]

Markus,

I hope you will be able to get some info using the sniffing tool.  In the mean time, I build another DLL which contains a small change I hope will have some good effect.

Here it is.

[CountryBumkin]

After all the work/time your spending on fixing this problem. I sure hope there is more than "one person" out there using this card. 
Good luck.

[beckma]

Hello CountryBumkin,
it's not only about this card. It's about SAT>IP.
This is the next big thing here in Europe regarding satelite TV.

Regrads
Markus

[Yaobing]

I am sorry, I should not have suggested Fiddler as a tool for getting info on SatIP traffic.  Fiddler turns out to work only (?) for HTTP/HTTPS, but we need to capture RTSP traffic.  Please try using WireShark.

[Yaobing]

I did some playing with Wireshark.  Here are a few simple steps one can take to filter packets for a particular device:

1. Start Wireshark.

2. On menu bar, click Capture > Capture Filters...

3. At the lower left corner of the "Wireshark - Capture Filters" dialog, click the "+" button, to add a new filter.

4. A new filter is added at the bottom of the list, named "New capture filter".  Type "host 192.168.xxx.xxx" (where xxx.xxx should match your network device's IP address), in the "Filter" column.  You can rename the filter by double-clicking the filter name (for example name it "SatIP only").  Click OK to exit the dialog.

5. Capture menu again.  Select "Options...".  On the resulting dialog (Input tab), select the network on which the network traffic for the SatIP device is expected (you may or may not have multiple network to choose from, but you should have at least one .

6. Select a capture filter.  This is done by clicking the green icon next to the text "Capture filter for selected interfaces", and choose "SatIP only: host 192.168.....
 from the pop up list.  Click "Start" on the Options dialog to exit the dialog and start capturing.  Wireshark now captures all traffic to and from your SatIP device.

7. Start your SatIP client program (DVBView), and play a SatIP channel.  As soon as the channel starts to play normally (you see video), stop playing, and stop capturing on Wireshark by clicking the red square button.

8. Save the captured data in a file by clicking File > Save.

I hope I did not miss anything.  You can email me the saved file.  yaobing at jriver dot com

[beckma]

Hello Yaobing,
I send you a mail with the capuring results.
If somebody else will try.
You have to start Wireshark with Administrator privileges to see "interfaces"

regards
Markus

[Yaobing]

Thanks Markus.

I will have to make some changes.  

There are some things I do not understand.  Part of the request URL is not in Sat>IP specification:

&tnr=1,11494,22000,9750,0,0,3,2,5102,5101,5100,10301,134,0,24,0,1019,1,-1,192&prio=50

I did a search on the internet, and found that this seems to be related to scrambled channels.

Is this channel a free view channel?

[beckma]

Hello Yaobing,
this channel is free.
"Das Erste HD" first german tv channel.

Regards
Markus

[Nuts]

Thanks Markus.

I will have to make some changes.  

There are some things I do not understand.  Part of the request URL is not in Sat>IP specification:

&tnr=1,11494,22000,9750,0,0,3,2,5102,5101,5100,10301,134,0,24,0,1019,1,-1,192&prio=50

I did a search on the internet, and found that this seems to be related to scrambled channels.

Is this channel a free view channel?

Hi,

The "&tnr=....." part is a for communication (free and scrambled channels) between Recordingservice (Sat>IP Server by DVBViewer team) and DVBViewer (as Sat>IP client) only. It is related to scrambled channels but its not needed for your sat>ip implementation until you want to include some kind of special treatment for the Recordingservice as Sat>IP Server.

By the way digital devices octopus net has its own CI/CAM support for scrambled channels as well. They use another proprietary URL extension (like "&tnr...." in DVBViewer  ) for their CI/CAM system.
This is needed because Sat>IP specification says nothing about how to handle scrambled channels.
For details about their System you should contact team digital devices.

If you are willing to support the "&tnr..." part I could give you further informations how it works.  

Anyway for basic Sat>IP support both extensions are not needed. Recordingservice, octopus net or any other Sat>IP Server are working just fine without it for free channels (or descrambling by client).
Just follow the Sat>IP specifications, no reverse engineering is needed.

I hope it helps a little bit. Sat>IP support in jriver would be great.  

[beckma]

Hello Yaobing,
anything new?
Did you contact Nuts, who kows the secrets of dvbviewer server ( rec service) and octopus net server.
I think at the end we need some sort of handling for scrambled channels (preferable the dvbviewer method).
Because a lot of channels here in Germany (Europe) are scrambled.

regards
Markus

[Yaobing]

Please test again when MC22 build 17 or newer is released to the public.

[beckma]

I will check
Regards Markus

[Yaobing]

MC22 build 18 is out.

[tyler69]

how's the progress on this?

[beckma]

Hello Yaobing,
still not working with  MC22 V21.
Here is the log.

[Yaobing]

Hello Yaobing,
still not working with  MC22 V21.
Here is the log.

I could not get much useful info from the log file because you reset the log without trying to play a new channel.  As a result, when you played a channel after the reset, MC just skips regular code and says its the same channel.

Please try again, by restarting MC and then going straight to playing a channel.

[tyler69]

Hi there. Any news?

[Yaobing]

Sorry, no news.

[tyler69]

Hi there. Any news? Are there any plans on when SAT-IP should be supported?

[Yaobing]

Sorry, still no news.  I have been busy with other stuff and put this one down temporarily.  I hope to pick up again soon.

[tyler69]

Bump

[tyler69]

Bump.

[Yaobing]

Can someone using the latest version of MC22 try playing a (manually added) channel and send me a log package again?  Please turn logging verbosity to 2 and restart MC before trying to play.  Don't forget to turn logging verbosity back to 0 after the log is captured.

[tyler69]

I can do it but where do I set the verbosity?

[Hendrik]

In the Options, Television -> Advanced (way at the bottom of the page)

[tyler69]

OK, thanks. There was also an option to enable logging somewhere also, right? EDIT: found it. Attached log, however I do not see the OctopusNet in the devices list (they were available some time ago in an earlier version of MC if I remeber correctly).

[tyler69]

I see both tuners in television options -> manage devices but no tuner when i go to television options -> setup

[tyler69]

I managed to somehow click through the setup and it seems like a tuner is available. I manually added a channel according to the settings in a screenshot on the last page and started to play this channel. It seems, that no signal can be found.

[Yaobing]

Thanks for the logs.

I found one bug by reading the last log.  Not sure if this bug is the main culprit, I made a new DLL for you to test.

Please first install the latest build (.81) from MC22 board.  Then download, unzip, and copy the DLL into MC installation folder.

[tyler69]

Attached you'll find the log after trying to play the channel with the DLL included in installation folder. Now MC says "something went wrong with playback" after a few seconds when trying to open up the stream. What I also noted now: since adding the channel last time i get a continous popup of "mx2xml" and "mc2xml lineup" selections. They come up every few seconds regardless of my selections.