Techsurvivors
Archives => 2008 => Topic started by: beacher on October 27, 2008, 02:10:24 PM
-
Hey guys, I did a "search" for this problem, but can't find an answer. I went to burn a songlist from iTunes, today, and lo and behold, it won't let me burn it. Doesn't matter which songlist I click on, the burn icon wont show up in the right hand corner. Haven't had any problems with it before, and I just hauled the song list over to Toast 8, and it burned it OK, but iTunes wont read the titles off the disk. I haven't changed anything, except updating to 10.4.11and this may be the first time I've tried to burn within iTunes since then. I did a permisssions repair and ran Diskwarrior, and the same thing happens. Any ideas? As usual, thanks in advance!
-
First, I'm assuming the 'playlist' would actually fit on a CD? Have you checked that your iTunes prefs are set correctly?
Not sure what version of iTunes you have or where it came from but it sounds like time to re-install it/update it with 'pure' code. Or, maybe that part of your screen has lost contact with your cursor? Try moving the window...
-
Beacher, what version of iTunes are you using?
I just had a look at mine (8.0) and the "Burn Disc" is there and available as it should be when I select a playlist.
Are there any protected AAC files in that playlist? They apparently cannot be burned to MP3 in iTunes. Also, there is a limit on the number of times you can burn a playlist (something like 7?) - all you need to do is change one song on the list and it will do it. Any chance either of those issues apply?
-
Well, I have to 'fess up to the fact that I'm still using iTunes 5.?, because I wanted to avoid the burn limit, due to the fact that I use some of the tunes in there for examples for some of my students. But I can't even get the burn icon to show up even when I highlight a playlist that has never been burned. I think that this weekend I may go back and reinstall Tiger, and then bring it up to only 10.4.9, because I didn't have this problem before I updated to 10.4.11. After I do that, I'll let you know if it corrected the prob!