Fennec/PerformanceReBoot

Task Breakdown for JP, Sheila: Automation: [one time tasks, not camera specific] - Automation had to be written and tested - Phones rooted, A-Team's android agent installed - Phones integrated with a test server (in this case it was my system, which had to be set up)

[repeated tasks] - .ini files need to be updated for perameters such as ip address, sd card presence, etc. before the tests run (this would need to happen prior to each camera run if we shoot deployed phones *other* than the hardware ctalbert has already set up in haxxor. This is not difficult or time consuming but worth stating.

Camera Capture: [one time tasks] - ID camera and purchase - ID set up - ID best comp. for phone placement/camera [repeated tasks] - capture footage of tests (3 hours) - stop/start camera and trouble shoot as needed (ctalbert will need to be available if for the first 1-2 times if we don't shoot the phones in haxxor just in case)

Editing [one time] Title design (quick) Design compositing workflow to place an icon for each browser (bug), titling for the ms count, and multi-up display. This includes steps that will have to happen again, although it should be faster since we have a template: - For each brower (4 total): importing branding icon and sizing, stepping through the footage to id the correct ms number, create a title with that number, export quicktime movie. - Import all 4 QT movies, place 4 video tracks (3 for 3-up, 2 for 2-up), size accordingly - Polish with analysis titles and export sequence/convert to .m4v - Create vimeo account/upload sequences and play back

[repeated tasks] 1. AVCHD footage acquisition from SD card -> editing system (45min) 2. Create QT clips with titles and export 3. Import QT clipss 3. navigate to the correct "start frame" for each clip (in the case the last frame before the black screen goes away and the clip begins) 4. composite 2-up/3-up/4-up 5. Export/Convert to m4v 5. Upload to vimeo