Default action for handling one file should be only playing that file

[Teo]

Browse a folder in Nautilus containing some audio files.

Double click on one audio file

Expected behavior: Banshee should play only that file and then stop.

Observed behavior: Banshee plays that file, and then other files taken from some playlist made of remembered files that were played in the past.

I guess the file you open is automatically added to some "default" playlist, or to the last used playlist or something. That is not the correct behavior. If the user double clicks one file he wants to play one file. If you select a bunch of files and hit Enter, then only those files should be played (one after another), not those plus some other that have been remembered automatically who-lknows-when without the user EVER asking.

If this is the way Banshee works by design and it is considered a cool way of managing music files, then maybe Banshee shouldn't be the default player for handling files double-clicked in Nautilus.

It's not safe to assume that every time a user needs to play an audio file he's going to "listen to some music".

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: banshee 2.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-19.33-generic 3.0.27
Uname: Linux 3.0.0-19-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sat May 5 11:11:46 2012
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: banshee
UpgradeStatus: Upgraded to oneiric on 2011-12-07 (149 days ago)

[Chow Loong Jin (hyperair)]

I have tried to reproduce this issue on my laptop running Ubuntu 12.04 using the
following steps, and have failed to observe the behaviour you are mentioning.

1. Double click on a file in Nautilus
2. File opens in the "File system Queue" in Banshee and begins playing
During this first time, it is the only item in the File system Queue.
3. I wait for it to complete
4. I double click another file in Nautilus
5. It appears in the File system Queue and begins playing.
(Two items in queue now)
6. Upon finishing, it just stops.
7. Exit Banshee
8. Restart Banshee, notice that the File System Queue has been cleared.

So, no, this isn't a "cool way of managing music files" as you have assumed.
Please try to avoid using such a provocative tone in your bug reports in the future.

It would also be nice to have some step-by-step instructions to reproduce the
bug, since I can't see it here.

  status incomplete

--
Kind regards,
Loong Jin

[Teo (teo1978)]

How exactly do you exit Banshee and restart it?
When I close Banshee (meaning I click on the "x" on its window bar or I chose "quit" from the Media menu), it "remains" under the volume tray icon (I mean, if I click on the volume tray icon, Banshee's controls appears under the volume controller).
And if I open it again, my file system queue is never cleared. And (at least in some cases) the queue doesn't get cleared even across reboots.

Now I cleared my file system queue manually and started all over again. I've found out how to reproduce the issue(s):

* In Nautilus, double click on file A, and wait for it to play completely and end.
* Close Banshee's window (I would expect it to exit, and forget all about the file, don't keep any queue, but whatever)
* In Nautilus, double click on file B, and wait for it to paly completely to end.
* Close Banshee's window
* In Nautilus, double click on file C, and wait for it to paly completely to end.
* Close Banshee's window
* In Nautilus, double click on file B _again_

=> observe as banshee still remembers the whole queue A,B,C, and now has gone back to item 2 in the list which was file B.

So when B is over, it goes on with file C.

If a queue has to be managed at all, default action for double clicking a file should be adding an instance of it at the end of the queue regardless of whether or not another instance already exists at some point of the queue.

(but unless some file is actually _playing_ when you double click a file, I would rather not have any queue at all and just play it; and if you select multiple files and hit Enter when nothing is currently playing, I would rather have it create a queue with the selected files than pushing them into any existing queue)....

Anyway the two certain non-opinion bugs are:
- when you open a file that had previously been open and was in the file system queue, Banshee goes back to it in the queue (and then keeps playing the queue when that file is over) instead of adding a new instance of it to the end of the queue
- file system queue is (almost?) never cleared

the second one making the first one slightly worse.

[Teo (teo1978)]

And I didn't mean to be provocative. I hypothised (not "assumed", I said "if") this issue may be the result of an intended feature, oriented to a particular use of the program (listening to music for entertainment), in which case (if that had been the case) the proper action to take would not be to change Banshee's behavior but to choose another player as the default for Ubuntu (which I still think would be a good idea anyway for other reasons, e.g. it takes ages to load).

[Chow Loong Jin (hyperair)]

On 05/05/2012 22:58, matteo sisti sette wrote:
> And I didn't mean to be provocative. I hypothised (not "assumed", I said
> "if") this issue may be the result of an intended feature, oriented to a
> particular use of the program (listening to music for entertainment), in
> which case (if that had been the case) the proper action to take would
> not be to change Banshee's behavior but to choose another player as the
> default for Ubuntu (which I still think would be a good idea anyway for
> other reasons, e.g. it takes ages to load).
>

Actually the default on Ubuntu 12.04 is Rhythmbox. Perhaps you should upgrade.

--
Kind regards,
Loong Jin

[Chow Loong Jin (hyperair)]

On 05/05/2012 22:52, matteo sisti sette wrote:
> How exactly do you exit Banshee and restart it? When I close Banshee (meaning
> I click on the "x" on its window bar or I chose "quit" from the Media menu),
> it "remains" under the volume tray icon (I mean, if I click on the volume
> tray icon, Banshee's controls appears under the volume controller). And if I
> open it again, my file system queue is never cleared. And (at least in some
> cases) the queue doesn't get cleared even across reboots.

If you stop playback, and then close the Banshee window, it will quit (complete
with controls removal from the Sound Menu). This is part of the Sound Menu
specification.

>
> => observe as banshee still remembers the whole queue A,B,C, and now has gone
> back to item 2 in the list which was file B.
>
> So when B is over, it goes on with file C.

Hmm, perhaps what needs to be done is to make the File system queue behave more
like the Play Queue, both behaviourally and visually.

Could you check if "Clear on quit" is checked in the File System Queue context
menu? (Right click the File system Queue item in the sidebar)

> [..]

--
Kind regards,
Loong Jin

[Teo (teo1978)]

> If you stop playback, and then close the Banshee window, it will quit (complete
> with controls removal from the Sound Menu). This is part of the Sound Menu
> specification.

Well, here the Banshee controls in the sound menu _never_ go away. That's why I thought it was not "quitting".

> Could you check if "Clear on quit" is checked in the File System Queue context
> menu? (Right click the File system Queue item in the sidebar)

Oh, actually it wasn't! That should be the default (I had never touched it)
Now I've checked it and it does clear when I close Banshee.

> Hmm, perhaps what needs to be done is to make the File system queue behave more
> like the Play Queue, both behaviourally and visually.

Probably

[Chow Loong Jin (hyperair)]

Oh right, I keep forgetting you're running Ubuntu 11.10. In that case, when Banshee is running, you should see a triangular indicator on the left of the Banshee icon. When it quits, the triangular indicator disappears.

[Chow Loong Jin (hyperair)]

I've forwarded this bug to the upstream bug tracker (see gnome-bugs link above). Please CC yourself to that bug to receive updates.