Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases iTunes 7.0.1
- Thread starter skoker
- Start date
- Sort by reaction score
i think iTunes 7 is absolute crap. and the update fixed nothing. i cant see what it takes 25-30% of the CPU to play any MP3 of low quality. the older versions only took like 10%-15% to play a high quality MP3. this version is just really not optimized enough to use properly on anything below a 1ghz cpu . granted it has great features and all and correctly implemented then iTunes 7 will be great.
but the movies/video's hardly play at all. the video looks like a slideshow when movies are playing then the video moves normally then goes back to jumpy. i can play higher quality video in VLC compared to the video on iTunes and VLC play's it smooth compared to iTunes. in iTunes your are hardly even likely to even see 0.5 FPS of the movie that is playing.
this version of iTunes isn't fit to recommend. but it does have cool features with it once its all said and done maybe apple will set this version right. dont get me wrong i like iTunes and all but this version was just was not ready to be released yet
but the movies/video's hardly play at all. the video looks like a slideshow when movies are playing then the video moves normally then goes back to jumpy. i can play higher quality video in VLC compared to the video on iTunes and VLC play's it smooth compared to iTunes. in iTunes your are hardly even likely to even see 0.5 FPS of the movie that is playing.
this version of iTunes isn't fit to recommend. but it does have cool features with it once its all said and done maybe apple will set this version right. dont get me wrong i like iTunes and all but this version was just was not ready to be released yet
I'm still having the problem on my MacBook, but only when tapping the trackpad instead of clicking the trackpad button. I haven't updated my G4 yet to see if the problem is still there.Project said:
madmax_2069 said:
Unfortunately, that's the way with technology. When you have a really old machine, things don't work as well. Obviously, a 450 MHz or even 466 MHz machine goes back 5 or 6 years. Most computer companies wouldn't keep 3 year old machines in mind for software and game companies don't. Plenty of 1.25 GHz G4s are out of date already.
You shouldn't expect the latest software to run on your machine well.
What about the Visualizer?
Still no dedicated Visualizer botton (just that useless "Browsing Eye" button).
Anyone know why the Visualizer options (Half Size, Double Size, etc.) are all greyed out?
Not a big deal, just curious as to why this feature is all of a sudden crippled.
Still no dedicated Visualizer botton (just that useless "Browsing Eye" button).
Anyone know why the Visualizer options (Half Size, Double Size, etc.) are all greyed out?
Not a big deal, just curious as to why this feature is all of a sudden crippled.
still no luck
I tried uninstalling my only itunes plugin (ivisualizer) but itunes still crashes, usually in conjunction with an interaction with teh icon in the dock. I've tried everything i can think of, repairing permissions, restarting, removing and adding the icon to the dock. does anyone have other suggestions? Also, i can't figure out how to roll back to 7.0. any ideas?
I tried uninstalling my only itunes plugin (ivisualizer) but itunes still crashes, usually in conjunction with an interaction with teh icon in the dock. I've tried everything i can think of, repairing permissions, restarting, removing and adding the icon to the dock. does anyone have other suggestions? Also, i can't figure out how to roll back to 7.0. any ideas?
They'd better get that phone out soon or the hype will eat the release. Well, I guess it is Apple, so that would never happen.
madmax_2069 said:
Dude, you have a 450MhZ overclocked G3. It is ridiculous for you to expect that your machine would run this software well. Drop a few hundred and get a mini for god sakes.
Does the Windows v 7.0.1 automatically recreate its shortcuts in the Start menu, desktop, if you delete them?
mickhyperion said:
Same here. I'm using Macbook Pro and the trouble is only with trackpad tap. The click button works fine. I think this seems to be related to trackpad. Any PB/iB users with this problem?
The weired font scrambling at the titlebar is gone now and got back the beautiful Aqua UI of iTunes 6 thanks to AguaT.
I dont use the build in station but open streams from our country's local radio station; advanced open stream;telecomm said:
example;
http://mp3.streampower.be/stubru-high
mcarnes said:He's running 10.2 also.
humm wrong im running 10.4.7
i wasnt able to update my sig to show that its running tiger for some odd reason
oh and BTW mini's blow, id rather get a MBP
WTF does everyone have against older hardware. they are great to see what programs are optimized or not. AKA this is a great bit of proof of that. there should be no way a low quality MP3 (AKA in itunes 7) to take more cpu % then a high quality MP3(in other versions). in itunes 7 it takes 25-30% to play a low quality MP3. and in any other version of itunes only takes 10-15% for a high quality MP3. itunes should use the same cpu usage playing the same quality MP3 no matter the version of itunes.
now i can see the deal with the video on a slower system some what. but then again i cant. cause i can play better quality movies/video's threw VLC smoother than what iTunes can. in itunes it basically a slideshow with sound popping in spots and the control panel disappearing and appearing at will and just down right horrid response in general with the control's in itunes. the only thing that moves smoothly in itunes is the rotating GFX when your in the ITMS.
madmax_2069 said:
if you were Apple, what will you make better? I guess you can't. you just blame for no matter what it is. unfortunately you didn't read system requirement. minimum G3 500 mhz or better. if you want to satisfy with performance, at least you should have G5 powerPC mac. sorry, your mac is way to out of date.
Attachments
permissions problem & iTunes permissions problems
I have removed the messages about correcting the problems.
Determining correct file permissions.
Permissions differ on ./Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/MacOS/InternetUtilities, should be -rw-rw-r-- , they are -rwxrwxr-x
Oh look! bad permissions on "InternetUtilities"! what is to become of us? Nothing at all. It just made the file NONEXECUTABLE, whereas it was executable before. Is this a bad thing? Yes, as it turns out. That file is the program that is run by the InternetUtlities bundle. Making it non-executable means iTunes will not be able to run that bundle when it tries to. And the permissions "repair?" changed this! that's not cool.
This is what irritates me about your comment--you didn't specify what "problems" iTunes causes. Of course Apple and other FUDdy sites mention that faulty installers can muck with permissions, but this is actually very rare in modern OS Xery. Application installers which cause such problems are generally OS 9-ported Carbon apps like Quark or Photoshop, and even those generally aren't that bad.
- Danced around the front yard with my shirt off
- Watched my friend wreck his bicycle
- Drank some herbal tea
- Ate a cold slice of pizza
- Sat in a puddle of warm water, which may or may not have been my own urine.
And days later, my cold went away! isn't that amazing?
your example of the third party app making /Applications read-only is a good example of a permissions issue--one that is not necessarily a problem, though--you shouldn't be writing to the /Applications folder, ever, unless you are installing software, in which case you should be getting root access to do so. That third party app actually made /Applications a little more secure...
Here's the thing I've been trying to get at. Permissions repair is a wash because it's just the same as faulty installers. OS X keeps a library of installed filenames and their original permissions in /Library/Receipts. When you install software, the installers WRITE package receipts into this folder! So, if an application can mess up permissions of files it INSTALLS, it can also mess up the permissions listed in the package receipt it writes during an install. This is especially true of an install like iTunes or QuickTime--those are core system packages, meaning that their receipts actually get checked in a permissions repair, whereas third-party receipts do not.
Moreover, it RARELY matters whether a file has different permissions than the listing says it should be. Usually it's not a problem, it's just DIFFERENT, causing no problems at all.
But back to my main point, for all of you worried about Installers messing up permissions, I should warn you that they can also mess up the receipts they write, which would make your permissions repair screw up permissions that may have been fine before. Of course this rarely if ever happens, but it's still as possible as an installer messing up permissions is.
If you want to waste your time, that's of course fine. The thing that bugs me, though, is when people write in with faulty logic (as above), saying or suggesting that permissions repair helped them because they always do it before and after installing applications, etc.
Allow me to suggest another path. If you're reading this thread, chances are you are a Mac/Computer geek. Why don't you learn about how permissions work, and how to check what they are in Terminal (ls -l is a good command to know)? Why don't you also learn how to set them yourself (chmod for changing permissions, chown for changing owner)? While you're at it, you could also learn how to identify permissions problems for REAL. like, I mean, fool-proofedly. Here's how:
1. Notice that an application is acting funny. It won't run, or something is wrong with its behavior.
2. Open Console.app and look at system.log. If an application tried to look at/write to/execute a file and was denied permission to do so, it will ALWAYS be logged. Usually, it will be logged in system.log, which is open by default when you run Console.app. if you see nothing there, check out the "logs" button, and look at the tree of logs there. check out console.log. it usually prints funny application issues, like if mail can't fetch mail on a mailbox, it will print that out here. Remember in all this log viewing that there is a timestamp on every message, so you should only scan the log messages from the last few minutes, because if your error is logging with the wrong time, you have MUCH bigger problems... Drop down ~/library/logs and /Library/logs and check if your breaking app has a listing in the CrashReporter folder in either of these locations. If so, check that out.
3. Don't try to understand the logs, just look for something obvious, like [iTunes] Thu Sept 27 19:04:45 : couldn't open file: /Applications/iTunes.app/blah/blah/blah.blah
4. Now, you know that that file has bad permissions. at this point, you could fix it yourself, or try repairing permissions. The former is guaranteed to work (if you take the time to learn how permissions work, which is quite simple). The latter may or may not work.
Again, permissions issues in the modern OS X running recent software are rare, and permissions repairing will only fix a very small number of them. Sometimes it may actually set the WRONG ones, as in my iTunes example above: I had to manually change that InternetUtilities file back to be executable to allow that InternetUtilities bundle to work. After "repairing" permissions, it had acrtually made that program non-executable, which broke my AirTunes facility, and also my ability to access the iTunes store. So much for "Repair Permissions" fixing all my problems!
I find it truly ironic that a user complains of iTunes messing up permissions, only to find (myself) that I had NO problems before, decided to run "Repair Permissions" to see if iTunes had even modified permissions to something other than the receipt file, and the permissions repair friggin' BROKE iTunes' internet utilities, disabling my music streaming to my stereo!
Sorry for the long rantish post, guys. I don't know if I will change any minds on the issue, but I hope you will consider my examples and explanations and investigate the issue in a real way. If not, I would at least suggest finding a more interesting placebo than restarting and repairing permissions after installing software, because both of those activities are REALLY boring. Instead, why not do something like running around the block and waving your hands around while you wait for the installation to complete? You could also make up a chant praying that your permissions don't get messed up! if you do that, please record it and post it on MR, I might actually try to learn it myself.
My friend, that would be because you (or someone else) deleted all the .pkg files in /Library/Receipts on your hard drive. This isn't necessarily a bad thing, but it does mean that you will never be able to run repair permissions on that OS X installation.spicyapple said:
OK, this statement really frustrates me, because it's so uninformed! What does iTunes 7 mess up when installed? Does it not run correctly before the repair? Of course it runs right! Check this out. I haven't repaired my permissions since I got my Mac, and I just did. Look at these log snippets:telecomm said:
I have removed the messages about correcting the problems.
Determining correct file permissions.
Permissions differ on ./Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/MacOS/InternetUtilities, should be -rw-rw-r-- , they are -rwxrwxr-x
Oh look! bad permissions on "InternetUtilities"! what is to become of us? Nothing at all. It just made the file NONEXECUTABLE, whereas it was executable before. Is this a bad thing? Yes, as it turns out. That file is the program that is run by the InternetUtlities bundle. Making it non-executable means iTunes will not be able to run that bundle when it tries to. And the permissions "repair?" changed this! that's not cool.
This is what irritates me about your comment--you didn't specify what "problems" iTunes causes. Of course Apple and other FUDdy sites mention that faulty installers can muck with permissions, but this is actually very rare in modern OS Xery. Application installers which cause such problems are generally OS 9-ported Carbon apps like Quark or Photoshop, and even those generally aren't that bad.
We never wanted to actually debunk or debate whether permissions repair is useful or not--The first poster said iTunes 7 caused permissions issues, and we wanted to know what specific permissions issues it caused. As it turns out, iTunes 7 does not.840quadra said:
You know, I had a cold last week, and I found the cure for it. Isn't that great? Check this out! I did the following:quigleybc said:
- Danced around the front yard with my shirt off
- Watched my friend wreck his bicycle
- Drank some herbal tea
- Ate a cold slice of pizza
- Sat in a puddle of warm water, which may or may not have been my own urine.
And days later, my cold went away! isn't that amazing?
what do you mean by "yield results?" Just because they quieted the special permissions stuff, doesn't mean they stopped changing those permissions--they just stopped logging it.bousozoku said:
your example of the third party app making /Applications read-only is a good example of a permissions issue--one that is not necessarily a problem, though--you shouldn't be writing to the /Applications folder, ever, unless you are installing software, in which case you should be getting root access to do so. That third party app actually made /Applications a little more secure...
Here's the thing I've been trying to get at. Permissions repair is a wash because it's just the same as faulty installers. OS X keeps a library of installed filenames and their original permissions in /Library/Receipts. When you install software, the installers WRITE package receipts into this folder! So, if an application can mess up permissions of files it INSTALLS, it can also mess up the permissions listed in the package receipt it writes during an install. This is especially true of an install like iTunes or QuickTime--those are core system packages, meaning that their receipts actually get checked in a permissions repair, whereas third-party receipts do not.
Moreover, it RARELY matters whether a file has different permissions than the listing says it should be. Usually it's not a problem, it's just DIFFERENT, causing no problems at all.
But back to my main point, for all of you worried about Installers messing up permissions, I should warn you that they can also mess up the receipts they write, which would make your permissions repair screw up permissions that may have been fine before. Of course this rarely if ever happens, but it's still as possible as an installer messing up permissions is.
If you want to waste your time, that's of course fine. The thing that bugs me, though, is when people write in with faulty logic (as above), saying or suggesting that permissions repair helped them because they always do it before and after installing applications, etc.
Allow me to suggest another path. If you're reading this thread, chances are you are a Mac/Computer geek. Why don't you learn about how permissions work, and how to check what they are in Terminal (ls -l is a good command to know)? Why don't you also learn how to set them yourself (chmod for changing permissions, chown for changing owner)? While you're at it, you could also learn how to identify permissions problems for REAL. like, I mean, fool-proofedly. Here's how:
1. Notice that an application is acting funny. It won't run, or something is wrong with its behavior.
2. Open Console.app and look at system.log. If an application tried to look at/write to/execute a file and was denied permission to do so, it will ALWAYS be logged. Usually, it will be logged in system.log, which is open by default when you run Console.app. if you see nothing there, check out the "logs" button, and look at the tree of logs there. check out console.log. it usually prints funny application issues, like if mail can't fetch mail on a mailbox, it will print that out here. Remember in all this log viewing that there is a timestamp on every message, so you should only scan the log messages from the last few minutes, because if your error is logging with the wrong time, you have MUCH bigger problems... Drop down ~/library/logs and /Library/logs and check if your breaking app has a listing in the CrashReporter folder in either of these locations. If so, check that out.
3. Don't try to understand the logs, just look for something obvious, like [iTunes] Thu Sept 27 19:04:45 : couldn't open file: /Applications/iTunes.app/blah/blah/blah.blah
4. Now, you know that that file has bad permissions. at this point, you could fix it yourself, or try repairing permissions. The former is guaranteed to work (if you take the time to learn how permissions work, which is quite simple). The latter may or may not work.
Again, permissions issues in the modern OS X running recent software are rare, and permissions repairing will only fix a very small number of them. Sometimes it may actually set the WRONG ones, as in my iTunes example above: I had to manually change that InternetUtilities file back to be executable to allow that InternetUtilities bundle to work. After "repairing" permissions, it had acrtually made that program non-executable, which broke my AirTunes facility, and also my ability to access the iTunes store. So much for "Repair Permissions" fixing all my problems!
I find it truly ironic that a user complains of iTunes messing up permissions, only to find (myself) that I had NO problems before, decided to run "Repair Permissions" to see if iTunes had even modified permissions to something other than the receipt file, and the permissions repair friggin' BROKE iTunes' internet utilities, disabling my music streaming to my stereo!
Sorry for the long rantish post, guys. I don't know if I will change any minds on the issue, but I hope you will consider my examples and explanations and investigate the issue in a real way. If not, I would at least suggest finding a more interesting placebo than restarting and repairing permissions after installing software, because both of those activities are REALLY boring. Instead, why not do something like running around the block and waving your hands around while you wait for the installation to complete? You could also make up a chant praying that your permissions don't get messed up! if you do that, please record it and post it on MR, I might actually try to learn it myself.
shadowfax said:
OK, look, if you don't want to repair permissions, you find it boring, or you don't like ice cream, I don't think anyone here is really going to get upset.
In my first post in this thread, which seems to have started this whole mess, all I meant to note was that Disk Utility reported that permissions needed repairing on an iTunes file. Whether this is a problem with the file permissions, or with the package receipt, I really don't know. It seems, though, that it's the result of sloppy work in either case: either the receipt should be corrected, or the file permissions changed. This is the "simple fix" to which I was referring.
Oh, and by the way, after changing these permissions AirTunes streaming and the store worked fine here, so I'm not sure why you think your manual permissions "repair" fixed that.
If you want to further explain permissions issues maybe that would be more appropriate in another thread, since we seem to be getting a bit off topic here.
shadowfax said:
I'm glad you know everything. We should all feel humbled by your presence.
I've been using UNIX and other multiple user systems since the early 1980s and have been the security officer at many jobs. Yes, I know how to take care of permissions manually but why should I? There is no reason for any user to go through the system checking files to see if they're correct or not. The system itself should be taking care of the issue. Things were different when there were no administrative utility applications but we don't edit the password file directly any more to add new users, either.
The third party software installation made the /Application folder so secure that nothing else could write to it. Yeah, that's good. The next installation failed. Oh wait, but I don't understand how permissions work so I should have been feeling good that the folder was so secure.
Permissions repair isn't always a wash. It's not needed as much as it had been needed and I'd had dozens of issues that were resolved with permission repairs. Oh wait, but I don't understand what it was doing so it was just my ignorance working.
Well, thanks for your enlightenment. Good thing we had you here to tell us that we didn't gain anything over the years through Permissions repair. Then again, I suspect you're not omniscient or omnipotent.
jettredmont said:
While I completely agree, Firewire iPods are MUCH faster to sync than USB ones on the same machine, your complaint about transfer speed numbers isn't quite right. First off, you are comparing MB/s to Mbps, 480 Mbps does not equal 480 MB/s at all, it's more like 41 MB/s or something. Secondly, the iPod hard drive can't even read or write as fast as a Firewire connection allows, so it's limited by its drive, not the connection.
Personally I think we should have iPods based on 3.5" drives that run at 10,000rpm with Firewire 800 syncing and an RV battery to power the whole thing
Fixed!
I think i fixed it. i had tried deleting itunes from the applications and then reinstalling but that didn't work (the installer said there was nothing to install). after deleting the itunes prefs and receipts it installed fine and is still working without a crash. yippee!
I think i fixed it. i had tried deleting itunes from the applications and then reinstalling but that didn't work (the installer said there was nothing to install). after deleting the itunes prefs and receipts it installed fine and is still working without a crash. yippee!
what?
I don't think it's ugly at all. It isn't flashy and in your face like the Aqua stuff was, but like any app, it does what you want and stays outta the way while it does it. A too flashy interface gets in the way and is distracting. Pleasantly, perhaps, but still distracting.
And I like the BLUE icon better - green never was my fav color...!
umijin said:
I don't think it's ugly at all. It isn't flashy and in your face like the Aqua stuff was, but like any app, it does what you want and stays outta the way while it does it. A too flashy interface gets in the way and is distracting. Pleasantly, perhaps, but still distracting.
And I like the BLUE icon better
- green never was my fav color...!I use missing sync for my windows mobile smartphone on my macbook pro. The windows phone shows up as a device in iTunes! Its got a mobile phone logo in iTunes. I tried transferring songs to the device, it shows a progress bar. But it hangs after a few minutes.