Match - Replace my current MP3 collection (without iCloud)?

[iBrody]

Like many people, I have two iTunes accounts on one MBP, and each account is associated with a different iPhone.

I am not bothered about using the iCloud feature, I just want to streamline the bitrate on all my mp3 tracks to 256kbps AAC and use these AAC tracks on multiple devices/accounts.

So this is what I was thinking of doing...

1. Copy my mp3 music collection to an external HDD for archive/back-up only
2. Purchase Match on one iTunes account
3. Match my collection from my MBP and then download the tracks, deleting the original mp3's
4. Turn iCloud feature off (if this is possible when using Match)
5. Sign in to iTunes on the second iTunes account, and use 'Add to Library' but without physically copying the files to the second account (as per my current set up).

Now will this work? And if it will work, what is the easiest and safest way of doing this as I am thinking my step-by-step guide above is wishful thinking on my behalf?!

I realise the iCloud/share feature isn't currently supported across multiple iTunes accounts, but all I am interested in doing is replacing my current MP3 library with an AAC library (mainly to save space as my mp3's are ripped to 320kbps CBR), and I want the AAC tracks to not be associated with any iTunes account - just the same as an AAC track that I have ripped from a CD.

Also, multiple iTunes account issue aside, if the above is possible, it will also be of use if I decide to transfer the AAC tracks to a non Apple device that supports AAC/M4a.

I have searched and read a lot of posts but am still pretty clueless about Match and how the newly downloaded AAC files can be utilised once they replace my existing mp3 files on my computer.

Please help!! :

 

[wonderspark]

Like many people, I have two iTunes accounts on one MBP, and each account is associated with a different iPhone.

I am not bothered about using the iCloud feature, I just want to streamline the bitrate on all my mp3 tracks to 256kbps AAC and use these AAC tracks on multiple devices/accounts.

So this is what I was thinking of doing...

1. Copy my mp3 music collection to an external HDD for archive/back-up only
2. Purchase Match on one iTunes account
3. Match my collection from my MBP and then download the tracks, deleting the original mp3's
4. Turn iCloud feature off (if this is possible when using Match)
5. Sign in to iTunes on the second iTunes account, and use 'Add to Library' but without physically copying the files to the second account (as per my current set up).

Now will this work? And if it will work, what is the easiest and safest way of doing this as I am thinking my step-by-step guide above is wishful thinking on my behalf?!

I realise the iCloud/share feature isn't currently supported across multiple iTunes accounts, but all I am interested in doing is replacing my current MP3 library with an AAC library (mainly to save space as my mp3's are ripped to 320kbps CBR), and I want the AAC tracks to not be associated with any iTunes account - just the same as an AAC track that I have ripped from a CD.

Also, multiple iTunes account issue aside, if the above is possible, it will also be of use if I decide to transfer the AAC tracks to a non Apple device that supports AAC/M4a.

I have searched and read a lot of posts but am still pretty clueless about Match and how the newly downloaded AAC files can be utilised once they replace my existing mp3 files on my computer.

Please help!! :

If you use iTunes Match to convert your songs right now, a lot will get screwed up. I have it, and some get converted to live concert tracks, some explicit versions get converted to bleeped out versions, and there are complaints of clean versions being converted to explicit versions, too. Some tracks are simply changed to the wrong song completely. It's not a good idea right now unless you want to spend a lot of time listening to every song and re-ripping the messed up ones like I have been doing.

 

[iBrody]

Oh, maybe I will leave it until these issues are resolved then.

Any thoughts on whether I can freely use the MAtch downloaded AAC tracks across all devices as per my current ripped mp3's?

 

[wonderspark]

Oh, maybe I will leave it until these issues are resolved then.

Any thoughts on whether I can freely use the MAtch downloaded AAC tracks across all devices as per my current ripped mp3's?

That part is good news. Yes. It replaces your files with .m4a files, which are unprotected. I just tested by playing one with VLC, and it works... so if your other devices play m4a files, you're good to go.

 

[iBrody]

That part is good news. Yes. It replaces your files with .m4a files, which are unprotected. I just tested by playing one with VLC, and it works... so if your other devices play m4a files, you're good to go.

Cool, and I guess that also means I can log into iTunes using a different account and use the 'add to library' function so that songs can be played with 2 iPhones?

And which I would also assume means it is only the iCloud feature that cannot be used for both iTunes accounts with one library?

Is this correct?

 

[roebeet]

Cool, and I guess that also means I can log into iTunes using a different account and use the 'add to library' function so that songs can be played with 2 iPhones?

And which I would also assume means it is only the iCloud feature that cannot be used for both iTunes accounts with one library?

Is this correct?

Not on the same system - if you attempt this on the same system, I heard that you get that "you cannot login using another Apple ID for 90 days" problem. So I would be careful. On a separate system, I believe it would work as expected (login using a different ID, copy the files to that system, then sync them to the iOS device).

Also, the iTunes Matched files are unprotected, but they do have the original Apple ID embedded as an extended metatag. So obviously you don't want to be passing them to people outside of your immediate control.

 

[iBrody]

Not on the same system - if you attempt this on the same system, I heard that you get that "you cannot login using another Apple ID for 90 days" problem. So I would be careful. On a separate system, I believe it would work as expected (login using a different ID, copy the files to that system, then sync them to the iOS device).

Also, the iTunes Matched files are unprotected, but they do have the original Apple ID embedded as an extended metatag. So obviously you don't want to be passing them to people outside of your immediate control.

But if the AAC (Match) files are unprotected, regardless of my email address being embedded in the metadata, then how come I can currently run two iPhones off two computer libraries/iTunes accounts but with one set of mp3 files being shared across both accounts?

Also, I have a couple of albums that were originally DL from the iTunes store (not by me) with someone else's iTunes account (which includes their email address embedded in the metadata) and the files work fine on both my iTunes libraries and devices.

Why would the 90 day rule apply if the AAC files are unprotected? From earlier responses, I assumed that this would only be a problem if I was using iCloud to DL the tracks to my devices, and not by replacing my whole library on my hard drive with the AAC files first.

Sorry but I am well confused again. A workflow of how Match and iCloud works would be helpful, does one exist for the simpleton?

Cheers

 

[roebeet]

But if the AAC (Match) files are unprotected, regardless of my email address being embedded in the metadata, then how come I can currently run two iPhones off two computer libraries/iTunes accounts but with one set of mp3 files being shared across both accounts?

Also, I have a couple of albums that were originally DL from the iTunes store (not by me) with someone else's iTunes account (which includes their email address embedded in the metadata) and the files work fine on both my iTunes libraries and devices.

Why would the 90 day rule apply if the AAC files are unprotected? From earlier responses, I assumed that this would only be a problem if I was using iCloud to DL the tracks to my devices, and not by replacing my whole library on my hard drive with the AAC files first.

Sorry but I am well confused again. A workflow of how Match and iCloud works would be helpful, does one exist for the simpleton?

Cheers

It's local files in comparison to iCloud files. Once the unprotected files (be it MP3's or AAC's) are on your local drive, you can move them around any way you want to. But if you are trying to log onto two different ID's on the same system, that's a different story.

Don't be concerned if you're confused -- I think a lot of people have issues with iCloud, in general.

 

[iBrody]

It's local files in comparison to iCloud files. Once the unprotected files (be it MP3's or AAC's) are on your local drive, you can move them around any way you want to. But if you are trying to log onto two different ID's on the same system, that's a different story.

Don't be concerned if you're confused -- I think a lot of people have issues with iCloud, in general.

So although I can currently log in with 2x different usernames and 2x libraries but using 1x location of where the music files are stored for my MP3 collection, are you saying that AAC files permanently downloaded on to my hard drive via Match which will take place of my MP3 files, will only work with 1x username and 1x library?

 

[roebeet]

So although I can currently log in with 2x different usernames and 2x libraries but using 1x location of where the music files are stored for my MP3 collection, are you saying that AAC files permanently downloaded on to my hard drive via Match which will take place of my MP3 files, will only work with 1x username and 1x library?

No, it's not about local files - my understanding is that it's about iCloud. So if login with an Apple ID on one system that has iCloud enabled, then you logoff and logon to another ID with iCloud enabled, you get that 90 day message. At least that's my understanding.

 

[iBrody]

Ok thanks.

Therefore as I won't be using Cloud, then the only downside I guess will be the fact that my username will be tagged in all the AAC files.