in FLAC, you'll get a 444 MB in files. Is this an omen or what??

It's unclear to the rest of the world.
You should clarify your interpretation of this omen since you are arogant and the rest of the world is not.

"4" in Chinese, if mispronounced, means "death".
"8" could mean "lucky".

lt's an omen only for you if you believe in it.

"in FLAC" is also an incomplete rationale.
It depends what version of FLAC you are using: 1.2.1, 1.3.1.
If you use 1.3.0, I would find that an omen since it is superceeded by 1.3.1 with bufixes and security patches.
There is also FLACCL (former FlaCuda) build of FLAC using Nvidia's OpenCL.

It also depends what compression level you use 0-8 or unsupported higher compression level 11.

If you want to be superstitious, you can just adjust any one of those variables and get file sizes.

With the right settings you could probably rip anything to be about 444 MB.

Technically, and I mean by limitations of the software, that's an impossible feat as you can't really set a bitrate to FLAC like you would if you were to encode a video using x264.
It's variable by nature.
You'd have to be a coding wizard to hack FLAC to work out of its element (and break its total "lossless" properties).

With lossy encodings, you can set CBR and try to aim for that file size.

Lossless codecs don't allow CBR, however.

I'm not talking about ripping one file to be 444 MB - that'd be quite hard to do - but what OP said was that all the contents in total turned out to be 444MB. In truth it's probably more like 443.95 MB, and Windows is just rounding up when he hovers over the folder.

Though I think Handbrake has a feature where you can set it to rip DVDs/Blu-rays so that you reach a target filesize. Dunno how accurate it is, though.

It's all a moot point though since I sorta doubt that franzito is receiving an omen through his FF IV rip. :p

If using "anything" to pertain to a whole project like FF4 (another 4!), then it can be feasible.
But far more tasking than trying not to reach 444Mb in total size.
Each file would need to be tested in different compression levels and then databased with something like Excel to find which combination of files would sum up to the ominous 444, or any variation consisting of only 4 (4, 44, 444, 444, 4444...).
Humanly insane, by all rights.

Handbrake does allow for target filesize.

The video encoder is the open-source AVC/H264 encoder "x264", which allows target bitrate (which can be used to calculate bitrate to achieve a desired file size--if you have the final filesize of the audio taken into calculation) and variable bitrate modes.
Audio can be encoded to MP3 or AC3 which would allow for more accurate target bitrates.
AAC has bitrate modes, but that's the "nominal" bitrate. You won't ever get target bitrate with AAC.

MP3 and AC3 is much more absolute in filesize target.

Even with x264, or any video encoder, for that matter, you won't always get exact bitrates and filesize.
You'll be off several MB, at least.
The source has a huge impact as well as the settings.
Handbrake has presets and very limited options, while it also allows custom command lines where you can use every option for the given x264 binary.

However, I would not call moot yet.
We've yet to hear from franzito on whether or not he is cursed by this omen.

For all that we know, he's already dead.

Thanks guys for the clarifications. I found this funny because it was an exact 444 MB file of the 2 CDs. I used dBpoweramp at FLAC Compression Level 5. I called an omen because the Japanese believe the number 4 is an unlucky one (is sometimes pronounced shi, which is also the word for death).