Rockbox Development > Feature Ideas

Implementing a Push-To-Listen system

<< < (2/2)

[Saint]:
Is it not a whole lot more practical, and courteous to simply remove your earphones?

At least one of them...surely?

I would certainly find it rude if someone would rather listen (or attempt to listen) to a conversation I was attempting to have with them through a DAP.

I also have the thought "If you want to listen to your external environment, why are you listening to a DAP in the first place?".

Alternatively, use less dampening monitors when you're in an environment that you know calls for it.

Just thoughts,



[St.]

Gliderguy:
The times I am interested in doing this I particuarly want good isolating phones- mowing the yard, for example.  Sometimes you are doing things like that and someone comes up and wants to say a few words.  Maybe my hands are already dirty and I dont want to be digging in my ears, or maybe I might even be wearing gloves. 

Maybe I am listening at home on my couch at a nice reference level and my wife wants to just say a word or two.  I am already being considerate by not blasting my choice of music on the stereo when others are in the house.

Maybe I don't like listening to crappy non isolating buds.

If this feature is totally impractical from a  programming perspective  (I have read that it requires using the same buffer for music and recording and it is potentially a programming nightmare to try to mix the two at the same time) then please just say so instead of questioning why someone might want a feature.  There are millions of people using DAPs and they all have different situations.

torne:
Whether it seems useful is much *more* relevant than whether it's hard to implement, generally; developers often enjoy the challenge of working on difficult features but they rarely implement features they consider to be useless. :)

Llorean:
It can also be helpful to have a problem fully identified. Even if someone isn't interested in your feature, if they're aware of an existing problem they may be able to address it partially or wholly with other features as the project moves forward, so looking at the whole problem (and challenging it to see why it's a problem, and why certain workarounds aren't acceptable) can help to get a better picture for everyone.

Navigation

[0] Message Index

[*] Previous page