Channels Plugin
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Re: Channels Plugin
I did (multiple times to succeed) install the previous version, and I got the .exe ones, than changed to 2.22 version and after waiting for morning and a better internet it's somehow betterSharkHunter wrote:Sounds like it worked as it should (more or less)...... I know for sure that SVTPlay works and TPB.

Thanks for your help, but not sure where I'm suppose to go from there, even the channel log file does not seem to be very helpful.
- SharkHunter
- Developer
- Posts: 648
- Joined: Fri Jun 01, 2012 9:36 pm
Re: Channels Plugin
If you upload the logs we can see what goes on. Which channels did you try? Make sure you try stuff just before you pack the logs as they are clear on restart...DTigerBKK wrote:I did (multiple times to succeed) install the previous version, and I got the .exe ones, than changed to 2.22 version and after waiting for morning and a better internet it's somehow betterSharkHunter wrote:Sounds like it worked as it should (more or less)...... I know for sure that SVTPlay works and TPB.Some channels got lists of movies or tv shows, but for now I can only watch some SVT videos (too bad I don't get the language).
Thanks for your help, but not sure where I'm suppose to go from there, even the channel log file does not seem to be very helpful.
We reject: kings, presidents and voting.
We believe in: rough consensus and running code.
We believe in: rough consensus and running code.
Re: Channels Plugin
Hi.SharkHunter wrote:Nope SubJunk has to do an update there. You can manually download version 2.22 from here https://sharkhunter-shb.googlecode.com/ ... ug_222.jar and place that file in the plugins dir (remove the 2.21 version also).
I tried this. Obviously I cannot test the PnP as such until Subjunk has done the update but I tried to start UMS with the 2.22 plugin anyway. So more precisely this is the sequence:
UMS 3.0.0 working on Ubuntu 12.04
PnP install of Channels 2.21 (hangs after pepy.zip as before and as expected)
Stopping UMS
Replacing Channels plugin to Channels 2.22
Starting UMS
Getting the same same error as before after having restarted UMS after an unsuccessful PnP install (but not the same as at PnP install). Anyway, I attach the fresh log.
Not sure if I should also remove the PMSEncoder plugin (since it is now the failing one)? But can I run without it?
Pen
- Attachments
-
debug.log
- (10.08 KiB) Downloaded 979 times
Server Ubuntu 12.04, Renderer Samsung 46D6300
- SharkHunter
- Developer
- Posts: 648
- Joined: Fri Jun 01, 2012 9:36 pm
Re: Channels Plugin
Yes PMSEncoder should be removed since it crashes. I look into it and see if I can upgrade there. In the future use the DbgPacker to pack all logs. See viewtopic.php?f=9&t=556
We reject: kings, presidents and voting.
We believe in: rough consensus and running code.
We believe in: rough consensus and running code.
Re: Channels Plugin
Ok, so I removed the PMSEncoder and channels starts. Now I can browse SVTPlay but when I try to start a media UMS refuses to use FFMpeg to play it. It's the same FFMpeg as I use for UMS 2.6.5 so it should play HTTPS. It all ends up in that it tries with VLC instead which isn't there:
- TRACE 2013-11-15 17:44:03.404 [New I/O worker #6] Matched format WEB to "http://svtplay7h-f.akamaihd.net/i/world ... m3u8?null="
TRACE 2013-11-15 17:44:03.405 [New I/O worker #6] Getting player for resource "1670 Kbps"
TRACE 2013-11-15 17:44:03.406 [New I/O worker #6] Player "MEncoder" is incompatible
TRACE 2013-11-15 17:44:03.407 [New I/O worker #6] tsMuxeR cannot determine compatibility based on audio track for http://svtplay7h-f.akamaihd.net/i/world ... m3u8?null=
TRACE 2013-11-15 17:44:03.407 [New I/O worker #6] Player "tsMuxeR" is incompatible
TRACE 2013-11-15 17:44:03.407 [New I/O worker #6] Player "FFmpeg" is incompatible
TRACE 2013-11-15 17:44:03.407 [New I/O worker #6] Player "FFmpeg Audio" is incompatible
TRACE 2013-11-15 17:44:03.407 [New I/O worker #6] Player "Audio High Fidelity" is incompatible
TRACE 2013-11-15 17:44:03.408 [New I/O worker #6] Player "FFmpeg Web Video" is incompatible
TRACE 2013-11-15 17:44:03.408 [New I/O worker #6] Returning compatible player "VLC Web Video"
- Attachments
-
- ums300Ch222_dbg.zip
- (126.77 KiB) Downloaded 863 times
Server Ubuntu 12.04, Renderer Samsung 46D6300
- SharkHunter
- Developer
- Posts: 648
- Joined: Fri Jun 01, 2012 9:36 pm
Re: Channels Plugin
Try moving FFmpegwebvideo up to the top of the engines.
We reject: kings, presidents and voting.
We believe in: rough consensus and running code.
We believe in: rough consensus and running code.
Re: Channels Plugin
Ok, let's start with the current list. In the console it looks like this:
Web Video Streaming Engines:
- FFMpegWebVideo
- VLCWebVideo
- VLCWebVideo(Legacy)
- MEncoderWeb
Web Audio Streaming Engines:
- VLCWebAudio(Legacy)
Obervations
- VLC is in the list of both Video and Audio web streaming engines - why? For the non web engines VLC is correctly detected by UMS as missing but for the web engines it is not? Is VLC Web supposed to be bundled with UMS - i.e. VLC is hard coded to exist?
- With UMS 2.6.5 PMSEncoder is within the list - but FFMpeg is anyway used and working correctly. With Ums 3.0.0 PMSEncoder is not within the list - so this is correct.
- According to the trace, UMS is really considering FFMpeg web video, but of some reason it claims that it is incompatible - so is it really the order that is wrong? I would rather suspect that it is the decision criteria that is wrong or as if the discovery of encoder capabilities got wrong somehow.
Tried work arounds:
Since FFMpeg web video is already higest in the list of web engines the only way to change the list is by manually configuring the UMS.conf file. Tried this:
- Put the ffmpegebvideo in front of everything in the list of engines (even before the non web engines). No success.
Pen
Web Video Streaming Engines:
- FFMpegWebVideo
- VLCWebVideo
- VLCWebVideo(Legacy)
- MEncoderWeb
Web Audio Streaming Engines:
- VLCWebAudio(Legacy)
Obervations
- VLC is in the list of both Video and Audio web streaming engines - why? For the non web engines VLC is correctly detected by UMS as missing but for the web engines it is not? Is VLC Web supposed to be bundled with UMS - i.e. VLC is hard coded to exist?
- With UMS 2.6.5 PMSEncoder is within the list - but FFMpeg is anyway used and working correctly. With Ums 3.0.0 PMSEncoder is not within the list - so this is correct.
- According to the trace, UMS is really considering FFMpeg web video, but of some reason it claims that it is incompatible - so is it really the order that is wrong? I would rather suspect that it is the decision criteria that is wrong or as if the discovery of encoder capabilities got wrong somehow.
Tried work arounds:
Since FFMpeg web video is already higest in the list of web engines the only way to change the list is by manually configuring the UMS.conf file. Tried this:
- Put the ffmpegebvideo in front of everything in the list of engines (even before the non web engines). No success.
Pen
Server Ubuntu 12.04, Renderer Samsung 46D6300
- SharkHunter
- Developer
- Posts: 648
- Joined: Fri Jun 01, 2012 9:36 pm
Re: Channels Plugin
Ok, issue the command
and paste the output here. I suspect that http isn't supported by your ffmpeg.
Code: Select all
ffmpeg -protocols
We reject: kings, presidents and voting.
We believe in: rough consensus and running code.
We believe in: rough consensus and running code.
Re: Channels Plugin
It's your ffmpeg, pen. I checked this url on the command line with the UMS ffmpeg binary on my system (Ubuntu 12.04 64bit) and it works for me.pen wrote:DEBUG 2013-11-15 17:43:15.591 [main] FFmpeg supported protocols: [mms, https]
Re: Channels Plugin
Here is the FFMpeg information:
And here are some more important facts:
I have UMS 2.6.5 and UMS 3.0.0 istalled on the same (physical) Ubuntu 12.04 64-bit server. I have carefully made sure that they do not share any config files. I have disabled the bundled FFMpeg image in both versions and replaced them with symlinks to the same Ubuntu "native" FFMpeg image. I only run one of the versions at a time.
Channels SVTPlay A-Z works on UMS 2.6.5 but not on UMS 3.0.0
So I'm pretty sure that the URL works on FFMpeg command line, since I fighted alot to find a working FFMpeg for SVTPlay HTTPS and tested it from command line and since it works when it's called by UMS 2.6.5 but not from 3.0.0.
infidel.... the line
"DEBUG 2013-11-15 17:43:15.591 [main] FFmpeg supported protocols: [mms, https]"
is present in the logs of both UMS 2.6.5 and UMS 3.0.0 - still it only works with UMS 2.6.5
What should the line read to be compliant?
Pen
Code: Select all
admin@Athena:/opt/ums-3.0.0$ ffmpeg -protocols
ffmpeg version 0.10.7-6:0.10.7-0jon1~precise Copyright (c) 2000-2013 the FFmpeg developers
built on Jul 15 2013 21:27:54 with gcc 4.6.3
configuration: --arch=amd64 --disable-stripping --enable-pthreads --enable-runtime-cpudetect --extra-version='6:0.10.7-0jon1~precise' --libdir=/usr/lib/x86_64-linux-gnu --prefix=/usr --enable-bzlib --enable-libdc1394 --enable-libfreetype --enable-frei0r --enable-gnutls --enable-libgsm --enable-libmp3lame --enable-librtmp --enable-libopencv --enable-libopenjpeg --enable-libpulse --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-vaapi --enable-vdpau --enable-libvorbis --enable-libvpx --enable-zlib --enable-gpl --enable-postproc --enable-libcdio --enable-x11grab --enable-libx264 --shlibdir=/usr/lib/x86_64-linux-gnu --enable-shared --disable-static
libavutil 51. 35.100 / 51. 35.100
libavcodec 53. 61.100 / 53. 61.100
libavformat 53. 32.100 / 53. 32.100
libavdevice 53. 4.100 / 53. 4.100
libavfilter 2. 61.100 / 2. 61.100
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 6.100 / 0. 6.100
libpostproc 52. 0.100 / 52. 0.100
Supported file protocols:
I.. = Input supported
.O. = Output supported
..S = Seek supported
FLAGS NAME
-----
I.. applehttp
I.S cache
I.S concat
I.. crypto
IOS file
IO. gopher
IOS http
IO. httpproxy
IOS https
I.S mmsh
I.. mmst
.O. md5
IO. pipe
IO. rtmp
IO. rtmpt
IO. rtmpe
IO. rtmpte
IO. rtmps
IO. rtp
IO. tcp
IO. tls
IO. udp
I have UMS 2.6.5 and UMS 3.0.0 istalled on the same (physical) Ubuntu 12.04 64-bit server. I have carefully made sure that they do not share any config files. I have disabled the bundled FFMpeg image in both versions and replaced them with symlinks to the same Ubuntu "native" FFMpeg image. I only run one of the versions at a time.
Channels SVTPlay A-Z works on UMS 2.6.5 but not on UMS 3.0.0
So I'm pretty sure that the URL works on FFMpeg command line, since I fighted alot to find a working FFMpeg for SVTPlay HTTPS and tested it from command line and since it works when it's called by UMS 2.6.5 but not from 3.0.0.
infidel.... the line
"DEBUG 2013-11-15 17:43:15.591 [main] FFmpeg supported protocols: [mms, https]"
is present in the logs of both UMS 2.6.5 and UMS 3.0.0 - still it only works with UMS 2.6.5
What should the line read to be compliant?
Pen
Last edited by pen on Sun Nov 17, 2013 5:54 am, edited 1 time in total.
Server Ubuntu 12.04, Renderer Samsung 46D6300