Does MakeMKV write a log?

[russellbateman]

If so, where does it live. I can't find anything. It would be useful to know if MakeMKV had already finished transcribing from a disc should I find my computer host crashed and wonder whether to restart the transcription or not. Could be useful for other reasons too like asking questions in this forum.

Thanks.

[Woodstock]

If you enable debug logging (FAQ link in my signature says how to do it), it will write a log. The location of the log file will be included in the opening display of the bottom window of the display.

[BermudaLamb]

I've turned on Debug Logging, stopped and restarted the application. Even though "DEBUG" messages have been showing up in the log windows, I'm not seeing anything that indicates the location of the log file. Can you please provide the location of the log files?

[Woodstock]

When you start MakeMKV, the log window should show something like:

Code: Select all

MakeMKV v1.14.7 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\XXXXXXXXXX/MakeMKV_log.txt

[70tas]

I'm closing this thread because it appears that the collection has some big problems. This is the Louis Malle Collection, which someone got for me a long time ago. There are many problems with it, which I've been able to work around by enabling MakeMkv libraries for Windows, and then using HandBrake or VLC. But what Handbrake can rip, VLC can't, or MakeMkv has problems.
In any case, I believe this is a very old set from BN, I can't return it.

Thank you for all of your help
Tas

[Bandito]

Hello,
i read and test it
Debug logging enabled, log will be saved as C:\Users\XXXXXXXXXX/MakeMKV_log.txt

Is it possible, that the logfile is saved to the same Folder where the ripped Movie are?
or the Logfile become the same NAME like the Move are?

That will be nice or a nice feature for the next update.
I think, no big thing to program it.

[Woodstock]

Theoretically possible, but not likely. The location will be listed during start-up, though, as shown in my example above.

[Bandito]

Theoretically possible, but not likely. The location will be listed during start-up, though, as shown in my example above.

I know the location, but every RIP will be have a own LOG will be nice.
Not clean the log and safe every time by hand.

It was only an idea...
I make it by hand...

[mike admin]

The console makemkvcon has an option --debug which enables logging with no options and optionally allows to specify the log fie itself as in --debug=/path/to/file.log

[flojo]

In regards to the GUI, this isn't too bad as you could background a watching script and foreground makemkvgui. It seems that deleting the log file creates a stale file handler so it seems you have to use "truncate -s 0 $FILE". One good thing on my system is that it always seems to write the log to "/home/$USER/MakeMKV_log.txt". The starting line apparently starts with "005014:0000 Saving ". That is enough.

You really should have better options, in particular pre/post scripts. There's a CCExtractor option in the GUI, but I've never tried to jig it for other purposes. The GUI is open source, but I'm not sure that if you've made changes, that they would be incorporated, so that might lead to a maintenance nightmare.

Or use makemkvcon.