<!> This page is now protected by an ACL (writable by Koumbit Members only) because of repeated spam attacks. -- TheAnarcat 2008-08-02 14:13:55

Welcome to the FilmForge development pages! If you're just looking for a description of the project, check out FilmForge. If you want to see a demo, check out http://filmforge.koumbit.net. If you want to help with development, you've come to the right place!

Timeline

Known issues

Transcoding checklist

Checklist of filetypes and whether we have succesful test for upload, thumbnail, and transcode to flv. (later let's test transcode to ogg, working in browser w/cortado, and torrent.)

Format

Upload?

Thumbnail?

flv?

ogg?

torrent?

mov

yes

yes

yes

?

?

avi

yes

yes

broken

?

?

mp4

yes

yes

yes

?

?

wmv

?

?

?

?

?

ogg

?

?

?

?

?

H.264

?

?

?

?

?

x264

?

?

?

?

?

MPEG2

?

?

?

?

?

MPEG4

?

?

?

?

?

DivX

?

?

?

?

?

wmv

?

?

?

?

?

lagarith

?

?

?

?

?

(etc.)

?

?

?

?

?

Video edit errors

I see this error when editing a video node (without uploading a new video in):

The video then doesn't show up anymore and the node needs to be re-edited to show the vid properly. -- TheAnarcat 2007-06-27 09:45:51

Another problem: sometimes, the interface gets stuck on "Sending video... please wait.". -- TheAnarcat 2007-06-27 09:48:55

Editing youtube nodes breaks them. -- TheAnarcat 2007-06-27 12:42:36

Transcoding issue: no sound

Transcoded videos don't have sound. -- TheAnarcat 2007-06-27 12:42:36

Fixed with:

aptitude install w32codecs  ffmpeg sox toolame vorbis-tools lame lame-extras faad

-- TheAnarcat 2007-06-27 13:53:05

Notes about the implementation of the FilmForge site

This should be useful both during the project for monitoring and decision-making and after for reporting/writing about the experience on drupal.org and other outlets.

Applied / contributed patches

  1. mpg support (patch adapted)

  2. redo conversion on updates (contributed)

  3. ffmpeg deployment instructions (contributed)

  4. "busy.flv" processing video (contributed)

  5. fix infinite loop (contributed)

  6. .pot update (contributed)

  7. full-screen flash player (contributed)

  8. Video info (ffmpeg_helper) fails on pre-existing videos (patched, then reverted)

  9. ffmpeg_helper tries to process external videos (contributed)

  10. ffmpeg_helper: don't say you're not doing anything (contributed)

  11. Youtube thumbnails (patch adapted)

  12. no sessions patch (contributed, reverted)

Video

Really Free Video

we join with others on a CMS agnostic ogg&cortado solution:

transmission has implemented ffmpeg2theora in combination with Cortado a couple of months back, just haven't had time to tie up the loose ends and release it yet. We are also going to implement the metavid method of using Javascript checking for:

Mozilla browsers)

and installing Cortado plugin if the first two are not available. This covers other efforts to support Ogg in the browser that are emerging, as well as providing Cortado as a baseline. We are using the Icecast streaming server to serve Ogg files with this Indytube implementation. It all seemed to work quite smoothly.

Flash Video

Some codecs were missing, which was breaking sound:

aptitude install w32codecs  ffmpeg sox toolame vorbis-tools lame lame-extras faad

video.module

cck video field

Neighborhood CCK

Images

Wiki

Multi-lingualism

Needing French translation

Needing Korean translation

Needing German translation

Categories / taxonomy

We have decided not to translate taxonomy items due to limitations of the i18n/taxonomy hooks (which don't work very well) and I have enabled the freetaging for the "Tags" vocabulary (formerly known as "Category"). -- TheAnarcat 2007-06-27 09:38:29

Question: does tags currently support other character types (for example here, hangool (korean) characters? If not, this would be interesting functionality for the korean team to implement.

Modules installed/to install/to review/rejected

To install

High priority for review

Low priority for review (possibly useful in future versions, can ignore for now)

Reviewed and rejected (why?)

Meetings

<< <  2014 / 7 >  >>
Mon Tue Wed Thu Fri Sat Sun
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31      

The meeting planner is useful to figure out proper times for meetings. We usually hold meetings at 1600UTC (1200EDT / 0900PST / 0100KST), but another window of good meeting time is also 2300UTC (1900EDT / 1600PST / 0800KST).

Analysis

At the beginning of the project, we documented each tool with "Existing software" and "Spike":

Existing software
software that already exists and that we'll need to install/deploy on a demo.
Spike

a SpikeSolution we'll need to implement as a proof of concept

From this, we determined what functionality to include in the first version and what would have to be pushed back for future development.

Script tool

This would be a wiki; project initiators could determine levels of access to collaboration, anywhere from no collaborators (the script is already complete) to invited collaborators (project initiators invites particular individuals and they get script editing permission) to registered users to completely open (anyone can access and modify the script). Once the script is 'done' (to be determined by either project initiator or all participants), it can be 'frozen' (or forked) and the project can move to the next stage: storyboard.

Existing software
Spike

Storyboard tool

Based on the script, project collaborators (again, open/closed determined by project initiator) use this tool to generate storyboard from the script.

Existing software
  • image module and the general file upload mechanisms allow crude file sharing

  • Slideshow modules: slideshow, slideshow_creator, useful for viewing, maybe, but not for producing

Spike

Shot (media) acquisition tool

Based on storyboard, participants submit media (footage, stills, audio, etc.) to the project's media bin / pool.

Existing software
Spike
  • Make sure those generate thumbnails (with the Video FFMPeg Helper module)

Logging tool

(maybe combined with acquisition). This allows participants to view, select, tag, and rate media that has been submitted to the project. With video clips, needs to be able to allow browser based submission of in and out points. Ideally this is done directly within the clip viewer (see example of this capability at http://jumpcut.com; http://eyespot.com) but can also be a simple webform for entering timecode in/out.

Existing software
Spike
  • ?

Editing tool

Again, remember that project initiators can open or close the editing stage as much as they want. Maybe they have a particular editor they want to work with; maybe they want it completely open to public. Maybe only some segments of the project are open, while others are closed. Collaborative editing can be thought of in at least two ways:

1. shared editing via the browser window, where the user drags media files from the media bin/pool into a project timeline and sets in/out points (See http://eyespot.com for kind of clunky, but working, implementation of this idea; http://jumpcut.com for a slightly better version - and rabble tells me these are built on top of FOSS Gstreamer: http://gstreamer.freedesktop.org/).

2. local editing with user's preferred editing software, but shared Edit Decision List (EDL) across the project. Either instead of, or in addition to, shared editing via the browser window a la JumpCut, we should make it easy for people to edit locally and then export their EDL back into a shared project database. Think of the EDL as a wiki that a lot of people could write to. This requires tracking and versioning, both of the EDL and of the media files to which it refers. So for example, when people want to view the current version of the project, they can either just download the EDL and watch using local media files, or maybe the server can generate a low quality (flash?) version to be seen via the browser. In addition, if people are 'subscribed' to a project then perhaps they can automatically download any new source material that gets added? (This could be done by sharing all source media files via P2P, so the project server doesn't have to serve everything.) Also, most editing (either browser based or locally in a dedicated video editing program) can be done using low quality, highly compressed versions of the source material, used as 'thumbnails' of the original full quality material. A copy of the full quality remains on the project server, and whenever needed, an export of the full project can be done at any quality (using ffmpeg?)

Spike
  • tool for editing offline or in-browser (flash?)
  • edl (ToDo) to allow on-server processing of the edits

Transcript and subtitling tool

Example: see http://www.dotsub.com or Subtitles Workshop which seems to be a freeware see http://www.urusoft.net/downloads.php?lang=1

Existing software
  • there are some subtitle edition software i forgot the name -- TheAnarcat

Spike
  • some subtitle module? or flash client-side thing?

Distribution tool

In addition to distro of the films (p2p), a tool to facilitate large numbers of people participating in arranging screenings, sales. (example: see http://crm2.metamute.org/)

Spike

Film Forge theme and graphic design

Put notes about theme, logo, graphic design here

We went through three rounds of concept, sketches, and modification and came up with the current logo: http://filmforge.koumbit.net/files/filmforge_logo.png

Film Forge theme

comar is developing the Film Forge basic theme, following the logo design and the mockup for video.indymedia by schock (view the mockup).

Graphic design To Do list

Running notes on graphic design to do

Film Forge drupal installation profile

One of the most interesting parts of this project is that we're going to use it to create a Film Forge Drupal installation profile customized for video community sites. Everyone working on this part of the project should read this HOWTO: http://drupal.org/node/67921, then come contribute to the FilmForge/DrupalProfile.

Update July 5, 2007: JohnSeb notes: "In order to help myself build the FilmForge profile, I created a "Profile Wizard" module. For now, it basically dumps the database in a .profile file. See http://filmforge.koumbit.net/en/profile_wizard/filmforge (you need to be admin). Starting from that, we can easily remove the crap. It will also set the ground for a real profile wizard."

Along with the installation profile, we need to write down a readme file, with links to all related Drupal modules on drupal.org.

FilmForge/ToDo (last edited 2009-11-05 16:23:58 by localhost)