Here comes the Boom

[wag03]

Hello,

Used dvdfab to get the movie to my hard drive. Now when I go to put it on a dvd I keep getting an error that says Failed to Burn DVD, Do you want to burn again? I have included the log below. Any help would be greatly appreciated.

Thanks!



DVDFab 9.0.2.6 (2013/02/18 07:19:15)

0m 00.01s: Start preload dll...
0m 00.07s: Load dll successful.
0m 00.07s: Start load fabplay dll...
0m 00.15s: Load fabplay dll successful.
0m 00.17s: Windows os type is: 13.
0m 00.17s: Transfer settings successful.
0m 00.23s: GPUAccelerate: 851973
0m 00.24s: CUDA cap: 0
0m 00.24s: Support coreavc decode: 0
0m 00.24s: Graphics info: Intel(R) HD Graphics 3000 : :
0m 00.28s: Qt Translator file load success
0m 00.32s: Start get sys number.
0m 00.34s: Serial number is:
0m 00.34s: Reg URL link is:
0m 00.34s: Version is: 9026
0m 00.34s: Product is: 2
0m 00.34s: Connect type is: 0
0m 01.21s: Times of connecting error is: 0
0m 01.21s: Parse string is: 2:1419126433
0m 01.21s: Parse string is: 1:23
0m 01.23s: Parse string is: OV:9026
0m 01.23s: Parse string is: BV:9024
0m 01.23s: Parse string is: S:62d348063580a0b192cac53df35ab613
0m 01.35s: End check info.
0m 01.35s: Load config successful.
0m 01.87s: Init profile data driver sucessful.
0m 01.87s: Profile Manager :: Begin Load Profile
0m 01.87s: Init GPU settings sucessful.
0m 01.87s: option dvd2dvd 1 dvd2mobile 1 bluray2bluray 1 bd2mobile 1 bd23d 1 bd2dvd 1 file2dvd 1 file2bluray 1 file2mobile 1 filemover 1
0m 01.87s: dvd2dvd:dvd2mobile:blu-ray2blu-ray:blu-ray2mobile:blu-ray23d:blu-ray2dvd:file2mobile:file2dvd:file2bluray:
0m 11.12s: Profile Manager :: End Load Profile
0m 21.40s: Begin init preview play engine.
0m 21.41s: Init DirectShow engine successful.
0m 24.08s: Init burn engine successful.
0m 24.32s: opening drive E
0m 24.32s: opened i/o
0m 24.53s: got max lba 342015
0m 24.61s: got disc type 0
0m 24.64s: opening drive F
0m 24.66s: opened i/o
0m 24.66s: got media type 12
0m 24.67s: got max lba 0
0m 41.72s: set folder G:/Movies/Here Comes The Boom/FullDisc/HERE_COMES_THE_BOOM/VIDEO_TS/ with type 0
0m 41.73s: opening folder G:/Movies/Here Comes The Boom/FullDisc/HERE_COMES_THE_BOOM/VIDEO_TS/
0m 43.32s: set folder G:/Movies/Here Comes The Boom/FullDisc/HERE_COMES_THE_BOOM/VIDEO_TS/ with type 0
0m 43.32s: opening folder G:/Movies/Here Comes The Boom/FullDisc/HERE_COMES_THE_BOOM/VIDEO_TS/
0m 43.46s: pathplayer enabled
1m 01.25s: Burn data size is: 4484
1m 01.25s: Burn disc space is: 4482
1m 01.66s: burn folder G:\Movies\Here Comes The Boom\FullDisc\HERE_COMES_THE_BOOM\ with VSO

[Jonatan]

faild

The same happened here but when it ejected i played in standalone player and it was a good burn used imgburn dint know why fab failed at end of burn but it completely burned the main movie

Hope it helps

[wag03]

I can't even get it to start the burn phase.

[Jonatan]

I noticed that too but i switched burn module to img burn and it workes d/l imgburn and run it with fab remember to set automatic write speed to half the rated speed of media and it should burn fine

[Axel Slingerland]

I go even farther that that and set the burn speed to as slow at it will go. Some people say that may be a bit extreme, but I have only had one actual failure in burning several hundred DVDs. It takes a few minutes longer, but it's worth it. It sure beats having to do it again.

[CBR929]

Hi Axel Slingerland
Please post your logs the default location is:
For Win7 C:\Users\User Name\My Documents\DVDFab\Log
or Vista C:\Users\User Name\Documents\DVDFab\Log
or for XP C:\Documents and Settings\User Name\My Documents\DVDFab\Log
Please use attachment button and attach your most recent, Burn log and post right here.
CBR929

[Axel Slingerland]

Are you referring to wag03? I was just commenting on how I prefer the slowest burn speed, because it makes a better copy. My logs wouldn't really apply to this thread, since I never even heard of this movie.

[CBR929]

Hi Axel Slingerland
Burning at the slowest speed can also cause problems.
It recommended to burn your media at 1/2 the rated speed of your discs.
CBR929

[geilee]

Hi,wag03

Hello,

DVDFab 9.0.2.6 (2013/02/18 07:19:15)

Boom/FullDisc/HERE_COMES_THE_BOOM/VIDEO_TS/
0m 43.46s: pathplayer enabled
1m 01.25s: Burn data size is: 4484
1m 01.25s: Burn disc space is: 4482
1m 01.66s: burn folder G:\Movies\Here Comes The Boom\FullDisc\HERE_COMES_THE_BOOM\ with VSO

Burn data size is:4484, it is oversize.
You can attempt to use a dual disc to burn it.

[CBR929]

Hi wag03
Along with what geilee suggested, please go into Fabs settings and make sure that your write size is not over 4472.
CBR929

[halil1972]

here comes the boom log file,HELP

DVDFab 9.0.2.6 (2013/02/20 16:11:50)

0m 00.00s: Start preload dll...
0m 00.06s: Load dll successful.
0m 00.07s: Start load fabplay dll...
0m 00.15s: Load fabplay dll successful.
0m 00.15s: Windows os type is: 13.
0m 00.15s: Transfer settings successful.
0m 00.24s: GPUAccelerate: 851973
0m 00.24s: CUDA cap: 0
0m 00.24s: Support coreavc decode: 0
0m 00.26s: Graphics info: Intel(R) HD Graphics 3000 : :
0m 00.26s: Qt Translator file load success
0m 00.31s: Start get sys number.
0m 00.31s: Serial number is: 20-e5-2a-14-5d-ba:20-e5-2a-14-5d-ba:80-ee-73-3d-a0-a8
0m 00.31s: Reg URL link is:
0m 00.31s: Version is: 9026
0m 00.31s: Product is: 2
0m 00.31s: Connect type is: 0
0m 01.02s: Times of connecting error is: 0
0m 01.04s: Parse string is: 2:1416447182
0m 01.04s: Parse string is: OV:9026
0m 01.04s: Parse string is: BV:9024
0m 01.04s: Parse string is: S:ccb2f3c9a8f8574871bf809ca5387041
0m 01.32s: End check info.
0m 01.32s: Load config successful.
0m 01.51s: Profile Manager :: Begin Load Profile
0m 01.51s: Init profile data driver sucessful.
0m 01.51s: Init GPU settings sucessful.
0m 01.51s: option dvd2dvd 1 dvd2mobile 1 bluray2bluray 1 bd2mobile 1 bd23d 1 bd2dvd 1 file2dvd 1 file2bluray 1 file2mobile 1 filemover 1
0m 01.51s: dvd2dvd:dvd2mobile:blu-ray2blu-ray:blu-ray2mobile:blu-ray23d:blu-ray2dvd:file2mobile:file2dvd:file2bluray:
0m 05.61s: Begin init preview play engine.
0m 05.61s: Init DirectShow engine successful.
0m 05.78s: Init burn engine successful.
0m 05.99s: opening drive D
0m 06.00s: opened i/o
0m 06.00s: got media type 4
0m 08.00s: got max lba 3648527
0m 08.02s: got disc type 10
0m 08.07s: type DVD-VIDEO
0m 08.08s: volume label HERE_COMES_THE_BOOM
0m 08.09s: opening drive E
0m 08.09s: opened i/o
0m 08.09s: failed to detect media type: sensekey 00 asc 00 acsq 00
0m 08.09s: got max lba 0
0m 08.13s: internal path D:/VIDEO_TS/
0m 08.17s: got copyright 1 f2
0m 08.81s: got udf/iso
0m 10.67s: Profile Manager :: End Load Profile
0m 11.48s: got discinfo
0m 11.49s: pathplayer enabled
0m 12.78s: button: vts_1 menu_1 pgc_14 cell_2 sector_715 count_4
0m 19.78s: button: vts_1 menu_1 pgc_20 cell_1 sector_38375 count_5
0m 19.96s: button: vts_1 menu_1 pgc_17 cell_1 sector_38210 count_5
0m 20.10s: button: vts_1 menu_1 pgc_14 cell_3 sector_19302 count_4
0m 20.35s: button: vts_1 menu_1 pgc_17 cell_2 sector_76019 count_5
0m 20.86s: button: vts_1 menu_1 pgc_18 cell_1 sector_38268 count_12
0m 25.65s: button: vts_1 menu_1 pgc_19 cell_1 sector_38320 count_11
0m 26.80s: button: vts_1 menu_1 pgc_24 cell_1 sector_38429 count_15
0m 27.03s: button: vts_1 menu_1 pgc_24 cell_2 sector_76243 count_15
0m 27.25s: button: vts_1 menu_1 pgc_17 cell_3 sector_76325 count_5
0m 27.48s: button: vts_1 menu_1 pgc_24 cell_3 sector_76529 count_15
0m 27.68s: button: vts_1 menu_1 pgc_17 cell_4 sector_76670 count_5
0m 27.89s: button: vts_1 menu_1 pgc_24 cell_4 sector_76828 count_15
0m 28.09s: button: vts_1 menu_1 pgc_17 cell_5 sector_76913 count_5
0m 28.33s: button: vts_1 menu_1 pgc_24 cell_5 sector_77128 count_15
0m 29.50s: button: vts_1 menu_1 pgc_15 cell_1 sector_37928 count_9
0m 29.67s: button: vts_1 menu_1 pgc_15 cell_2 sector_38006 count_9
0m 29.92s: button: vts_1 menu_1 pgc_15 cell_3 sector_38085 count_9
0m 30.15s: button: vts_1 menu_1 pgc_15 cell_4 sector_38164 count_9
0m 58.13s: button: vts_1 menu_1 pgc_14 cell_5 sector_38932 count_4
0m 59.07s: button: vts_1 menu_1 pgc_14 cell_6 sector_57433 count_4
3m 03.69s: user cancelled
3m 03.69s: pathplayer drive error 1
3m 03.70s: pathplayer drive error 1
3m 03.70s: pathplayer drive error 1
3m 03.70s: pathplayer drive error 1
3m 03.70s: pathplayer drive error 1
3m 03.70s: pathplayer drive error 1
3m 03.70s: pathplayer drive error 1
3m 03.70s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.71s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.72s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.73s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.74s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.75s: pathplayer drive error 1
3m 03.76s: failed to open 1