Pietenpol-List: building log--keeping it simple
Posted: Thu Dec 13, 2007 4:21 pm
Original Posted By: "Cuy, Michael D. (GRC-RXD0)[ASRC]"
Idea of having build video's is great.Not very practical. Start to finish you might have 1000-2000 hrs of video, maybea bit more or less.However.. no one I know would watch 1000 hrs of video.To edit video and make something useful out of it you typically make at least threepasses watching and editing each part, and most the material ends up beingcut.The idea of not having to do anything to capture the video is questionable, asyou would need a camera man keeping the right thing in the picture, zooming inwhen needed, etc.What you could do is to map out your activities ahead of time, and figure out whatyou want to capture, then capture it, adding all those things that happenthat you didn't count on. Time wise that would amount to editing before you capture,and would reduce your 1000+ hrs of video to a small fraction of that (100hrs-200hrs maybe), would force you to think it out ahead of time to.I am building my first plane and find it challenging to keep up a build log, getdigital pictures, track expenses and still have enough time to get work donewith all the zillion things that come up. So my experience is not from buildingplanes, its from my work. At work I have to document how I built computer monitoringsystems that are big and complex and take as long as a year to build.For that I have found it works far better to break project into key pieces,figure out what someone would need to know to accomplish the key things, thendocument those. It takes me about a week of total time to pull together a systemsdocument from all my notes I do during that year of building a system. (Courseits software so I can take all my pictures at the end, for construction youwould need to do it during the build.) With Still pics I think this approachwould work pretty good. Video is much harder to do well, setting up a cameraand going in front of it to do stuff will suprise you, you will probably notbe happy with one take, but will want to redo and redo the "scenes".Go for it if you can, but it would distract me from building to much to do it theway your thinking of doing it. Over the years I have written about twenty-fiveaprox 300 page books of documentation for my work, and its been manageable.Only one project did I use video's, and it took about 5-6 times as long andI hated the sound of my voice on them.Just some things to think about.Good luck,JimRead this topic online here:http://forums.matronics.com/viewtopic.p ... ___Subject: Pietenpol-List: building log--keeping it simple Date: Thu, 13 Dec 2007 16:38:04 -0600
Idea of having build video's is great.Not very practical. Start to finish you might have 1000-2000 hrs of video, maybea bit more or less.However.. no one I know would watch 1000 hrs of video.To edit video and make something useful out of it you typically make at least threepasses watching and editing each part, and most the material ends up beingcut.The idea of not having to do anything to capture the video is questionable, asyou would need a camera man keeping the right thing in the picture, zooming inwhen needed, etc.What you could do is to map out your activities ahead of time, and figure out whatyou want to capture, then capture it, adding all those things that happenthat you didn't count on. Time wise that would amount to editing before you capture,and would reduce your 1000+ hrs of video to a small fraction of that (100hrs-200hrs maybe), would force you to think it out ahead of time to.I am building my first plane and find it challenging to keep up a build log, getdigital pictures, track expenses and still have enough time to get work donewith all the zillion things that come up. So my experience is not from buildingplanes, its from my work. At work I have to document how I built computer monitoringsystems that are big and complex and take as long as a year to build.For that I have found it works far better to break project into key pieces,figure out what someone would need to know to accomplish the key things, thendocument those. It takes me about a week of total time to pull together a systemsdocument from all my notes I do during that year of building a system. (Courseits software so I can take all my pictures at the end, for construction youwould need to do it during the build.) With Still pics I think this approachwould work pretty good. Video is much harder to do well, setting up a cameraand going in front of it to do stuff will suprise you, you will probably notbe happy with one take, but will want to redo and redo the "scenes".Go for it if you can, but it would distract me from building to much to do it theway your thinking of doing it. Over the years I have written about twenty-fiveaprox 300 page books of documentation for my work, and its been manageable.Only one project did I use video's, and it took about 5-6 times as long andI hated the sound of my voice on them.Just some things to think about.Good luck,JimRead this topic online here:http://forums.matronics.com/viewtopic.p ... ___Subject: Pietenpol-List: building log--keeping it simple Date: Thu, 13 Dec 2007 16:38:04 -0600