Why Photostory 3 Video Won't Play on your Smartphone Without WMP10 Mobile

[Jason Dunn]

<div class='os_post_top_link'><a href='http://www.microsoft.com/windows/windowsmedia/9series/codecs/video.aspx' target='_blank'>http://www.microsoft.com/windows/windowsmedia/9series/codecs/video.aspx</a><br /><br /></div>When PhotoStory 3 came out, and I saw that it had video export templates for Pocket PCs and Smartphones, I immediately whipped up a video and tried to play it on my Orange C500 Smartphone...and only got audio. Puzzled, I started to dig deeper, and I eventually found the answer - and I wasn't pleased about it.<br /><br />When Windows Media 9 Series came out, it introduced a series of new codecs that completely broke the Windows Media platform when it came to mobile devices. People using Windows Media Player 8 Mobile couldn't get a new version of the player, or the codecs, so there was a period of frustration and users had no choice but to buy new devices if they wanted to play back Windows Media content based on the 9 Series codecs. It was a frustrating period of time, and it upset a lot of people who felt they weren't getting the full benefit of their investment, but I thought that sort of thing would only happen once. I should have known better. :?<!><br /><br />The exact same thing is happening again now with Windows Media Player 10 Mobile and certain types of video files. With no fanfare, two new types of video codecs were introduced to the Windows Media family: Windows Media Video 9 Advanced Profile and Windows Media Video 9 Image Version 2. The latter one is causing the problem, because that's the codec that Photo Story 3 uses. Here's a description of that codec and what it does:<br /><br /><i>"With this new codec, still images can be transformed into video by using pan, zoom, and various transition effects. By combining transitions with pans, zooms, and cross-fades, an almost unlimited number of effects can be created. The results can then be delivered at data rates as low as 20 kilobits per second (Kbps). These files, compressed using either constant-bit-rate (CBR) or one-pass variable-bit-rate (VBR) modes, can be shared easily because they are much smaller than the original image files. Note that Windows Media Video 9 Image version 2 is not compatible with the previous version of the codec."</i><br /><br />So, in essence, this codec was needed in order for Photo Story to use the transitions from Windows Movie Maker. My question is, why? The Ken Burns-style photo zooms and pans are a perfect way to present photos. Cheesy video transitions might look good on a marketing bullet list, but in real life they should be avoided.<br /><br />The story for owners of Pocket PCs and Smartphones without Windows Media Player 10 Mobile is grim: <b>unless the OEM who made your device decides to release an update, you'll never get the player</b>. And even though the codec is all you need, Microsoft has no system in place to update WMP9 Mobile with the new codec - even though, technically, it should be possible because it has a codec-pluggable architecture.<br /><br />This is yet another sign that the OEMs who make and sell the devices want us to think of them as appliances, like a microwave, instead of real computers that can be updated with new software. :?

[Mike Temporale]

Is it not possible for someone to take the codec from one device and move it to another?

[phillypocket]

So, in essence, this codec was needed in order for Photo Story to use the transitions from Windows Movie Maker. My question is, why? The Ken Burns-style photo zooms and pans are a perfect way to present photos. Cheesy video transitions might look good on a marketing bullet list, but in real life they should be avoided.

It is my understanding that the codec facilitates panning, zooming, and fading programmaticly. Instead of 24 frames for every second of video, you can use a single frame and tell an application to zoom a particular amount, to a particular point. The question is how much work is done within the codec and how much work is done within wmp10. If it's happening all within the codec then maybe it can be added, (even thought that appears not to be the OEM's wish) howver the more I think about it the more I believe that WMP10 knows how to initiate the pans, zooms, and fades, and the codec facilitates this. In other words the instructions and raw material may be in the codec, but wmp10 may be needed for the interpretation.

And though I was initially annoyed that the format changed, I feel that the tradeoff at least makes sense. It may not be best for me, but I can see the logic behind it. And frankly, I long ago learned despite what I might want, I buy any unit that's not a computer (camera, game system, wma player, pda, phone, toster, electric shaver) for what it can do today, not the promise of what it might do tomorrow. Because for whatever reasons, that I may or may not agree with or understand (cost, time, profit, or feasability) it might change.

[Jason Dunn]

It is my understanding that the codec facilitates panning, zooming, and fading programmaticly. Instead of 24 frames for every second of video, you can use a single frame and tell an application to zoom a particular amount, to a particular point.

Interesting...thanks for the further details.

I understand what you're saying, but ultimately when Microsoft builds a platform they need to make sure they don't break it. Imagine if your desktop computer couldn't play a new type of video that they put out - you'd be ticked off. ;-)

[David Horn]

Likewise, Jason. When I bought my C500 I did it on the assumption that WMP10 would be released in a ROM update. Orange have no idea what's going on, and actually referred me to a Microsoft number.

[tvalentin]

I spoke to Orange about this a few times.

They have either told me to get in from Microsoft or even from HTC. 8O I think they don't know what they are doing.

It was particuarly infuriating to have Bill Gates (at the Media Cetre 2005 launch) hold up the US equivalent to the C500 (think it is an AT&amp;T) and say that this runs WMP Mobile 10.

Anyone else feel like trying to convince Orange to get this update for the C500

[nirav28]

I just bought a SMTP5600 (a C500 to you folks across the pond). Check the version in the about screen in WMP and it says WMP 10.0.

Not sure why orange left that one out.

Also, does anyone know if the i-mate version of C500 rom update will work on a SMT5600 , without turning it into a $350 doorstop? It was just recently released with some bluetooth bug fixes and several other issues. Since I bought this phone from AT&amp;T without a contract agreement. I think I'm SOL in terms of getting new updates. Audiovox is no help either. Not that I need an update. But who knows it might fix issues that I haven't yet ran across. :)

[phillypocket]

I understand what you're saying, but ultimately when Microsoft builds a platform they need to make sure they don't break it. Imagine if your desktop computer couldn't play a new type of video that they put out - you'd be ticked off. ;-)

That why back in the day I always built my systems. Companies from Apple to Packard-Bell felt that a component upgrade meant purchasing a new system that came standard with that component. Sometimes you could work around it... sometimes you couldn't.

Actually until I get a clearer understanding of what exactly the constraints are (which of course is unlikely, as getting sodium-pentathol into all parties in a small room ain't gonna happen) I'm not sure who I'd be annoyed at. Maybe I'll go up on C9 and see if I can get an answer there.

[Fred]

Can WMP10 (and maybe a DLL or two) be copied from the ROM of a SMT5600 and run from RAM in a C500? I'm only a recent convert from PocketPC (and PocketPC Thoughts) so I'm assuming these things work in a similar way. Would this be legal? It hardly seems like a copyright infringement, but I suppose technically it could be.

I know that the iMate ROM can be flashed to a C500 as I tried it, so I presume that the SMT5600 one would work OK too.

[Mike Temporale]

It might be possible. It's more work than it's worth, IMHO.

As for the legality of it, I think it would be illegal, no question. The ROM image is licensed to the handset manufacturer by Microsoft. They don't pay for WMP10, then it would be a copyright infringment to have it on the device. Just because the individual features and elements of the OS appear to be free to us, doesn't mean they aren't paid for in some manner. :wink: