Hi guys-
I've been getting debug code 233's while opening discs. Discs are pretty clean looking. The operation will successfully complete, but just worried if this will have an effect on the output file. Here is an example:
DEBUG: Code 233 at TsrjXW7K3NzKbFPrMZ8OdiAA:0
DEBUG: Code 233 at tRFaDW+UZkB6Fa565UBB3NqF:0
DEBUG: Code 233 at CFW/XS/xDGjXZwU0KO/0OCek:0
DEBUG: Code 233 at wMZdXTzQu0r6uNc8zUMvL/wW:0
DEBUG: Code 233 at gmTsGY9/rYogzfvR6dy0uA0b:0
DEBUG: Code 233 at 8XlJMd4smp8YFl0r1axV0C9V:0
DEBUG: Code 233 at om9Y7gmjfq+7eY0J22mGRqvM:0
DEBUG: Code 233 at n1LcCIOjVyRHkWqD+5c8jRzx:0
DEBUG: Code 233 at Hy1zk+0PFzb3V/w+BS3K2PIi:0
DEBUG: Code 233 at n6+7epG0Lmc/PiCvDVPejA4b:0
if the operation is successful, should i worry? is this a sign of a failing drive?
debug code 233
Re: debug code 233
Only Mike has the magic decoder ring to discuss debug codes, but...
Generally speaking, if you get an "Operation completed successfully" message, things are OK. Most debug messages are for tracking how MakeMKV got to where errors occur, but if the error doesn't occur, it's harmless information.
Generally speaking, if you get an "Operation completed successfully" message, things are OK. Most debug messages are for tracking how MakeMKV got to where errors occur, but if the error doesn't occur, it's harmless information.
MakeMKV Frequently Asked Questions
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
Re: debug code 233
Thanks for the response. Hopefully it's nothing. I'll post back if i notice anything weird.