Seamless Combining of HF-G10 Clips

rtbond wrote on 1/14/2013, 7:27 AM
I used my Canon HF-G10 to record a concert (AVCHD). The HF-G10 splits the recording into multiple files during recording, with file sizes not exceeding 2GB. I imported the recorded files from the camera using the Canon VideoBrowser (v1.0) utility (Windows 7, x64). When editing these imported clips in Sony Vegas Pro 12 there is small time discontinuity between clips. This cause a noticeable audio discontinuity in the recording live concert.

Any thoughts?

p.s.: I notice the same small audio drop-out occurring during payback of these imported clips from the timeline of the Canon VideoBrowser editor. I have also posted a similar question on the Canon forum.

--Rob

Rob Bond

My System Info:

  • Vegas Pro 22 Build 194
  • OS: Windows 11.0 Home (64-bit), Version: 10.0.26100 Build 26100
  • Processor: i9-10940X CPU @ 3.30GHz (14 core)
  • Physical memory: 64GB (Corsair Vengeance LPX 64GB (2 x 32GB) DDR4 DRAM 3200MHz C16 memory kit)
  • Motherboard Model: MSI x299 Creator (MS-7B96)
  • GPU: EVGA GeForce RTX 2070 SUPER XC ULTRA (Studio Driver Version =  536.40)
  • Storage: Dual Samsung 970 EVO 1TB SSD (boot and Render); WDC WD4004FZWX, 7200 RPM (media)
  • Primary Display: Dell UltraSharp 27, U2723QE, 4K monitor with 98% DCI-P3 and DisplayHDR 400 with Dell Display Manager
  • Secondary Display: LG 32UK550-B, entry-level 4k/HDR-10 level monitor, @95% DCI-P3 coverage

Comments

john_dennis wrote on 1/14/2013, 9:07 AM
Start here.
rtbond wrote on 1/14/2013, 4:09 PM
Thanks Dennis!

The DOS "copy /b file-1.mts+file-2.mts+file-N.mts Combine_File.mts" (where "Combine_File.mts" is the output file) does work with the Canon HF-G10 camera truncated files.

I found that I can seamlessly combine the multiple HF-G10 created files from a continuous shoot using this simple concatenation technique.

BTW, the Vegas Pro 12 Device Explorer made any effort to do this (i.e., both import the clips from the camera and concatenate the files truncated by the camera recording process). I say "made an effort" because there results were mixed (some camera-truncated files were properly imported and stitched back together while others were not stitched together

--Rob

Rob Bond

My System Info:

  • Vegas Pro 22 Build 194
  • OS: Windows 11.0 Home (64-bit), Version: 10.0.26100 Build 26100
  • Processor: i9-10940X CPU @ 3.30GHz (14 core)
  • Physical memory: 64GB (Corsair Vengeance LPX 64GB (2 x 32GB) DDR4 DRAM 3200MHz C16 memory kit)
  • Motherboard Model: MSI x299 Creator (MS-7B96)
  • GPU: EVGA GeForce RTX 2070 SUPER XC ULTRA (Studio Driver Version =  536.40)
  • Storage: Dual Samsung 970 EVO 1TB SSD (boot and Render); WDC WD4004FZWX, 7200 RPM (media)
  • Primary Display: Dell UltraSharp 27, U2723QE, 4K monitor with 98% DCI-P3 and DisplayHDR 400 with Dell Display Manager
  • Secondary Display: LG 32UK550-B, entry-level 4k/HDR-10 level monitor, @95% DCI-P3 coverage
Tom Pauncz wrote on 1/14/2013, 4:14 PM
Rob,
Device explorer will only stitch files that have been split due to FAT filesystem size constraints.

If an event has not been split, it will be imported as is. Surprised it if's any other way.

Tom
john_dennis wrote on 1/14/2013, 6:22 PM
Tom is likely correct that not many files are split in the camera because the scenes are mostly not that long. I rarely see a file approaching 1 GB from my son's AVCHD camera.

One thing I do see all the time with one of my cameras is that the camera stops recording audio two frames before it stops recording video. ( I know, I need another camera.) Since the audio is a flat line, it can be jarring if I don't edit the edges of every event. One or two frames is usually not the end of my world, but it gets tedious.

Here's how it looks on the timeline.
Chienworks wrote on 1/14/2013, 7:43 PM
The majority of my commercial video efforts are shooting live stage events and lectures. It's rare that i'll ever have a "single scene" shorter than several split files. I get about 23 minutes 10 seconds in a 4GB file while a typical event often has 40 to 85 minute continuous shots.
rtbond wrote on 1/14/2013, 9:17 PM
My comment about Device Explorer not stitching properly in some cases was specifically concerning files that the camera split because they exceed the 2 GB limit of its FAT file system. My current project had numerous such camera-splits because my "scenes" were in fact sets of a live performance.

In any case, the good old MS-DOS COPY /b was the solution. Thanks!

--Rob

Rob Bond

My System Info:

  • Vegas Pro 22 Build 194
  • OS: Windows 11.0 Home (64-bit), Version: 10.0.26100 Build 26100
  • Processor: i9-10940X CPU @ 3.30GHz (14 core)
  • Physical memory: 64GB (Corsair Vengeance LPX 64GB (2 x 32GB) DDR4 DRAM 3200MHz C16 memory kit)
  • Motherboard Model: MSI x299 Creator (MS-7B96)
  • GPU: EVGA GeForce RTX 2070 SUPER XC ULTRA (Studio Driver Version =  536.40)
  • Storage: Dual Samsung 970 EVO 1TB SSD (boot and Render); WDC WD4004FZWX, 7200 RPM (media)
  • Primary Display: Dell UltraSharp 27, U2723QE, 4K monitor with 98% DCI-P3 and DisplayHDR 400 with Dell Display Manager
  • Secondary Display: LG 32UK550-B, entry-level 4k/HDR-10 level monitor, @95% DCI-P3 coverage
Former user wrote on 1/14/2013, 9:29 PM
My Canon Vixia records as AVCHD as well and the Device Explorer in Vegas has always stitched them perfectly. Curious as to why it fails with yours sometimes.

Dave T2
rtbond wrote on 1/14/2013, 9:33 PM
John,

The audio drop-effect is what I see if I put to clips on the Vegas timeline that the camera split because they exceed the 2 GB file limit of the HF-G10's FAT file system. Using COPY /b to combine these two files eliminates the apparent audio drop-out in Vegas. (I understand the example you are citing is caused by an ailing camera)

Recording at the highest quality setting, the HF-G10 generates a new file about every 11.5 minutes of continuous shooting. Live event shoots generate lots of these camera-generated breaks.

Rob Bond

My System Info:

  • Vegas Pro 22 Build 194
  • OS: Windows 11.0 Home (64-bit), Version: 10.0.26100 Build 26100
  • Processor: i9-10940X CPU @ 3.30GHz (14 core)
  • Physical memory: 64GB (Corsair Vengeance LPX 64GB (2 x 32GB) DDR4 DRAM 3200MHz C16 memory kit)
  • Motherboard Model: MSI x299 Creator (MS-7B96)
  • GPU: EVGA GeForce RTX 2070 SUPER XC ULTRA (Studio Driver Version =  536.40)
  • Storage: Dual Samsung 970 EVO 1TB SSD (boot and Render); WDC WD4004FZWX, 7200 RPM (media)
  • Primary Display: Dell UltraSharp 27, U2723QE, 4K monitor with 98% DCI-P3 and DisplayHDR 400 with Dell Display Manager
  • Secondary Display: LG 32UK550-B, entry-level 4k/HDR-10 level monitor, @95% DCI-P3 coverage