Bug #4150
m3u8 not working anymore
0%
Description
So I've search now for hours and tried different options and hope that someone here can help me to fix the issue.
Issue: I have setup a .m3u8 as one of my TV channels half a year back working fine. The provider has changed the link. After I changed the link as well on my end the Stream does not work for me anymore.
Setup:
NAS: Synology DS212j DSM 6
TVHeadend: 4.1.2389 from dirks site
FFMPEG: 3.1.2-4
Added IPTV Network (not Automatic)
Added new Mux:
EPG Scan: Disabled
URL: pipe:///usr/bin/ffmpeg -loglevel fatal -i https://nhkwtv-i.akamaihd.net/hls/live/263942/nhkwtv/index_2100.m3u8 -vcodec copy -acodec copy -metadata service_provider=BBC -metadata service_name=BBC1 -f mpegts pipe:1
I change no other Mux settings and kept the standards.
Log:
subscription: 006A: "scan" subscribing to mux "NHK_IPTV", weight: 6, adapter: "IPTV", network: "new_IPTV", service: "Raw PID Subscription"
spawn: Executing "/usr/bin/ffmpeg" ---- This line keeps repeating for a few seconds
mpegts: NHK_IPTV in new_IPTV - scan no data, failed
subscription: 006A: "scan" unsubscribing
The m3u8 works for me just fine in vlc player.
Any help would be appreciated. If you need more data, do let me know. Thanks for the help
History
Updated by Jaroslav Kysela almost 8 years ago
Try the ffmpeg command on the command line if something is not wrong on your tvh server. Here it works perfectly on tvh v4.1-2399-g806a5b7 .
Updated by Maurice C almost 8 years ago
I tried the following and it gives me this output. Maybe something was fixed between 4.1.2399 and 4.1.2389?
admin@DS212j:/$ usr/bin/ffmpeg
ffmpeg version 2.7.1 Copyright (c) 2000-2015 the FFmpeg developers
built with gcc 4.6.4 (Marvell GCC release 20150204-c4af733b 64K MAXPAGESIZE ALIGN CVE-2015-0235)
configuration: --prefix=/usr --incdir='${prefix}/include/ffmpeg' --arch=arm --target-os=linux --cross-prefix=/usr/local/arm-marvell-linux-gnueabi/bin/arm-marvell-linux-gnueabi- --enable-cross-compile --enable-optimizations --enable-pic --enable-gpl --enable-shared --disable-static --enable-version3 --enable-nonfree --enable-libfaac --enable-encoders --enable-pthreads --disable-bzlib --disable-protocol=rtp --disable-muxer=image2 --disable-muxer=image2pipe --disable-swscale-alpha --disable-ffserver --disable-ffplay --disable-devices --disable-bzlib --disable-altivec --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libmp3lame --disable-vaapi --disable-decoder=amrnb --disable-encoder=zmbv --disable-encoder=dca --disable-encoder=ac3 --disable-encoder=ac3_fixed --disable-encoder=eac3 --disable-decoder=dca --disable-decoder=eac3 --disable-decoder=truehd --cc=/usr/local/arm-marvell-linux-gnueabi/bin/arm-marvell-linux-gnueabi-ccache-gcc
libavutil 54. 27.100 / 54. 27.100
libavcodec 56. 41.100 / 56. 41.100
libavformat 56. 36.100 / 56. 36.100
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 16.101 / 5. 16.101
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.100 / 1. 2.100
libpostproc 53. 3.100 / 53. 3.100
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...
Updated by Jaroslav Kysela almost 8 years ago
No, try the whole command like:
/usr/bin/ffmpeg -loglevel fatal -i https://nhkwtv-i.akamaihd.net/hls/live/263942/nhkwtv/index_2100.m3u8 -vcodec copy -acodec copy -metadata service_provider=BBC -metadata service_name=BBC1 -f mpegts pipe:1 > output.ts
Updated by Maurice C almost 8 years ago
Sorry for the weird wording. What I meant was that I ran the command, and I received then an empty output.ts file in the folder. I'm not sure if this means that it works as expected or if there should be more to it?
Also do you know when dirks will release the latest version for the Synology NAS? Maybe that fixes the issue, since you are running a newer version than I do. Maybe something has changed in the code in those few iterations?
Updated by Jaroslav Kysela almost 8 years ago
- Status changed from New to Invalid
It means that your command does not work (the file should contain the MPEG-TS stream). You may replace pipe:1 with the filename in the next test and watch what ffmpeg tells you. It's not a tvh issue.
Updated by Maurice C almost 8 years ago
Thanks for helping me troubleshooting.
So what you mean is run the following in the commmand line? If I run this nothing is return. Do you know if there is somewhere a log file for ffmpeg that could help?
/usr/bin/ffmpeg -loglevel fatal -i https://nhkwtv-i.akamaihd.net/hls/live/263942/nhkwtv/index_2100.m3u8 -vcodec copy -acodec copy -metadata service_provider=BBC -metadata service_name=BBC1 -f mpegts /volume1/Video/Recordings/output.ts
Updated by Maurice C almost 8 years ago
So overall it seems that the last time the channel worked was on the 23rd of December.
However nothing has changed that day. There hasn't been an update of any packages or the NAS it self. TVH was updated 10 days before but the channel still worked in between.
The only update happening afterwards was on the 27th then again, with a NAS minor patch update regarding RAID that shouldn't affect tvh or ffmpeg.
Any ideas would be appreciated
Updated by Jaroslav Kysela almost 8 years ago
Use loglevel info instead fatal to see what is ffmpeg doing.
Updated by Maurice C almost 8 years ago
This might give a little more info. Here the info Log:
/usr/bin/ffmpeg loglevel info -i https://nhkwtv-i.akamaihd.net/hls/live/263942/nhkwtv/index_2100.m3u8 -vcodec copy -acodec copy -metadata service_provider=BBC -metadata service_name=BBC1 -f mpegts /volume1/Video/Recordings/output3.ts --enable-cross-compile --enable-optimizations --enable-pic --enable-gpl --enable-shared --disable-static --enable-version3 --enable-nonfree --enable-libfaac --enable-encoders --enable-pthreads --disable-bzlib --disable-protocol=rtp --disable-muxer=image2 --disable-muxer=image2pipe --disable-swscale-alpha --disable-ffserver --disable-ffplay --disable-devices --disable-bzlib --disable-altivec --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libmp3lame --disable-vaapi --disable-decoder=amrnb --disable-encoder=zmbv --disable-encoder=dca --disable-encoder=ac3 --disable-encoder=ac3_fixed --disable-encoder=eac3 --disable-decoder=dca --disable-decoder=eac3 --disable-decoder=truehd --cc=/usr/local/arm-marvell-linux-gnueabi/bin/arm-marvell-linux-gnueabi-ccache-gcc
ffmpeg version 2.7.1 Copyright (c) 2000-2015 the FFmpeg developers
built with gcc 4.6.4 (Marvell GCC release 20150204-c4af733b 64K MAXPAGESIZE ALIGN CVE-2015-0235)
configuration: --prefix=/usr --incdir='${prefix}/include/ffmpeg' --arch=arm --target-os=linux --cross-prefix=/usr/local/arm-marvell-linux-gnueabi/bin/arm-marvell-linux-gnueabi
libavutil 54. 27.100 / 54. 27.100
libavcodec 56. 41.100 / 56. 41.100
libavformat 56. 36.100 / 56. 36.100
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 16.101 / 5. 16.101
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.100 / 1. 2.100
libpostproc 53. 3.100 / 53. 3.100
https protocol not found, recompile FFmpeg with openssl, gnutls,
or securetransport enabled.
https://nhkwtv-i.akamaihd.net/hls/live/263942/nhkwtv/index_2100.m3u8: Protocol not found
Updated by Jaroslav Kysela almost 8 years ago
You have ffmpeg without enabled https:
https protocol not found, recompile FFmpeg with openssl, gnutls, or securetransport enabled. https://nhkwtv-i.akamaihd.net/hls/live/263942/nhkwtv/index_2100.m3u8: Protocol not found
Updated by Maurice C almost 8 years ago
Sadly I am not a linux guru, can you tell me what commands are needed on my commandline on my NAS to enable and recompile?
Thank you
Updated by Jaroslav Kysela almost 8 years ago
Please, ask people around your distro. It's not really tvheadend issue.
Updated by Maurice C almost 8 years ago
They are not responding over there... But I'll keep trying, maybe I'll find a description somewhere on how to.
This can be closed than as this is not a tvheadend issue but a configuration issue of ffmpeg.
Thanks for good the support so far.
Updated by Maurice C almost 8 years ago
As a final note for whoever might stumble upon this as well.
Issue resolved. It seem Synology has several different instances of ffmpeg installed (like for Video and Audiostation) which automatically link to bin as the main used ffmpeg. Thus to fix this issue one has to directly link to the ffmpeg from the syno package e.g. pipe:///volume1/@appstore/ffmpeg/bin/ffmpeg
With this the issue is then fixed.