Time for imported AAC files is changing to 789:57:13

Changing file names from m4a to mp4 does indeed make them playable and the length of each cut is displayed correctly, but the itunes "info" says that the music has been sampled at bit rates slightly lower than 192 kbps (which is what I used to create the files, and also what the m4a files say the bit rate is -- these m4a files are the ones that itunes displays but won't play). For example, the bit rates shown for mp4 files vary from 184 to 189 kbps even though when they are named m4a files, the bit rate says 192 kbps. I'm worried that somehow the mp4 files are being incorrectly interpreted (i.e., sampled at something other than 192 kbps).

Anyway writing a script to rename all my files might be an option, but I don't find it satisfactory. Apple should fix the bug(s) in itunes so that it can read properly created m4a files!

I had the same problem as well. I just deleted the newest version of iTunes and all associated programs (Bonjour, QuickTime, etc) and simply downloaded a previous version. Problem solved!

Thank you for this thread! Something is clearly amiss with iTunes 12.9.4,102. I'm using a previous version of iTunes on another computer (also Windows 10) with the same music files and they all work fine.

In my iTunes library, each song is identified under the 'Kind' field as a WAV, MPEG, Purchased AAC, or AAC audio file. Using the 12.9.4.102 version, the WAV, MPEG, and Purchased AAC files all work fine. The ones that don't work are the AAC audio files that were edited using my wave editing software (WavePad Sound Editor by NCH Software). When attempted to play now, the duration is changed to 789:57:13 and it does not play.

I can remove the hundreds of music files affected from my iTunes library, then save them in another format and add back to my library, but that would be a huge undertaking. Not only would I lose all the data including number of plays, date added, etc., but also many of the songs are included in multiple playlists, so I would have to manually go through each playlist and reinsert each of the reformatted songs one by one. Not feasible!

I did uninstall this newer version, and uploaded a previous version, but I could then not access my library. I was getting the message that my iTunes Library.itl file was from a newer version (i.e., 12.9.4.102) and this did not work with a previous version. Until Apple can fix this issue, it seems this is the most feasible path to go, but when downgrading to a previous version, how can you restore a compatible Library.itl file so the songs will play?

It seems Apple is unwilling to, but can someone here summarize the step by step procedure for going back to a previous version? I'm using Windows 10. Thank you!

Thanks for all of the info TT2. I went ahead and reverted back to the previous version of iTunes (12.9.3.3) and was able to restore things to normal. Obviously I am not thrilled with what has transpired but my vinyl transfer project can continue. My guess is Apple is aware of the issue at this point but will add my feedback as well...I am optimistic there will be a fix in an upcoming iTunes version

Hi, I have the same problem both on Mojave on Mac and Windows 7 on PC

I am thinking this problem will occur with the last issue of iTunes, 12.9.4, but not sure !

For the Mac I have used the Tag Stripper application which erases the tags of music files, it seems it is working well

For the PC under Windows 7, I uninstalled iTunes 12.9.4 and reinstall an older version 12.7.1 ; I did it yesterday evening, at this time it seems OK, but to be confirmed

I believe it can, though I've not had reason to test it personally. Remove each of the components from Apple in turn starting with iTunes and working alphabetically backwards, then install the older build. Here are the links:

• iTunes 12.9.3.3 for Windows (32-bit) - iTunesSetup.exe (2019-01-24)
• iTunes 12.9.3.3 for Windows (64-bit) - iTunes64Setup.exe (2019-01-24)

tt2

I just encountered this same problem earlier this week with files that were edited and saved with Audacity. I may have found a potential workaround:

I also use an app called Wondershare Video Converter Ultimate. This app can convert formats for video as well as audio. The current version 10 does not allow me to import any file formatted with AAC (.m4a) into iTunes. I don't know why but suspect that perhaps iTunes thinks I acquired a song illegally. Anyhow, I still have an older version of Wondershare, version 5, which does import .m4a files into iTunes. It also allowed me to take one of the affected files that reads 789 hours and convert it to another .m4a file and it imported/played just fine.

The user interface of Wondershare allows you to select multiple audio/video files and to convert them all at once. So if you have multiple files that are affected, this should reduce the amount of time for file conversion. And you retain a better format than .mp3. I know, we shouldn't have to do this at all, but at least this might be a good workaround for the time being.

Hi gdpetrie/Steve DB I have auto update also but hadn’t any notifications but after reading MD’s post I went to the Apple logo, - About this Mac, clicked software update, initially it said no update available for Mojave, then a second later an update for Mojave and iTunes appeared. I’m downloading what appears to be a very large update as we speak. Fingers crossed it will do the trick. Pete

UPDATE:: Confirmed it works as you play the tracks it puts them back to correct time. 👍🏻

After updating iTunes on Windows to version 12.9.4.102, some of my files show duration 789:57:13 and no longer play.

Before that I was using 12.7.4.76. The same files show proper duration and play fine.

On my Mac I have version 12.9.5.5, and everything works fine.

The files used to play on my iPhone, but after I removed and re-added them to iTunes, and synced, they are silent. The duration still seems fine on the iPhone.

I see other people complaining about the same issue here:

https://forum.audacityteam.org/viewtopic.php?t=104442

I have an update on this issue but unfortunately not good news other than I shared earlier. Uninstalling and going back to an earlier version of iTunes before 12.9.4 will correct the issue but is not the best solution for the long term. See my prior posts. I have contacted Apple Support on Twitter @AppleSupport and conversed with someone there throughout today. I shared details of the error, screen shots, video etc. Generally, they indicated that they felt this was my problem because I used a third party file converting program to create files for iTunes. But, as many have mentioned, that has been the case for years and iTunes worked fine with all AAC encoded m4a files. The alternative is to create files using the ALAC codec if you have that option, but the file size will be significantly larger. If you have thousands of music files, that will not be desirable. In any case, there are many threads here all regarding this issue. I suggest perhaps contacting Apple Support as I have as they seem to think this is a minor issue with no impact to customers. By the number of discussions I see today here, that is not really the case. See below. Apple Support is also on Facebook in addition to Twitter.

https://discussions.apple.com/search?page=1&q=AAC%20789&content=filterDiscussions&time=week

Like I have mentioned earlier, I have thousands of songs affected. Best solution (for Now) is load an older version of iTunes. It fixes the problem at least in the short term. Unfortunately, apple tech support wont help you do that.

I have installed 12.9.3.3. and it is fine.

For anyone else reviewing - Do not install 12.9.4.102

This problem is also happening for me, also on Mojave 10.14.4, to content bought from 7 digital some years ago.

The files I am having problems with can be opened with QuickTime player, and using 'Export As' -> 'Audio Only' creates a m4a file that works with iTunes.

Steve_DB...if it makes you feel any better I also had a less than satisfactory interaction with Apple support on this very issue at least initially. I believe the person I talked to placed the blame firmly on Audacity (which he was very happy to announce wasn't supported by Apple) and the issue couldn't possibly be an iTunes problem despite no other updates to my Windows 10 system EXCEPT iTunes. I am a SW developer/engineer by trade so I found the response infuriating and humorous at the same time.

Once I did some more investigation and was able to identify an interim workaround (import music in an uncompressed format and create an AAC version in iTunes), I called support back with the specific, albeit short term workaround. The support person I talked to was very helpful and interested in solving the problem. The individual took some notes and asked me to repeat some things to make sure he got the details correct) which I assume he was going to pass on.

My point is technical support experiences vary widely and how positive the experience is depends a great deal on how much the technical support person cares and how much they are able to help.

I am at the point of doing one of two things...re-import all my vinyl recordings into iTunes in uncompressed format and having iTunes perform the AAC conversion ( A lot of work!) or punt iTunes completely and start using a different service (e.g. MusicBee) to manage my music library full time. I'd revert back to an earlier version but as others have said, this is only a temporary fix.

The other posts I see where support points the finger at third party software is of grave concern to me...Apple should be fairly concerned that a change has been introduced that (I assume) inadvertently caused an issue with music being unplayable that was perfectly valid earlier. This same music remains playable on all other media players that I own. It's a clear functionality regression (and not exactly a minor one at that) which is not acceptable and should be corrected. Brushing such a regression aside as a "feature" or "the fault of 3rd party software" doesn't fly with me and shouldn't with any other user of iTunes. I am watching to see what happens. I am optimistic that the Apple development staff will identify what happened an issue a fix for the problem.

Mrlonzo.

I have same prob as u with thousands of bad songs. I downloaded an older version and it got me out of trouble. Do not go to apple as they will not help u install an older version