INTERACT FORUM
Windows => Television => Topic started by: Beamer on August 13, 2022, 06:44:49 am
-
I have been trying to setup and play from my TRIAX SAT>IP server without success. I can watch with DVBViewer without issue. I can even install an app on my Android phone and watch without problems.
I am unable to get it to work with JRiver. Scanning does not find any channels in spite of the Triax hardware being found. I was also able to download the channels from the Triax which according to the WiKi indicates compatibility.
I am in the UK and trying to watch Astra on 28 deg.
Any help greatly appreciated.
I am running the latest JRiver release.
-
Are you running 29.0.85?
https://yabb.jriver.com/interact/index.php/topic,133730.0.html
Did you find the setup instructions?
https://yabb.jriver.com/interact/index.php?topic=129272.0
-
Yes running latest and greatest.
The setup instructions seem to be more inclined towards iptv rather than a local sat>ip server.
I have no idea how to get a m3u8 file. Why can't JRiver scan the transponders like most other programs. In theory this should be a plug and play exercise. It took all of 5 minutes to have dvbviewer up and running and even less on my phone app.
-
There are sometimes two "latest". Latest on the MC29 board and the Stable version on the Download Page. Having the full version helps.
I can't help you, but try reading other posts on the forum.
https://www.google.com/search?q=sat%3Eip+jriver&oq=sat%3Eip+jriver
-
Just to clarify I'm running the latest stable release v29.0.83.
Thanks for the search links, unfortunately I had already tried and exhausted Google of help.
-
Are you using MC on Windows? If so, we do support scanning channels through transport stream. It should be an option during setup.
If you are using Mac or Linux, we only support using m3u8/m3u file.
Your Sat>IP server might have an option to export an m3u channel list.
-
Yes I'm running Windows 11 Pro.
In theory the Triax qualifies for your whitelist as it can download channel information.
On the basis of a picture is worth a thousand words I have attached some screen captures in case you can see something obvious that I'm doing or not doing ;)
-
I have attached a log after the failed scan.
-
Thanks for the log. I will take a look.
In the meantime, you can check if the frequency table is correct. The table is in a file, one for each satellite transponder. For your case, it is "28.2°E Astra 2E,2F,2G.xml", located in MC installation folder's "TV\DVBS" subfolder.
I believe there is also an option not to use this static table but use BAT table received in the transport stream.
-
I have not checked all the frequencies but the ones I am interested in are present and correct.
-
I have attached a working log from an app that works just fine. Hopefully it will give you some pointers.
-
@yaobing Have you had time to look through the logs?
-
Not yet. Been busy on other things. I should be able to get to it next week.
-
I had a look at the log file and found this in it:
0083233: 14736: Reader: JRRTSPClient: [URL:"rtsp://<DeviceIPAddress>:554/?fe=1&msys=dvbs&src=1&freq=11038.0&pol=v&mtype=qpsk&sr=22000&fec=56&pids=all,0"]: Failed to set up the "video/MP2T" subsession: 400 Bad Request
Not sure why the server rejects this request, but it might have been "&pids=all,0". It should have been just "&pids=all". I changed it so that no ",0" is added if &pids= is followed by "all" instead of an actual list. I hope that was it.
Please first update MC to the latest MC29. Then download the following DLL:
JRTelevision DLL for MC29 64-bit (https://files.jriver.com/mediacenter/test/JRTelevision_29_2022-08-22.zip)
Unzip and copy to <MC29 installation> folder.
-
Sorry no luck with the replacement dll. I have assumed you wanted me to use the latest released version rather than beta!
FYI Attached log.
-
Let's try again with this one:
JRTelevision DLL for MC29 64-bit (https://files.jriver.com/mediacenter/test/JRTelevision_29_2022-08-23.zip)
-
Negative :(
Log attached
-
We are able to go much further this time. The server used to reject our SETUP request. Now we have passed that part. That is the good news. But I will have to figure out why we are not getting channels.
Have you ever tried manually creating a channel? Try creating one and play it. If it plays, we know we at least have solved one part of the problem.
-
Thanks for your help, Beamer.
-
Please see screen capture.
Would it help if I setup a vpn to allow you remote access to the TS 400 Tuner?
If it makes sense for you I will PM you the details to gain access.
-
Please see screen capture.
That error message usually is shown when MC cannot find the device, because MC has not gone through DLNA discovery yet.
Would it help if I setup a vpn to allow you remote access to the TS 400 Tuner?
If it makes sense for you I will PM you the details to gain access.
Let me try getting more info from your log files first.
-
Let's try again with this one:
JRTelevision DLL for MC29 64-bit (https://files.jriver.com/mediacenter/test/JRTelevision_29_2022-08-24.zip)
What I found from the last log file you posted was that there was no signal on the channel that was tuned to. The device server accepted our request for SETUP, and PLAY. But we got this information back:
a=fmtp:33 ver=1.0;src=1;tuner=1,0,0,0,10847.00,v,dvbs,qpsk,off,0.35,23000,34;pids=all
The part of the line beginning with "tuner=" represents "tuner=<feID>,<level>,<lock>,<quality>,<frequency>,<polarisation>,<system>,<type>,<pilots>,<roll_off>,<symbol_rate>,<fec_inner>"
As you can see, the signal level, lock, and quality are all 0.
Normally, after we send PLAY request, the server should start sending transport stream data. We did not receive a signel byte.
This is puzzling, I assume the transponder you selected, i.e. at frequency 10847 MHz should have signal.
Please send another log file after trying with the new DLL.
Also, have you tried using the transponder list in the static file, instead of scanning the NIT (network information table)?
-
Unfortunatley the link to the new test dll does not work for me:
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>0E5F99WBBGTHXCVF</RequestId>
<HostId>osberOPqqaQ/+F8PBZCTnL6BZGx2I2XbFS7Mq/369cat6lARai8se0vbF/xiYzyFMOVGhY0+2vQ=</HostId>
</Error>
The Triax tuner has four LNB inputs, presently I only have #1 connected. I have attached a capture of the diagnostic facility indicating lock on the parameters used.
Did you take a look at the log from working software for any clues?
-
This is taken while watching with alternate software:
-
Unfortunatley the link to the new test dll does not work for me:
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>0E5F99WBBGTHXCVF</RequestId>
<HostId>osberOPqqaQ/+F8PBZCTnL6BZGx2I2XbFS7Mq/369cat6lARai8se0vbF/xiYzyFMOVGhY0+2vQ=</HostId>
</Error>
Oops! I forgot to set permission properly. Please try again.
-
Log attached
-
Did you take a look at the log from working software for any clues?
Yes I did. I was not able to get any clues from it, partly because I don't know their logging. I looked for any RTSP activities but could not find any.
In any case, I notice one thing from your log and your recent screenshots. The channel at frequency 10847 MHz is actually a DVB-S2 channel, yet we are treating it as just DVB-S. Maybe that is the issue? However, when we send a DESCRIBE request to the device server, with &msys=dvbs in the URL, the server did not reject it, and actually returned a description that also says msys is "dvbs", not "dvbs2".
Our DVBS setup files, such as "28.2°E Astra 2E,2F,2G.xml", do not contain information about whether the transponder is DVB-S or DVB-S2.
Now I am going to ask you to create a channel in MC manually again. Last you tried, it did not work, and I replied:
"That error message usually is shown when MC cannot find the device, because MC has not gone through DLNA discovery yet.
It turns out, that is not the reason. You truly don't have a tuner that can handle the channel you created manually, as you created a DVB-S channel which is different from a Sat>IP DVB-S channel. Please create a channel as shown in the screenshot below.
-
Sorry if I'm being a bit thick but as far as I am aware I have ALWAYS selected the channel modulation as "S2"
Please see screen capture. Am I missing something?
-
Select "Sat>IP" for Type, don't select DVB-S for it.
Don't try to edit the channel you previously created, as you are not allowed to change Type when you edit. Add a new channel, making sure you select Sat>IP for Type.
-
Got it and seems we are getting closer. The interface is somewhat confusing to me but I now see the error I made.
Blank screen with BBC1 HD on the bottom.
Deleted earlier channel as requested
-
A couple of more errors in your manually setup channel.
The frequency in our interface should be entered using KHz unit, i.e., you need to add three zeros.
The PID list should include a few more numbers (0,6941,5400,5401,5402,5403).
You can edit your existing channel to correct these.
-
Still No Luck sorry Lock ;D
Are you sure it would not be easier for both of us if you had a direct link via vpn?
-
Still No Luck sorry Lock ;D
Are you sure it would not be easier for both of us if you had a direct link via vpn?
I am just not sure how we could do it. Will your device be discovered on my desktop or do I have to access your desktop?
-
Sorry you are correct it would not be easy as it most probably will not be recognised your end. Desktop connection would work, do you have a preferred desktop connection software?
If its any consolation the TS400 MK2 is very popular in Europe. Its really surprising this issue has not cropped up before.
-
I could set you up with a TeamViewer connection?
-
OK. Let's try that tomorrow. Thanks.
-
Unfortunately I was not able to get much information by remotely accessing your device. I will need to do some research.
-
Thanks for trying.
-
Seems you may have progressed further than you expected. Out of curiosity I played a BBC1 channel that I imported from the Trax 400 and it worked with the updated dll !
Log attached
-
Thanks for the info.
You played an URL directly. The playback was done outside of TV engine, and handled by different code. At least we know playback is possible.
The main difference between this URL (which you played successfully):
http://<device IP>/dlna/?type=DVB-S2&src=1&freq=10847&pol=v&sr=23000&pids=0,6941,5400,5401,5402,5403&msys=dvbs2&mtype=8psk
and the URL we try to use in TV engine is that we try to use RTSP protocol, whereas this URL is HTTP. So MC's TV engine uses this URL instead:
rtsp://<Device IP>:554/?fe=4&msys=dvbs2&src=1&freq=10847.0&pol=v&ro=0.35&mtype=8psk&plts=off&sr=23000&fec=34&pids=0,6941,5400,5401,5402,5403
Besides the protocol difference, I see only one thing that we do not do: we do not specify "type=DVB-S2".
I wonder if the device fully supports RTSP.
You can use the HTTP URL to set up an IPTV channel. I think that will work.
-
I'm not sure where we are going. Are you asking me to try something or concluding JRiver is not going to be able to work with the Triax 400?
-
It looks like currently JRiver is not able to work with this device to set up Sat>IP channels because our Sat>IP channels are designed to work with RTSP protocol. You can use JRiver MC to set up IPTV channels, using URLs exported by the device, as an alternative method. If it exports all channels into a single M3U file, you can set up these channels using Television Setup wizard. Just select "Streaming (from a network device or from the internet) for "Service Type".
If no m3u file is available, then you will have to do it manually, channel-by-channel.
It maybe possible for us to support this device as a DMS device. I can explore that possibility and add it in the next major version.
In summary:
The device should work in MC29 if you set it up as an IPTV device. It may be supported as a DMS device in the next major version of MC.
The difference between these two methods is that we do get more info from the device if it is a DMS device, for example we can discover how many tuners are available, so we can actively manage the availability of tuners. On the other hand, we treat IPTV channels as just based on URLs. We don't know how many tuners there are. It is therefore possible for MC to try loading more tuners than the actual number of them (MC might try recording 5 shows in the same time-slot, for example).