View Code? Open in Web Editor
NEW
This project forked from gdroberts /rashomon
Toolset for compiling, viewing and grokking multiperson chronologies of contestable events.
Home Page: http://automation.berkeley.edu/rashomon
CSS 8.07%
JavaScript 88.54%
PHP 3.39%
rashomon's People
rashomon's Issues
not sure where we'd put it, but easy to drop a google map into ui if we have the data.
deploy db/api to handle metadata requests
Submitting new content via upload. Needs back end intake code as well. Will break into constituent issues as 'pieces' become more clear.
Enable filtering by date-range (both of metadata and upload date), tags, duration &c.
events either need to key to relative time to an existing clip or to an absolute time.
first implementation will likely be as abs timestamp
if you page down and then up, you get duplicate rows
BrowserID? Needs UI elements, some back end work.
Most of the way finished, need to plot them on timeline.
occasionally the sync thing will start reporting 10-20k offsets for no apparent reason, points to something going wrong.
5+ videos playing at once is cacophonous, selectively unmute on rollover? use control widgets?
Build/popup table of metadata for given clip including map where appropriate.
Drifts report as (generally minus) several seconds off. ONLY SOMETIMES, so probably a race condition. Could be rashomon.earliest somehow getting changed? offsets getting transposed?
Clips continue to play when eeking to near end of timeline (after they should be done).
Ways to set, remove, move... per collection of videos? per user? permissions?
Also, display something when event happens/begins?
For metadata ~poor, few potential methods of manual sync
*Unlock, click & drag on timeline?
*Event identification (depends on better event mgmt)
Bring photo methods up to current functionality/structure of video stuff. Be able to minimize either group.
uploaded files go into dir for processing, cron job with transcode queue.
Detect when thigns go out of sync, be smart about not doing this too often on slow connections
Match colors on the video lines to outlines (or backgrounds? see what looks good) below.
Worth testing, sync will be problematic if they inject ads.
Given metadata-rich files, the 'zero' point from which offsets are calculated should be set to the start of the video with the earliest start point).
Sometimes firefox gets stuck, videos dont seem to pass readystate=2
current system uses click/drag. need handlers for hover/touch/drag.
part of content intake
strip identifying data, determine temporal metadata quality, device &etc.
Select span of time in #maintimeline section, play will loop that section. Find some method to unselect a span and play as current.
on hitting play button, if clip is visible and playhead is > offset (and beyond offset + duration), clip plays.
Do some testing on existing width/height, make sure 16:9 don't inadvertently go offscreen.
support reading metadata from exiftool (see metadata folder for examples)
play, stop, pause. should be more visible than what's currently in use.
This means an extra div around each .vidtime that matches #maintimeline. offsets will then be calculated in % instead of pixels.
time/date vs. relative to start of timeline. also show time data based on mouse location for seeking.
use DOM traversal on single events rather than attaching to each video, bar, &c.
with media-specific metadata, visualization on timeline, display in content area and fullscreen support.
currently 90% complete.
Fix timespan selection with loop mode.
howabout a thin bar along the bottom?
Timebase may need to be refactored, like if elements are added outside of current time scope.
Make sure each relevant element can redraw as needed.
Enable the first (up to) 5 videos by default. Having 'videos' section empty on start is a little confusing.
see $(".vidnum").click(function () { line
~401
ideally transcode scripts can read rotation metadata and use ffmpeg '-vf:transpose'