Affiliate Disclosure
If you buy through our links, we may get a commission. Read our ethics policy.

iTunes update to address truncating glitch

Apple is working on a maintenance update to its iTunes software that will address a number of performance issues, AppleInsider has learned, including nasty bug which shaves off a portion of the last track during CD imports.

Apple reportedly became aware of the truncating problem following a flurry of reports from disgruntled users who've been congregating on the company's support forums for the past three weeks.

One, going by the name of dlalla, reported that since upgrading to iTunes 7.6.1, all his CD imports have resulted in the last 6 seconds of the final track getting cut short.

"I'm having the same issue, and didn't notice it until today," said another. "Considering the volume of CDs I import on a regular basis, this is going to be a real pain - I have to go back now and figure out when I upgraded, and what I have imported since then that will need to be fixed."

Other users confirm the glitch to have turned up as part of the iTunes 7.6.1 update released February 21st. They note that the issue is particularly prevalent while importing to compressed formats such as AAC or MP3 using a speedy optical drive. Users of slower optical drives say they haven't noticed the issue.

While they await the forthcoming iTunes update, some users have resorted to a workaround. They've found that by importing the final track of each CD to AIFF format, then converting it to a compressed format afterwards, they can avoid the problem.



23 Comments

stompy 18 Years · 412 comments

Quote:
Originally Posted by AppleInsider

"I have to go back now and figure out when I upgraded, and what I have imported since then that will need to be fixed."

The support forums probably have the following tip (but no link from AI). It's pretty simple to make a smart playlist that will identify potentially bad rips.
1. "Date Added" "is after" "2/20/2008"
2. "Track Number" "is" "1"

Get info on the first track, see if 7.6.1 was used to encode it. Command + N through the playlist.
This will identify each CD that might have the 6 second problem; then listen to the last track to verify good/bad rip.

Sucks if you ripped a lot in those 3 weeks though.

zanshin 17 Years · 350 comments

Quote:
Originally Posted by stompy

The support forums probably have the following tip (but no link from AI). It's pretty simple to make a smart playlist that will identify potentially bad rips.
1. "Date Added" "is after" "2/20/2008"
2. "Track Number" "is" "1"

Get info on the first track, see if 7.6.1 was used to encode it. Command + N through all tracks.

Sucks if you ripped a lot in those 3 weeks though.

I didn't think anybody bought CDs anymore... Aren't they dead? Where would you even go to find one to buy???

porchland 19 Years · 477 comments

I've had problems getting the optical drive in my PowerBook to eject a disc after I burn it since the last update of iTunes.

webfrasse 16 Years · 147 comments

Quote:
Originally Posted by zanshin

I didn't think anybody bought CDs anymore... Aren't they dead? Where would you even go to find one to buy???


amazon.com. It's cheaper than on iTunes and MUCH better sound quality.

/Mikael

louzer 20 Years · 1054 comments

Quote:
Originally Posted by stompy

The support forums probably have the following tip (but no link from AI). It's pretty simple to make a smart playlist that will identify potentially bad rips.
1. "Date Added" "is after" "2/20/2008"
2. "Track Number" "is" "1"

Get info on the first track, see if 7.6.1 was used to encode it. Command + N through all tracks.

Sucks if you ripped a lot in those 3 weeks though.

Isn't item #2 incorrect, since it is the last track, not the first one, that is bad?