4Gb file size limit .. most frustrating thing ever :(

This constraint really costs lot of time; I very hoped, they would solve the issue with the new version (3.2.0), but they only set up a workaround with those options to chose antother resolution or quality. Even the estimated file size does not come close to the real written amount of data, so you often have to initiate a rerun of hours of render time...

Pathetic! :(

A year or so back (when I first got my Virb Elite) I also complained about this. I suggested that they just break the export down into 4Gb pieces and export each piece *with its own SYNCHRONISED data* - so we could just join each exported piece together to make 1 large video clip. And they couldn't be bothered to do even this.
The net is littered with various free good quality video file joiners - it would be SO simple to do it this way; it would completely solve the problem. But NO. Apparently, they have something against this. Or it would be done already.... :(

ah damn .. I was hopping this would be fixed quickly ... :(

so what now? can this estimated file size can at least be fixed?

I also hoped they would have fixed it by now.
Looking at how badly Microsoft(=NSA) wants to invade our privacy, in cluding keyloggers and spy ware in win10 and "updating" win7 to also have these "features", I'm thinking about upgrading to Linux.
In the mean time I still use Win7 with unwanted updates un-installed and blocked.
I believe more people have no warm feelings about Win10 and the 4G limit should be fixed.

For the old 2.6.2 I have made a work around, no shrinking of the video, no reduce of framerate or quality (except for secondary rendering).
https://forums.garmin.com/showthread.php?75263-How-To&p=382929#post382929

Yeah, the 4GB file limit is horribly lame. They are probably using some ancient built-into Windows module, to save a few cents on licensing costs. They could have used open source like ffmpeg, but then they would have had to pay a license fee for the use of H.264/AVC encoding, and since they are giving away Virb Edit for free, they can't even affort 25c or so per copy. I would have gladly paid for a Plus/Premium version of Virb Edit with the 4GB limit removed. The limit has stopped me from purchasing a Virb, but now I have access to a Macbook, and the Mac version of Virb Edit has no such limit.

Unfortunately, the Mac version can't even import content with AVC video and PCM audio (from an SJCAM action camera) and I have to transcode the files before import. Also pretty lame, but easier to work around than the 4GB file size limit. The worst Mac problem is that it freezes with an eternally spinning beach-ball frequently and I was never able to complete a single video.. !

Doesn't make sense

They are probably using some ancient built-into Windows module, to save a few cents on licensing costs.

This is precisely the reason the 4Gb limit exists on Windows 7 (but not Windows 8 - I don't know about Windows 10; that seems to have its own problems). In a way, I can understand their position in not wanting to add extra costs and legal complications. What I *cannot* understand is their unwillingness to introduce the workarounds already suggested - or explain why they too are not feasible.

How much exactly would it cost them to use (for example) the codex you suggested? And how does this work - must an amount be paid per Virb sold, or per Virb Edit software downloaded, or per video exported from Virb Edit, or per video published online? And how much is this likely to be? I cannot see it being prohibitively expensive - if someone is going to spend a few hundred dollars on an action video camera, how much extra must be paid for the video output (as a percentage of this)?

And their unwillingness to use a paid codex does not explain their decision to use a paid mapping service for embedding in our videos - especially when free alternatives are available. Some VERY strange business decisions were made there... :(

Clearly they have some great thinkers on their team to come up with ideas for cycle computers, action cameras, etc. I just wish they had more thinkers on the strategic side of the business..... :(

There are actually 2 limits of Garmin Virb Edit:

1. Limit 1 - Win7 related - unable to create output file larger than 4GB (not present in Win8)
2. Limit 2 - Win8 (and also probably Win7) related - unable to accept input file larger than 4GB.

Limit 2 is also annoying in case you have several 4GB files from the camera (e.g. from a long bike ride) and you want to join them (using external editor) in order to sync the FIT file only ONCE and not every time for each 4GB segment created by the camera (which is sometimes impossible in case your ride is in the middle of the forest or a deserd without any characteristic points to base on).

It was working like that in 2.9.2 (I stay with this version for now due to observed stability issues in the newer ones).

Now the question is: does the "limit 2" also exist in 3.2.0? Has anyone tested?

How much exactly would it cost them to use (for example) the codex you suggested? And how does this work - must an amount be paid per Virb sold, or per Virb Edit software downloaded, or per video exported from Virb Edit, or per video published online? And how much is this likely to be? I cannot see it being prohibitively expensive - if someone is going to spend a few hundred dollars on an action video camera, how much extra must be paid for the video output (as a percentage of this)?

I don't know the details, but it's certainly at least a set amount per copy of Virb Edit downloaded. The amount per downloaded copy may appear small, but adds up for a lot of copies downloaded. I found the quote below in this article (http://www.zdnet.com/article/a-closer-look-at-the-costs-and-fine-print-of-h-264-licenses/).

"There's no royalty for the first 100,000 units of a licensed product; sublicensees pay 20 cents per unit up to 5 million and 10 cents per unit above 5 million. The current agreement includes an annual limit: “The maximum annual royalty (‘cap’) for an Enterprise [is] $6.5 million per year in 2011-2015."

I am not sure how accurate this is, but when they can use a poor, but free version included in Windows (with the 4GB) limit, I am sure that's the reason.

The H.264 encoder and file export module that comes with OS X is 10X better than the Microsoft version and also free.. I know from experience, since I work in this field (video compression).