0
Fixed

When adding by URL, edits to "Name" and "Genre" are not preserved

sergeymk 12 aastat tagasi uuendaja Jona (Lead Developer) 11 aastat tagasi 1

I am on Nexus 4, jelly bean, but I believe this issue has been around for a year or more (I had a different phone then).


I am a longtime XiiaLive Pro user -- thanks for the great software.


When adding a station to favorites using a URL, Xiia pulls in the station "name" and "genre" if available. It then immediately shows you the station properties, offering to change the "name" and "title. However when you save this, any changes you've made are ignored. So you have to go back, find that station you've added, and change everything again. On second try it saves your edits. But this is a big time sink, to have to edit twice on the phone. If you could please fix this bug, I would greatly appreciate it. 


As an example you can use the following stream:


http://www.kqed.org/radio/listen/kqedradio.m3u

Vasta

Vasta
Fixed

UPDATE 06/18/13: 

Issue has been resolved. Will be part of release v3.0.2.3.

Kavandatud

Thanks for the post. I have tried doing what you said and it worked just fine for me. Just to confirm here is what I did.


1. Add the URL you provided as a favorite.

2. Edit the name and genre and save.


Something to note is that if you already previously played the station and you try adding it to favorites via the "+ ADD URL" option it will fail to save any changes. This is a bug for sure in that case and I'll fix it.

Yes you are exactly right with respect to the "previously played" bug. The problem I am experiencing only manifests itself if I am adding to favorites by URL, and that station already exists in "history". This is a pretty typical situation, because I would usually "test" a stream to make sure it works, check the bitrate and codec etc, before adding to favorites. So the bug affects me almost every time.

Fixed

UPDATE 06/18/13: 

Issue/Bug has been resolved. Will be part of release v3.0.2.3.

Vasta
Fixed

UPDATE 06/18/13: 

Issue has been resolved. Will be part of release v3.0.2.3.