# Track does not return radio stream title

**URL:** <https://discourse.mopidy.com/t/track-does-not-return-radio-stream-title/4224>\
**Category:** Misc\
**Created:** [August 11, 2020, 10:14am UTC](https://discourse.mopidy.com/t/track-does-not-return-radio-stream-title/4224 "2020-08-11T10:14:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gkzsolt](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/gkzsolt/32/1670_2.png) [@gkzsolt](https://discourse.mopidy.com/u/gkzsolt)\
**Post date:** [August 11, 2020, 10:14am UTC](https://discourse.mopidy.com/t/track-does-not-return-radio-stream-title/4224/1 "2020-08-11T10:14:37Z")

</div>

I am playing some radio streams, by putting their url-s in a playlist like this:  
In file `Internet Radio.m3u`:

```
 http://prem4.radiotunes.com:80/soundtrack
 http://prem2.radiotunes.com:80/other-station

```

The stream is played, but no stream info is gathered into the Track objects returned by mopidy. This worked in mopidy 2, my client could get a stream name/title to which it updated the ui; now (on mopidy 3) this is gone, the only attribute of the returned Track is the uri. What can I do here?

I also don’t know how to parse some .pls files, given by my radio streaming service. I’ve read that Mopidy _can_ parse these, but have no idea how. There is no one example, the documentation is very succint at some places.

Many thanks,

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [August 11, 2020, 10:52am UTC](https://discourse.mopidy.com/t/track-does-not-return-radio-stream-title/4224/2 "2020-08-11T10:52:46Z")

</div>

Need more information. What frontend, what commands are being used?

Also, in which version of Mopidy 2 did this work?

---

<div class="post-metadata">

**Author:** ![gkzsolt](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/gkzsolt/32/1670_2.png) [@gkzsolt](https://discourse.mopidy.com/u/gkzsolt)\
**Post date:** [August 11, 2020, 1:25pm UTC](https://discourse.mopidy.com/t/track-does-not-return-radio-stream-title/4224/3 "2020-08-11T13:25:24Z")

</div>

Sorry, I have to take back my stance 😉 I am developing my own front-end, and got a bit mislead by my mistake. But it is OK now, the track reports the station name from the stream, and everything works.

Btw, do you know how can I parse a .pls file with mopidy?

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [August 11, 2020, 2:07pm UTC](https://discourse.mopidy.com/t/track-does-not-return-radio-stream-title/4224/4 "2020-08-11T14:07:28Z")

</div>

We have internal methods to parse .pls files which are used by the Stream Backend. If you play a stream that points to a .pls file, that playlist file will be parsed and the first working URI found is used for playback. Other Backends (e.g. Mopidy-TuneIn) define their own implementations for parsing .pls files. But we do not have anything in the Core API to expose that functionality to frontends.

I guess we could have a Mopidy-PLS backend, which provided the tracks similar to Mopidy-M3u. But nobody has written that (yet).

---

<div class="post-metadata">

**Author:** ![gkzsolt](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/gkzsolt/32/1670_2.png) [@gkzsolt](https://discourse.mopidy.com/u/gkzsolt)\
**Post date:** [August 11, 2020, 2:16pm UTC](https://discourse.mopidy.com/t/track-does-not-return-radio-stream-title/4224/5 "2020-08-11T14:16:03Z")

</div>

Thanks. To play the first URI is not so interesting, a Mopidy-PLS backend, as you suggested would be more useful. But I don’t think it’s important, either.
