MakeMKV creates .tgz files

[debearly]

Ever since I reinstalled Windows and installed the 1.9.5 release of MakeMKV (I don't know what version it was previously), MakeMKV has been creating .tgz files when I load disks. Version 1.9.6 does this too. For example: I just loaded "The Godfather" blu-ray, and there is now a "MKB_v7_GODFATHER_PART1.tgz" file in my default output folder. I haven't ripped it yet. I get no error messages, I can find no setting that might explain it, and the discs seem to rip fine. I also found a .tgz file for the last BD I ripped in the .MakeMKV hidden folder. Why is this? Any way to turn the behavior off?

Windows 7 Home Premium 64-bit
MakeMKV v1.9.6 win(x64-release)

[Woodstock]

Check your settings - in Preferences, Protection, there is a setting to "Always create BD+ dumps". If it's checked, a BD+ dump will be created whenever a BD has BD+ protection, even if MakeMKV can figure it out.

With it unchecked, the .tgz file will only be created if you get the "No FUTs" message from ripping a Bluray.

[debearly]

The BD+ dump setting was my suspicion, but it was unchecked. I also received no error message that I was aware of; is "No FUTs" an actual error condition, or is it an informational message that I perhaps missed in the output window? Because the BDs ripped fine...

Thanks for the quick response, BTW!

[Woodstock]

No FUTs is an informational message... but it is best to treat it as an error, simply because the result is usually unusable.

I've processed about a dozen disks this week with v1.9.5, and the only .tgz files it has created is one for Beyond the Boundary, because it has v57 AACS ... really should forward that to Mike, even though it did not cause a problem for MakeMKV.

[debearly]

Hmm. The result of the BDs with .tgz files all came out fine. I'll keep an eye on the output messages, tho, and forward anything that looks screwy.