Messages

Hi.
I thought this might be interesting for people here, either as an external tool or including it inside GMB. I haven't tried it myself but looks interesting.

http://beets.radbox.org/

Cheers.

Actually, I use it mainly in (but not limited to) random mode. While listening to a random playlist sometimes I have a song of the day following my mood that I like to hear now and then, so I queue that song when I feel like I'm wanna hear it again but then I have to take action to avoid entering an infinite loop. :D

I agree with the other comments, the queue is useful to jump to another song in the playlist without cutting the one playing. So I think it would be better adding a new mode than replacing the current one.

I would suggest to consider how good it would be to add a "play next" command that would have the same operation than normal queue mode has now. It might be more useful and intuitive than using the queue for that, maybe not.

Hi. I'm not sure what's the intended mode operation for the queue in normal mode, but I thought it would play all enqueued songs and go back to the play list at the point where it jumped to play the queue. I don't know if older GMB versions did this or it's my imagination. Now, enqueuing a song jumps to that song in the play list.

Let's say my playlist has songs A, B, C, D, E, F,... and while A is playing E is sent to the queue, I would expect to hear A, E, B, C, D and so on. Instead I hear A, E, F,...

I've given it a spin in my head after reading bardo's post.

When adding directories to the library we should annotate the first mount point going up the directory tree. Mount points can be taken from /proc/mounts.

When searching for updated/deleted songs we should check if the mount point for the directory is mounted. When it's not we should ignore that directory.

Removing the songs when that mount point doesn't exists anymore would be possible just deleting that directory from the library.

Problem is, what happens when we add a directory containing mount points? We should break it down into several directories (or alternatively, ignore anything inside a mount point not being the directory added by the user). We could do it internally and show the internal mount points just when they're gone, with a warning to let the user remove them from the library. This is maybe the hardest part.

I don't know if this has been already reported. When you have two albums with the same name and different artist the album browser messes when I double click one of of them. The list of songs shows the album I want but it starts playing both albums from both artists. I'm using last git version.

The same happens for removable media, external hdd, etc., and in such cases I've hit another problem. Scanning for new/deleted songs when it's not mounted will erase all the songs there and then they have to be re-added the next time it's mounted. Detecting that the volume isn't mounted and ignoring those songs in the library when scanning would be great.

Thanks, this fix is good enough. Still, muting/unmuting volume in gmb did re-set the volume, but it's not important for me as I never do it, I just noticed it when testing the fix.

I have some files than I don't want to be played normally, interviews, segues, bad sounding tracks,... The way I keep them from playing is tagging them as dontplay or something more specific, then I setup a new filter than doesn't ever play files with these tags.

Doing this change on the latest git version returns these errors when pressing play and playing doesn't start:

*** unhandled exception in callback:
***   type GStreamer::Pipeline does not support property 'flags' at /usr/bin/../share/gmusicbrowser/gmusicbrowser_gstreamer-0.10.pm line 105.
***  ignoring at /usr/bin/gmusicbrowser line 1164.
*** unhandled exception in callback:
***   Can't call method "get_name" on unblessed reference at /usr/bin/../share/gmusicbrowser/gmusicbrowser_gstreamer-0.10.pm line 181.
***  ignoring at /usr/bin/gmusicbrowser line 1164.

Thank you very much, you pointed the flaw. I didn't remember about the volume bar in gmb, the layouts I use don't have it.

So, the problem is that I can't control the volume level from the pulseaudio icon tray since it gets overriden by the gmb level setting everytime a song starts. While pulseaudio gets the volume updates from gmb, gmb doesn't get the volume changes done from the pulseaudio volume control, thus gmb resets volume every new song.

Thanks for answering. It happens just with gmb, I've tried changing volumes from the pulseaudio-mixer for Totem and VLC but they never get saved/restored. It's pretty annoying since volume resets with every song change making the soft volume useless. Do you know where this volumes may be saved?

I'm using pulseaudio 0.9.21-3 in a Debian Sid.

Hi.

I've just noticed this today. I was using a recent git version and I've updated to the latest right now to try. When I start gmb the volume goes automatically to 90% from whatever level it had, I adjust it with the multimedia keys or from the volume tray icon and whenever a song starts it resets again to 90%. I use the gstreamer backend with pulseaudio, it doesn't happen with other backends.

I have no idea where's the fault, anyone?

The problem I see with the current logo is that at small sizes it gets unrecognizable, it becomes a cloud of dark pixels. The current icon is good at medium/big icon sizes, but a small version enhanced for small icon sizes would be more suitable for the tray, IMHO.

It might seem a crazy idea, but there's this big music library called Jamendo (http://www.jamendo.com) that I'd like to access from gmbrowser. There's an API to it (http://developer.jamendo.com/en/) and there's some players that support it although I haven't tried any of them, maybe someone else has. I don't know how difficult would it be implementing this backend in gmb but I think it would be a cooler feature than radio streaming and it would integrate better into gmb.

Ok, thank you for the hint, I'll do a bit of research.