elisa-developers team mailing list archive

[David Mcleod <daiode@xxxxxxx>]

Can imagine your frustration if you single press FFWD and go to the next episode in a Season.

Although, this interaction is eased somewhat if / when you go back it asks you if you want to pick up where you left off from last time you viewed (which in reality was 2 seconds ago after you swore at yourself :p).

Unwatched/Half watched videos and the ability for the app to ask you if you would like to carry on from where you left off is another feature discussion.
I also agree about your Chapter selection methodology... it is how I saw it also. Thing is most ripped videos dont have chapter markers so, it would have to default back to say a thumbnail image every 5 minutes perhaps as 'pretend' chapters.

Anyway... not to alter the direction of this email thread with those feature ideas.


On 18 May 2010, at 23:23, Peter wrote:

> On Tue, May 18, 2010 at 10:59 PM, David McLeod wrote:
>> 
>> Just for my 2 cents worth after seeing this type of discussion
>> on a lot of media related projects.... [snip] ... volume ... [snip]
>> ... seeking ... [snip] ... Is all of the above available with a
>> remote? I'm not sure. ... [snip]
>> David
> 
> Hi David,
> 
> I share many of those views, and have tried some of this in
> Moovida with mixed success. See the forum thread
> referenced at the start of this email discussion for more:
> http://www.moovida.com/forums/viewtopic.php?f=8&t=1696
> 
> I do however completely disagree that a single press of
> left/right should jump to the start of the current/next episode
> or track. This is really annoying if done by accident in the
> middle of a TV show or a long music track. This happens to
> me sometimes with my DVD remote (all the buttons are the
> same shape) when I hit a chapter skip button by mistake.
> 
> I have some ideas for chapter navigation too which are related
> to this, but perhaps best for another thread. Essentially I'd
> use a menu where you pick from automatically generated
> thumbnails. Actually writing the code is beyond me though :(
> 
> For now however, it looks like we have a consensus that making
> single presses of left/right seek back/forward by 20s is a good
> improvement over the current rather limited functionality (which
> jumps 60s).
> 
> Peter