www.makemkv.com

This maybe a moot point, and maybe not completely needed or is not needed.

When I make a MKV file of the movie from a Blu-ray. I maintain full quality. I don't make any changes except to choose the tracks I want, and make the MKV.

As I understand it, all that it is really doing is demuxing, and remuxing the tracks that I want into a MKV file. So no decoding/encoding is taking place. Is that correct?

If all that is taking place is demuxing/remuxing MakeMKV would have no need to use the multiple cores of my CPU, or of the CUDA cores as well. Is that correct?

Thanks

At the moment quite a lot of players are incapable of decoding TrueHD and/or DTS-HD (MA, HRA, Express) and way back when MakeMKV first started almost none were, so MakeMKV is capable of transcoding audios to other formats (otherwise they'd be useless, even handbrake can't decode the DTS-HD profiles yet) but that's as far as MakeMKVs re-encoding abilities go.

I doubt there are any Cuda capable FLAC/AAC/AC3 encoders around, but they should all be capable of using the multiple cores in a CPU.

ndjamena wrote:I doubt there are any Cuda capable FLAC/AAC/AC3 encoders around, but they should all be capable of using the multiple cores in a CPU.

Actually most open-source audio encoder/decoders aren't threaded. FFmpeg has a small selection of threaded decoders, IIRC (I don't think it's ever been ported to libav though).

FLAC keeps complaining that it was compiled without threading support, but I just assumed MakeMKV was taking over the threading process. It's definitely using more than 12.5% of the CPU and Process Lasso seems to think all 4(8) cores are being used to some extent. Since it's ripping at 0.3x I'm pretty there's nothing but FLAC encoding taking up that 26-27% of the CPU for however many hours it takes to rip a disc.

Maybe that's just FLAC though. AAC/AC3 are too fast to make judgements on and I doubt even if they did use multiple cores anyone could notice the difference.

ndjamena wrote:FLAC keeps complaining that it was compiled without threading support, but I just assumed MakeMKV was taking over the threading process.

I'd have to check whether FFmpeg threaded their FLAC encoder, but if libavcodec says it wasn't built with threading support, kind of a moot point…

FFENC001: [flac @ 0000000023939010] Warning: not compiled with thread support, using thread emulation
FFENC001: [flac @ 0000000023939010] compression: 12
FFENC001: [flac @ 0000000023939010] lpc type: Cholesky factorization, 8 passes
FFENC001: [flac @ 0000000023939010] prediction order: 1, 32
FFENC001: [flac @ 0000000023939010] order method: full search
FFENC001: [flac @ 0000000023939010] partition order: 0, 8
FFENC001: [flac @ 0000000023939010] block size: 4608
FFENC001: [flac @ 0000000023939010] lpc precision: 15

Maybe thread emulation is enough. SOMETHING is using a quarter of my CPU, unless the monitors aren't taking hyper-threading into account, but then why is Process Lasso showing all the cores lit up more or less equally? ST Avisynth really does use 100% of a single core.