Usecase dissonance

[Jon Loldrup]

There are some differences between the following use cases:

1. Listening to music
2. Listening to podcasts/eBooks

Lets have a look:
1. When listening to random music tracks, you don't want your music player to suddently start playing part of an ebook.
2. When looking through your music collection, to find the next track to play, you don't want to see your ebooks being listed, as that would be noise in that context. The opposite is the case when you want to look through your ebook-library. In that situation seeing music tracks listed would be noise.
3. Often ebooks come in a set of files. You will want to play them in order, and you don't necessarily want to auto-start the next ebook after the currently playing ebook has finished. This is more important than for the sets of tracks on music records.
4. When listening to an ebook, it is paramount to save state in between sessions. You want to start listening right where you left, in a given sound file. This is not of importance when listening to music.
5. When listening to ebooks, you don't want to be able to activate shuffled playing order. If you, by accident, activated this feature, your experience would become a complete mess and the player would instantly become completely useless to you.
6. When you want to play an ebook, and some of your ebooks happened to be divided into several files, you would prefer to have your ebook player simply abstract away the fact that your ebooks are inconveniently split up. You would want your player to simply abstract that fact away and just show you one entry per book. Not an entry per file.

Now I have some questions for the team behind Noise:

* Is Noise targeted to play only music, or both music and ebooks?
* If Noise is only for music, will Noise actively filter away ebooks from being listed? (you should, IMO).
* If Noise is intended for both, have you considered splitting Noise into two applications, so as to avoid having to create an overly complicated user interface to account for the two rather different use cases?

Regards
An elementary OS lover.

PS. Where should I ideally post a text like the one above?

[Corentin Noël (tintou)]

Thanks for your suggestion, his place is for sure on the Bluesprint section.

Now let's talk about your suggestion. I assume you are talking about audiobooks instead of ebooks.
This could be for sure be included in a plugin. (I think that the Album view is appropriate and that if an audiobook is split in several part, it's because there are chapiters).
But I also think that it needs designers input.

[Jon Loldrup (loldrup)]

Yes, audiobooks it is.

I have now filed it as a blueprint:
https://blueprints.launchpad.net/noise/+spec/usecase-dissonance

regards
Jon Loldrup

On 12 December 2012 18:47, Corentin Noël <email address hidden> wrote:

> Thanks for your suggestion, his place is for sure on the Bluesprint
> section.
>
> Now let's talk about your suggestion. I assume you are talking about
> audiobooks instead of ebooks.
> This could be for sure be included in a plugin. (I think that the Album
> view is appropriate and that if an audiobook is split in several part, it's
> because there are chapiters).
> But I also think that it needs designers input.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1089456
>
> Title:
> Usecase dissonance
>
> Status in Noise Audio Player:
> New
>
> Bug description:
> There are some differences between the following use cases:
>
> 1. Listening to music
> 2. Listening to podcasts/eBooks
>
> Lets have a look:
> 1. When listening to random music tracks, you don't want your music
> player to suddently start playing part of an ebook.
> 2. When looking through your music collection, to find the next track to
> play, you don't want to see your ebooks being listed, as that would be
> noise in that context. The opposite is the case when you want to look
> through your ebook-library. In that situation seeing music tracks listed
> would be noise.
> 3. Often ebooks come in a set of files. You will want to play them in
> order, and you don't necessarily want to auto-start the next ebook after
> the currently playing ebook has finished. This is more important than for
> the sets of tracks on music records.
> 4. When listening to an ebook, it is paramount to save state in between
> sessions. You want to start listening right where you left, in a given
> sound file. This is not of importance when listening to music.
> 5. When listening to ebooks, you don't want to be able to activate
> shuffled playing order. If you, by accident, activated this feature, your
> experience would become a complete mess and the player would instantly
> become completely useless to you.
> 6. When you want to play an ebook, and some of your ebooks happened to
> be divided into several files, you would prefer to have your ebook player
> simply abstract away the fact that your ebooks are inconveniently split up.
> You would want your player to simply abstract that fact away and just show
> you one entry per book. Not an entry per file.
>
> Now I have some questions for the team behind Noise:
>
> * Is Noise targeted to play only music, or both music and ebooks?
> * If Noise is only for music, will Noise actively filter away ebooks
> from being listed? (you should, IMO).
> * If Noise is intended for both, have you considered splitting Noise
> into two applications, so as to avoid having to create an overly
> complicated user interface to account for the two rather different use
> cases?
>
>
> Regards
> An elementary OS lover.
>
> PS. Where should I ideally post a text like the one above?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad...

[Danielle Foré (danrabbit)]

Invalidating this report since it was superseded by a blueprint.

OP, in the future please file a separate ticket for each problem you have. Multi-bug reports like this one are not possible to track, making it unlikely that developers will be able to complete them.