Bugzilla – Bug 1607
Analog VU screensaver should show now playing at start of each track
Last modified: 2008-06-03 14:48:55 UTC
I love the Analog VU screensaver and have it set to turn on after 30 seconds. However, I like to know what each new track is called, so constantly have to press Now Playing when a new track starts. There should be an option to make the screensaver interrupt every time a track start event is fired. Note, I don't just want the track information to be inserted into the screensaver - visualiser does this, but it's generally to small to be read from across the room.
Ever since I started using my Squeeze I thought this feature would be great. The Analog VU is dope but knowing what track I'm listening to is also important. Great idea!
how about a showBriefly on a trackStartEvent ? Lets say 3 seconds at each event. I cna make it a pref to show or not if that's desired. Dean can assign to me with comments on specifics, and I'll take care of it if that idea fits.
Sounds reasonable, but let's hold off post 6.1
Great suggestion! Maybe whatever new code is put together for this could be made available for all graphical screensavers? A "toast" option, set globally in Now Playing or in the Visualizer Plugin options dialog?
refer to bug 1901. there is a first crack at some other settings for the visualiser. may or may not be right to include there, and still no final word on the design. many other priorities at the mo, at least for me.
No rush on my part... It's only a feature request, not a bug. Do we want to mark this request as a duplicate of 1901, for the sake of keeping things tidy?
No - this bug is in no way a duplicate of #1901!
please relax, Max. There are several aspects that overlap. No need to get excited about dupes. They are used for a good reason. Bugzilla is, and always will be, a developer tool. If a developer wants to have it combined into one task, then so be it. There is little point in having an option just for the analog vu, and not for the others. Obviously, as it the case for every freaking feature, it will have to be an option....thus the link as a set of vis prefs. At this point, my prediction is that the it is going to end up being me that eventually writes this stuff in, and I can certainly so that in that case, it will be combined. I can 't see any reason to have the features distinct...thus in SOME way, they are indeed dupes. However, since I am not working on this, and it is not flagged for 6.2 or 6.5, it can just left alone for "future".
My understanding of these bugs is that they're for different things, and therefore shouldn't be duped. However, I'm not overly excited either way. The point of this bug is to have the screensaver stop completely when a track changes, allowing the Now Playing screen to show. After, say, 15 seconds the screensaver should then start again. The point of the other bug is to have the screensaver run continuously, but to have an option of whether to periodically display some now playing information as part of the screensaver. The analog vu never displays this text anyway, so the option isn't relevant.
That's a very different implementation than I had in mind. I wasn't planning to kill the screensaver, etc. Now that you mention it, it isn't very difficult to do that. Nuisance part is the potential need for a different timer, for users that have some long screensaver timeout and only want, say, 5 seconds interruption on track start. I'm so jaded now, my motivation just dies whenever I have to consider the infinite list of new prefs just to add a tiny little feature like this. Implement one enhancement, wait for 6 new ones as a result. :) Keep talking implementation. A fully designed idea is much easier to actually write.
This is an interesting feature; I'll vote for it. Now that I think of it, I recall choosing not to use the meters screensavers as track info was not displayed upon track change. A generalized mechanism might be better than forcing Now Playing - perhaps a "Choose a screensaver to use on track changes" setting. Where users can specify their choice. I suppose a time duration could accompany this too, but seems lower priority.
Have you looked at my SaverSwitcher plugin? http://www.tux.org/~peterw/slim/SaverSwitcher.html
This plugin looks great.