OK, today it's official: I'm a geek because I:
- figured out how to and then navigated to a specific location on my computer using the command line terminal!
- wrote my 2nd xml file
- successfully executed a script from the terminal command line
- even found several errors and successfully solved them in the instructions for the use of Chapter Tool
I've always freely admitted to being a geek. Today, it's official! By the way, Chapter Tool is cool!
If you want to submit your podcasts to the iTunes store, which is what I was doing today that necessitated all of this outrageous behavior, here are a few things you need to make your life easier:
- The directions on how to publish a podcast to the iTunes store
- Chapter Tool, which will make your podcast do the crazy things Steve talked about in the Apple Developers' Conference.
- This is also a handy link to a free RSS 2.0 validator at FeedBurner, the specification iTunes requires
Now, some advice for those geeks out there who want to get this to work. I give the advice because I had to resort to reading French and German websites to try to sort this stuff out. I'm serious. And I don't even read French or German. Google translation is way cool! There's not much information out there right now. I hope this information helps.
1. There are some errors in the instructions!
- If you use the sample.xml file Apple provides as your template for the xml file you must create, beware that the author forgot to close 2 <picture> tags. They close with /picture> and not the required </picture> tag. Those that know xml know it is utterly unforgiving on such things. Your project will not work with these incorrectly closed tags. Be sure to fix them in your document.
- In the "About Chapter Tool" document, there is a typo "./ChapterTool -x mypodcast.xml -a mypodcast.m4a -o myenhancedpodcast.m4a"-- one dot at the beginning of the command instead of 2. As I was blundering my way through trying to make this work, this just complicated things. I luckily assumed it was supposed to be 2 dots. It is!
- In step one of the same file, the reader is directed to use the command line in the terminal to navigate to Music/ChapterTool in your home folder. No. The way the remainder of the directions are written, I do not think this is accurate. I believe you must navigate to Music/ChapterTool/MYPODCAST where MYPODCAST is whatever name you give the folder you are directed to make for this project's files. Only then was I able to get the command line to execute without error.
2. If you need help learning Unix commands in the terminal, today I learned everything I know (which is not much) at these two web addresses:
3. The AAC file format, which has the .m4a file extension, will not work in Safari! It doesn't work in IE for Mac either. I don't know what happens in Windows. Unbelievable after all of this work!! Apple is working to resolve the issue--using my site to test it might I add. I spent a good bit of time bonding with them this afternoon when it all didn't work! Safari just downloads jibberish. And since it's a large file, it's a lot of jibberish to download! Even with Quicktime 7.0.1's MIME setting correctly set to enable proper handling of AAC and MPEG4 files, it doesn't work.
Firefox works properly by passing the file off to iTunes. Apple wanted to say it was a server-side configuration problem. I don't know. It could be. I'm working to sort that out and will let everyone know. But I rather doubt that. If Firefox can handle the file properly, Safari should be able to as well.
4. The mp3 file format works fine--just without all of the cool features made available in AAC--which is why I went to all of the trouble to learn all of this today. So, I decided to convert my m4a (AAC) file to the mp3 format in the mean time (until Apple gets it fixed). This is no longer an intuitive process. In fact, I searched for a long time trying to find where Apple hid the MP3 encoder--no mention of it in the Help files or on Apple's support site at all, grrr.
I'll save you the hassle I had. I don't think you're going to find this documented anywhere, and I knew it was in iTunes because I had used it years ago. I worried they had dropped the encoder because of a licensing issue. Here's where it is:
- In iTunes, under Preferences, click on the orange importing button.
- "Import using:" must be set to MP3 encoder.
- This then changes the drop down menu under [Advanced] for "Convert Selection to..." from whatever it was (mine was AAC) to MP3.
- It makes no sense whatsoever that the import preference changes the "convert selection to" command! This is somewhat akin to having to click on "Start" to shutdown a windows machine! Horrific thinking here! Apple needs to add to the preference button a selection drop down for "Convert selection to:".
OK, since you suffered through this whole post, you must have some interest in doing this. Here is the link to what I'm working on right now. You can see what works and what doesn't and how it behaves and misbehaves. If you figure out why, let me know.
Recent Comments