Indeed, the original song release date or at least year should be the most prominently displayed info, as it currently still is in the song listing, and as it has been on the song pages as far as I can remember before the recent redesign (look at the legacy website, it still shows 1973). The particular release date, if available, could also be displayed to help listeners figure out why for instance the version of Tubular Bells I last heard on RP sounds weird, because it seems to have been replaced by some re-issue where Oldfield fiddled with the knobs.
I'm not a fan of anyone fiddling with "the knobs" except myself, either...
Other than this, industry rights & regs may be involved - which definitely tend to screw a scientific / historical approach, as we (sometimes suffocatingly) live in a free-market world, where even rice - the world's no. 1 food supplement - can be traded so a world majority may suffer from free and open trade to the point of starvation, while farmers are dependent on stock markets.
For us elders, yes. Maybe not to an alien consumer from outer-space, though.
In the end, I guess it is a DJs choice to date an album-release. And for simplicity, it is accepted across the industry (which is still eager selling their releases). As for historical accuracy, that's a different thing, an original release date should be mentioned somewhere, imo.
Indeed, the original song release date or at least year should be the most prominently displayed info, as it currently still is in the song listing, and as it has been on the song pages as far as I can remember before the recent redesign (look at the legacy website, it still shows 1973). The particular release date, if available, could also be displayed to help listeners figure out why for instance the version of Tubular Bells I last heard on RP sounds weird, because it seems to have been replaced by some re-issue where Oldfield fiddled with the knobs.
For us elders, yes. Maybe not to an alien consumer from outer-space, though.
In the end, I guess it is a DJs choice to date an album-release. And for simplicity, it is accepted across the industry (which is still eager selling their releases). As for historical accuracy, that's a different thing, an original release date should be mentioned somewhere, imo.
I suspect there's a volunteer position available, checking and correcting metadata on 30,000 songs.
Yes but many tracks on RP show the reissue date. It can be confusing, I agree, but the wikipedia link is right there so if it's important we can look there. Usually the error is off by decades so it's obvious that something's not right...
For us elders, yes. Maybe not to an alien consumer from outer-space, though.
In the end, I guess it is a DJs choice to date an album-release. And for simplicity, it is accepted across the industry (which is still eager selling their releases). As for historical accuracy, that's a different thing, an original release date should be mentioned somewhere, imo.
But for things like Pink Floyd, probably nobody cares that the version played here might be some remaster from 2013, it SHOULD display 1973 as it has always been the case until recently.
Yes but many tracks on RP show the reissue date. It can be confusing, I agree, but the wikipedia link is right there so if it's important we can look there. Usually the error is off by decades so it's obvious that something's not right...
Yes, for the classical songs it is dubious, the most correct thing to do would be to show both the date when it was composed and the date when the specific performance played here on RP was released.
But for things like Pink Floyd, probably nobody cares that the version played here might be some remaster from 2013, it should display 1973 as it has always been the case until recently.
When it comes to classical music, there are performers (artists), titles, and composers, and album releases. It just seems silly to name Antonio Vivaldi as an artist (performer). No?
MY thoughts are that those are the two sorts of anomalies you'll always find here. The Pink Floyd track was likely ripped from a remastered version and the system picked up that release date. They can be fixed manually but what a chore. And classical songs tend to show the composer as the artist, rather than the orchestra/band as it is with every other genre. So "released" becomes a difficult to define category; at best it's the same as Pink Floyd, where the release date is when that particular disc was released. Date it was written or first performed would be okay but is that really the "release" date? But I assume that the song metadata just doesn't have anything in that slot. Again, it could be a manual fix but what date should be in there?
Yes, for the classical songs it is dubious, the most correct thing to do would be to show both the date when it was composed and the date when the specific performance played here on RP was released.
But for things like Pink Floyd, probably nobody cares that the version played here might be some remaster from 2013, it should display 1973 as it has always been the case until recently.
Something is wonky about the release dates shown on certain song pages. After digging around, my guess is that the problem occurs when the song has no full date associated with it, but only a year.
Example 1: https://radioparadise.com/musi... â The âWhat's Playingâ page correctly shows 1973, but the song page reads: âreleased: 2013â.
Example 2: https://radioparadise.com/musi... â should be 1716 as shown in the list, but on the song page: âreleased: nullââ¦
And while I'm at it: it would be nice if the âWhat's playingâ entry in the Music menu would act as a regular hyperlink that can be right-clicked or long-pressed or shift-clicked, for instance to open it in a new tab.
MY thoughts are that those are the two sorts of anomalies you'll always find here. The Pink Floyd track was likely ripped from a remastered version and the system picked up that release date. They can be fixed manually but what a chore. And classical songs tend to show the composer as the artist, rather than the orchestra/band as it is with every other genre. So "released" becomes a difficult to define category; at best it's the same as Pink Floyd, where the release date is when that particular disc was released. Date it was written or first performed would be okay but is that really the "release" date? But I assume that the song metadata just doesn't have anything in that slot. Again, it could be a manual fix but what date should be in there?
Something is wonky about the release dates shown on certain song pages. After digging around, my guess is that the problem occurs when the song has no full date associated with it, but only a year.
Example 1: https://radioparadise.com/musi... â The âWhat's Playingâ page correctly shows 1973, but the song page reads: âreleased: 2013â.
Example 2: https://radioparadise.com/musi... â should be 1716 as shown in the list, but on the song page: âreleased: nullââ¦
And while I'm at it: it would be nice if the âWhat's playingâ entry in the Music menu would act as a regular hyperlink that can be right-clicked or long-pressed or shift-clicked, for instance to open it in a new tab.
Hello,
i hope this is the right place for this report:
Massive Paket lost with audible Streamerrors here in Germany:
â- stream.radioparadise.com ping statistics â-
100 packets transmitted, 88 packets received, 12.0% packet loss
round-trip min/avg/max/stddev = 16.550/17.124/20.222/0.550 ms
Same problem when I try it through my university account. Unfortunately no ping statistics because of the firewall restrictions. But, the dropouts in the stream are audible there as well.
It looks like Worldstream may have a load problem.
Yup this is the right place.
We've had a few complaints from Germany recently.
Hello,
i hope this is the right place for this report:
Massive Paket lost with audible Streamerrors here in Germany:
—- stream.radioparadise.com ping statistics —-
100 packets transmitted, 88 packets received, 12.0% packet loss
round-trip min/avg/max/stddev = 16.550/17.124/20.222/0.550 ms
Same problem when I try it through my university account. Unfortunately no ping statistics because of the firewall restrictions. But, the dropouts in the stream are audible there as well.
It looks like Worldstream may have a load problem.
No battery involved, it is mains all the time. Fixed ethernet 1 GB. Very fast mediaplayer.
The web based player keeps playing all the time on all devices in my house. The android app does not. It seems to loose connection at random intervals, stutters a bit and then continues.
I am sorry to stop using the app, i am a long time Radio paradise supporter and love the look and feel of the app. It is alas too unreliable. I have the same problem on my Samsung s20 ultra with the RP app.
Their might be an issue with the most recent Android update. I'll have to look into this.
But in general battery optimization is the first thing to try disabling on apps having issues.
As it has been the cause of all sorts of quirky behavior since it was introduced.
On some devices, disabling battery optimization for the app can help if it's been enabled. The setting keeps moving around, but there's usually a list of apps in phone settings.
That lets you manage which apps are battery optimized.
No battery involved, it is mains all the time. Fixed ethernet 1 GB. Very fast mediaplayer.
The web based player keeps playing all the time on all devices in my house. The android app does not. It seems to loose connection at random intervals, stutters a bit and then continues.
I am sorry to stop using the app, i am a long time Radio paradise supporter and love the look and feel of the app. It is alas too unreliable. I have the same problem on my Samsung s20 ultra with the RP app.