elisa-developers team mailing list archive

[David McLeod <daiode@xxxxxxx>]

Just for my 2 cents worth after seeing this type of discussion on a lot of media related projects....


Volume
It is best to offer 'single' presses that allow for a small incremental change. This is for volume up particularly.
if the remote can support it... 'press and hold', or 'double tap' presses to jump the volume in greater increments.

Ideal interaction:
single press: 	+1 volume increment
Double tap: 		+2 / +3 volume increments 
Press n hold: 	max vol / min vol in 0.5 second? (extrememly useful for when you want to -vol quickly... effectively muting your system uber quick).


Seeking
Understanding there are a lot of Linux users here. I tend to look at the more popular media players (iPod's) and various desktop media apps.
Here we see a combo button on the OSD (we have this glyph/icon button on the Moovida OSD currently) that combines both next/prev on a single press and when held... it seeks (same for physical buttons on the remote). 
Usually in the desktop environment, outside of DVD player apps, the seeking is one speed. Meaning, you hold the button and it FFWD's or RWD's at one speed. 
In a media center environment, I feel it is best to invoke a press n' hold scenario whereby, the longer the button is held down, you get a faster rate of seeking. (This was discussed in the past, think the max speed to go up to was x64? Florian?)

Ideal Interaction (FFWD):
Single press: 	jumps to next video/track (e.g. next episode)
Press n hold: 	seeks... longer its held, rate of seeking increases.

Ideal Interaction (RWD):
Single press: 	goes to beginning of video/track, press again during first second of playback to go to previous (e.g. previous episode)
Press n hold: 	seeks... longer its held, rate of seeking increases
Double tap:		Think it is Meedios that does this with an Apple remote... double tap say RWD and it jumps back 20s. 

*For more advanced / geeky options, I always wanted to have these made available via a 'cog' glyph on the OSD to do things like chapter selection etc... basically stuff 'normal' people wouldn't be using everyday.


Is all of the above available with a remote? I'm not sure. Via the OSD I don't see why not. My experience of what is possible with an IR remote is on Mac OSX and the Apple remote which provides a lot of opportunity to do multiple things with the buttons, single press, double press, press n hold: they can do different things and different interactions can be set for each. (e.g. via the Menu button a single press goes back one page... press and hold to go all the way back 'x' number of pages to the Main Menu).

David


On 18 May 2010, at 22:17, Paul van Tilburg wrote:

> Hi!
> 
> On Tue, May 18, 2010 at 09:32:44PM +0100, Peter wrote:
>> On Mon, May 17, 2010 at 9:33 AM, Olivier Tilloy <olivier@xxxxxxxxxx> wrote:
>>> When this was implemented, the idea was to mimic the behaviour of the
>>> gnome-volume-control applet. It is the opposite of what you write
>>> though: one may want to decrease the volume quickly and then fine-tune
>>> it by increasing it in small steps.
>> 
>> This surprised me when I first found it, until I realised it was done
>> on purpose and I could see the point. It probably confuses some
>> folks but I don't recall seeing it discussed much on the forum.
> 
> LOL, so for me and my friends/family the situation is reversed. My brains
> just cannot get used to it because sometimes you also want to decrease
> slightly but it won't.  There are actually more cases where I want to
> have decrease it slightly than when I want to decrease it fast.  I have
> changed them to 0.10/0.10 for my setup now.
> 
>>>> Yes, it's definately a step forward, one minute is a lot to have as
>>>> most fine-grained.  However, IMO it's hard to get an agreement here,
>>>> it's all about expectation here and this is often not shared.  Maybe
>>>> 20/20 is fine and we need to propagate this to a setting?
>>> 
>>> Both pairs of values are fine by me, let's see what others reckon. And
>>> Peter seems to be willing to write a more complete patch to make this a
>>> configurable setting, which would be great!
>> 
>> I've now tried the 10s/30s version and I didn't like it. It is fine for just
>> going back or just going forward, but for jumping about in a video or
>> music track I found it far more intuitive to have the left/right buttons
>> move by the same amount. 
> 
> I only just go back and forward.   What is an example use case of
> jumping back and forward through a video?  I am genuinely curious.
> 
>> I found it very disconcerting that pressing
>> left N times then right N times did not return to my starting point.
> 
> But for volume you say:  until I realises it was done on purpose and
> I could see the point.  
> 
> By the way, I am not critising you in anyway; I am interested in
> understanding the different usages.  The ones I share here are a
> combination of experiences of myself and my housemate, who obviously use
> it regularly and have known Elisa/Moovida for a long time, friends that
> visit regularly, but also of friends/family that often use it for the
> first time.
> 
>> I would vote for making this 20s/20s right now, with the plan to make
>> it configurable later (perhaps making the volume settings configurable
>> too at the same time?).
> 
> Definately! 
> 
> Paul
> 
> -- 
> PhD Student @ Eindhoven                     | email: paul@xxxxxxxx
> University of Technology, The Netherlands   | JID: paul@xxxxxxxx
>>>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~elisa-developers
> Post to     : elisa-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~elisa-developers
> More help   : https://help.launchpad.net/ListHelp