Problem Burning DVD

harrismith escrito el 12.09.PM a las 17:43 horas

Using - Magix Movie Edit Pro 2013 on Windows 8.

My Samsung DVD Burner is recognised in Device Manager and appears as an option in the Magix  'Burning' dialogue box. So Far so good.

The Disc format selected is 'Standard PAL'

When I hit the 'Burn' button I am asked if the existing VTS.VOB file/s should be used and I haven't a clue!

What are they and which options should be selected.

The options are;

Rewrite chapter menu; Rewrite film menu

Encode all, Encode, Use, Use all

Comentarios

johnebaker escrito el 12.09.PM a las 22:11 horas

Hi

These options appear once you have carried out a burn to DVD, first you need to know the structure of a DVD which has the following components:

VTS_01_1.VOB - contains the movie - there may be more each sequentially numbered

Video_TS.VOB - is the menu 'movie'

The IFO and BUP files contain information and instructions for the DVD player about the menu actions, where the chapters etc are located in the VOB's and where the movies are located on the DVD.

The options are used as follows, as I understand them (if the order of use appears odd all will become clear I hope):

1.  Encode All - MEP will re-encode everything on the timeline  - think of this as 'disaster recovery' for re encoding everything for the DVD ie recreate the entire DVD structure

2.  Encode - will re-encode the VOB indicated, if a movie goes over more than VOB then the message will appear again. Use for recreating that paticular VOB if it has a problem in playback.

3. Use - will reuse the existing VOB already created in the first or subsequent burn run, may reappear if more than 1 VOB for the movie -  if the contents of the VOB have changed on the movie timeline then it will be re-encoded.

4.  Use All - will reuse all VOB's created where possible - if you have made changes to the menu or the movie then it will be re-encoded.

5. Rewrite options - forces a re-encode of the options selected in any combination with the above - you would use these if the menu / navigation fails to work on the finished DVD.

On a personal note I always use Encode All + both rewrite options checked.

HTH

John

Modificado por última vez por johnebaker el 12/09/2013, 22:11 Horas, modificaciones en total: 1

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 24H2 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.

harrismith escrito el 13.09.PM a las 16:37 horas

Many thanks for your comprehensive explanation. I sort of understand now!
The only problem is that this is the ‘first’ time that I am attempting to burn a DVD!
It might be that the disc I am using is not empty as I have had a few aborted attempts using the same disc. Is this a possibility?
Anyhow, with a new disc inserted I followed your advice and used Encode All + both rewrite options checked, and the burn started seemingly OK.
But after cut 2 of 7,  the burn was aborted due to ‘internal error while processing’.
So I had a look at the log file an found:


Step 1 of 7, Encoding movie 1 ...
Step 1 done
Step 2 of 7, Encoding movie 2 ...
Step 2 done
ERROR: PrepareDVDVideoFiles() failed with errNo 39 - cannot add menu to authoring image
!!! DBK error in BurnProject: 2 - unspecified failure !!!

This has been the case with all my attempts to burn. Do you have any ideas what I might be doing wrong? I hope so because I'm at my wits end!

johnebaker escrito el 13.09.PM a las 19:42 horas

Hi

. . . . I have had a few aborted attempts using the same disc . . . .

That is the cause of the Encode All etc message you are getting - the movie has already been rendered and the DVD structure set up.  The next stage, which is where your problem is, in the burning of the DVD files to the disc.

. . . . It might be that the disc I am using is not empty as I have had a few aborted attempts using the same disc. Is this a possibility? . . . 

Highly likely.

. . . . ERROR: PrepareDVDVideoFiles() failed with errNo 39 - cannot add menu to authoring image . . .

Try changing the menu template to see if you can complete the burn - some templates have been known in the past to cause this issue.

Check if your MEP is patched up to date.

To save wasted discs I always do my initial burns to DVD-RW or BD-RE discs - if there is a problem or I spot changes needed to the video then I have not wasted a disc - I just erase the disc and start again.

Once I have a good burn and the movie is correct then I copy the rewriteable to DVD-R or BD-R disc - I do not use MEP to write the final disc.

HTH

John

 

Modificado por última vez por johnebaker el 13/09/2013, 19:43 Horas, modificaciones en total: 2

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 24H2 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.

Arthur-LW escrito el 15.09.AM a las 10:43 horas

I may be spouting heresy here, but after my MEP created its first coaster I stopped letting it do my burning and went with Nero and always let MEP create a disc image onto hard drive first.  Nero has always been the burn software of choice for many, and these days it's not good for a whole lot else, though it works flawlessly for burning (just an aside here).  In fact, when you tell it to check data after burning and it tells you there were errors found, then (assuming you are using quality discs like Verbatim) it probably means your burner is going south.

And by the way, it's always desirable to have both Nero and MEP check data, as things can sometimes go wrong.  If MEP says it successfully completed burning (to HD) then you are good to go with your burning tool.  A trick johnebaker taught me was to have a dual-layer empty disc in the DVD burner (assuming a movie that requires more space than a single-layer disc can hold).  Then in the Burner selection at the top when you change from Image recorder to the DVD drive it will show some white space on the  used-space indicator.(as long as you don't go over the capacity of a DL DVD, that is).  Just be sure to remember to change it back to Image recorder before you begin the burn process.

Here is where things can get tricky.  If your used-space indicator says your compilation won't fit even on a DL disc you can adjust the bit rate or leave it alone and see if MEP makes it ok or if it chokes.  It may go all the way, or it may report there was an error saving to hard drive.  Me?  I always set it for the maximum quality (9724) by default, but if the used space indicator shows to be over the limit of the disc then I back off the 9724 to 9700 and don't worry if the compilation is still too big for the disc.  Once I learned this trick of going down to 9700, MEP stopped showing burn errors at the end of the burn process.

Sometimes even though MEP says you are needing more space than the disc can hold, it may end up leaving some blank space on the disc anyway (something like 7.65 Gb used).  Other times, for some strange reason, it will end up with a compilation that truly is bigger than a DL can hold.  In this case I use DVD Shrink to back it up to a separate folder on the hard drive that I name [movie title]-shrunk.  It works perfectly and can determine the percentage of shrink needed to fit it on the disc (sometimes just one or two percent) is needed).

DVD Shrink is freeware and can be acquired here:  http://www.majorgeeks.com/files/details/dvd_shrink.html

Just FYI:  Beware of the "official" DVD Shrink site. It is full of traps.

Arthur-LW escrito el 19.09.PM a las 14:26 horas

Using - Magix Movie Edit Pro 2013 on Windows 8.

My Samsung DVD Burner is recognised in Device Manager and appears as an option in the Magix  'Burning' dialogue box. So Far so good.

The Disc format selected is 'Standard PAL'

When I hit the 'Burn' button I am asked if the existing VTS.VOB file/s should be used and I haven't a clue!

Not sure if this applies in your case, but when I see this message it is because MEP started to burn to disc instead of to hard drive, this being due to the fact that I forgot to change from my optical drive to Image recorder in the Burner selection.  MEP had already begun to create a folder in its
"C:\Users\[Your Name]\Documents\MAGIX\Movie_Edit_Pro_MX_Plus_Download_Version\Disc Images" folder.
I find if I just delete the folder just created and start over MEP breezes right through into creating an image onto the hard drive.  HTH

johnebaker escrito el 05.10.PM a las 18:05 horas

Hi

@Arthur-LW

. . . . In fact, when you tell it to check data after burning and it tells you there were errors found, then (assuming you are using quality discs like Verbatim) it probably means your burner is going south. . . . 

Not necessarily - you nearly always get errors on discs for various reasons eg bad data blocks, imperfect dye spots etc.

The disc structure and the softwares method of writing can 'fix' most of the errors - when it can't then you get a bad disc error.

Consider how a well used disc still plays despite hundreds of fine scratches on the surface.

Signs that . . . . your burner is going south . . . are:

     - Not recognising brand new discs when it did before - although this can be agravated by using the disc manufacturer changing dyes and the burner has not got the settings for the dye used - usually requires a firmware update .

     - Fresh burned discs becoming unplayable in other players - usually due to the burner optical head going out of alignment through wear and tear.

John

Modificado por última vez por johnebaker el 05/10/2013, 18:06 Horas, modificaciones en total: 2

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 24H2 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.

Arthur-LW escrito el 05.10.PM a las 21:07 horas

Hi

@Arthur-LW

. . . . In fact, when you tell it to check data after burning and it tells you there were errors found, then (assuming you are using quality discs like Verbatim) it probably means your burner is going south. . . . 

Not necessarily - you nearly always get errors on discs for various reasons eg bad data blocks, imperfect dye spots etc.

John

All I can go by is what the disc checker tells me, John.  Nero has proven to be flawless (at least when it comes to burning discs anyway).  I've only had two Verbatim discs ever show bad data checks.  When I tested the discs themselves with a disc checker it reported they were 100% with no bad sectors, etc. whatsoever.  When I flung the burner in the recycle bin and replaced it with a new one, guess what?  Flawless burns without a single error from then on.

There simply isn't any reason to live with discs that do not come from the factory totally 100%.  It's doable.  I had one Verbatim I thought was bad and they quickly mailed me out a replacement without a peep.  It was only later that the burner quit entirely, and I was able to look back in hindsight to see it was the burner hardware that was on the way out that caused the bad data check, not the disc. 

When I get that sort of treatment from a company, you can bet they have my loyalty for life.   

Extreme escrito el 25.07.AM a las 10:13 horas

Good day, I am using Magix Edit Pro 2013 and have a project that needs to be burned to a 8.5 disc. The project is only 7707MB and leaves 444MB free on disc, however when I press burn it tells me there is not anuff space! please can someone advice me on what to do.

Thanks...

jak.willis escrito el 06.12.AM a las 07:15 horas

Good day, I am using Magix Edit Pro 2013 and have a project that needs to be burned to a 8.5 disc. The project is only 7707MB and leaves 444MB free on disc, however when I press burn it tells me there is not anuff space! please can someone advice me on what to do.

Thanks...

I have been experiencing this same problem lately and it is very annoying! Did you ever find the reason and a fix?

emmrecs escrito el 06.12.AM a las 11:25 horas

@jak.willis

This is a very old thread, referring to a very old version of MEP! Can I suggest you start a new thread, with specific details of exactly what problems you are experiencing?

Thank you.

Jeff
Forum Moderator

Win 11 Pro 64 bit, Intel i7 14700, 32 GB RAM, NVidia RTX 4060 and Intel UHD770 Graphics, Audient EVO 16 audio interface, VPX, MEP, Music Maker, Vegas Pro, PhotoStory Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam