• AnyStream is having some DRM issues currently, Netflix is not available in HD for the time being.
    Situations like this will always happen with AnyStream: streaming providers are continuously improving their countermeasures while we try to catch up, it's an ongoing cat-and-mouse game. Please be patient and don't flood our support or forum with requests, we are working on it 24/7 to get it resolved. Thank you.

Burn failure

Ch3vr0n

Ch3vr0n

Translator NL
Thread Starter
Joined
Sep 27, 2009
Messages
24,312
Likes
3,530
Just tried the CLBD burn engine for the first time on a BDR from mediarange (PHILIP-W02-000).Works fine in IMGburn. CLBD failed with

Burn failed with error 24
Burn error

only setting changed from 2x to max speed (which is technically still 2x on that disc)

Kept temp folder, launched IMGBurn, fed CLBD output, started to burn just fine. Can't attach clbd log. At 10.5MB it's too big. Forum seems to load but doesn't attach
 
Ch3vr0n said:
Just tried the CLBD burn engine for the first time on a BDR from mediarange (PHILIP-W02-000).Works fine in IMGburn. CLBD failed with

Burn failed with error 24
Burn error

only setting changed from 2x to max speed (which is technically still 2x on that disc)

Kept temp folder, launched IMGBurn, fed CLBD output, started to burn just fine. Can't attach clbd log. At 10.5MB it's too big. Forum seems to load but doesn't attach
Click to expand...

the forum allows up to 70MB for certain file types (including cbdlog).
Maybe some PHP limit....

Error 24 is actually "The disc is not erasable." (which is a correct statement for a BD-R).
So it appears the burning engine saw a non-empty BD-R.
 
Well it didn't accept mine. And that disc was NOT a bd-r. It was a bd-re. I can post the imgburn info if you'd like.

Sent from my Nexus 6P with Tapatalk
 
Ch3vr0n said:
Well it didn't accept mine. And that disc was NOT a bd-r. It was a bd-re. I can post the imgburn info if you'd like.
Click to expand...
Ok, well you said BD-R, so I went with that.
The only thing that would help, is a CloneBD log file.

Did you try it again with the same disc? (After Imgburn burned it)
 
Typo. I'll try again for the logfile this evening. Did you mean retry as in redo the whole cloning process or just feed the clbd output to clbd again full copy and burn that way?

Sent from my Nexus 6P with Tapatalk
 
Ch3vr0n said:
Typo. I'll try again for the logfile this evening. Did you mean retry as in redo the whole cloning process or just feed the clbd output to clbd again full copy and burn that way?
Click to expand...
Easiest would be to open an ISO with CloneBD, small enough to fit, then do "complete copy" to disc.
That way, the ISO will get burned directly (no extra copying to HDD etc...)
 
Well it's a folder. I always delete the disc.inf file that gets copied too. I'll just do a complete copy again from the original DL AnyDVD iso rip. With HW acc it'll only take 20min to hit the burning phase again. I'll report back this evening with the outcome.

Sent from my Nexus 6P with Tapatalk
 
IMGBurn report pre-clone redo:

Code: 
HL-DT-ST BD-RE  BH16NS40 1.03 (SATA)
Current Profile: BD-RE

Disc Information:
Status: Complete
State of Last Session: Complete
Erasable: Yes
Sessions: 1
Sectors: 12 219 392
Size: 25 025 314 816 bytes
Time: 2715:27:17 (MM:SS:FF)
MID: PHILIP-W02-000
Supported Write Speeds: 2x

TOC Information:
Sessie 1... (LBA: 0)
-> Track 01  (Mode 1, LBA: 0 - 12219391)
-> LeadOut  (LBA: 12219392)

Disc Definition Structure:
Certified: Yes - Full
Scanned: No

BD Disc Information:
Disc ID: PHILIP-W02-000
Disc Type: BD-RE
Disc Size: 120 mm
Disc Class: 0
Disc Version: 2
Number of Layers: 1
Layer Type: Rewritable
DVD Layer Present: No
CD Layer Present: No
Channel Bit Length: 74.50 nm (25 GB Per Layer)
BCA Present: Yes
Maximum Transfer Rate: Not Specified
First PAA of Data Zone: 131 072
Last PAA of Data Zone: 1 658 494

Format Capacities:
DT: 0x02 - NB: 12219392 (0x00BA7400) - TDP: 0
FT: 0x00 - NB: 11826176 (0x00B47400) - TDP: 12288
FT: 0x30 - NB: 11826176 (0x00B47400) - TDP: 12288
FT: 0x30 - NB: 11564032 (0x00B07400) - TDP: 20480
FT: 0x30 - NB: 12088320 (0x00B87400) - TDP: 4096
FT: 0x31 - NB: 12219392 (0x00BA7400) - TDP: 2048

Performance (Write Speed):
Descriptor 1...
-> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00
-> EL: 12219391 (0x00BA73FF)
-> RS: 26 976 KB/s (6x) - WS: 8 992 KB/s (2x)

Status message: Ready (Disc not empty). <= normal for rewriteable discs, meaning ready to overwrite

CloneBD reports: The writeable disc in drive H:\ is not empty and all contents will be overwritten.

Cloning commenced, full disc mode, best quality. ETA 1h inclu burning (if it'll work this time)

* edit * @Pete burning just started. For now this issue is "resolved". Perhaps a fluke or due to the "backup discs hidden bug in anydvd beta's". The only thing that was different between this attempt and the problem one is that i had reverted back from AnyDVD 8175 to the latest stable release 8170. I'll keep an eye on this if it reoccurs

* edit 2 * burn successful, I'll keep an eye on things. I'll test the burn result by playback tomorrow.
 
Last edited:
Just want to report, but probably won't be the issue.

I had issues burning a 4.6 GByte ISO (eg. Knoppix) with ImgBurn over to an DVD-RAM with already data on it.
Got write errors / and or content not readable. Still the disc was clean and no visible scratches.

Only thing that helped helped was to fully erase the disc before burning.
(The fast erase mode didn't help.)
Had a relating problem as with DVD-RAM when burning an image over an occupied DVD+RW.
 
You must log in or register to reply here.
Back
Top