Jump to content

Recording speed of BD-R drops halfway (it is stable for BD-RE)


Recommended Posts

Posted

Hi everyone,

 

When I try to burn BD-R disc (I have tried Verbatim CMCMAG-BA5-000, and Panasonic with some other dye) using both my Samsung SE-506BB and SE-506CB they would ignore maximum writing speed, and try to record with highest available. 

 

Then, in the middle of the single-layer disc the speed drops dramatically (to 0.6x-0.7x) and stays that way until the very end.

 

The discs play fine afterwards, but I wonder what might be the reason for this behaviour. It doesn't happen on BD-RE from Emtec. 

 

I have OPC enabled. ImgBurn 2.5.8.0, Windows 8.1 (though it was the same on windows 7 and Ubuntu 13.10).

 

Any ideas?

Posted (edited)

Sure, sorry :) This one is from yesterday - speed was set at 6x, now I am burning with 2x and the same happens - I will post the second log when it finishes.

I 21:53:18 ImgBurn Version 2.5.8.0 started!
I 21:53:18 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
I 21:53:18 Total Physical Memory: 2 994 640 KiB  -  Available: 1 354 568 KiB
I 21:53:18 Initialising SPTI...
I 21:53:18 Searching for SCSI / ATAPI devices...
I 21:53:18 -> Drive 1 - Info: TSSTcorp BDDVDW SE-506CB TS01 (G:) (USB 2.0)
I 21:53:19 -> Drive 2 - Info: Optiarc DVD+-RW AD-7580S FD06 (F:) (SATA)
I 21:53:19 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (H:) (SCSI)
I 21:53:19 Found 1 DVD±RW/RAM, 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL!
I 21:53:49 Operation Started!
I 21:53:49 Building Image Tree...
I 21:53:59 Calculating Totals...
I 21:53:59 Preparing Image...
I 21:53:59 Contents: 12 Files, 16 Folders
I 21:54:00 Content Type: BD Video
I 21:54:00 Data Type: MODE1/2048
I 21:54:00 File System(s): UDF (2.50)
I 21:54:00 Volume Label: Inglorious Basterds
I 21:54:00 Size: 23 809 772 312 bytes
I 21:54:00 Sectors: 11 625 873
I 21:54:00 Image Size: 23 810 801 664 bytes
I 21:54:00 Image Sectors: 11 626 368
I 21:54:02 Operation Successfully Completed! - Duration: 00:00:12
I 21:54:02 Operation Started!
I 21:54:02 Source File: -==/\/[BUILD IMAGE]\/\==-
I 21:54:02 Source File Sectors: 11 626 368 (MODE1/2048)
I 21:54:02 Source File Size: 23 810 801 664 bytes
I 21:54:02 Source File Volume Identifier: Inglorious Basterds
I 21:54:02 Source File Volume Set Identifier: 4564AEB800B16711
I 21:54:02 Source File Application Identifier: ImgBurn v2.5.8.0
I 21:54:02 Source File Implementation Identifier: ImgBurn
I 21:54:02 Source File File System(s): UDF (2.50)
I 21:54:02 Destination Device: [0:0:0] TSSTcorp BDDVDW SE-506CB TS01 (G:) (USB)
I 21:54:02 Destination Media Type: BD-R (Disc ID: CMCMAG-BA5-000)
I 21:54:02 Destination Media Supported Write Speeds: 2x; 4x; 6x
I 21:54:02 Destination Media Sectors: 12 219 392
I 21:54:02 Write Mode: BD
I 21:54:02 Write Type: DAO
I 21:54:02 Write Speed: MAX
I 21:54:02 Hardware Defect Management Active: No
I 21:54:02 BD-R Verify Not Required: Yes
I 21:54:02 Link Size: Auto
I 21:54:02 Lock Volume: Yes
I 21:54:02 Test Mode: No
I 21:54:02 OPC: Yes
I 21:54:02 BURN-Proof: Enabled
I 21:54:02 Write Speed Successfully Set! - Effective: 26 976 KB/s (6x)
I 21:55:01 Filling Buffer... (80 MiB)
I 21:55:05 Writing LeadIn...
I 21:55:25 Writing Session 1 of 1... (1 Track, LBA: 0 - 11626367)
I 21:55:25 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 11626367)
I 00:03:48 Synchronising Cache...
I 00:03:53 Closing Track...
I 00:03:54 Finalising Disc...
I 00:05:15 Exporting Graph Data...
I 00:05:15 Export Successfully Completed!
I 00:05:15 Operation Successfully Completed! - Duration: 02:11:13
I 00:05:15 Average Write Rate: 3 019 KiB/s (0.7x) - Maximum Write Rate: 19 307 KiB/s (4.4x)

https://drive.google.com/file/d/0B9LKKOOjI1e6VG5rM1VhYkt6T1U/

Edited by mstefanski1987
Posted

2014-11-05_11-14-16.png

 

Looking at the graph data for the 6x burn, I'd say you're hitting the limits of USB 2.0 on your drive/usb controller combo and the drive is then having to throttle itself back (badly).

 

That's causing the latter part of the burn to be really stop / start.

 

I'll now await the same info from your 2x burn.

Posted

And this is where it gets interesting  - drive chose to ignore my settings and just went with burning with maximum speed.

I 07:09:23 Operation Started!
I 07:09:23 Building Image Tree...
I 07:09:23 Calculating Totals...
I 07:09:23 Preparing Image...
I 07:09:24 Contents: 9 Files, 15 Folders
I 07:09:24 Content Type: BD Video
I 07:09:24 Data Type: MODE1/2048
I 07:09:24 File System(s): UDF (2.50)
I 07:09:24 Volume Label: Appleseed Alpha
I 07:09:24 Size: 23 620 826 748 bytes
I 07:09:24 Sectors: 11 533 613
I 07:09:24 Image Size: 23 621 861 376 bytes
I 07:09:24 Image Sectors: 11 534 112
I 07:09:27 Operation Successfully Completed! - Duration: 00:00:03
I 07:09:27 Operation Started!
I 07:09:27 Source File: -==/\/[BUILD IMAGE]\/\==-
I 07:09:27 Source File Sectors: 11 534 112 (MODE1/2048)
I 07:09:27 Source File Size: 23 621 861 376 bytes
I 07:09:27 Source File Volume Identifier: Appleseed Alpha
I 07:09:27 Source File Volume Set Identifier: 4565392B00AFFEAD
I 07:09:27 Source File Application Identifier: ImgBurn v2.5.8.0
I 07:09:27 Source File Implementation Identifier: ImgBurn
I 07:09:27 Source File File System(s): UDF (2.50)
I 07:09:27 Destination Device: [0:0:0] TSSTcorp BDDVDW SE-506CB TS01 (G:) (USB)
I 07:09:27 Destination Media Type: BD-R (Disc ID: CMCMAG-BA5-000)
I 07:09:27 Destination Media Supported Write Speeds: 2x; 4x; 6x
I 07:09:27 Destination Media Sectors: 12 219 392
I 07:09:27 Write Mode: BD
I 07:09:27 Write Type: DAO
I 07:09:27 Write Speed: 2x
I 07:09:27 Hardware Defect Management Active: No
I 07:09:27 BD-R Verify Not Required: Yes
I 07:09:27 Link Size: Auto
I 07:09:27 Lock Volume: Yes
I 07:09:27 Test Mode: No
I 07:09:27 OPC: Yes
I 07:09:27 BURN-Proof: Enabled
I 07:09:27 Write Speed Successfully Set! - Effective: 8 992 KB/s (2x)
I 07:10:26 Filling Buffer... (80 MiB)
I 07:10:30 Writing LeadIn...
I 07:10:49 Writing Session 1 of 1... (1 Track, LBA: 0 - 11534111)
I 07:10:49 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 11534111)
I 09:17:16 Synchronising Cache...
I 09:17:20 Closing Track...
I 09:17:21 Finalising Disc...
I 09:18:46 Exporting Graph Data...
I 09:18:46 Graph Data File: C:\Users\marci_000\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_BDDVDW_SE-506CB_TS01_5-LISTOPAD-2014_07-09_CMCMAG-BA5-000_2x.ibg
I 09:18:46 Export Successfully Completed!
I 09:18:46 Operation Successfully Completed! - Duration: 02:09:18
I 09:18:46 Average Write Rate: 3 040 KiB/s (0.7x) - Maximum Write Rate: 18 377 KiB/s (4.2x)

https://drive.google.com/file/d/0B9LKKOOjI1e6T3Nlc0ZvbUZEcUE

Posted

Oh, great!  Verbatim is now using CMC for their BD-R's!  :angry:  I wonder how long it will be before ALL you can get from Verbatim is CMC :horse:  :rolleyes:

Posted

If the drive's firmware ignores 2x, try 4x.

 

USB might just manage 4x ok and you may end up with a nice smooth write speed line without the drive having to spin up and down/pause all the time.

Posted

Still the same. Why is the recorder ignoring the settings? Is there a way to force it?

I 07:36:24 ImgBurn Version 2.5.8.0 started!
I 07:36:24 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
I 07:36:24 Total Physical Memory: 2 994 640 KiB  -  Available: 1 088 116 KiB
I 07:36:24 Initialising SPTI...
I 07:36:24 Searching for SCSI / ATAPI devices...
I 07:36:27 -> Drive 1 - Info: TSSTcorp BDDVDW SE-506CB TS01 (G:) (USB 2.0)
I 07:36:28 -> Drive 2 - Info: Optiarc DVD+-RW AD-7580S FD06 (F:) (SATA)
I 07:36:28 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (H:) (SCSI)
I 07:36:28 Found 1 DVD±RW/RAM, 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL!
I 07:36:54 Operation Started!
I 07:36:54 Building Image Tree...
I 07:36:54 Calculating Totals...
I 07:36:54 Preparing Image...
I 07:36:54 Contents: 27 Files, 16 Folders
I 07:36:54 Content Type: BD Video
I 07:36:54 Data Type: MODE1/2048
I 07:36:54 File System(s): UDF (2.50)
I 07:36:55 Size: 22 132 388 487 bytes
I 07:36:55 Sectors: 10 806 848
I 07:36:55 Image Size: 22 133 473 280 bytes
I 07:36:55 Image Sectors: 10 807 360
I 07:36:57 Operation Successfully Completed! - Duration: 00:00:03
I 07:36:57 Operation Started!
I 07:36:57 Source File: -==/\/[BUILD IMAGE]\/\==-
I 07:36:57 Source File Sectors: 10 807 360 (MODE1/2048)
I 07:36:57 Source File Size: 22 133 473 280 bytes
I 07:36:57 Source File Volume Identifier: Apollo 13
I 07:36:57 Source File Volume Set Identifier: 45663C9B00A4E7C0
I 07:36:57 Source File Application Identifier: ImgBurn v2.5.8.0
I 07:36:57 Source File Implementation Identifier: ImgBurn
I 07:36:57 Source File File System(s): UDF (2.50)
I 07:36:57 Destination Device: [0:0:0] TSSTcorp BDDVDW SE-506CB TS01 (G:) (USB)
I 07:36:57 Destination Media Type: BD-R (Disc ID: CMCMAG-BA5-000)
I 07:36:57 Destination Media Supported Write Speeds: 2x; 4x; 6x
I 07:36:57 Destination Media Sectors: 12 219 392
I 07:36:57 Write Mode: BD
I 07:36:57 Write Type: DAO
I 07:36:57 Write Speed: 4x
I 07:36:57 Hardware Defect Management Active: No
I 07:36:57 BD-R Verify Not Required: Yes
I 07:36:57 Link Size: Auto
I 07:36:57 Lock Volume: Yes
I 07:36:57 Test Mode: No
I 07:36:57 OPC: Yes
I 07:36:57 BURN-Proof: Enabled
I 07:36:57 Write Speed Successfully Set! - Effective: 17 984 KB/s (4x)
I 07:37:54 Filling Buffer... (80 MiB)
I 07:37:56 Writing LeadIn...
I 07:38:16 Writing Session 1 of 1... (1 Track, LBA: 0 - 10807359)
I 07:38:16 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 10807359)
I 09:29:14 Synchronising Cache...
I 09:29:22 Closing Track...
I 09:29:23 Finalising Disc...
I 09:30:49 Exporting Graph Data...
I 09:30:49 Graph Data File: C:\Users\marci_000\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_BDDVDW_SE-506CB_TS01_6-LISTOPAD-2014_07-36_CMCMAG-BA5-000_4x.ibg
I 09:30:49 Export Successfully Completed!
I 09:30:49 Operation Successfully Completed! - Duration: 01:53:51
I 09:30:49 Average Write Rate: 3 246 KiB/s (0.7x) - Maximum Write Rate: 19 238 KiB/s (4.4x)

 

 

I am not attaching file because it is pretty much the same.

Posted

It must be a bug in the drive's firmware. No, you can't force the drive to do anything... the firmware either accepts or rejects commands that programs send it, but ultimately, it'll do whatever it wants!

 

Your drive *thinks* it has accepted the write speed the program has asked it to use, that's why the 'Effective' speed says what you've set it to. The 'Effective' speed is the speed the drive reports it's going to burn at and isn't linked to the speed you select in ImgBurn.

 

I wonder if some different discs would behave differently? There's a thread for this drive at the MyCE forums. Maybe some of their tests/results will show a disc burning ok at 2x. I know I saw a post over there yesterday saying the TS01 firmware update didn't fix the disc burning at 6x instead of the selected 2x (i.e. the problem you're having).

Posted (edited)

I've seen the exact topic you've mentioned only about a week ago. 

 

http://club.myce.com/f105/samsung-se-506cb-336191/

 

I am wondering if there is any chance of forcing a producer to release an update - or altering speed table in the firmware and upload it to the drive.

 

Kind of like with this tool: http://ala42.cdfreaks.com/MCSE/

 

Do you have any ideas?

 

Edit: I have unpacked the firmware TS01 into *bin file and tried to edit it with Media Code Speed Edit, but the program is not supporting this file and shows me nothing. I will try to do some "hexedit research" in my free time and post some results.

Edited by mstefanski1987
Posted

It isn't the speed tables that are the problem, your drive lists that it supports the speeds you're trying to use for that media.

 

The problem appears to run deeper than that.

Posted

I have contacted the producer directly and I will keep you posted about the results, unless you believe I should do this on another forum, since the issue is not imgburn-related.

 

 

DlZRtKJ.png

Posted

vsLv5dX.jpg

 

Just FYI - this is the "quality" of SE-506CB burn on CMCMAG-BA5.

 

Seriously, I have never been so dissapointed wiith any hardware as much as with Samsung BD burners. Avoid it at any cost :(

Posted

I believe CDForum's opinion of Samsung drives is that they're near the bottom of the quality list, along with Panasonic.

 

 

Of course, the quality here could be because of the CMC medium.  They do make the worst optical media out there.  :)

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.