Adobe’s Flash Player has been getting a lot of press lately. Mainly in regards to HTML5, the Apple iPad (and its closed garden), performance on the Mac OS X platform, the changing face of mobile and other related discussions. The crux being Flash’s relevance and importance now and in the future. Posts and comments around the web have covered the entire spectrum, with everything from loquacious pontificating, to lugubriously laconic, to outrageously uninformed. They have all been quite polarizing in one direction or another. The biggest take away for me after absorbing everything for a week or two, has been the fact that the right people are listening and hear us and are also speaking up or acting. There have been several posts that I felt were especially well said and or align well with my own personal thoughts, so I wanted to highlight a few of them:

• Kevin Lynch, Adobe CTO: Open Access to Content and Applications
• Follow up comments from Kevin on that posting.
• John Nack, Adobe Photoshop Product Manager: Sympathy for the Devil and Adobe Isn’t in the Flash Business
• Grant Skinner: My Thoughts on the Future of Flash
• Jeremy Allaire, CEO of Brightcove: The Future of Web Content – HTML5, Flash and Mobile Apps
• Mike Chambers, Principal Developer Relations Adobe: Some personal thoughts on Apple and the trend towards closed platforms

There are quite a number of other great posts around, and even more that I felt were just way off base or totally wrong – but for me again the biggest take away is that people are listening and acknowledging things that can be improved and putting their money where their mouth is and committing to certain actions and more transparency. Kevin’s promise to have the Flash Player teams publish some performance metrics for the various platforms, the transparency and insight that Emmy Huang Flash Player Product Manager blogged about and some plans to improve bug reporting process’s around the Flash Player – these are really great things that exemplify the level of commitment and care that Adobe places on its products and the community of developers and designers that use them.

So how can you get involved to improve things and shape the future and stability of Flash Player 10.1 and AIR 2.0? Get involved and install the latest betas and test them!

Download and install Flash Player 10.1 Beta 2 and AIR 2.0 Beta 2

Then test against your existing content and applications, surf the web and check out existing content and most important of all: Report any bugs or problems you find at http://bugs.adobe.com/ – This is the critical step as engineering teams use bug reports to reproduce errors, and improve the overall quality and stability of the releases. You can also browse through existing bugs and ECR’s (requests for enhancements/new features) and vote for ones you determine to be important.

Flash Player 10.1 and AIR 2.0 are both at public beta 2 and available through http://labs.adobe.com/ with beta 3 releases a few weeks away and final candidates expected within 60 days. Now is the time to get involved and test and report any issues bugs you find.

There are public discussion forums you may also leverage: Flash Player 10.1 and Adobe AIR 2.0

Ted Patrick has a great post summarizing this effort, and another way you can help is to spread the word by tweeting directly about this: Improve Flash 10.1 & AIR 2.0 via Beta 2 http://bit.ly/cty7Nm READ & RT #Flash #AIR #QUALITY

Finally, its also worth noting that you can sign up to be considered for Adobe’s Prerelease teams to get further involved in beta testing their products via this link: http://labs.adobe.com/wiki/index.php/Prerelease

• Applications for iPhone via Flash CS5 Professional:
  http://labs.adobe.com/technologies/flashcs5/appsfor_iphone/
• Developing for the Apple iPhone using Flash:
  http://www.adobe.com/devnet/logged_in/abansod_iphone.html
• Public Beta of Flash CS5 Professional coming this year:
  http://labs.adobe.com/technologies/flashcs5/

Great article on what exactly this means and some more details by Mike Chambers here: http://www.mikechambers.com/blog/2009/10/05/building-applications-for-the-iphone-with-flash/

You can learn more about this announcement in the FAQ below as well as in the following places

• Adobe News Room (http://www.adobe.com/aboutadobe/pressroom/)
• Information about apps for iPhone on Adobe Labs (http://www.adobe.com/go/iphone)
• Information about Flash Professional CS5 on Adobe Labs (http://www.adobe.com/go/flashprobeta)

More about Flash Professional CS5

What did Adobe announce at MAX regarding Flash Professional?
Adobe previewed an early version of the next major version of Flash, Adobe Flash Professional CS5. Adobe also announced that a public beta of Flash Professional CS5 will be available for download from Adobe Labs later this year. That beta will include support for the ability to compile ActionScript 3® projects in Adobe Flash Professional to run as applications for iPhone. Interested designers and developers can go to Adobe Labs to sign up and to be notified when the beta is available.

What are the new features of Flash Professional CS5?
There are many new and exciting features in Flash Professional CS5. These include
• New text capabilities via the Text Layout Framework (TLF). Get unprecedented control and creativity with text in Flash projects. Advanced styling and layout, including right to left text, columns, threaded text blocks let you work with text in Flash like never before.
• XML based FLA files let you manage and modify project assets using source control systems, and enable teams to easily collaborate on files.
• Code Snippets panel provides pre-built code that can be injected into projects for greater interactivity and also reduces the ActionScript 3 learning curve. The panel includes code for timeline navigation (ie: click to go to the next scene) actions (ie: drag and drop), animation (ie: move with keyboard arrows), audio and video, event handlers (ie: mouse events) and loading and unloading of assets.
• Flash Builder integration. Use Flash Builder to write ActionScript code within Flash projects.
• Improved ActionScript editor, including custom class code-hinting and completion

When will the Flash Professional CS5 beta be available for download?
The beta will be available for download from Adobe Labs before the end of 2009.

How much will Flash Professional CS5 or Creative Suite cost?
We are not announcing any pricing at this time.

Where can customers go to be notified when the beta is available?
You can sign up to be notified: https://www.adobe.com/cfusion/mmform/index.cfm?name=fpcs5_notify

More information about applications for iPhone

Q: When will Adobe Flash Platform tooling support building applications for iPhone?
A public beta of Flash Professional CS5 including support for building applications for iPhone is planned for later this year. Sign up to be notified when the beta is available.: https://www.adobe.com/cfusion/mmform/index.cfm?name=fpcs5_notify

Q: How does the Flash Platform tooling update help developers?
The tooling update allows developers to use Flash technologies to develop content for iPhone and iPod touch, devices that were previously closed to them. Developers can write new code or reuse existing web content to build applications for iPhone. Because the source code and assets are reusable across the Flash Platform runtimes,—Adobe AIR and Flash Player—it also gives developers a way to more easily target other mobile and desktop environments.

Q: How is this different from Adobe Flash Player 10 coming to iPhone? Will iPhone users be able to view web content built with Flash technology in the iPhone browser?
The new support for iPhone applications in the Flash Platform tooling will not allow iPhone users to browse web content built with Flash technology on iPhone, but it may allow developers to repackage existing web content as applications for iPhone if they choose to do so.

Flash Player uses a just-in-time compiler and virtual machine within a browser plug-in to play back content on websites. Those technologies are not allowed on the iPhone at this time, so a Flash Player for iPhone is not being made available today.

Flash Professional CS5 will enable developers to build applications for iPhone that are installed as native applications. Users will be able to access the apps after downloading them from Apple’s App Store and installing them on iPhone or iPod touch.

Q: Can applications for iPhone built with Flash Platform tooling be delivered through Apple’s App Store?
Yes. Developers can deliver applications built with Flash Platform tooling just like any other iPhone application. This will require the developer to be a member of the iPhone Developer Program and follow the program guidelines.

Q: Do developers need to participate in Apple’s iPhone Developer Program in order to develop or deploy applications for iPhone using the Flash Platform tools?
Yes. A developer certificate from Apple is required in order to test and deploy applications to iPhone. Apple provides information on its developer programs at http://developer.apple.com/iphone/.

Q: Are applications for iPhone built with Flash Platform tools interpreted at runtime?
No. IPhone applications built with Flash Platform tools are compiled into standard, native iPhone executables, just like any other iPhone application.

Q: Can applications load SWF files or other code at runtime, such as a module from a website?
No. iPhone applications built with Flash Platform tools are compiled into standard, native iPhone executable packages and there is no runtime interpreter that could be used to run ActionScript bytecode within the application.

Q: Which version of the iPhone SDK/operating system is supported by the applications?
Applications can be built targeting iPhone OS 3.0 and later.

Q: Will applications built with Flash Platform tools work on iPod touch? iPhone 1.0? iPhone 3G? iPhone 3GS?
Applications should work on all iPhone and iPod touch devices. However, as the hardware specifications of the devices are widely divergent, content performance may vary between devices and device generations.

http://flashcamp.pfpaug.org/

Keep an eye on the site and on our twitter account: @flashcampphilly for more news and updates!

More info and event site to launch next week.

Stay tuned – it’s gonna rock!

• Tweetie – Atebits
• Google Earth – Google
• OmniFocus – OmniGroup
• Truphone for iPhone – Truphone

All great applications from very cool companies and talented developers – so just finding out we had been nominated in the same category was pretty cool, but finding out we had won was totally unexpected. Thanks Macworld! I also have to give total props to all the super talented and friendly developers and staff at Wolfgangs Vault – it was their vision in seeing the value of creating an iPhone app, as well as their amazing efforts and incredible content that made putting the Concert Vault app together possible. Thanks to Matt, Scott, Wade, Bill, Eric, Jeremy, and all the others who work behind the scenes at Wolfgangs Vault, Daytrotter and Crawdaddy – awesome job guys! Thanks for the opportunity!

We did have some good reviews of the app earlier in the year, one snippet from Rolling Stone magazine named Concert Vault one of the “Best Music Apps” which was really cool to find out. I was especially excited to hear we had won the Macworld UK award as this had been the first iPhone project that I worked on as I am primarily a Flash Platform developer. I am still teaching myself Objective C/Cocoa/Xcode, so I played a far lesser role than Andy did. I contributed some aspects of design, iconography, back end web services support, QA and a bit of project management, but securing Andy to work on the project is what I am most proud of as he is a truly talented developer and really knocked this one out the park. If you own or have seen a Neat scanner with the Mac version of NeatRecipts you have seen some of Andy’s other software development efforts (along with some other friends of mine at Neat) Andy is also doing a fantastic job running the local Cocoaheads group, where I have been fortunate enough to make a number of additional friends and discover that we have a large and talented group of Apple Mac/iPhone developers in the local area. I was quite aware of all the local Flash and Flex talent in and around Philadelphia thanks to the Flash Platform User Group I manage with my friend J Marziani, but I hadn’t really been exposed to all the other Mac native application developers in the area. Thanks to Andy and the group, I’ve found out that the following developers and their popular Mac/iPhone apps are right in our area:

• Mike Zornek and his application Billable (which I actually use for all my client invoices)
• Jason and Chris Laan most recently responsible for the great new iPhone version of Tweetdeck
• Jason Allum, Dave Martorana and the rest of the guys at Indy Hall labs who are responsible for apps like: RipIt!, Twistori, MultiPlex
• Far McKon – fellow co worker of Andy’s at Neat Receipts (lots of great guys at Neat including Vanja Buvac, Harris Romanoff and others)
• Louis Gerbarg who wrote the original PPC backend for the venerable LLVM compiler and numerous other projects directly for Apple
• Corey Floyd who along with his team at Advanced Medical Data Solutions are responsible for the iPhone app Compounds
• Jason Tremblay, Chris Conley and Randy Schmidt of iSepta fame
• Of course Philadelphia can also claim John Gruber of daringfireball.net fame as one of our own (John when are you gonna come to a meeting?)

These are just folks off the top of my head that are related to Mac development in the area, there are way more talented people and companies in the tech industry covering a wide range of disciplines all over the area (I should start making another big list for a future post). I want to make sure and give a shout-out to Alex Hillman and Geoff DiMasi of Indy Hall and all the folks who call Indy Hall home, as they have been very generous and supportive in allowing both the Cocoaheads group and our Flash Platform User Group to meet at Indy Hall, including run classes and sponsor our events – thanks guys!

I’d like to wrap this post up by noting that I keep seeing more and more talented Flash developers taking on and delivering some really amazing Objective-C/Cocoa applications both for the desktop and iPhone/iPod touch devices. Apple has done a really great job with the app store and not only do developers clearly see a straightforward path to monetizing their efforts but so do managers, owners, investors, etc. As much as I am enjoying learning Objective-C/Cocoa, and can see all the potential reasons why Apple wouldn’t even consider allowing a Flash player of some sort on the iPhone. I am still a Flash developer at heart, and I am really rooting for Apple and Adobe to come to an agreement and get a Flash player or some solution for allowing Flash content to be deployed to iPhones/iPod Touch devices. I just got my 32GB iPhone 3GS today and it is super snappy fast with its 600Mhz ARM-A8 processor. Considering that Adobe and others have made announcements about the Open Screen project agreements with Intel and other hardware manufacturers to get Flash Player 10 working on ARM based devices that utilize ARMv6, ARMv7, and ARM11 chips and the  Cortex-A (ARM Cortex-A8) found in the iPhone 3GS  (some of those running at only 400Mhz) – and to accelerate performance through custom ASICs and GPU chips from the likes of Nvidia, as well as deliver Flash to set top boxes and other consumer devices, not to mention some special sessions at Adobe MAX 2009 later this year. I have to believe and have faith that at this point, it is literally down to Apple and Adobe coming to some mutual agreements as opposed to any true technical hurdles. So guys, here’s to working it out, and making even more opportunities for success for all of us developers and consumers trying to raise the bar.

I liked how Ryan handled the line numbering on the left, but it was missing a nice way to quickly view the code in plain text, copy the code to your clipboard, or save it directly as a download. Several of the other solutions had features like that in the top header of the code, and I liked that, so I quickly hacked in support for that. The show in plain text icon simply leverages the built in thickbox.js built into Wordpress and some JavaScript to get that done I quickly shoehorned that in. The other two icons for copy to clipboard and download and save were done through Flash. I leveraged the System.setClipboard() function to quickly push the code onto the users clipboard, as well as externalInterface to pass back a success notification to the browser and end user.

For the file download and save code, I was going to use AS3 and the filereference.download feature, and javascript to parse the code out of the page, and then download it directly to the users system with a standard OS dialog – but it was late and I didn’t feel like spending the time to parse the innerHTML with JS before passing it in to Flash – so I cheated and just pass it all in as a urlencoded Flashvar, and then do a roundtrip to my server with the code as POST data, and then leverage the filereference.download feature of Flash 8 AS 2.0 to accomplish what looks like the identical behavior. I’ll probably go back and clean this up and redo it the right way with AS3 so I don’t have to make that server trip, but I’ll save that for another day. The current version is smart enough to know when ActionScript is the language and automatically set the default filename extension to .as – and it also broadcasts a little download complete to the browser via externalInterface when things are complete, so its 99% of what I wanted and also nearly 100% compatible with most users installs of Flash. The tiny nature of the size of the SWF doesn’t lend itself to even using the Express Install feature of Flash 6+ to upgrade to 9, so think this was a good compromise, although I already have a workaround for that as well, with a self-resizing DIV and SWF combo.

I would also like to clean things up a bit more including making some more XHTML friendly changes to the html output and then submit my changes to Ryan for inclusion in a future version, as it would probably be too much ongoing work to make and then maintain a plugin that patches his plugin. Anyway, below is a quick sample of the output with a handy little contrain/resizing function I use often. Including some basic CSS adjustments to give alternating background colors on the lines (it looks decent in Safari at default text settings, but I have to put in some conditional CSS tweaks for other browsers to get the alternating line colors to line up better) – at least I now have a solution I like for posting code snippets. If anyone wants to get the source for this and hack away at it yourself, let me know and maybe I’ll bundle things up as they stand now and someone else can refine things a bit further, its really only some changes to the main wp-synax.php file, a dependency on SWFObject 2.1, and the custom little Flash widget I put together.

// AS3 example function to constrain an object's width/height proportionally with a given objects new targeted dimensions with optional rounding
function reSize (originalSize:Object, targetConstraints:Object, round:Boolean):Object {
    var scaleFactor:Number = Math.min( (targetConstraints.width / originalSize.width), (targetConstraints.height / originalSize.height) );
    var newSize:Object = new Object  ;
    newSize.width = round ? Math.round(scaleFactor * originalSize.width) : (scaleFactor * originalSize.width);
    newSize.height = round ? Math.round(scaleFactor * originalSize.height) : (scaleFactor * originalSize.height);
    return newSize;
}

var obj = new Object;
obj.width = 800;
obj.height = 600;

var newObj = new Object;
newObj.width = 640;
newObj.height = 500;

var objTarg:Object = reSize(obj, newObj, true);

trace (objTarg.width+"x"+objTarg.height);

 

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

// AS3 example function to constrain an object's width/height proportionally with a given objects new targeted dimensions with optional rounding function reSize (originalSize:Object, targetConstraints:Object, round:Boolean):Object { var scaleFactor:Number = Math.min( (targetConstraints.width / originalSize.width), (targetConstraints.height / originalSize.height) ); var newSize:Object = new Object ; newSize.width = round ? Math.round(scaleFactor * originalSize.width) : (scaleFactor * originalSize.width); newSize.height = round ? Math.round(scaleFactor * originalSize.height) : (scaleFactor * originalSize.height); return newSize; }   var obj = new Object; obj.width = 800; obj.height = 600;   var newObj = new Object; newObj.width = 640; newObj.height = 500;   var objTarg:Object = reSize(obj, newObj, true);   trace (objTarg.width+"x"+objTarg.height);

Takanobu Izukawa of the Spark project:
http://www.libspark.org/wiki/SWFWheel/en
http://www.libspark.org/wiki/SWFSize/en

Gabriel Bucknall – PixelBreaker – AS3.0 MouseWheel on Mac OS X
http://blog.pixelbreaker.com/flash/as30-mousewheel-on-mac-os-x/

Ali Rantakari – Mac OS X Mouse Wheel Support for ActionScript 3 Flash Applications (v.2+)
http://hasseg.org/blog/?p=138

Matt Giger – Simple solution for MOUSE_WHEEL events on Mac
http://blog.earthbrowser.com/2009/01/simple-solution-for-mousewheel-events.html

And here is a link to download a modified version of the JavaScript portion of Gabriel “PixelBreaker” Bucknall’s solution that I worked on to fix a few issues and add some functionality grab it here. I like Gabriels version as he put together an AS2 and AS3 version, it works perfectly with SWFobject 2.1, and with my fixes, multiple items on a page. I had started working on another version that also used externalInterface to leverage the anonymous function injection approach, but given that all three other variations on this issue already provide that functionality, I didn’t want to re-invent the wheel.

Also, note that all these approaches rely on leveraging externalInterface to pass info back forth between the browser/JavaScript and Flash. If AllowScriptAccess is set to NEVER in your embed, none of these projects will work. For what its worth there is a bug thats been logged on Adobes JIRA Bug system here: http://bugs.adobe.com/jira/browse/FP-216 – that is looking for extra votes – it is related to the current inability to reliably detect what AllowScriptAccess and other HTML properties of Flash have been set to. The best solution and request is to make these items available as System.capabilities.xxxx properties available at runtime. That would be great – so make sure you check out the link and vote it up for the next release of the Flash player!

UPDATE 03.10.09 – 12:51AM: I initially uploaded an old version accidentally – doh! I’ve updated the file, which fixes some issues with multiple instances of Flash on a page. Specifically where Flash instances not registered with SWFMacMouseWheel were still preventing the default page/document scroll if you happened to be mousedover them and they were receiving input. I also included a reference to Richard “Rillkill” Rodney for his tweaks for Safari for PC in the JS and AS3 code – which I failed to note requires changes in the AS to support Safari for PC. I also made a quick change to the AS2 version and zipped them both up and added them to the downloads page. If you don’t need Safari for PC support then you can stick with the original AS files from Gabriel/Pixelbreaker. Enjoy!

The video in question was over 8 hours in length, 8 hours 26 minutes and 26 seconds to be exact. It was encoded using the On2 VP6 CODEC and clocked in at 1.4GB in size. Not the typical average length and size for an FLV by any means, but I thought it certainly should be supported as it plays fine when streamed, or progressively downloaded, but the duration value was wrong. The other metadata values were correct, just duration.

Unfortunately this file was to be hosted on bitgravity’s network using their advanced-progressive delivery – a customized high performance, scalable version of the pseudo-streaming technique made popular by Stefan Richter and others as described here. So this compounded the problem as the bitgravity player requires the duration to be correct in order to calculate the proper position of the scrub/seek bar and to keep track of the offset of the beginning of the video when jumping/seeking which causes new requests for the video to be sent out, where a server side process looks at the video and its embedded keyframe metadata as well as the duration, recalculates the proper header, and begins sending data from the approximate requested keyframe position onward. So having an incorrect duration really fouled up playback in this specific instance of the bitgravity player.

Each tool I tried using to inject/view the metadata, including: flvtool2, flvtool++ and jflvtool all inserted incorrect values – and the results varied from tool to tool. I was going to try Burak Kalaycis FLVMDI metadata injector tool, but as luck would have it, Burak is also on Stefans mailing list, and he chimed in and mentioned that FLVMDI has some other limitations on the file size of videos that it can process (currently limited to 700MB), and that I would probably hit that issue first. So I didn’t run it through FLVMDI – but Burak did also confirm that his tool also suffers from the same problem, where the duration value would be incorrect, and if he gets a chance to fix it, he would update us on that.

The key issue does indeed relate to the length or duration of the .FLV itself and the FLV container format and specs for how the duration metadata value is stored. For videos that are under approximately 4.5 hours, everything is fine. However, once a video exceeds a little over 4 hours and 39 minutes, this is when the duration values appear incorrect with these tools, and all of them report back a value of around 16777.990 seconds in duration, a little more than half of the 8 hours 26 minutes of the video I was working with, which should have reported 30386 seconds.

I assumed that the problem might have something to do with the extra long duration, so thats when I began doing some research on the maximum length of FLV’s. I determined thanks to some help from Asa Whillock that the problem lies in how the duration value is stored in the .FLV container and the publicly available specs that were available at the time to third party authors that developed these applications. Originally the spec (prior to FMS 1.0) only designated a 3 byte integer type (UI24) to store the duration in milliseconds, or just enough to store a value corresponding to (256*256*256) 16.7 million or 16,777,990 milliseconds or 16777.990 seconds or 4 hours, 39 minutes, 37 seconds. So any video with a duration greater than that that can’t be represented with the single 3 byte sequence as the original FLV spec listed. Asa pointed out that in the recent spec they added an extended 7 byte UI8 tag named “TimeStampExtended”. This tag is to immediately follow the original 3 byte UI24 “TimeStamp” tag, and then both values are used to store the time. In this arrangement the original “TimeStamp” tag acts as the lower 24bits of the duration in milliseconds, and the “TimeStampExtended” acts as the upper 8 bits of the duration in milliseconds. This results in a 4 byte representation when combined, (256*256*256*256) so a maximum of 4.2 billion or 4,294,967,296 milliseconds or 4294967.296 seconds or 1193 hours, 2 minutes and 47 seconds or nearly 50 days straight worth of video. This would certainly allow just about any videos duration to be stored properly in the metadata.

So it looks like the solution to the the problem is to make sure the duration is stored using not only the “TimeStamp” tag but also the “TimeStampExtended” tag in order to store the full value of the duration for any video that exceeds 4 hours, 39 minutes and 37 seconds, otherwise the duration will be truncated to only the first 3 byte representation. To me this looks like a fairly easy fix (although the devil is always in the details). Burak is already aware of the issue, and I have gone ahead and emailed the info to Chris Norman of Facebook who wrote the c++ flvtool++ implementation, as well as Norman Timmler over in Germany who wrote the flvtool2 in Ruby. I still need to write the author of the java based jflvtool. Fernando Florez of Funciton Communications mentioned a colleague of his has a Python based metadata injector that also suffers from this issue, but they are working on a patch and will try to release that as open source at some point. So I have hope we will have a third party tool capable of handling videos of this length in the short term.

If it helps anyone else working on similar tools, the exact reference to the “TimeStampExtended” tag is on page 9 of Adobes Video File Format Specification Version 9

I haven’t yet had a chance to see if any commercial products like Sorenson Squeeze, On2 Flix, and the Flash CS3 Video Encoder correctly store the duration for videos over 4:39:37 in length – but will try to validate that and update this article once I’ve had a chance. I’m making an assumption the Adobe’s encoder does support it properly.

Thanks to Asa Whillock of Adobe for input and validation on this, as well as fellow Adobe Community Experts Fabio Sonnati and Stefan Richter and his invaluable FLASHMEDIA mailing list and to Burak Kalayci and Fernando Florez for their input and thoughts. Thanks guys!

UPDATE: 09/02/08 - I found another nice FLV metadata injector: YAMDI – http://yamdi.sourceforge.net/ but it also appears to suffer from the same bug.

Its been several days and I still have yet to hear back from Bitgravity about their FLVMDU tool that their CTO Barrett Lyon posted about in the comments. I emailed him directly right after the comment was posted, as well as through support as he noted and got a ticket #1678, but have yet to receive a response from Barrett or their support staff. Chalking it up to the holiday weekend.

UPDATE: 09/03/08 -I spent some extra time tonight trying to locate a copy of the Bitgravity FLVMDU tool and with a little careful url guessing, was successful and found this link to the tool – it also includes the source under a GNU license which is nice. This version is dated 06-18-2008 as version 1.0.0. Unfortunately after running it through the same series of tests on a video with a duration greater than 4 hours 39 minutes and 37 seconds, it also fails to write the proper duration on such a long video. So it appears that bitgravity needs to also update their utilities to support the “TimeStampExtended” tag. There was a note to contact a “pclarke” at bitgravity in regards to bugs – so I’ve dropped them a note and pointed them at this article. Hopefully they will be able to fix things as of right now every FLV metadata injector tool I’ve tested suffers the same problem.

UPDATE: 09/03/08 12:37AM – I found one more nice flv metadata injector and dumper called flvmeta available here http://code.google.com/p/flvmeta/. The source, and pre-made binaries for windows and Mac OS X are available, but it too appears to suffer from the bug I’ve been exploring since it doesn’t appear to support the “TimeStampExtended” tag either. Looks like everyone completely missed this in the spec, or just didn’t implement it for some reason.

UPDATE: 09/03/08 12:24PM – I heard back from Perry Clarke at Bitgravity in response to my email to him about the bug/lack of support for “TimeStampExtended” in their FLVMDU tool. Perry noted, “I haven’t reproduced the issue you report though I can believe it’s a problem. I’ll look into it when I have time.” So if you rely on FLVMDU when working with bitgravity, you’ll probably need to pester Perry or their support team to implement proper support in FLVMDU if your video is longer than 4 hours 39 minutes 37 seconds, especially if you are using their advanced progressive http delivery for videos – as that service requires the keyframe/metadata hinting and proper metadata duration tag otherwise it wont work properly. If they don’t update the tool, you’ll need to deliver your video in smaller chunks (less than 4 hours 39 minutes 37 seconds). I’d recommend smaller chunks anyway given the memory usage.

UPDATE: 09/08/08 7:40PM – Last week I heard back from Dan Weatherford of Facebook and the primary author of flvtool++ He was very responsive in working with me to get in the proper support for the “TimeStampExtended” tag for proper durations on long videos. We made a number of test files from a variety of all the popular FLV exporters and transcoders and Dan was able to implement the full spec in the latest version of flvtool++ 1.1.2 available here: http://mirror.facebook.com/facebook/flvtool++/ The funny thing was that we found was that not a single tool, none of the flv metadata injectors out there, nor any of the FLV encoders we tested put in the proper duration in “TimeStampeExtended” format. Not ffmpeg, not Squeeze 5, not On2 Flix, not even Adobe Flash CS3 Video Encoder (standalone or Quicktime Exporter) and even a few upcoming apps currently in beta that I have access too – none of them inserted the proper duration in “TimeStampExtended” format for videos over 4 hours 39 minutes and 37 seconds. I thought this was especially odd for the Adobe apps – so it just looks like everyone totally overlooked this. Thanks so much to Dan Weatherford for his time in implementing proper support into flvtool++. Its currently the only tool I know of that properly supports “TimeStampExtended”