Crash/Bug Report: "Fatal error occurred, program will now exit." (Code 256 at re...)

Please post here for issues related to Blu-ray discs
Post Reply
mattpr
Posts: 9
Joined: Wed Dec 30, 2020 9:03 am

Crash/Bug Report: "Fatal error occurred, program will now exit." (Code 256 at re...)

Post by mattpr »

Getting this error trying to rip Lost Season 5, Disc 5 (German Blu-Ray). Haven't had this issue with any other discs in this series.
Was happening on the v1.14.x version of MakeMKV I was running. Upgraded to v1.15.4 darwin(x64-release) and the same thing is happening.

Image

The errors in the debug log before the fatal crash are the following:

Code: Select all

DEBUG: Code 256 at re?OLf|b.Bo BE/^+%>:121264533
DEBUG: Code 256 at re?OLf|b.Bo BE/^+%>:121264533
Based on a couple screenshots I took before exiting (after fatal error popup), it isn't always the same title causing the crash. I've observed both 00456.m2ts and 00457.m2ts being the active "source file" at the point of crash. This may not mean anything as the UI might not be updated with what is actually happening at the time of the crash.

Debug log attached but doesn't show much other than the two "Code 256" lines I included above.

Perhaps this is a well known error type but I didn't see anything about this type of error in the pinned post at the top of this board...and I assume if this was a common error case it would be handled differently than crashing with a fatal error.

Let me know if there are further things I can do to help troubleshoot this. Thanks!
MakeMKV_log.txt
(17.38 KiB) Downloaded 334 times

Code: Select all

Drive Information
OS device name: /dev/rdisk8
Current profile: BD-ROM
Manufacturer: ASUS
Product: BW-16D1HT
Revision: 3.10
Serial number: XXXXXXXXX
Firmware date: 2119-01-04 10:14
Bus encryption flags: 1F
Highest AACS version: 70

LibreDrive Information
Status: Enabled
Drive platform: MT1959
Firmware type: Patched (microcode access re-enabled)
Firmware version: 3.10
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

Disc Information
Label: LOST_SEASON5_DISC5
Timestamp: 2009-09-04 14:19:41
Data capacity: 40.75 Gb
Disc type: BD-ROM
Number of layers: 2
Channel bit length: 74,5 nm (25.0 GB max. per layer)
Image
Last edited by mattpr on Mon Jan 04, 2021 9:16 am, edited 1 time in total.
mattpr
Posts: 9
Joined: Wed Dec 30, 2020 9:03 am

Re: Crash/Bug Report: "Fatal error occurred, program will now exit." (Code 256 at re...)

Post by mattpr »

Another debug log trying the same disc with a different physical drive. Same thing. Don't have problem this problem with other discs (ever so far). Have tried cleaning the disc multiple times. So I suspect this is a disc authoring/production issue or an unhandled case on makemkv's end.

I do find it strange that there is a fatal error rather than a read error or something.
MakeMKV_log-secondDrive.txt
(17.44 KiB) Downloaded 330 times
mattpr
Posts: 9
Joined: Wed Dec 30, 2020 9:03 am

Re: Crash/Bug Report: "Fatal error occurred, program will now exit." (Code 256 at re...)

Post by mattpr »

A related question...while trying to figure out which title on the disc is repeatably causing this issue...I noticed that I really don't understand the title "added or skipped" log.

See in the screenshot.

You will see that makemkv is currently processing a title that was supposedly going to be skipped.
I also see makemkv processing titles with numbers that were not mentioned in the log at all (to be added or skipped).
Is there a document that explains what is going on here as I find the current output quite confusing? I don't mind reading man pages, just haven't found anything.

Thanks!

Image
dcoke22
Posts: 2560
Joined: Wed Jul 22, 2020 11:25 pm

Re: Crash/Bug Report: "Fatal error occurred, program will now exit." (Code 256 at re...)

Post by dcoke22 »

The part about skipping relates to what MakeMKV decides to show as titles for the user to choose to rip or not. It does not mean that a particular .m2ts file can't be part of a larger title.

I don't know why it is crashing for you; hopefully Mike can look at it. In the mean time, you could try making a backup of the disc first (I'm assuming this is not a DVD) and then try to rip from the backup. Also, you could try to rip a subset of the titles on the disc, as opposed to all 41 in a single go.
mattpr
Posts: 9
Joined: Wed Dec 30, 2020 9:03 am

Re: Crash/Bug Report: "Fatal error occurred, program will now exit." (Code 256 at re...)

Post by mattpr »

dcoke22 wrote:
Fri Jan 01, 2021 6:25 pm
I don't know why it is crashing for you
I appreciate the suggestions.


I've tried the same disc with 3 different drives now all of them have the same fatal error/crash on this blu-ray disc.
MakeMKV_log-Pioneer.txt
(17.98 KiB) Downloaded 327 times

Code: Select all

BD-RE ASUS BW-16D1HT 3.10d          <-- fatal error
BD-RE ASUS BW-16D1HT 1.01d          <-- fatal error
BD-RE PIONEER BD-RW BDR-XD05 3.10d  <-- fatal error
dcoke22 wrote:
Fri Jan 01, 2021 6:25 pm
Also, you could try to rip a subset of the titles on the disc, as opposed to all 41 in a single go.
This is why I was asking about understanding the title log (currently processed vs added/skipped in log)...idea was to more precisely exclude the problematic title(s) rather than playing guess and check. But as I am confused about what title is being processed at the time of the fatal error/crash, I haven't tried this yet.

For instance: it looks like "source file" 00457.m2ts is the file being processed at the time of the fatal error/crash (see screenshot in original post). However when I scroll through the list of titles that makemkv has selected and look in the right hand pane for each of the selected titles, I do not see any of them with source file 00457.m2ts.

Image

However maybe I need to be looking at the "segment map" for that title ID?

Image
dcoke22 wrote:
Fri Jan 01, 2021 6:25 pm
you could try making a backup of the disc first (I'm assuming this is not a DVD) and then try to rip from the backup
Okay. I did a backup (no decryption) and the backup completed without any errors or crash.
MakeMKV_log-backup-nodecrypt.txt
(1.07 KiB) Downloaded 331 times
However, when I went to create MKV from that successful encrypted backup on disk I got the same fatal error/crash (also on 00457.m2ts).
MakeMKV_log-crash-from-backup.txt
(17.48 KiB) Downloaded 343 times
Image

Given the "no decryption" backup ran without a problem, and that all three drives had the same issue on the same m2ts source (00457.m2ts), I am going to assume this isn't a hardware/read error.
I am guessing that the data in that area of the disc is damaged through authoring, production or wear issues (e.g. data is read but somehow corrupt in a way that makemkv can't handle during decryption routines).

I am not sure if there is an easy way to troubleshoot this particular m2ts on disc since it is encrypted.

Code: Select all

$ ffprobe LOST_SEASON5_DISC5/no-decrypt/BDMV/STREAM/00457.m2ts
ffprobe version 4.3.1 Copyright (c) 2007-2020 the FFmpeg developers
  built with Apple clang version 11.0.0 (clang-1100.0.33.17)
  configuration: --prefix=/usr/local/Cellar/ffmpeg/4.3.1_4 --enable-shared --enable-pthreads --enable-version3 --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libdav1d --enable-libmp3lame --enable-libopus --enable-librav1e --enable-librubberband --enable-libsnappy --enable-libsrt --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librtmp --enable-libspeex --enable-libsoxr --enable-videotoolbox --disable-libjack --disable-indev=jack
  libavutil      56. 51.100 / 56. 51.100
  libavcodec     58. 91.100 / 58. 91.100
  libavformat    58. 45.100 / 58. 45.100
  libavdevice    58. 10.100 / 58. 10.100
  libavfilter     7. 85.100 /  7. 85.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  7.100 /  5.  7.100
  libswresample   3.  7.100 /  3.  7.100
  libpostproc    55.  7.100 / 55.  7.100
LOST_SEASON5_DISC5/no-decrypt/BDMV/STREAM/00457.m2ts: Invalid data found when processing input
dcoke22
Posts: 2560
Joined: Wed Jul 22, 2020 11:25 pm

Re: Crash/Bug Report: "Fatal error occurred, program will now exit." (Code 256 at re...)

Post by dcoke22 »

mattpr wrote:
Mon Jan 04, 2021 10:27 am
However maybe I need to be looking at the "segment map" for that title ID?
Yes, this is correct.
mattpr wrote:
Mon Jan 04, 2021 10:27 am
Okay. I did a backup (no decryption) and the backup completed without any errors or crash.



Given the "no decryption" backup ran without a problem, and that all three drives had the same issue on the same m2ts source (00457.m2ts), I am going to assume this isn't a hardware/read error.
I agree.
mattpr wrote:
Mon Jan 04, 2021 10:27 am
However, when I went to create MKV from that successful encrypted backup on disk I got the same fatal error/crash (also on 00457.m2ts).
That's interesting. I assume that if you tried to make a decrypted backup, you'd get the same fatal error/crash.

If you skip any titles with the offending 00457.m2ts, do the rest of the rips process successfully?
mattpr
Posts: 9
Joined: Wed Dec 30, 2020 9:03 am

Re: Crash/Bug Report: "Fatal error occurred, program will now exit." (Code 256 at re...)

Post by mattpr »

dcoke22 wrote:
Mon Jan 04, 2021 3:13 pm
That's interesting. I assume that if you tried to make a decrypted backup, you'd get the same fatal error/crash.
I also figured the same thing and so didn't bother to test making a decrypted backup. But if it is useful I can of course test this case as well.

Only one title had the 457 in the segment map.

Excluding this problematic title and making mkv from the other 40 ran without error (well without fatal error/crash anyway).

Code: Select all

...
005005:0080 40 titles saved
005036:0104 Copy complete. 40 titles saved.
Strangely after this when I tried to rip the problematic title alone (with and without audio track) it ran without the fatal error/crash.

Fairly long debug log of the above steps attached.

The problematic title (alone)

Ripping video only (LPCM audio track deselected) runs without anything in the log.

Code: Select all

005014:0000 Saving 1 titles into directory file:///Volumes/Drobo5D/000-exclude/makemkv_out/Lost/s05/d5-t04-vid-only
005005:0080 1 titles saved
005036:0104 Copy complete. 1 titles saved.
Ripping the whole title (video + LPCM audio track) runs without crash but has more in the log...

Code: Select all

005014:0000 Saving 1 titles into directory file:///Volumes/Drobo5D/000-exclude/makemkv_out/Lost/s05/d5-t04
DEBUG: Code 256 at re?OLf|b.Bo BE/^+%>:121264533
002008:0020 Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
002008:0020 Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
002008:0020 Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
002008:0020 Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
002008:0020 Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
002008:0020 Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
002008:0020 Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
002008:0020 Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
002008:0020 Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
002008:0020 Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
005005:0080 1 titles saved
005036:0104 Copy complete. 1 titles saved.
So now I really don't know what is going on.
  • Selecting all titles results in fatal error on 00457.m2ts.
  • Selecting all but the offending title goes without problem.
  • Selecting the offending title alone runs without problem (well without the crash at least).
MakeMKV_log.txt
(40.92 KiB) Downloaded 316 times
Last edited by mattpr on Mon Jan 04, 2021 5:42 pm, edited 1 time in total.
mattpr
Posts: 9
Joined: Wed Dec 30, 2020 9:03 am

Re: Crash/Bug Report: "Fatal error occurred, program will now exit." (Code 256 at re...)

Post by mattpr »

Here is the mkvinfo on the problematic title.

Code: Select all

$ mkvinfo S05/d5-t04/Lost-\ Season\ 5\ \(Disc\ 5\)_t04.mkv
+ EBML head
|+ EBML version: 1
|+ EBML read version: 1
|+ Maximum EBML ID length: 4
|+ Maximum EBML size length: 8
|+ Document type: matroska
|+ Document type version: 2
|+ Document type read version: 2
+ Segment: size 1266458411
|+ Seek head (subentries will be skipped)
|+ EBML void: size 1021
|+ Segment information
| + Timestamp scale: 1000000
| + Multiplexing application: libmakemkv v1.15.4 (1.3.10/1.5.2) darwin(x64-release)
| + Writing application: MakeMKV v1.15.4 darwin(x64-release)
| + Duration: 00:12:13.315000000
| + Title: Lost: Season 5 (Disc 5)
| + Date: Mon Jan 04 17:20:47 2021 UTC
| + Segment UID: 0x57 0x8b 0x7b 0xdd 0x06 0x06 0xa3 0x1c 0xa2 0x7c 0x75 0xa9 0x71 0x6b 0x18 0xb7
|+ Tracks
| + Track
|  + Track number: 1 (track ID for mkvmerge & mkvextract: 0)
|  + Track UID: 1
|  + Track type: video
|  + Default track flag: 0
|  + Lacing flag: 0
|  + Minimum cache: 2
|  + Codec ID: V_MPEG2
|  + Codec's private data: size 98
|  + Default duration: 00:00:00.041708333 (23.976 frames/fields per second for a video track)
|  + Video track
|   + Pixel width: 1920
|   + Pixel height: 1080
|   + Display width: 1920
|   + Display height: 1080
| + Track
|  + Track number: 2 (track ID for mkvmerge & mkvextract: 1)
|  + Track UID: 2
|  + Track type: audio
|  + Default track flag: 1
|  + Lacing flag: 0
|  + Codec ID: A_PCM/INT/LIT
|  + Language: eng
|  + Default duration: 00:00:00.033333333 (30.000 frames/fields per second for a video track)
|  + Name: Stereo
|  + Audio track
|   + Sampling frequency: 48000.0
|   + Channels: 2
|   + Bit depth: 16
|+ Chapters
| + Edition entry
|  + Edition flag hidden: 0
|  + Edition flag default: 1
|  + Edition UID: 7508653948536747564
|  + Chapter atom
|   + Chapter UID: 10761387243387959637
|   + Chapter time start: 00:00:00.000000000
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:01:00.060000000
|   + Chapter display
|    + Chapter string: Chapter 01
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 13047872819402887022
|   + Chapter time start: 00:01:00.060000000
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:02:00.120000000
|   + Chapter display
|    + Chapter string: Chapter 02
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 15831574668978734281
|   + Chapter time start: 00:02:00.120000000
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:03:00.180000000
|   + Chapter display
|    + Chapter string: Chapter 03
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 12223631164542537845
|   + Chapter time start: 00:03:00.180000000
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:04:00.240000000
|   + Chapter display
|    + Chapter string: Chapter 04
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 5106042208266134752
|   + Chapter time start: 00:04:00.240000000
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:04:08.539958333
|   + Chapter display
|    + Chapter string: Chapter 05
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 14404334666854164594
|   + Chapter time start: 00:04:08.539958333
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:05:08.891916666
|   + Chapter display
|    + Chapter string: Chapter 06
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 15349760480074752099
|   + Chapter time start: 00:05:08.891916666
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:06:08.951916666
|   + Chapter display
|    + Chapter string: Chapter 07
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 7380317688067002958
|   + Chapter time start: 00:06:08.951916666
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:07:09.011916666
|   + Chapter display
|    + Chapter string: Chapter 08
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 13680882984503158411
|   + Chapter time start: 00:07:09.011916666
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:08:09.071916666
|   + Chapter display
|    + Chapter string: Chapter 09
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 16245300584127188973
|   + Chapter time start: 00:08:09.071916666
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:09:09.131916666
|   + Chapter display
|    + Chapter string: Chapter 10
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 12067357040934590900
|   + Chapter time start: 00:09:09.131916666
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:10:09.191916666
|   + Chapter display
|    + Chapter string: Chapter 11
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 8471616349312990630
|   + Chapter time start: 00:10:09.191916666
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:11:09.251916666
|   + Chapter display
|    + Chapter string: Chapter 12
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 18304125691540417912
|   + Chapter time start: 00:11:09.251916666
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:11:10.252916666
|   + Chapter display
|    + Chapter string: Chapter 13
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 3109164712675602126
|   + Chapter time start: 00:11:10.252916666
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:11:11.253916666
|   + Chapter display
|    + Chapter string: Chapter 14
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 12580825601395791472
|   + Chapter time start: 00:11:11.253916666
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:11:12.254916666
|   + Chapter display
|    + Chapter string: Chapter 15
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 13505804685485048983
|   + Chapter time start: 00:11:12.254916666
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:11:13.255916666
|   + Chapter display
|    + Chapter string: Chapter 16
|    + Chapter language: eng
|  + Chapter atom
|   + Chapter UID: 14162754289675341467
|   + Chapter time start: 00:11:13.255916666
|   + Chapter flag hidden: 0
|   + Chapter flag enabled: 1
|   + Chapter time end: 00:12:13.315916666
|   + Chapter display
|    + Chapter string: Chapter 17
|    + Chapter language: eng
|+ EBML void: size 1021
|+ Cluster
mike admin
Posts: 4065
Joined: Wed Nov 26, 2008 2:26 am
Contact:

Re: Crash/Bug Report: "Fatal error occurred, program will now exit." (Code 256 at re...)

Post by mike admin »

mattpr wrote:
Mon Jan 04, 2021 5:34 pm
So now I really don't know what is going on.
  • Selecting all titles results in fatal error on 00457.m2ts.
  • Selecting all but the offending title goes without problem.
  • Selecting the offending title alone runs without problem (well without the crash at least).
The worst thing is that I can't reproduce it with all your data. It is certainly a glitch in 00457.m2ts . This is part of the (useless) menu title. But still, a lurking bug...
Tankerhank
Posts: 3
Joined: Mon Sep 16, 2019 6:23 pm

Re: Crash/Bug Report: "Fatal error occurred, program will now exit." (Code 256 at re...)

Post by Tankerhank »

Receiving the same "Fatal error occurred, program will now exit" message with Dexter Season 3 disk 3 . Didn't have an issue with disk 2. But the issue is there with Season 4 disk 1 and Season 5 disk 1.

Running Linux Mint, 20.2. MKV version 1.16.4 , running a Pioneer BD-RW BDR-212D 1.00 (firmware)

It stalls out when trying to read the MovieObject.BDMV
chrisjohnson00
Posts: 4
Joined: Thu Jun 25, 2015 4:56 am

Re: Crash/Bug Report: "Fatal error occurred, program will now exit." (Code 256 at re...)

Post by chrisjohnson00 »

Similar issue here on Linux, MakeMKV 1.16.4, openjdk 11.0.11
I've two drive that I rip with, different manufacturer, both exhibit the same issue at the same point, so it leads me to think it's crashing while processing some invalid data.
It's crashing while parsing a background.jpg file.

Here's the debug logs:

Code: Select all

Debug log started at Tue Aug 24 21:14:31 2021 , written by MakeMKV v1.16.4 linux(x64-release)
001005:0000 MakeMKV v1.16.4 linux(x64-release) started
001004:0000 Debug logging enabled, log will be saved as file:///home/chris/snap/makemkv/367/MakeMKV_log.txt
Using 262272KB for read cache.
001003:0020 DEBUG: Code 0 at :dF09'kc`L+X+;OGG >t^*:29393631
002016:0000 Failed to get full access to drive "HL-DT-ST BDDVDRW UH12NS40". Make sure that you either have write access to device "/dev/sr1", are member of "cdrom" group or have CAP_SYS_RAWIO enabled.
001003:0020 DEBUG: Code 0 at :dF09'kc`L+X+;OGG >t^*:29393631
002016:0000 Failed to get full access to drive "PLDS DVDRWBD DS-6E2SH". Make sure that you either have write access to device "/dev/sr0", are member of "cdrom" group or have CAP_SYS_RAWIO enabled.
001003:0020 DEBUG: Code 0 at <_zSP&06Pi+Hb)S):213143968
SDF  v07e: HL-DT-ST_BDDVDRW_UH12NS40_1.03_212005080959_K9PI27A2803
DEBUG: Code 2317353400 at p!='djK>XQNgT8MA0:213132974
DEBUG: Code 0 at p!='djK>XQNgT8MA0:121264786
DEBUG: Code 2317353400 at p!='djK>XQNgT8MA0:213132974
DEBUG: Code 1 at p!='djK>XQNgT8MA0:121264786
DEBUG: Code 2317353400 at p!='djK>XQNgT8MA0:213132974
DEBUG: Code 2 at p!='djK>XQNgT8MA0:121264786
DEBUG: Code 2317353400 at p!='djK>XQNgT8MA0:213132974
DEBUG: Code 3 at p!='djK>XQNgT8MA0:121264786
DEBUG: Code 2317353400 at p!='djK>XQNgT8MA0:213132974
DEBUG: Code 4 at p!='djK>XQNgT8MA0:121264786
DEBUG: Code 2317353400 at p!='djK>XQNgT8MA0:213132974
DEBUG: Code 5 at p!='djK>XQNgT8MA0:121264786
DEBUG: Code 2317353400 at p!='djK>XQNgT8MA0:121264648
DEBUG: Code 0 at ^2aHJUMJJ*&rXd17:121269823
SDF  v07e: HL-DT-ST_BDDVDRW_UH12NS40_1.03_212005080959_K9PI27A2803
No  SDF v07e: PLDS_DVDRWBD_DS-6E2SH_CD11
SDF id v07e: PLDS_DVDRWBD_DS-6E2SH_CD11
DEBUG: Code 2317353400 at p!='djK>XQNgT8MA0:213132974
DEBUG: Code 0 at p!='djK>XQNgT8MA0:121264786
DEBUG: Code 2317353400 at p!='djK>XQNgT8MA0:213132974
DEBUG: Code 1 at p!='djK>XQNgT8MA0:121264786
DEBUG: Code 2317353400 at p!='djK>XQNgT8MA0:213132974
DEBUG: Code 2 at p!='djK>XQNgT8MA0:121264786
DEBUG: Code 2317353400 at p!='djK>XQNgT8MA0:213132974
DEBUG: Code 3 at p!='djK>XQNgT8MA0:121264786
DEBUG: Code 2317353400 at p!='djK>XQNgT8MA0:213132974
DEBUG: Code 4 at p!='djK>XQNgT8MA0:121264786
DEBUG: Code 2317353400 at p!='djK>XQNgT8MA0:213132974
DEBUG: Code 5 at p!='djK>XQNgT8MA0:121264786
DEBUG: Code 2317353400 at p!='djK>XQNgT8MA0:121264648
DEBUG: Code 0 at ^2aHJUMJJ*&rXd17:121269823
003007:0000 Using direct disc access mode
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
DEBUG: Code 2147483648 at <_zSP&06Pi+Hb)S):121264625
DAFD=PAAAADAAAAEABDQkEFgACAQ==
DCE=oyHOyFPhNETCOt1M5ZIqKkJKcqAv5eGjFHCe0u2fvIXZtlEipc66bU7yJW/KJggn44wtn48qdXCnpIIM5D85QTZdVnxtXNJQzj4XBsKPntCUdeXeJx5DdIsEAXAzgtvIQCbHf3kDTu4FBaZ91lf4FE/XAHcqkkdsuA==
DCE=14VzKGkm+TN1mrMQIq7TLWKkdLoBPnfLtFpDZ+5Pcl4zalyCcprucoFXNy4oT1GLtfP1tPenwaktVtr0MKln9PGbVyl4Om0RM+FNFGQczIV/2O9WrK9AwapkdxJNdS8d6T3NhzMVEBatgqGhXds/CgDKFAbtqSM7sw==
003344:0000 Using Java runtime from /usr/bin/java
Post Reply