Posted by aaron on March 6, 2008 at 3:31pm
During our Drupal Multimedia panel on Monday, Nate Haug (quicksketch) mentioned that soon we will be discontinuing the Image module, and providing a migration for existing Image Nodes to ImageField (or its replacement).
The same thing needs to happen to the Video module. That could happen now. The module that provides a migration path for Video nodes will be king. But they'll also need to tap into the planned hook_file for d7, to keep from being dethroned.
Even if the Video module wants to survive, it will need to migrate from its current 4.6 mindset of video-as-a-node.
I'm just saying.
Comments
A big one to think through
Thanks for starting this thread. I'd like to see the concept of "video" split away from the two (or more) things that it comprises. "Video" really means file storage and presentation- I'm not sure that we should have something that is specific for "Video" storage, but clearly there need to be presentation options that solve some of the issues that video files have for web browsers.
An abstracted storage solution has the added benefit that it could be used for audio or other rich media formats. I think a field that can work with or without CCK that uploads the file and (possibly) has options to set the presentation options (choose a player from a set of players that implement a presentation hook) or the field sets a suggested presentation layer via file type.
I'm arguing for this because I think it can provide a high level of integration with other projects (for example, the flvmediaplayer module could provide a presentation layer for flv and xspf files), potentially simplifying the process of uploading rich media, and decreasing the complexity of administration.
I think we should also be watching the fileAPI discussion very closely. Particularly if it becomes possible to implement hooks on various file operations, this could heavily influence the direction that we want to go.
I'm arguing for a solution that is lightweight and focuses on extensibility over features. Let's follow CCK and Views and build a core that encourages the development of contributed modules.
http://24b6.net
emotionally invested
I would like to contribute to this conversation as well. I've got three or four community organizations, mostly media oriented, that are gnawing off their own hands while they wait for the a stable Drupal video solution to rise to the top. The Video module hasn't been stable in -years- and its not clear how long Asset might take to roll out, and the only solutions for these clients is to custom code a video module that is way out of their budget.
So, if there is anything that I can do to help out, test, discuss, debate, etc, then please let me know how to pitch in. I am very emotionally invested in finding a solution.