I haven't listened to it yet, but it says 39 minutes and change. I listened to the very beginning and end. Seems ok
I'm on the East Coast so my iTunes was open long before you pushed the podcast. I opened up iTunes around 10 am (7 am PST) and kept it up all day. It automatically looks for downloads. I just checked the preferences and it checks for downloads once per hour. It stated the next time it will check is at 4:45 pm (EST). So if you put it in the feed at 15 minutes after the hour (for example), my iTunes wouldn't have checked for it for 30 minutes. Perhaps this is important?
Hope this helps.
I have heard from a reasonable amount of people over the past week about issues downloading BOL. Today, for example, it seems a lot of people only got a 7 minute podcast. I am trying to investigate how this is happening because, quite frankly, before I ever push the podcast live to everyone, I check the link, wait for it to download the podcast entirely, and then check the downloaded audio to ensure that the entire podcast was served to me. Then and only then do I publish the XML feed that updates your podcatchers.
My question: If you ended up with a 7 minute podcast today, do you normally keep iTunes up all the time (or rather, was it up from 11AM PST and onward)?
My guess is that the podcast hasn't cached completely to all of our servers... and so if you happened to have iTunes up when the feed hits iTunes, then iTunes will see that and try right away to download the podcast. If it hasn't fully cached, then a 7 min podcast ends up in your feed. In order to get the full podcast, you would then have to delete the podcast and redownload the episode.
Did this happen to anyone who opened their iTunes after 1PM PST? And by open, I mean launching it for the first time today at around 1PM PST?
That is important for me to know the distinction. If anyone can help throw some info my way, I can try to see why this keeps happening and figure out a way to prevent it in the future.
We all want the podcast up ASAP. But waiting for a file to cache in an unknown-to-me server somewhere in CNET makes this task a much more difficult thing to figure out a solution for. Any info appreciated.