Is the velocity profile basically useless?

[David Shirey]

[Peter Holt] “Anyway I have multiple options here. Probably the best is to investigate using Handbrake to merge the 4GB chunks with the minimum loss.”

I guess so but it seems like the best option would be to try Sony’s official software that John and I linked to. You know it’s designed specifically for that camera so it ought to do what you’re seeking. Is transferring huge video files over wifi very efficient? I have to say I’ve never tried it, but if the gel in the waterproof housing really “wastes” away through usage you should probably be leaving negative reviews for this thing all over the internet, as that’s a glaring flaw in an action camera. I’d always prefer to connect via usb or eject a memory card and put it in my own usb 3.0 card reader.

[John Rofrano]

[Peter Holt] “the camera has to be USB-connected (which means removing it from its waterproof housing – not always desirable, because it “wastes” a silica gel moisture absorbing pad) and you need to carry a windows computer.”

Wow, what that’s a major design flaw. I’m glad I bought a GoPro. I have no such problems opening the GoPro housing to use via USB and then closing it again. Sorry to hear what a horrible design Sony has.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[Peter Holt]

Different people have different requirements and preferred workflows. I use the Sony for aviation videos – some here
https://vimeo.com/user8026275/videos
with this one
https://vimeo.com/178217220
being the most complex I have attempted so far, with a GPS track converted into SRT subtitles, imported with Vegasaur, etc. To you guys this is trivial stuff 🙂 but I find the learning curve to be steep.
The Sony was chosen over the Go-Pro for
– much better aerodynamics (much smaller frontal area)
– stabilisation
– smaller angle of view – about 120 degrees – so much less distortion to deal with in the video editor (NewblueFX Lens Correction)
– better image quality, arguably, according to reviews of both
The complete thing is described here
https://www.euroga.org/forums/website/5534-sony-fdr-x1000v-good-for-flying-movies?page=3#post_107006
As you can see, I could in fact access the USB without opening the waterproof housing, had I included a waterproof connector between the housing and the battery pack…
I prefer WIFI transfer because it avoids opening the waterproof housing, and the fact that 100GB takes all night doesn’t matter. Others think this is crazy 🙂
Based on the general view here it is desirable to combine the 4GB chunks before Vegas and there are several tools, one of which is Sony’s Play Memories Home which I am not told doesn’t need the camera connected and can input files from the PC.
However on some projects like the last URL above where I am doing an intermediate render to get the GPS subtitles in, the 4GB breaks get removed anyway…

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Ron Whitaker]

How do you apply the VP to a clip?

[Peter Holt]

Not sure I understand. Is there more than one way to apply a VP?

This is where a break (caused by the 4GB file boundary) breaks the VP application. The VP can be applied to only one chunk (I guess you call that a “clip” or an “event”?) at a time. You cannot apply a VP to say a 12GB piece of the timeline (3 4GB chunks). Well, you can but you get weird results.

The basic issue is that Vegas maintains the breaks between the imported media, after it is all placed onto the timeline, and there is no way to remove the breaks. I believe one can remove splits (the breaks done by pressing “S”); I mean by means other than Undo 😉 Some other editors, reportedly, can remove the breaks.

Anyway, I found two tools which will losslessly merge mp4s. One is Machete and the other is AviDemux. Neither is fully automatic (neither takes a *.mp4 etc input spec) but the latter is a lot quicker due to some UI details.