I'm trying to get Zattoo channels integrated into ChannelsDVR but have hit a dead end.
I've been using telerising-api (https://github.com/sunsettrack4/telerising-api) to create a m3u playlist that lets me access my zattoo account.
When I loaded up the m3u from telerising-api directly as a source in ChannelsDVR, I was able to see the video for each channel but was getting no audio.
From what I can ascertain the issue is Zattoo feeding a HLS5 or HLS7 playlist and I'm assuming channels doesn't support these (any chance of supporting these types of playlists?). Connecting direct to telerising-api's m3u file with VLC works perfectly with the newest version of VLC (slightly older older versions get video with no audio)
To solve this, first I tried feeding the m3u from telerising --> hlsproxy to re-encode the streams, but when I tested the output from hlsproxy with VLC it also had no audio (so it doesn't appear that hlsproxy is able to handle these hls 5 or hls 7 playlists either).
Then I tried feeding the m3u from telerising into xteve (using the VLC option to re-encode, without reencoding, no audio comes through). Once I confirmed that both audio and video where coming out of xteve (using VLC)
I then added the xteve instance as a m3u file to ChannelsDVR (setting stream setting as Mpeg-TS instead of HLS).
I am able to view the Zattoo channels (both audio and video) when accessing using a web browser connecting to my.channelsdvr.net (it does take a bit of time to start the stream 15 seconds or so). (I'm setup with telerising & xteve running on a seperate machine from my channelsdvr machine)
The only issue is when I try accessing these channels from either an iphone/ipad/fire tv, after a few seconds I get the "Tuner Not Available" message (once it has worked, when the stream started particularly fast), otherwise I haven't had any success accessing from any of these devices. I have confirmed that if I record once of the zattoo channels, I am able to play back the recording on either the web or ios/fire tv clients.
Given it has worked once, when the stream started particularly fast. I'm pretty confident after trying a range of options to troubleshoot that the issue is that there is a shorter timeout on the client apps (seems to be about 8 seconds) before it sends you to the "Tuner Not Available" message. If I access via a webbrowser, it will just keep trying until the stream finally starts after 10-15 seconds.
Is there any way for the developers to extend the timeout time on the ios/fire tv clients to a longer period before sending you to the "Tuner not available" message (i'm using the betas for both ios and firetv).
Thanks in advance for any help.