Allegro.cc - Online Community

Allegro.cc Forums » Off-Topic Ordeals » Video editing, comments?

This thread is locked; no one can reply to it. rss feed Print
Video editing, comments?
jhuuskon
Member #302
April 2000
avatar

So I made some further tests. I found out that my Contour Roam can record in 1080p if I drop the FOV down to 120 degrees from 170 deg. I wanted to test the narrower FOV and how it affects the feeling of speed. I also wanted to test recording with an external recorder and syncing the audio in post-production (the Contour doesn't have an external mic jack and the built-in mic is absolute rubbish), also I figured out might as well try this trick for some future advanced gauge overlay control.

So I give you, for your comments, my latest not-definitely-a-masterpiece:

video

For comparison, here's some raw 720p footage with 170 degree FOV and audio using built-in mic from the Contour, unedited and unprocessed:

video

Personally I don't think the narrower FOV makes much difference to the sensation of speed, but the better audio quality is a vast improvement. I ordered a 15€ shotgun mic off eBay and some adapters and accessories so I should be able to plug that into the M4 for recording more of the exhaust note and less of my congested breathing, once it arrives I guess it's time to record another test video.

You don't deserve my sig.

AMCerasoli
Member #11,955
May 2010
avatar

You used the phone for the GPS stuff?

jhuuskon said:

I also wanted to test recording with an external recorder and syncing the audio in post-production

I think this is going to be always the best solution for professional audio recording.

jhuuskon
Member #302
April 2000
avatar

Yes. I used the phone on the left to record GPS position and OBD2 data with RaceChrono Pro. Map and speed (and lap times, if there had been any) are calculated by Dashware from GPS data, RPM and throttle position are recorded straight from OBD2. Throttle position needed to be normalised manually in Dashware and synchronising the telemetry to video is a bitch of a job.

The phone on the right recorded the audio.

Yesterday I bought a used GoPro HD Hero mainly because it was cheap. I also stumbled upon some suitable bits of scrap metal at the workshop and fabricated this:

{"name":"610462","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/b\/e\/befc2d6acc9cb1835b828c8e40e4b73a.jpg","w":3840,"h":2160,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/b\/e\/befc2d6acc9cb1835b828c8e40e4b73a"}610462

The knob on the left allows me to bolt it onto a specific type of auxiliary headlight bracket that is mounted using the front license plate screws, allowing me to set up the GoPro real low without using adhesives, suction cups or drilling holes into the bumper. I ordered an adapter that fits the GoPro case that needs to be bolted down to the flat bit on the right, but once I bolt that one down we're in business. I'm aiming for a perspective similar to this, but without the vibrations:

video

I hope I'll have the setup including the external mic figured out and ready by mid-august when the merry folks of the GTI club have booked Ahvenisto race circuit. It's pretty much the most awesome race track in the nordic countries. A combination of sweeping and tight corners with almost no straightawawys. Real old school, a slow track suitable for slow cars. Check it out:

video

So yeah, I've pretty much gone off the deep end, hard. ;D

You don't deserve my sig.

Chris Katko
Member #1,881
January 2002
avatar

I don't like the camera being on the right. It most all of the "action" (other cars going by, your steering wheel and hand movements) on the far left side of the screen.

-----sig:
“Programs should be written for people to read, and only incidentally for machines to execute.” - Structure and Interpretation of Computer Programs
"Political Correctness is fascism disguised as manners" --George Carlin

bamccaig
Member #7,536
July 2006
avatar

I like the new camera configuration. I don't like the wide angle from that particular position because most of what you're seeing is the car interior stretched... The telemetry is the most cool thing about this. I wonder if I could get something like that accomplished. :o I can't believe that DashWare, the guage software, is gratis. :o That said, I feel like adding the telemetry gauges to videos must be a lot of work and probably isn't worthwhile unless you actually have a cool video to pull it all together. I bet it'll be great for your work on the racetrack. I don't know that I'll gain much from it... :( How much did the OBD2 unit cost you? That is pretty damn cool, though it's difficult to trust it's throttle gauge in your video. Maybe it wasn't synced precisely? Hard to tell, but you'd have a better idea. I wonder if that would work on a bike. :D Too bad there's probably no brake data available... Without third party sensors probably. Then again, perhaps an ABS aware computer would be able to measure braking force artificially?

jhuuskon
Member #302
April 2000
avatar

The bluetooth OBD2 unit cost something in the vicnity of 8€ off eBay. Unfortunately the standard OBD2 protocol doesn't carry any useful realtime information apart from RPM, throttle position and manifold pressure. It doesn't specify any realtime brake data, only some fault bits. There are however some manufacturer-specific additions to the protocol that may carry said information.

Syncing the telemetry to video really is difficult. Just as I was writing this post I figured out a quick and dirty way that at least saves time on getting the telemetry into the ballpark fast, but I'll have to experiment to see how close I can get.

The telemetry data carries the UNIX timestamp of each data frame, so just as on a film set the clapperboard that displays timecode in realtime, I'll just have to catch the system time of the phone that records the telemetry on video, take a frame where the seconds tick over, find the matching data frame by comparing the UTC second from the CSV data exported from RaceChrono, figure out the data frame offset and punch that into DashWare manually. I may have to try that tonight, shouldn't be too hard and in theory I should be able to get within one data frame duration of precision.

Syncing audio is OTOH is much easier because you'll have to be REALLY out of sync for the human brain to tell, so as long as it's in the ballpark, it's synced fine for all intents an purposes.

I can wholly understand why DashWare is free. It's a piece of crap compared to its paid competitors, such as RaceRender. But it's free and gets the job done, so I rather have that than suffer crippleware or pay through the nose for something I use twice a year.

You don't deserve my sig.

bamccaig
Member #7,536
July 2006
avatar

Unfortunately the weather is rain today and my GoPro was forgotten plugged into my computer after the battery died yesterday, but I digress. I installed Racechrono (the free version so far) onto my phone last night, enabled location services, and "started" the "race" when I left home in my pickup truck to commute to work. It seemed to work. It isn't necessarily all that accurate where I am. It said up to 32 meters off in places and if you review the telemetry over the Google Earth data you can clearly see where it veers off the road, sometimes repeatedly in sharp Vs, and I do not remember any of that. :P In any case, it's probably accurate "enough" to be a nice addition to videos if I can figure out an efficient way to add and sync the data with the video. I probably won't bother until I actually go on a spirited ride or a long trip or something.

jhuuskon
Member #302
April 2000
avatar

Well, it got messy right off the bat. DashWare converts the RaceChrono timestamp (seconds_since_unix_epoch.decimal) into its own format (minutes_since_unix_epoch:seconds.decimal), so I had to write a quick excel spreadsheet to convert between the timestamp formats. But once I got that down, I just find a frame where a new second begins on the clock, jot the time down in the spreadsheet and it'll show me the correct data frame in DashWare timecode for that video frame. I sync the data so the current data frame is closest to the timecode given by the spreadsheet and this is what i got:

video

I got pretty close by without any manual adjustment. Also, DashWare has a poor grasp of time zones, the timestamps in the telemetry data are in UTC and it didn't get the daylight saving time, that's why the clocks are off by an hour. But if you examine how the seconds tick away, it's surprisingly close.

You don't deserve my sig.

Go to: