I cannot burn a video to DVD. I keep getting the message that the disc is not writable, but it is

ianmo wrote on 8/28/2015, 7:48 AM

If I try to burn a DVD (actually a DVD+R) I get the following message:

"Burning was aborted with the following error:

Internal error while processing

Disc can only be read, not written"

However the disc is brand new and definitely writable. It shows as having 4.38GB free in both Movie Maker and in Windows

This is the relevant portion of the log file:

28/08/2015 13:41:33.944:   ------------ BurnToDisc ----------------
28/08/2015 13:41:33.948:   Used burn options:
simulation: off
DiscAtOnce: off
BurnOver: off
BurnProof: on
FormatDisc: off
ShortLeadOut: off
NoDefectMgmt: off
28/08/2015 13:41:33.950:    Booktype: don't care
28/08/2015 13:41:33.953:   setting write speed to 11080000  bytes/sec
28/08/2015 13:41:33.956:   this equals 8.000000x DVD / 62.811790x CD Speed
28/08/2015 13:41:33.958:   mounting volume on device...OK
28/08/2015 13:41:33.960:   Check on previously direct recorded session...OK
28/08/2015 13:41:33.963:   -- Volume mounted --
28/08/2015 13:41:33.965:   -- Recording on "E: PLDS BD COMBO DC6E2SH" --
28/08/2015 13:41:33.967:   -- Medium is "DVD+R" --
28/08/2015 13:41:33.970:   -- Manufacturer "UME02" --
28/08/2015 13:41:34.288:   AVSDK Message - INFO: :Recording volume ...
28/08/2015 13:41:34.295:   AVSDK Status - Begin operation Recording 1490640 sectors/frames
28/08/2015 13:41:34.303:   AVSDK Message - INFO: :Recording -> writing data ...
28/08/2015 13:41:35.384:   wrote LeadIn, start DataCopy
28/08/2015 13:41:51.185:   AVSDK Message - ERROR: :Cannot write to disc -> Power calibration or program memory area update failure (SK/ASC/ASCQ 03/73/03)
28/08/2015 13:42:01.812:   AVSDK Status - End operation Recording 1490640 sectors/frames
28/08/2015 13:42:01.819:   AVSDK Message - INFO: :Recording failed, refer to previous error messages for more information
28/08/2015 13:42:01.826:   !!! AVSDK error: BurnToDisc() calling AvVolWriteToDisc(): 202 - disc is not writable !!!
28/08/2015 13:42:01.832:   !!! DBK error in CBurnDevSupportPoint::BurnToDisc(): 220 - disc is not writable !!!
28/08/2015 13:42:01.838:   ------------ done ----------------
28/08/2015 13:42:01.844:   Step 7 done
28/08/2015 13:42:01.850:   project burning failed
28/08/2015 13:42:01.858:   !!! DBK error in CBurnDevSupport::BurnProject(): 220 - disc is not writable !!!
28/08/2015 13:42:01.863:   !!! DBK error in BurnProject: 220 - disc is not writable !!!

Comments

johnebaker wrote on 8/28/2015, 9:01 AM

Hi

The disc has already had an attempted burn or is faulty - the brand you are using (Tesco own brand?) has a history of mixed reliability.

Try using good quality DVD-R discs eg RiDisc, Ritek, Verbatim.

HTH

John EB

 

Last changed by johnebaker on 8/28/2015, 9:01 AM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

ianmo wrote on 8/28/2015, 9:05 AM

Thanks for the answer but I don't think that's it. I have tried 5 of them, they are all brand new. If I try writing files to them after the burn has failed in Movie Maker (just using Windows for example) they work fine. So I'm pretty sure there is nothing wrong with the discs.

ianmo wrote on 8/28/2015, 10:11 AM

I just went and bought a brand new TDK DVD+R, got exactly the same result. There must be something else wrong, it can't be the discs.

johnebaker wrote on 8/28/2015, 1:08 PM

Hi

What does the error log say for the last burn?

Which MEP are you using and what is its version number - under Help, About. . .

From the burn log you posted, it is possible that the burner has a problem with DVD+R discs - that is one of he reasons I specified DVD-R, the other being, in my experience, DVD+R and DVD+RW are not reliable enough - at least in the burners I have used over the years.

I also use DVD-RW discs for the initial burn - they can be re-used if burns fail and if successful and the movie needs no further editing they can be copied directly to permanent disc and re-used.

John EB

Last changed by johnebaker on 8/28/2015, 1:08 PM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

ianmo wrote on 8/28/2015, 1:24 PM

Thanks for your help John. I have pasted the log file below, it looks like exactly the same issue. It starts with "Power calibration or program memory area update failure (SK/ASC/ASCQ 03/73/03)".

Actually I have just managed to get one of the DVD+R discs to work. It was one that didn't work previously but just decided to work for no apparent reason. However no other discs will work.

I have tried a TDK DVD-R, it fails with the same issue.

It looks like some kind of intermittent bug. Really frustrating!

Is there some way to update the burner? I applied all outstanding updates before beginning so I assume that includes any updates to the burner. Clearly it's a bit buggy :-(

 

28/08/2015 19:19:06.999:   ------------ BurnToDisc ----------------
28/08/2015 19:19:07.003:   Used burn options:
simulation: off
DiscAtOnce: off
BurnOver: off
BurnProof: on
FormatDisc: off
ShortLeadOut: off
NoDefectMgmt: off
28/08/2015 19:19:07.005:    Booktype: don't care
28/08/2015 19:19:07.008:   setting write speed to 11080000  bytes/sec
28/08/2015 19:19:07.010:   this equals 8.000000x DVD / 62.811790x CD Speed
28/08/2015 19:19:07.013:   mounting volume on device...OK
28/08/2015 19:19:07.015:   Check on previously direct recorded session...OK
28/08/2015 19:19:07.018:   -- Volume mounted --
28/08/2015 19:19:07.020:   -- Recording on "E: PLDS BD COMBO DC6E2SH" --
28/08/2015 19:19:07.022:   -- Medium is "DVD+R" --
28/08/2015 19:19:07.025:   -- Manufacturer "MBI 01RG40" --
28/08/2015 19:19:07.336:   AVSDK Message - INFO: :Recording volume ...
28/08/2015 19:19:07.343:   AVSDK Status - Begin operation Recording 2052288 sectors/frames
28/08/2015 19:19:07.352:   AVSDK Message - INFO: :Recording -> writing data ...
28/08/2015 19:19:07.735:   wrote LeadIn, start DataCopy
28/08/2015 19:19:28.191:   AVSDK Message - ERROR: :Cannot write to disc -> Power calibration or program memory area update failure (SK/ASC/ASCQ 03/73/03)
28/08/2015 19:19:38.754:   AVSDK Status - End operation Recording 2052288 sectors/frames
28/08/2015 19:19:38.757:   AVSDK Message - INFO: :Recording failed, refer to previous error messages for more information
28/08/2015 19:19:38.760:   !!! AVSDK error: BurnToDisc() calling AvVolWriteToDisc(): 202 - disc is not writable !!!
28/08/2015 19:19:38.763:   !!! DBK error in CBurnDevSupportPoint::BurnToDisc(): 220 - disc is not writable !!!
28/08/2015 19:19:38.765:   ------------ done ----------------
28/08/2015 19:19:38.768:   Step 6 done
28/08/2015 19:19:38.772:   project burning failed
28/08/2015 19:19:38.779:   !!! DBK error in CBurnDevSupport::BurnProject(): 220 - disc is not writable !!!
28/08/2015 19:19:38.781:   !!! DBK error in BurnProject: 220 - disc is not writable !!!

johnebaker wrote on 8/29/2015, 3:23 AM

Hi

. . . . Actually I have just managed to get one of the DVD+R discs to work . . . .

That suggest to me that there may be an issue with the burner, however, to make sure that it is not the program, the latest burn routines are here. you may need to login with your email address and password.

NOTE  it is important that, for us to help you solve this problem, you give answers to the questions you are asked .

Is the burner an external USB device or in a laptop?

Which version of MEP are you using?

Which version of Windows are you using?

If the burner is an external USB device or is in a laptop,  then the issue may be that Windows is putting the USB port it is on is going into power save mode and it does not wake up fast enough for MEP. 

To stop this you need to change the USB ports set following these instructions - you should not need to follow any of the additional suggestions in the comments of the article.

 

John EB

 

Last changed by johnebaker on 8/29/2015, 3:23 AM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

ianmo wrote on 8/29/2015, 7:05 AM

Thanks again John.

In answer to the questions:

  • Is the burner an external USB device or in a laptop? It is an internal / integrated burner on an all-in-one PC (Lenovo A720), not connected via USB. I did the USB change anyway just in case but it didn't seem to help
  • Which version of MEP are you using? Movie Edit Pro 2013 Plus Version 12.0.4.2 (UDC2)
  • Which version of Windows are you using? Windows 10 Pro

I installed the latest burn routines but unfortunately they don't seem to have made a difference.