BBC radio streams not working

[simoncn]

(20-02-2015 09:59)PhilD Wrote:  Good question, the clients are in different rooms so I only heard the i83 stuttering before stopping the stream. I'm currently at work so I'll try to recreate the problem tonight or over the weekend then report back.

Phil

Thanks very much!

[Pastim]

(20-02-2015 09:11)simoncn Wrote:  

(20-02-2015 00:36)Pastim Wrote:  Both our responses were made at the same time - sorry.

No problem! I think we are close to resolving the misunderstanding.

Quote:However, I'm still a little puzzled. If I had another music source which generated aac, and I needed to transcode it through UPnP (maybe because a UPnP player didn't support aac), would I be unable to?

You would be able to do this for UPnP renderers by using the stream.transcode property. This creates a URL in a special format with /$!transcode.xxx at the end. Another option is to set a stream type in your .m3u playlist, which creates a URL in a special format with /$!stream.xxx at the end.

These special URL formats are used for MinimStreamer internal purposes only and for the UPnP case only. The '$!' suffixes should not be added by the user. (This is what I meant by hand-editing.) The only supported and tested way to define transcoding settings and stream types is by using the settings mentioned in the previous paragraph and described in the MinimStreamer documentation.

Transcoding is not currently supported when MinimStreamer is being used with a internet radio receiver (the MinimRadio case). It might be possible to make this work if it becomes necessary. This would require designing a user interface to support this, adding suitable user instructions to the documentation, and doing some testing with internet radio receivers.

Thanks, but I'm clearly still missing something fundamental.

I have minimserver & minimstreamer installed. I use them for UPnP and now for Internet Radio to resolve the BBC HLS issue. I understand these work separately. However, if I put a transcode in for aac for a UPnP purpose, Internet Radio stops working.

So are you saying I need two completely separate instances of minimserver/streamer because I can't have UPnP and Internet Radio in the one instance? I'm not quite sure how I'd do that, but I'm sure I can find out if I really need to.

[Redhanded]

(20-02-2015 08:41)simoncn Wrote:  

(20-02-2015 00:43)Redhanded Wrote:  No, I had been restarting minimserver but didn't realise that a rescan was necessary.

I did a rescan and it started working!

This is mentioned in the instructions but perhaps I need to give it a bit more prominence.

I confess I tend to jump in and try things out without giving instructions the attention they deserve...

[Pastim]

You are in What Hi-FI (via Naim) as well.

Code:

http://www.whathifi.com/news/listeners-complain-about-changes-to-bbc-internet-radio-streaming

Again, well done for being so quick.

[simoncn]

(20-02-2015 10:12)Pastim Wrote:  Thanks, but I'm clearly still missing something fundamental.

I have minimserver & minimstreamer installed. I use them for UPnP and now for Internet Radio to resolve the BBC HLS issue. I understand these work separately. However, if I put a transcode in for aac for a UPnP purpose, Internet Radio stops working.

So are you saying I need two completely separate instances of minimserver/streamer because I can't have UPnP and Internet Radio in the one instance? I'm not quite sure how I'd do that, but I'm sure I can find out if I really need to.

I understand the problem and I will think about how to solve it without requiring the user to create a separate instance.

[Pastim]

(20-02-2015 18:10)simoncn Wrote:  

(20-02-2015 10:12)Pastim Wrote:  Thanks, but I'm clearly still missing something fundamental.

I have minimserver & minimstreamer installed. I use them for UPnP and now for Internet Radio to resolve the BBC HLS issue. I understand these work separately. However, if I put a transcode in for aac for a UPnP purpose, Internet Radio stops working.

So are you saying I need two completely separate instances of minimserver/streamer because I can't have UPnP and Internet Radio in the one instance? I'm not quite sure how I'd do that, but I'm sure I can find out if I really need to.

I understand the problem and I will think about how to solve it without requiring the user to create a separate instance.

Good, and thanks for your patience with me.

[withanee]

(19-02-2015 23:42)withanee Wrote:  

(19-02-2015 23:26)simoncn Wrote:  

(19-02-2015 22:24)withanee Wrote:  I'm having a similar problem to redhanded, with minimserver installed on a ReadyNAS DuoV2 and trying to play to my Sonos system. All the minim parts appear to be installed correctly and running, but I also get an error from my Sonos controller, station not found.

As an example, my custom radio station URL in Sonos is:
http://192.168.1.11:9790/minimstreamer/*/R3

and the error log says:
MinimServer[NAS_A] is running
HTTPSource: unknown host for URL http://a.files.bbci.co.uk/media/live/man...three.m3u8
This is repeated several times before presumably giving up.

PS. I am using your sample BBC Radio.m3u file that is linked from your Internet radio how-to guide.

Any suggestions as to what I might have done wrong?

The "unknown host" error means that your NAS can't contact the BBC server. Do you have a firewall on your NAS or router that is blocking this connection?

One other possibility: are you located in the UK? This stream is for UK users only.

Thanks for the speedy reply Simon. Yes, I'm in the UK. I don't believe my router is blocking the connection as I can stream from the same URL via VLC player on my PC. As for whether the ReadyNAS has a firewall, I don't know, and will have to investigate. I can't recall seeing any settings for one in the Dashboard.

Now working beautifully on my ReadyNAS Duo v2, with Sonos! Not completely sure what has made it work now, but after experimenting with different DNS settings in teh NAS then putting them back as before, switching DNLA off and then back on again, and ultimately rebooting the NAS(!), it is able to access the BBC streams and is passing them on wonderfully to my Sonos. (It wasn't the rescanning on restart that did it though - I had tried rescanning via Minimwatch several times.)

Many thanks Simon for your wonderful software. A donation will be on its way to you soon.

[Santelises]

Since upgrading to the latest release of Minimstreamer/Minimserver I am seeing some issues with MinimWatch starting and stopping Minimserver running in my Synology 710+. I am also having a problem attempting to stream the new BBC streams to my renderer OPPO BDP105. This is an example of what I found in the log, but I see the same message for each attempt to play each BBC station:

HTTPSource: no working stream URL found in http://a.files.bbci.co.uk/media/live/man...extra.m3u8
Chain: error stopping chain
java.lang.NullPointerException
at com.minimstreamer.HTTPRequestTarget.stop(HTTPRequestTarget.java:109)
at org.jstreamer.core.ChainTarget.stop(ChainTarget.java:61)
at org.jstreamer.core.ChainImpl.stop(ChainImpl.java:121)
at org.jstreamer.core.TargetChain.stop(TargetChain.java:50)
at org.jstreamer.core.ChainImpl.stop(ChainImpl.java:121)
at org.jstreamer.core.ChainImpl.startLinks(ChainImpl.java:85)
at org.jstreamer.core.ChainImpl.start(ChainImpl.java:53)
at com.minimstreamer.Streamer$NetworkRequestHandler.processRequest(Streamer.java:15​60)
at com.minimserver.Server$StreamerRequestHandler.processRequest(Server.java:17585)
at org.jminim.lib.HTTPConnection$WriterThread.runWriterThread(HTTPConnection.java:4​52)
at org.jminim.lib.HTTPConnection$WriterThread.run(HTTPConnection.java:412)

[PhilD]

(20-02-2015 10:08)simoncn Wrote:  

(20-02-2015 09:59)PhilD Wrote:  Good question, the clients are in different rooms so I only heard the i83 stuttering before stopping the stream. I'm currently at work so I'll try to recreate the problem tonight or over the weekend then report back.

Phil

Thanks very much!

I've had the chance to play now and managed to recreate the dropouts, making the following observations:

1) If I stream from the pi to either Logitech Media Server (LMS) or the i83 alone, everything works perfectly. I can monitor the buffer on the i83 and it remains full 99% of the time with only tiny dips from time to time.

2) If I stream to LMS then start streaming to the i83 I get frequent dropouts on the i83 but LMS continues to play perfectly. The buffer on the i83 constantly fluctuates, reaching 0 a couple of times per minute. If I stop streaming to LMS the i83 dropouts and buffer fluctuations continue.

3) If I stream to the i83 and then start streaming to LMS both play perfectly. The i83 buffer behaves the same as in scenario 1) above.

A final observation, both LMS and the i83 are a few seconds out of sync, with LMS leading.

Hope this is of some help in the diagnostics. Let me know if you'd like me to try anything else.

Thanks,

Phil

[Pastim]

(20-02-2015 18:20)Pastim Wrote:  

(20-02-2015 18:10)simoncn Wrote:  

(20-02-2015 10:12)Pastim Wrote:  Thanks, but I'm clearly still missing something fundamental.

I have minimserver & minimstreamer installed. I use them for UPnP and now for Internet Radio to resolve the BBC HLS issue. I understand these work separately. However, if I put a transcode in for aac for a UPnP purpose, Internet Radio stops working.

So are you saying I need two completely separate instances of minimserver/streamer because I can't have UPnP and Internet Radio in the one instance? I'm not quite sure how I'd do that, but I'm sure I can find out if I really need to.

I understand the problem and I will think about how to solve it without requiring the user to create a separate instance.

Good, and thanks for your patience with me.

From the point of view of an ill-informed user such as myself, having one (set of) transcode setting(s) for UPnP, and a separate set for Internet Radio (if that's ever to be supported) would be easy enough to understand and manage. They could be separate by syntax, or a separate property. I have, of course, no idea if that would be easy of difficult to implement.

Just a thought.