Rupert, If instead of pasting the blip embed code, we use vPIP and paste the permalink to the blip files into vPIP -- will all this be sorted out beautifully? I believe so... vPIP also gives us the ability to have multiple formats on one post, and separate feeds for each of those formats.
Jen On Nov 7, 2007, at 7:18 am, Rupert wrote: > Thanks, Mike > I'd been meaning to write to you about it since I posted that here > yesterday, and hadn't got round to it. > The only problem with using the Blip feed for iTunes is that I'd lose > the ability to let people click through to my Blog from iTunes - > there are permalink arrows on each episode in iTunes that link back > to the original post. > If you take the rel="enclosure" off the flv link, that'd sort it out > fine. > You could also allow people to set what type of file they want to > prioritise for podcasting in their crossposting code. Feedburner will > make enclosure of the first file with a rel"=enclosure". If people > want that to be flash, fine, but maybe they could set that manually > from a little pulldown menu in the preferences or sharing menu. > I think your crossposting and autocrossposting is so futuristic that > it makes me want to cry, especially when combined with the mobile > upload. I highly recommend all videobloggers who use Blip to > investigate it. > > Rupert > http://twittervlog.tv/ > http://feeds.feedburner.com/twittervlog/ > > On 6 Nov 2007, at 20:58, mikehudack wrote: > > Hey guys, > > Thought I'd chime in here. A couple things: > > * You're going to have the best experience using blip to get to iTunes > if you use your blip iTunes feed to do it. Your blip iTunes feed is > http://yourname.blip.tv/rss/itunes/ > > * If you use FeedBurner in this fashion it'll still work, but you may > run into problems like these. > > * We're about to refactor our cross-posting system in an upcoming > release (probably maybe a month off) and we're going to address this > problem in that refactoring. The entire cross-posting workflow and > templating system will change... and those changes, in addition to > making everything more elegant and more efficient, will almost > definitely solve this problem. > > Yours, > > Mike > > --- In [email protected], Rupert <[EMAIL PROTECTED]> wrote: > > > > Schlomo, > > > > Feedburner will make an enclosure for the first video file it sees a > > link to, unless it sees a rel="enclosure" element. > > > > So when you used to just link to your mov file, it'd turn that into > > an enclosure that iTunes could see. > > > > But now you're copying the Blip copy & paste code. And that contains > > two links to Flash files with rel="enclosure"s in them. So > > Feedburner sees that and turns the flv file into the only enclosure > > for that post, and so iTunes ignores it. If you also had a > > rel="enclosure" in your Quicktime link at the bottom, Feedburner is > > smart enough to prioritise the mov file over the flv file. > > > > So what you need to do is add a rel="enclosure" to your Quicktime > > link. Then Resync your feed totally (the nuclear option) in the > > Troubleshooting section of Feedburner and you'll be fine. It will > > prioritize your mov rel="enclosure" over the two flv > rel="enclosure"s > > in the Blip player code. Though you could just delete those, just to > > be sure. > > > > Actually, there's something else you should be aware of. If you copy > > & paste your code immediately, before Blip's had time to do the > Flash > > conversion, the Copy & Paste code that they give you links to the > > original file (Quicktime mov or whatever), with a rel="enclosure". > > This is what you have on Rabbits and Weddings, which is the only > > other mov file that's an enclosure in your feed. > > > > But if you wait until the Flash conversion is done before copying & > > pasting, you get only the flv files in the Player code, with > > rel="enclosure" in the links, and that's what screws you up. > > > > What Blip should really do is either get rid of the rel="enclosure" > > attached to flv files, which hardly anybody wants, or just STOP > > changing the copy & paste code after it's done conversions. It > > should keep the original file in the copy & paste code. It'd still > > play in a Flash player when clicked, because of a magic little > script > > Blip puts in there that tells it to play the flv file if one is > > available. And it would stop you having to manually code a link to > > your mov file with a rel=enclosure. > > > > Rupert > > http://twittervlog.tv/ > > http://feeds.feedburner.com/twittervlog/ > > > > > > On 4 Nov 2007, at 18:18, David Howell wrote: > > > > Try resyncing your feed in feedburner. That might work. > > > > David > > http://www.taoofdavid.com > > http://www.davidhowellstudios.com > > > > --- In [email protected], "schlomo rabinowitz" > > <schlomo@> wrote: > > > > > > Thanks Bill and ssukotto for the advice; but I'm still confused... > > (I've > > > already tried to re-ping the services.) > > > > > > Ssukotto, how do I tell feedburner to use the quicktime? I've > > always put > > > the quicktime as a link in the title post so the aggregators take > > that > > > first. Always worked before; why the change? > > > > > > > > > > > > On 11/3/07, ssukotto <ssukotto@> wrote: > > > > > > > > > > > > > <http://feeds.feedburner.com/EchoplexPark> > > > > > > > > Hi Schlomo--the problem is in the Feedburner feed. For recent > > > > episodes, it is inserting the .flv version into the feed. Not > sure > > > > why, but since this version is not QuickTime compatible / > > > > downloadable, neither the iTunes Store nor individual copies of > > iTunes > > > > can see those episodes. Check the source feed, make sure the > > QuickTime > > > > version is properly referenced there, then ping it with > > Feedburner again. > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Schlomo Rabinowitz > > > http://schlomolog.blogspot.com > > > http://hatfactory.net > > > AIM:schlomochat > > > > > > > > > [Non-text portions of this message have been removed] > > > > > > > > > > > > > > > > > [Non-text portions of this message have been removed] > > > > [Non-text portions of this message have been removed] > > > [Non-text portions of this message have been removed]
