Quote Originally Posted by dflat View Post
Not sure what this means exactly. I know that many ISPs have a maximum file size restriction for (perhaps both) sending and receiving. This is why many use Dropbox or ftp or MobileMe (Mac), cloud-based services etc. for sending and receiving big files. Also if you are sending (or receiving) through your work, the computer system there might be restricting file sizes also.
- Not that our song codes are large, but if there is 'corruption' or alterations/additions or confusion of what it thinks it is, then it might create an error message (as unhelpful as it is.)
(referring to the error message I got) I suspect what it means is not that the data in the message/object/iRealBook thingy is too big. As far as I can tell, the song's entire content is being used as the link. So Chrome looks at it and sees it as a URL too big to parse. Does that make sense?

There has to be an easier way to "package" the song for transfer to an iPod etc that doesn't run into all these variables. But I admit I can't think what it would be.