TuneBar The driving concept behind TuneBar has always been its simplicity and unobtrusive design. Accessible in ways that provides iTunes control and information within mere seconds, TuneBar 3 is going to take your iTunes experience to a whole new level.
What's New
Version 3.6.1:
Resolved issue with TuneBar 3.6 which prevented in running on systems earlier than 10.5.8.
Requirements
PPC / Intel, Mac OS X 10.5 or later, iTunes 7.4 or later Growl (only if you plan on using Growl for your Notifications).
I renamed TuneX to TuneBar back in February 2007 so this is far from a recent change. The reasons for changing though were due to me becoming aware of a company in Europe owning the rights to the name "TuneX". I decided to change the name to avoid any kind of legal issues.
I have just checked TunesBar out and see that its version 1.0 was released about 1 year and 4 months after I renamed to TuneBar.
I purchased TuneBar when it was called TuneX. I have not used it in a long time and happened across it today. I can't find my registration number, so I was wondering if there is a way to email you directly to solve this?
Thanks for your time.
Why would the developer of TuneX rename his app to TuneBar when there's already an app called TunesBar with similar functionality?
Where has the originality gone these days?
I emailed the author about this but received not reply. It appears that using TuneBar to switch playlist doesn't actually switch the playlist in iTunes.
If I start a playlist in iTunes and then use TuneBar to switch to another playlist that part works. However, if I pause the tune in the new playlist when I unpause it the paused tune does not resume. Instead the original playlist starts over.
To Ivanovitch: I run TuneBar (2.7.2) on a dual monitor set up and it seems fine. This is on a DP G5, not an Intel. I also have it installed on an MacBook Pro, but I haven't used it there other than to start it up, set my preferences, and make sure that it worked.
Can you be more descriptive about the instability you see?
One thing I did notice is that if you use the standard TuneBar notification (instead of growl), then it does assume the left side monitor isn't there (it slides the notification off the right monitor and onto the left monitor). However, that's not a really a problem, and if you switch to using Growl notification, then it's not an issue at all.
In terms of the CPU issues I saw with earlier versions, that seems to be resolved. I still see CPU usage spike up, but that's to be expected. The constant CPU usage I saw before isn't happening.
Warning: not just unstable, but doesn't play nicely with dual-screen setups (plugging in an extra monitor causes problems, removing a monitor causes system instability).
I have just received a number of emails since releasing 2.6.2 stating that a few bugs seem to have surfaced for some people. If your experiencing any kind of problems with this version of TuneBar could you please email me any details of your system that you feel will be useful and I will fix the problem as soon as possible.
this program is pretty slick - i like the GUI design and its functionability
my one suggestion would be this:
add hotkeys for volume control!!! you have hotkeys for everything else, so why shouldnt you be able to adjust the volume the same way?
this is the only thing keeping me from making this my main itunes window program - right now i am using x-tunes and it has everything i need but the GUI is ugly as hell and i would much rather use TuneX.
Hmm, since you posted your initial bug report I have isolated where this problem is, but have not yet been able to fix the problem. On my computer I have never had this problem so have been unable to fix it as quickly as I would have liked. Thankyou for pointing it out though.
-uses alot of cpu
-menu bar displays either track or artist, i would like it to be both at the same time
-when the hotkey to show the controller is pressed, you have to go back to the mouse and click in the search part to actually search. you should just be able to start typing.
I purchased this a while ago. Nice app. However, I'm still using v2.5. The past two releases, 2.6 and 2.6.1 both consume a lot of CPU relative to 2.5. When you fire up 2.6+, both the TuneBar process AND a process called System Events start consuming 5-10% of the CPU each! This is on a DP 2.0 GHz PowerPC G5.
I'm assuming this has something to do with the "Sparkle Integration" mentioned in the 2.6 release notes.
I wrote directly to the developer when I saw this happen with 2.6, but did not receive a response.
I do not believe I have received any such email in the past few days (though there have been a lot of problems on my connection lately).
I will look in to this problem that you have encountered, though I do not see how the integration of sparkle could have caused this, though you never know and its best to check these things out.
Please login or create a new MacUpdate Member account to use this feature
Watch Lists are available to MacUpdate Desktop Members Upgrade Now
Download and auto-install
using MacUpdate Desktop. Save
time moving folders and cleaning-up.
TuneBar The driving concept behind TuneBar has always been its simplicity and unobtrusive design. Accessible in ways that provides iTunes control and information within mere seconds, TuneBar 3 is going to take your iTunes experience to a whole new level.
I have just checked TunesBar out and see that its version 1.0 was released about 1 year and 4 months after I renamed to TuneBar.
Thanks for your time.
+100
Where has the originality gone these days?
+59
+34
If I start a playlist in iTunes and then use TuneBar to switch to another playlist that part works. However, if I pause the tune in the new playlist when I unpause it the paused tune does not resume. Instead the original playlist starts over.
+1
Can you be more descriptive about the instability you see?
One thing I did notice is that if you use the standard TuneBar notification (instead of growl), then it does assume the left side monitor isn't there (it slides the notification off the right monitor and onto the left monitor). However, that's not a really a problem, and if you switch to using Growl notification, then it's not an issue at all.
In terms of the CPU issues I saw with earlier versions, that seems to be resolved. I still see CPU usage spike up, but that's to be expected. The constant CPU usage I saw before isn't happening.
+39
Thanks,
Tom
my one suggestion would be this:
add hotkeys for volume control!!! you have hotkeys for everything else, so why shouldnt you be able to adjust the volume the same way?
this is the only thing keeping me from making this my main itunes window program - right now i am using x-tunes and it has everything i need but the GUI is ugly as hell and i would much rather use TuneX.
Can I ask how much CPU usage your getting? I'm getting around 1% on my computer. What kind of computer do you use, what software are you using.
As for the other issues I will look in to these, and correct them.
Tom Hancocks
-2
typically not a very fast computer, imac g4 1.25ghz 512mb of ram
ill admit my trial of tunex somehow ran out, even though i used it for maybe half an hour
i can remember how much it was though
while just sitting around the app took up maybe 1%-5%
and when the little bar thing is activated it shot up to50-75%
for generally use its bearable, but if i try to open it up while doing something the whole computer hangs.
-2
attentionwandered reviewed on 17 Jul 2006
a few inconsistancies i noticed though
-uses alot of cpu
-menu bar displays either track or artist, i would like it to be both at the same time
-when the hotkey to show the controller is pressed, you have to go back to the mouse and click in the search part to actually search. you should just be able to start typing.
whenever I search for a song, nothing happeny
no matter which preference setting - search function doesn't work at all.
As to me this would be the killer feature, I have to delete the app and use SizzlingKeys again
+1
I'm assuming this has something to do with the "Sparkle Integration" mentioned in the 2.6 release notes.
I wrote directly to the developer when I saw this happen with 2.6, but did not receive a response.
Rob
I do not believe I have received any such email in the past few days (though there have been a lot of problems on my connection lately).
I will look in to this problem that you have encountered, though I do not see how the integration of sparkle could have caused this, though you never know and its best to check these things out.
Thanks for bringing this to my attention...
Tom