2015-04-10, 19:03
"To debug madVR: - Turn on debugging by running "activate debug mode" in the madVR folder. A debug log will appear on your desktop automatically on close..."
So, if the freeze mode log is produced "automatically", what does pressing Cntrl + Shift + Alt + Break/Pause do?
BTW: I didn't see you mention this.... if you leave DSPlayer/madVR at all it's default settings after you first set it up (scaling, smoothmotion, etc are all untouched; and disabled by default) and Kodi running in a Window, are you still able to make Kodi/madVR lockup hard consistently every time when you press STOP during media playback?
So, if the freeze mode log is produced "automatically", what does pressing Cntrl + Shift + Alt + Break/Pause do?
BTW: I didn't see you mention this.... if you leave DSPlayer/madVR at all it's default settings after you first set it up (scaling, smoothmotion, etc are all untouched; and disabled by default) and Kodi running in a Window, are you still able to make Kodi/madVR lockup hard consistently every time when you press STOP during media playback?
(2015-04-10, 18:15)Warner306 Wrote: Kodi debug logging probably won't catch anything, but you don't have to do anything special. Just turn it on and collect the kodi.log in the Userdata folder.
To debug madVR:
- Turn on debugging by running "activate debug mode" in the madVR folder. A debug log will appear on your desktop automatically on close. You must compress this debug log and upload it somehow. To deactivate debug mode, run "activate debug mode" once again.
- Crash reports are produced by pressing Cntrl + Shift + Alt + Break/Pause. On my Logitech keyboard, Break/Pause is FN+ P, so I have to press Cntrl + Shift + Alt + FN + P to produce a crash report. The crash report should be created once the system has locked and cannot be unlocked.
Uploading crash reports and kodi.log to Pastebin may be the easiest means of sharing these reports.
