Combining 4Gb clips

No. Formatted normally.
I personally never format low level.

Ok.
So I will simply try Canon tech for the info.
Format the card and see what happens in the test shot.

Thanks for your time !

CONCLUSION:
Just called Canon.
They told me that it will only go up to 4GB clips and then split the file.
FAT32 or EXFat.

So merging is the only option.

I've made a habit of low-level formatting each SD card the first time I put it in a specific camera, just to be sure that the camera's happy with it. Ran into an odd corruption issue once when I failed to do so.

It could be a situation where the camera can read Fat32, and the standard 'Format' just wipes the directory tree, while Low Level Format blows up the partition map and creates a new exFAT volume.

They don't go that deep in the documentation, and I don't have a 7D II to test with, so I'm guessing. But I'd still low-level format new cards in their respective cameras.

EDIT:  Just saw your reply.  It's crazy that the camera will only do 4GB on exFAT.

VTC wrote:

Quicktime Player. Open video file. Park playhead at end. Grab a group of files and drag into window. Save as...

WHAT??!! That's awesome. When I use the method I described above in great detail, the SAVE option is greyed out. This is so much easier and faster. And yes QT7 is definitely more versatile, but I'm glad current QT is this capable. I'll be wasting a lot less time now. Thank you.

dmetz wrote:

Found this blurb at the bottom of page 68 of the camera's manual:
"This device incorporates exFAT technology licensed from Microsoft

Weird the camera formats Fat32 as default then.

I'd try formatting a card ExFAT in the computer and see if the camera takes it. If no ominous formatting warning appears I'd roll off some maybe a 20 minute test video and check for 4gb segmenting. Could be camera defaults to FAT32 formatting in camera unless the card's already formatted ExFAT seeing as the manual states it will read ExFAT. Never seen a cam yet that allowed a choice of format type selectable in camera but who knows.

We've used a Canon 7D Mark II for years, on a Ronin-M and a few other types of rigs. Still have it today, but it's now used mostly for photos on sets. We always used a Sandisk 128GB Compact Flash card and never the SD slot, but FCP always recognized and automatically stitched any long clips. There is no option other than to FORMAT the card if you do it in camera. Haven't tried importing in the last couple of OS's but I'll bet you'll find it will work without issue. It is still listed as a supported camera for FCP on the Feb 2023 list.

Latest I tried and it works fine.
Synched my audio for both clips and dropped them on the timeline.
I only needed to shorten the clips to where video and audio meet by removing black frames.
Synch was perfect.
If I need to I can make a compound clip of the merging videos.

VTC wrote:

Quicktime Player. Open video file. Park playhead at end. Grab a group of files and drag into window. Save as...

This worked for me exactly once. Every time I have tried this since, SAVE is greyed out. Doesn't matter what drive the files are located on. Doesn't work. Not reliable. Only reliable method is going through the Photos app with the lengthy steps I listed above. Maybe it only works for certain codecs?

Every time I have tried this since, SAVE is greyed out. 

BONK! It just hit me. Try EXPORT. That should do it. (Or 'close' window at which time QT should ask what you want to do with it... save, export, discard, revert, etc.)

Yeah Export As works, but after you choose your resolution, you'll be asked to select Greater Compatibility (H.264) or Smaller File Size (HEVC), both of which will recompress the video even if the files are already H.264 or HEVC. Same for if you select SAVE after tapping the red button. Routing it through Photos allows you to keep the same codec of the original files without recompression, just like SAVE should.

Oh well at least I know I can drag files onto the QT window now instead of going through the menu.

Then again there's always EditReady if you're going to do this on a regular basis. There's a bypass re-encode or rewrap or something like in it it's framework.