iTunes match.......so slow to upload, 9 days , so far.......why?

I suspect it is taking so long because of internet speeds. Mine took a number of weeks.

You may be able to get a refund. You will have to ask Apple.

Well, I'm still busy uploading with a library of some 23.000 songs. And since iTunes keeps crashing while uploading songs I'm limited to uploading about 100 songs an evening. At this rate I should be done in slightly less than 2 weeks. Sooo .. it is quite slow indeed!

iTunes shouldn't keep crashing during the process (obviously 🙂).

If you can get to the bottom of that then it may speed things up a bit. Are there any clues as to why it crashes? Is this something that has just started with match?

Yeah, I know. It shouldn't. And it all went pretty smooth up to the last 2000 songs. Then of a sudden the process got interrupted each time by iTunes crashes. No error code no nothing. Just a crash. If I'm lucky I'm able to upload 50 or 60 songs in a straight run. Right now I'm down to having to upload about 1300 songs so it is doable I guess but it's a bit of bore, having to see the matching process about 10 times an evening.

I'll see if I can get something from the log as to why iTunes keeps crashing and will post back!

Well, I managed to get some more info from the console log:

Process: iTunes [12414]

Path: /Applications/iTunes.app/Contents/MacOS/iTunes

Identifier: com.apple.iTunes

Version: 10.6 (10.6)

Build Info: iTunes-10604001~1

Code Type: X86-64 (Native)

Parent Process: launchd [295]

Date/Time: 2012-03-10 00:23:53.787 +0100

OS Version: Mac OS X 10.7.3 (11D50b)

Report Version: 9

Crashed Thread: 26

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x000000011feb8000

VM Regions Near 0x11feb8000:

MALLOC_LARGE 000000011fce2000-000000011feb8000 [ 1880K] rw-/rwx SM=PRV

-->

MALLOC_LARGE 000000011ff73000-000000011ffc0000 [ 308K] rw-/rwx SM=COW

Application Specific Information:

objc[12414]: garbage collection is OFF

Thread 26 Crashed:

0 com.apple.audio.codecs.Components 0x000000010bab4bd1 AACEncoder::WriteBitstream(int*, unsigned char*) + 1879

1 com.apple.audio.codecs.Components 0x000000010bab3bef AACEncoder::AACEncodeOutput(unsigned char*, int, int*) + 67

2 com.apple.audio.codecs.Components 0x000000010bab392b AACEncoder::EncodeFrame(float*, unsigned int, AACCE_EncodeReturns*, unsigned char*) + 247

3 com.apple.audio.codecs.Components 0x000000010bab041a ACMP4AACBaseEncoder::ProduceOutputPackets(void*, unsigned int&, unsigned int&, AudioStreamPacketDescription*) + 252

4 com.apple.audio.codecs.Components 0x000000010baf67b1 _ZL20ProduceOutputPacketsPvS_PjS0_P28AudioStreamPacketDescriptionS0_ + 26

5 com.apple.audio.toolbox.AudioToolbox 0x00007fff88805836 _AT_AudioCodecProduceOutputPackets + 130

6 com.apple.iTunes 0x0000000104e1d237 0x104c83000 + 1679927

7 com.apple.iTunes 0x0000000105422072 0x104c83000 + 7991410

8 com.apple.iTunes 0x0000000105022e42 0x104c83000 + 3800642

9 com.apple.iTunes 0x00000001050233a9 0x104c83000 + 3802025

10 com.apple.iTunes 0x00000001050240eb 0x104c83000 + 3805419

11 com.apple.iTunes 0x00000001053ebae7 0x104c83000 + 7768807

12 com.apple.iTunes 0x00000001053ed121 0x104c83000 + 7774497

13 com.apple.iTunes 0x0000000105637b2a 0x104c83000 + 10177322

14 com.apple.CoreFoundation 0x00007fff8ffc8856 __CFDictionaryApplyFunction_block_invoke_1 + 22

15 com.apple.CoreFoundation 0x00007fff8ffaa311 CFBasicHashApply + 113

16 com.apple.CoreFoundation 0x00007fff8ffc8834 CFDictionaryApplyFunction + 212

17 com.apple.iTunes 0x000000010563ac40 0x104c83000 + 10189888

18 com.apple.iTunes 0x000000010563afd2 0x104c83000 + 10190802

19 com.apple.iTunes 0x000000010563b136 0x104c83000 + 10191158

20 com.apple.iTunes 0x000000010563c0b0 0x104c83000 + 10195120

21 com.apple.iTunes 0x0000000104cae1de 0x104c83000 + 176606

22 com.apple.iTunes 0x000000010551585a 0x104c83000 + 8988762

23 libsystem_c.dylib 0x00007fff8d87a8bf _pthread_start + 335

24 libsystem_c.dylib 0x00007fff8d87db75 thread_start + 13

For some reason crashes the AACencoder during writing the bitstream although I haven't got the faintest clue as to why...

Wow, I may have solved by actually looking for a solution to the problem. I ran into this posting: https://discussions.apple.com/thread/3575192?answerId=17048123022#17048123022

And it looks like the matching now continues. Lets see if keeps up this way!

Good news.

Well, it's official. ITunes Match is garbage.

Months after this issue was raised here the problem still exists.

I asked Apple for a refund based on the fact that Match is taking literally days to upload less than 1000 songs.

Not only this but it is sapping all my Internet speed on all other devices and my processor is running at full belt, rendering the computer useless for anything else.

Here is the response from Apple.

Hello Steven,

Evelyn here from the iTunes Store. I understand that you would like to have your purchase of iTunes Match considered for a refund as the process to upload is taking too long. I'm sure that you were not expecting the wait time to upload and enjoy your content. I will be happy to help.

Steven, I understand that you want to cancel your iTunes Match subscription and receive a refund. Once the cancellation is complete, you’ll no longer have access to matched or uploaded songs in the cloud. Therefore, please be sure to download everything before we issue the refund.

While I wait for your confirmation that you do want to move ahead with a refund, please keep in mind that your upload speed is not going to be as fast as your download speed. The time that you are reporting is expected behaviour.

SO, THIS IS EXPECTED BEHAVIOUR. I.E. YOU ARE WASTING YOUR TIME LOOKING FOR A FIX.

It's such a sub standard product that it's not fit for purpose.

Save your money.