how did convert vedio module 5.x to 6.x

I'm not a developer, though I will try to explain based on my several years experience working with Drupal. Video module was the first video/media module I tried with Drupal (as is common for many people, due to its good namespace "video"), and though it worked "ok" at that time, it was not what I could call a good experience. I then moved to FlashVideo module, which I found easier and more flexible. Later on I moved to SWF Tools due its substantial flexibility, ability to handle video and audio seamlessly, and its use of Filefield, which is the future standard of Drupal file handling. It also made it easy for me to use an Imagefield as the "preview" frame of a video, which in the case of a media portfolio like mine is preferable over an automatically generated thumbnail.

Video module approaches the process of a module in a manner that is no longer the "standard way" for modern Drupal modules. It was made before the time of CCK (which is an extremely powerful and versatile tool for adding fields to any content type), and Views (an extremely useful tool in Drupal which allows you to use a UI to generate a wide variety of custom listings of content or fields from content, without writing complex SQL queries or PHP to accomplish it). Since the tools and frameworks we now have in Drupal 5 and 6 were not available when Video module began, it did a lot of things on its own. It became a kind of "mega" module where it handles everything itself. Now though, most/every module is integrating closely with CCK/Views, sharing data and frameworks so that everything fits together kind of like lego blocks. The goal is for no module to ever have to "reinvent the wheel" so to speak (whereas in the past, nearly every module reinvented the wheel every time, so there was tons of duplicated effort by module developers as well as duplicated/inefficient code on end user's sites). A mega module like Video is left a bit on the sidelines in this... it does things its own way, and they're not necessarily compatible with other tools. This maybe isn't a big deal when you just focus on "video" on its own, though in the context of a full-featured site, this comes into play much more. Video module's project page says something about "custom fields" though this is not CCK, and won't integrate well with any other aspect of the site (and likely isn't a fraction as powerful as CCK). Views module support is evidently still on the "to do" list (though my impression is there is no one "doing", so it won't likely ever be done).

So far as the features of Video module you mentioned... * Most or all media handling modules in Drupal can work with all of these mentioned formats... * Other than Embedded Media Field module, most Drupal media modules are for local media only (some only display it, some such as Media Mover only process it, and some such as FlashVideo module both process and play it... * It's not clear what access controls Video module is referring to here - most other media modules also have access controls/permissions for various features. Actual "access control" though is done through a real access control module such as Content Access.

Anyhow, if you do not want to use Flash "converted" video that's ok (though using Flash does have the benefit of nearly universal compatibility, bypassing the need for system-installed applications as well as various codecs which some media might rely on). On the other hand, SWF Tools (or rather the flash players it can use such as JW Media Player or FlowPlayer) is "supposedly" able to wrap a variety of media types in the flash player's UI, and play them back (I've heard this "evidently" may allow the files of various formats to play so long as the user has Flash [not requiring the actual player applications] but I cannot confirm this). In some initial testing I've not had the best of luck getting files to play back in this way though... some files/formats played (though with issues like missing audio) and others gave errors. So I don't think that's a viable solution right now, or at least requires some level of extra setup I'm not aware of yet.

However if you wanted to avoid flash entirely and just rely on the end-user's installed applications for playback then you may prefer to go with Filefield (always, it is the standard file storage in CCK now) and instead of SWF Tools, look at jQuery Media. This relies on Javascript instead of Flash in order to deal with media files attached to a given node. From the original source, you can see that it does support non-flash media. There is a video guide on setting it up. With this you can use a flash player if you want, or alternately have the browser output the system's own media application (e.g. quicktime, windows media player, etc) assuming the user has the correct player and codecs installed (within the controlled environment of an internal intranet this is feasible, though on the internet for a general audience, will suffer from a lot of incompatibility). I've tried jQuery Media and found SWF Tools superior for my needs, but it's up to you.

In any case, I'd suggest you do not invest any time or resources into Video module (unless it's to create a migration tool for people who used it in Drupal 4 or 5 to switch to another video solution, though that's not likely something you'd want to do for your scenario... I haven't looked into it, but it's possible Media Mover could be used to help migrate people out of Video module). There's no support from the community and media developers for it, and it is essentially abandoned. Here's a quote from the Multimedia panel at the recent DrupalCon conference, by 3 of the top maintainers of multimedia-related modules in Drupal (including Aaron Winborn, who wrote the book "Drupal Multimedia"): "Just in case anybody here is fairly new to multimedia, we didn't mention the Video module and that's because nobody uses it. It's not used, don't use it. It's not maintained... just as a little warning." Similar comments have been made by various top Drupal developers working in the area of multimedia.

Anyhow, I hope this answer was helpful :)

Edit: added link to DrupalCon Multimedia video.