Webmaker/HiveChattanooga/Viditor
Contents
Project Summary
Viditor was an online video editor entirely based in the cloud and composed of modern and open web technologies like HTML5, CSS, JQuery, and more. Viditor, created by two University of Tennessee at Chattanooga students, makes advanced, collaborative video editing available to everyone. Viditor’s beta launch will be piloted with digital art and design classes at Baylor School and at the Chattanooga Public Library’s teen center. This project was cancelled in 2015.
Spring Project Timeline
- Week 1:
- Setup Blog and subdomains
- Link backend to front-end effectively
- Week 2:
- Update GItHub repository and set to update weekly.
- Establish Metrics for Mozilla
- Post a weekly demo of the project to a subdomain
- Week 3
- Demonstrate demo at the first Mozilla Meet Up
- Meet with Co-Lab to discuss business development
- Redesign interface
- Allow streaming HTML5 video
- Week 4
- Hook system into Google Drive API's
- List of views for front-end
- Include basic keyboard shortcuts, playback from timeline, and multiple timetracks
- Texts and transitions
- Meet with Decosimo to discuss finances
- Week 5
- Meet with Baylor School and allow students to test the application in a real setting
- Meet with Chattanooga Library to discuss the community times
- Timeline zooming
- Week 6
- Refining of user management system
- Develop video tour of system
- Start first library meeting this week
- Week 7
- Video of what has gone into development
- Refine user management system
- Week 8
- Begin development of video effects
- Search function
- Chat System
- Week 9
- Collaborative privileges.
- Catalogue of changes?
- Week 10
- Refine picture and audio placement in video
- Legal research
- Week 11
- Tablet compatibility
- Mobile compatibility
- Render video outside of Google Drive and downloading
- Week 12
- Refine compiling time
- User agreements
Summer Project Timeline
- Week 1:
- Setup Blog and subdomains
- Link backend to front-end effectively
- Week 2:
- Update GItHub repository and set to update weekly.
- Establish Metrics for Mozilla
- Post a weekly demo of the project to a subdomain
- Week 3
- Demonstrate demo at the first Mozilla Meet Up
- Meet with Co-Lab to discuss business development
- Redesign interface
- Allow streaming HTML5 video
- Week 4
- Hook system into Google Drive API's
- List of views for front-end
- Include basic keyboard shortcuts, playback from timeline, and multiple timetracks
- Texts and transitions
- Meet with Decosimo to discuss finances
- Week 5
- Meet with Baylor School and allow students to test the application in a real setting
- Meet with Chattanooga Library to discuss the community times
- Timeline zooming
- Week 6
- Refining of user management system
- Develop video tour of system
- Start first library meeting this week
- Week 7
- Video of what has gone into development
- Refine user management system
- Week 8
- Begin development of video effects
- Search function
- Chat System
- Week 9
- Collaborative privileges.
- Catalogue of changes?
- Week 10
- Refine picture and audio placement in video
- Legal research
- Week 11
- Tablet compatibility
- Mobile compatibility
- Render video outside of Google Drive and downloading
- Week 12
- Refine compiling time
- User agreements
Project Partners
Our first partner is the Baylor School, where we will be working with their design class and video editing lesson. This will be our first real test of the system, where students will be working in groups to create their video projects together. This will also be where we gather the first information about how students and users will truly use the system. For the students, we'll be helping them as design students to learn the basic principles of video editing and collaborative work.
Our second partner is the Chattanooga Public Library. Like the Baylor School, it will be a method to get user feedback and study how they use the system, both what needs to be fixed and how real people use it. Also, it will also be an opportunity to reach out to the community and help teach them the principles of video editing, whether they be students or otherwise..
Spring Metrics and Outcomes
Technical Outcomes
By the end of the 12 weeks, we should have functional beta project that will have the basic features of a simple video editor including 2-track editing, transitions, timeline zooming, and more. Also, our web-based features such as multiple users, a chat window, and permissions should also be set up and functioning.
Our account system should be running, first with Google Drive integration, then with our own servers. We should also begin the first phases of a public beta test.
Learning Outcomes
While working with the Baylor school, we expect to reach about 20-40 students with our project. Our goals for this include:
- Teaching these students the basics of video editing.
- Teaching them about how to collaborate on a video project
- For us, we want to learn how real users will use our project and the features given
While working with the Chattanooga Public library, our goals are very similar, We plan to reach about 75 people over the 5-6 weeks to teach them the concepts of video editing, how to get their video seen, and how to collaborate. Likewise for us, this means learning how users respond to the user interface and how to work with the social features we intend to implement.
Community Outcomes
A big part of what we want to do is to get video editing into the hands of the masses. We live in an era where video is more abundant and powerful than ever, and with that more people want to get into it. However, most video editing is limited to working on a single platform, and costing a lot of money. Free alternatives generally do not have near the feature parity and are usually even more restrictive than their paid counterparts. We want to get people to understand what goes into video editing and how to get their videos out to their intended audience. Even if the people who are using our product in this trial period do not continue to use Viditor, we hope we can teach them the core principles of what goes into video production so that they can use it themselves later on.
Summer Metrics and Outcomes
Technical Outcomes
By the end of the 12 weeks, we should have functional beta project that will have the basic features of a simple video editor including 2-track editing, transitions, timeline zooming, and more. Also, our web-based features such as multiple users, a chat window, and permissions should also be set up and functioning.
Our account system should be running, first with Google Drive integration, then with our own servers. We should also begin the first phases of a public beta test.
Learning Outcomes
While working with the Baylor school, we expect to reach about 20-40 students with our project. Our goals for this include:
- Teaching these students the basics of video editing.
- Teaching them about how to collaborate on a video project
- For us, we want to learn how real users will use our project and the features given
While working with the Chattanooga Public library, our goals are very similar, We plan to reach about 75 people over the 5-6 weeks to teach them the concepts of video editing, how to get their video seen, and how to collaborate. Likewise for us, this means learning how users respond to the user interface and how to work with the social features we intend to implement.
Community Outcomes
A big part of what we want to do is to get video editing into the hands of the masses. We live in an era where video is more abundant and powerful than ever, and with that more people want to get into it. However, most video editing is limited to working on a single platform, and costing a lot of money. Free alternatives generally do not have near the feature parity and are usually even more restrictive than their paid counterparts. We want to get people to understand what goes into video editing and how to get their videos out to their intended audience. Even if the people who are using our product in this trial period do not continue to use Viditor, we hope we can teach them the core principles of what goes into video production so that they can use it themselves later on.
Visuals
Learn More
Our project progress will be documented via weekly updates on our blog at blog.viditor.us . You can also find us on Twitter @viditor_project . Our github repository is here at https://github.com/Arcym/viditor.
