Jump to content

BirdDog

Members
  • Posts

    606
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by BirdDog

  1. Yep. That's all part of the process. :) Mate, I process video files here that are WAY bigger than that. I guess, if you have never done any serious video editing, then it probably is a mind mash. Once you get experienced, it's actually pretty easy. The trick is a VERY good computer to process it all. With regards to the 4GB files - Yep - no problem there. The GoPros are actually pretty good and when you butt those files together, there is not even a millisecond of loss etc. So you just bang them in one after the other. :)
  2. Hmm... Maybe you are doing it the hard way. My plan (if it works) is to import my GPS data and create an overlay of the gauges for the entire flight. Create a video file of that. Then bring that into Final Cut Pro X, and use it as the timebase for my video. I can then drop whatever videos from whatever camera feed I like into the mix, as long as the time lines up, it will match. For example... If I performed say a simulated engine failure 30 minutes into my flight, the gauges will show that in the way of slowing down, and whatever I happened to do next etc etc. I can grab any video feed I like from my 3 GoPros and drop them straight in. As long as the times line up (and that's actually an easy bit) then it will work perfectly. One trick is to get a moment in time to snap sync all of your videos. In other words... get all of your cameras running and then make a loud sharp sound that all of them can record. It can be as easy as clapping once really loud. (take a time check too for GPS data) That shows up as a spike in the audio stream when you drop it into the editor. Align all of your camera feeds up at that point, and for the rest of the editing experience, everything is on time. Hollywood has been doing that method for decades. ;)
  3. Yeah nice! I absolutely will be using DW. I just thought if I do an overlay, I can sync it myself etc. Looking forward to playing with it. I am hoping it can read my data from my Garmin.
  4. Yep! My plan would be to create an overlay video of the gauges, and manually sync. I have advanced post production skills, so that should be the easy bit. I might make a trip to the AD today and see what data is being stored on the Aera500. It may be my solution. :) I have read the manual and apparently as soon as you are travelling more than 30kts it starts recording data.
  5. Yeah - It stores the data in the MP4. If you load just that file into Quik - it will display all the telemetry nicely. I have a Garmin Aera500 on the Dash - Might look into that I think! :) Thanks - I didn't even think of that. Cheers John
  6. If you are not sure what Quik is - Telemetry and GPS Add New Layers to Your GoPro Story
  7. It certainly does for video - I have it running perfectly in Quik
  8. Yes - But which bit of it specifically?
  9. PS - I have posted on the GoPro forum - days gone by - no response. :(
  10. Thanks man... OK... Basically here is it in a nutshell.... I know the DATA is good - In Quik, it works fine. If I try to load it up in Dashware, it loads the video file, but no data. I have followed Dashwares tutorial. The one that states to start with "Quick Project" It load the video file, and the tutorial states it should punch out a CSV file - but that does not happen. If I try and start a new project and load the video file, I get an error stating "No Data Extracted" Not sure what else I can tell you. I have spent probably 3 hours on it, and I am no numpty - I know what I am doing. Tried a dozen or so files - same result.
  11. Hi Scott, Yeah man - Been there and done all that. Following Dashware's own tutorials, it fails. GoPro actually stores the data INSIDE the video file, and Dashware is supposed to extract it - yet it doesn't. It's driving me mad!
  12. Hi Tyson, Yeah - I am thinking of finding another way to capture data, as the GoPro is proving problematic. Even in their own software Quik, it gets out of sync etc. So might have to do some research.
  13. Yeah, but my rig is all setup for the Gopro - through the intercom etc. :(
  14. No - They are all standard GoPro footage in 720 and 1080. What happens is this... If I use Quik, they work. The gauges are crappy, but they work. So I try to use Dashware, following the tutorials, and it fails. If I use the "Quick Project" it imports the video, and the gauges look like they are there, but no data, and not all gauges. If I start a new project and then go to import a video file, I get an error stating No Data Extracted. For a company the size of GoPro, the lack of support is amazing! Might be time to dump GoPro and hit up a Garmin Virb.
  15. Hey all, Just wondering if anyone here has any experience with Dashware with files captured with a Hero5 black. It's doing my head in!! Cheers John
  16. WOW! I really noticed it when I moved my plane. She was down the coast - 34ft elevation. :) Then when I moved her up on the deck, I could feel how the plane reacted differently when it got hot. There are some really cool apps that will assist pilots. If they don't know, or can't do the crazy calculations, these apps will go a long way to letting you know what you might be in for. Right now my home strip has an AD of over 4000ft. 2000ft more than it should be. Makes a big difference!! Especially if you are weighted up!
  17. Same here mate. I am always looking at DA. My bird currently sits over 2000ft elevation, and when it gets hot, the DA goes up very quickly!
  18. Hmm... Does that "personality" come out late at night? ;)
  19. We use Page 2 of this document, and it stays in the logbook. Then replaced when it's all full. We keep them all in the logbooks. https://members.raa.asn.au/storage/maintenance-form.pdf
  20. ahahah! Yeah Nev.... The boat when it's hot, the plane when it's not!!
  21. I actually prefer not to fly in the heat. I went for a scoot yesterday and basically got bashed the whole way out and back. :(
  22. Thanks Nathan, Yep! My Motor RPM has direct connection to how fast my prop spins. Might is not constant speed. Just the pitch is adjustable. Cheers John
  23. Thanks Nathan, Great info. I have been talking direct to ROTAX and they have been a great help, and he put more emphasis on making sure I kept the motor RPM around the 5300 mark. I guess, if as you say, the prop RPM falls with an increase in pitch, so does the motor RPM fight? Hence the need for more power (more throttle) Roger (Rotax) has recommended 5300 RPM on motor, with 26-27 on the MP. And that's pretty much where she sat last flight, but had to back off, as it got too quick for the conditions I was flying in. It was not full pitch nor WOT, so not sure what she would actually do at full beans! LOL!
  24. Yep - Same. My Maintenance Release is kept in the binder with the logs on a separate sheet, and is looked after by my LAME. :)
  25. The sequence would be... Take off - Full fine - After climb, reduce power to bring the RPM back from max (Say 5300rpm) Increase prop pitch a couple of clicks. This will bring RPM down as it courses up. So increase throttle to get RPM back in range. Repeat and rinse! Then once cruising and you want to come down.... Decrease throttle, and reduce prop pitch. As the prop is reduced in pitch, the RPM will increase. Repeat and rinse! Take off = Full fine. Landing = full fine. Cheers John
×
×
  • Create New...