Shot List - Revision history

Marcin: /* Protocol */

2013-09-14T02:35:13Z

Protocol

← Older revision		Revision as of 02:35, 14 September 2013
Line 5:		Line 5:
	=Protocol=		=Protocol=

	#Use [[Shot List Template]].		#Use [[Shot List Template]]. Modify for the actual modules to be videoed
	#Take all the design files and procedures that exist and ~~create a~~ spreadsheet ~~of main~~ steps that you want to capture.		#Take all the design files and procedures that exist and fill in the spreadsheet all the steps that you want to capture - based on capturing a full build procedure.
	#Before the beginning of every build day - discuss with the builders ~~what~~ they will be doing to get a sense of the build steps required.		#Discuss the Shot List with the person doing the task.
	~~#Publish this as a Google spreadsheet~~.		#Before the beginning of every build day - discuss with the builders when they will be doing their steps to get a sense of the build steps required.
	#Discuss with builders. Make notes in your spreadsheet to explain the step - to be edited into the video later as subtitles or voiceover. This step assures the video person's understanding of the subject matter.		#Discuss notes about the steps with builders. Make notes in your spreadsheet to explain the step - to be edited into the video later as subtitles or voiceover. This step assures the video person's understanding of the subject matter.
	#Shoot video at these steps by checking in constantly with the work teams as to their status - to make sure that you don't miss a step.		#Shoot video at these steps by checking in constantly with the work teams as to their status - to make sure that you don't miss a step.
	#

Marcin at 01:39, 14 September 2013

2013-09-14T01:39:50Z

← Older revision		Revision as of 01:39, 14 September 2013
Line 1:		Line 1:
			=Introduction=

			The difference between eye-candy video and technical video (video which teaches you how to build something) is that a sufficient number of steps is represented in the video. To this end, a Shot List - a list of critical steps to video - is necessary.

	=Protocol=		=Protocol=

	#~~Work with designers and the design: Take~~ [[~~Fabrication Diagram~~]] and ~~add markers for specific~~ steps that ~~need~~ to be ~~videod~~.		#Use [[Shot List Template]].
	#~~Write~~ a ~~basic script to go~~ with ~~the fabrication step~~ to explain the step - to be edited into the video later as subtitles. This step assures the video person's understanding of the subject matter.		#Take all the design files and procedures that exist and create a spreadsheet of main steps that you want to capture.
			#Before the beginning of every build day - discuss with the builders what they will be doing to get a sense of the build steps required.
			#Publish this as a Google spreadsheet.
			#Discuss with builders. Make notes in your spreadsheet to explain the step - to be edited into the video later as subtitles or voiceover. This step assures the video person's understanding of the subject matter.
	#Shoot video at these steps by checking in constantly with the work teams as to their status - to make sure that you don't miss a step.		#Shoot video at these steps by checking in constantly with the work teams as to their status - to make sure that you don't miss a step.
			#

Marcin: Created page with "=Protocol= #Work with designers and the design: Take Fabrication Diagram and add markers for specific steps that need to be videod. #Write a basic script to go with the ..."

2013-09-14T01:31:51Z

Created page with "=Protocol= #Work with designers and the design: Take Fabrication Diagram and add markers for specific steps that need to be videod. #Write a basic script to go with the ..."

New page

=Protocol=

#Work with designers and the design: Take [[Fabrication Diagram]] and add markers for specific steps that need to be videod.
#Write a basic script to go with the fabrication step to explain the step - to be edited into the video later as subtitles. This step assures the video person's understanding of the subject matter.
#Shoot video at these steps by checking in constantly with the work teams as to their status - to make sure that you don't miss a step.