Request Policy

[lotus]

I just learned from Spaz that if Somebody reuqests a song from an Artist "A" now and I request a different song from this artist "A" five minutes later, the first will be played in 1 h +, but mine than only 3 hours later that that one.

So I would have to wait 4 h + for my request.

This is basically ok knowing the problems we had with overrequesters.

I see only one negative side on that: I am not notified that my reuqest would last so long. Wouldn't it be better to reject the request? Or at least (but I think this is not possible) notify when aprox. the request will be played?

[Rick and Roll]

The idea of a request is to hear a song that one wants to hear. Given the amount of programming and the "1+3" rule that lotus cites, it seems a request is not being heard by the requestor more and more frequently. Indeed, I had experienced that in the past.

Before I make my suggestion, I was under the assumption that the request IS denied when you choose the same artist. You then have to choose another song. What did I miss here?

I have a different approach to this, but I do not want to go into a long explanation because I'm not sure what is feasible by computer programs. Basically, I would like to see a requestor shut out of the next ten requests once a request is made.

Additionally, a request should be denied if the estimated time of playing is longer than three hours from the time of the request. That would take into account a show that is, say 30 minutes away. This keeps requested songs from backing up in the queue.

The actual idea is a lot more complicated than what I am saying - maybe a white room discussion sometime would be in order.

What would be accomplished by this is to have the person who requests enjoy the request, and have as many different people enjoy the feature of requesting. If we indeed have 100-175 listeners, it's really hard to justify someone requesting more than 3 times a day. In another thread, I was against a limit. But it seems to me a decent idea.

[Yesspaz]

Accidentally posted twice. Edited this one. Move on the next. I am a dork.

[Yesspaz]

Originally posted by Rick and Roll
I was under the assumption that the request IS denied when you choose the same artist. You then have to choose another song. What did I miss here?

You are denied if the artist recently played, and you get another request. But if the artist is in the queue/request pile, you are not denied. In other words, as I'm writing this, Yes "Astral Traveller' is playing. As of right now, no one can request Yes for two hours. "Your request has been denied: Artist recently played." After two hours, you can request Yes, wait an hour, Yes plays. But if someone requested Yes right before "Atral Traveller" started playing, their request would get through. "Astral Traveller" plays. Three hours later, the second Yes song plays. Either way, it's three hours. Six of one, half-a-dozen of the other.

Originally posted by Rick and Roll
What would be accomplished by this is to have... as many different people enjoy the feature of requesting. If we indeed have 100-175 listeners, it's really hard to justify someone requesting more than 3 times a day. In another thread, I was against a limit. But it seems to me a decent idea.

First, I personally don't see having 175 listeners as a hindrance to the request feature. If every single person requested in the same hour, that's 175 requests. But actually there's never more than 20 requests, and rarely more than 10 or 12. Usually it's around 5 to 7. So the fact is, most people don't request, they just listen. Until 75 people are requesting many times a day, I personally don't see an issue, but that's just my opinion (and not the opinion of anyone with any actual power). Now, I'll readily admit that I request often - once an hour if I'm around.

I say it's not hard to justify requesting more than thrice a day.

1. Everyone has the same access and privilege. Some use it. Some don't.
2. There are policies in place to stop request abuse, and abuse is the operative word. One can request as often as he or she likes (is allowed) and as long as they keep it spiced up, they're fine. That plus the 3hour rule keep variety in the playlist.

Finally, there actually currently is a limit on the number of songs one can request in a day. It's ten. I know this because I've hit that number twice (only) - those rare days when I'm in front of the computer all day. Typically, I average 3 or 4 requests a day.



In sum, the current request system (plus the advent of the RQFree Wednesday) keeps a great variety playing without any artist dominating and allows listeners to request as often as they like (or not to request as often as they like). So, my take is if it ain't broke, don't fix it.

[Rick and Roll]

I agree with all that you say, except for the point lotus brings up. The rq by the artist should just deny so there's no build up. And the rq's should drop off if not played within three hours (cause of a show, etc).

[progdirjim(Admin)]

Keep in mind we're trying to control TWO issues with the request rules - first, the overrequesting. The second is tougher - we're trying to control an artist being overplayed by accident - two (or more) people in different places requesting the same artist. This is only ever an issue for Yes, Genesis, King Crimson, Mike Oldfield, and a handful of others. In my opinion, the request feature should primarily be used to hear NEW music. Not old favorites. If you follow that rule, you're virtually guaranteed to never have a request fail or be delayed. If you want to hear a Yes song for the seventeenth gazillionth time, that's the risk you run.