Videos from the road

Rick Youngblood

CarbonCraft Master
Personally I think the Silvio

Personally I think the Silvio dumped me on purpose because she wants me to buy her one of those new single piece carbon seats.

Got a chuckle with that. Silvio is one smart bike and just plain good at anything. But Bob, you need to tame your beast, ride 'em hard! But don't let 'em throw you
tongue_smile.gif
!

I'll have to try iMove again, used it a few years ago, and man did it take hours. I used Final quite some time back and really liked it, seemed to be a lot faster than iMovie at the time.

I like making movies, but have got lazy, because it's so time consuming waiting for the dang things to load, save, upload, etc.

Your Summer Cruz movie, looked real good as far as HD goes, not jittery or stop and go, like my last few have been. Seems that YouTube is turning Hi-def HD movies into crap these days. But again your Summer movie was pretty darn smooth, and easy on the eyes.

..and in the movies the hills look flat going up or going down, unless you are opposed to one.
 

ratz

Wielder of the Rubber Mallet
Down convert from hires for

Down convert from hires for smooth playback....

Step 1 - build video - (don't stabilize if you can avoid it)
Step 2 - output to make hidef video pro-res level
Step 3 - use VideoMonkey to convert 5GB MOV file to a 300MB MP4 (use 2 pass encoding)

The 2 pass encoding working off a pro level source file will give you very very smooth video because you get massive look-ahead compression and anticipation; All the new mobile gear (iphone, android, etc) have hardware decoders for H.264 and will actually play it better than a PC/MAC....

Your final h.264 file will be something that youtube won't convert it's already what they want. Their converters suck because they have to suck; they are 1 pass and use a high bit rate to compensate. The high bit-rate trick is what TV shows use these days for online versions; it's useful because it's very fast on the encoding side usually better than 1-to-3 speed, but you get a much bigger file that is of questionable quality from a purest standpoint.

In the old days (I use to work on the ffmeg project) we could convert an entire Babylon-5 episode into a 150mb file; 45 minutes of CGI television. Of course it would take 2 hours to convert a 45 minute episode. An iTunes version of that same file these days is 540MB; It has a higher bit rate but it really doesn't look better; it's just more economical to produce.


The anti rolling and stabilizers in imovie and final cut should be avoided for moving videos like rides. Those feature are meant for shaky stationary camera (caffeine hand). If you use them on a ride you get nauseating results.

The other thing that helps a lot is these source files in hyperlapse; that time lapse stuff with the missing frame actually looks smoother than steady stream video. The summer cruise was a mix of straight video, instagram video, and hyperlapse. The longer the travel distance of a segment the better hyperlapse was; and it was by far the best at making great chase footage.
 

Eric Winn

Zen MBB Master
Expecting a double crash ride

Bob, the way that ride was going I was just about expecting a double crash ride with the second crash being in the leaf litter.

Lot of leaf litter here. This is the leaf battle time of year where I spend 3-4+ hours on weekend days blowing and raking leaves. Sometimes several days a week when it gets really bad.

My riding area is somewhat similar but with a lot more trees and very little open vistas.

Enjoyed it. Did you bark back at the dog? I have a bad habit of doing that...

-Eric
 

ratz

Wielder of the Rubber Mallet
Tis the season for leaves

Tis the season for leaves

Yes most of the MUPs here are not rideable over 8 mph; most run through wooded areas and they are a solid blanket from now until spring. That's annoying as it cuts off all the easy north bound get out of town routes....

Surprisingly that was my first dog of the year, fortunately just a Collie that wanted to "herd" me. Just didn't see him coming; usually do well ahead of time.

In retrospect I think the camera caused my crash. I had it mount dead center on the handle bars and vertical. It took a nice image but it was too much my center of vision. I slipped into the should because (1) I couldn't see the line dead in front of the bike easily and (2) It's fatiguing to have that camera swaying in and out of your line of vision and very distracting. I won't be repeating that mounting, option. That was pretty lucky on the crash; I fe;l a good way into the traffic lane and the cars had been semi frequent; happened to go down without a car passing again for about 3 minutes. I could do without the 6x6 patch of road rash on the hip; that better not be the last ride of the year.

The lack of trees out and about is something I'm pretty use to; it's all farm land down here; I have to go up to the lakes and the bad traffic to get trees; or way north of the cities. Around here we get trees in the river valley which is pretty and all but very hilly. I can ride west for 20 miles in a straight line and see nothing but fields. If you see a cluster of trees that means it's a small shelter for a house. That's part of the reason for our nasty winds there's just nothing to block them for miles; you have to watch the descents off tree covered hills it can be a bit rude when you clear the hill into the open and discover a 12+ cross wind you didn't think was there. The one positive is that enough of the road are paved; wide and smooth; the road of the crash is one of the few bad connectors we have to deal with and normally can be avoided.
 

mzweili

Guru
Fast rider

Beautiful trail.
You are a lucky guy.
Due to the cold and snow here in Quebec, my Silvio is on the rollers for at least the next two month.
 
Top