PrepareDVDFiceoFiles () failed with errNo 5 - encoding failed

mike-h escrito el 10.06.AM a las 00:49 horas

I'm using Movie Edit Pro 2016 Plus. I have tried multiple times to fix this error. It always aborts while trying to encode movie 2. Part of the frustration is that I don't even know which of the 7 movies is number 2. Why can't the error message include the title of the movie? I have re-exporting each of the 7 movies I'm trying to include on the Blu-Ray disk to new .m2ts files and include them in the disk burning project. I have even replaced the disk template multiple times.

Here's the log of the latest attempt:

------------------------- 6/9/2017 3:00:34 PM --------------------------

6/9/2017 3:00:34 PM.442:   DLLAV32.DLL loaded, all entry points available
6/9/2017 3:00:34 PM.443:   AVSDK MsgCbFunc registered
6/9/2017 3:00:34 PM.443:   AVSDK: StatCbFunc registered
6/9/2017 3:00:34 PM.565:   AVSDK Version 13.0.244
6/9/2017 3:00:34 PM.566:   ------------ Reading Device Info ----------------
6/9/2017 3:00:34 PM.566:   AVSDK: 2 device(s) found
6/9/2017 3:00:34 PM.576:   BurnSupport: 2 device(s) found
6/9/2017 3:00:34 PM.584:   Adapter=1 ID=1 LUN=16   G:HL-DT-ST BD-RE BH10LS30 Revision:1.01
6/9/2017 3:00:34 PM.585:   Adapter=0 ID=1 LUN=0   F:ATAPI BD E DH12E3SH Revision:MAA2
6/9/2017 3:00:34 PM.585:   BurnSupport: 2 record device(s) available
6/9/2017 3:00:34 PM.586:   BurnSupport: G: HL-DT-ST BD-RE BH10LS30 Rev. 1.01
6/9/2017 3:00:34 PM.586:   BurnSupport: F: ATAPI BD E DH12E3SH Rev. MAA2
6/9/2017 3:00:34 PM.587:   ------------ done ----------------
6/9/2017 3:00:34 PM.762:   setting no speed limit
6/9/2017 3:00:34 PM.763:   !!! DBK error in CBurnDevSupport::InvalidateDiscInfo(): 16 - burn support - invalid device !!!
6/9/2017 3:00:37 PM.225:   AVSDK Message - ERROR: :Cannot get device/media specific information -> functionality is not provided by device or by system
6/9/2017 3:00:42 PM.844:   AVSDK Message - ERROR: :Cannot get device/media specific information -> functionality is not provided by device or by system
6/9/2017 3:04:49 PM.092:   setting no speed limit
6/9/2017 3:04:51 PM.558:   AVSDK Message - ERROR: :Cannot get device/media specific information -> functionality is not provided by device or by system
6/9/2017 3:05:37 PM.941:   setting no speed limit
6/9/2017 3:05:38 PM.010:   AVSDK Message - ERROR: :Cannot get device/media specific information -> functionality is not provided by device or by system
6/9/2017 3:05:56 PM.733:   AVSDK Message - ERROR: :Cannot get device/media specific information -> functionality is not provided by device or by system
6/9/2017 3:05:58 PM.842:   AVSDK Message - ERROR: :Cannot get device/media specific information -> functionality is not provided by device or by system
6/9/2017 3:05:58 PM.881:   Open Project: 2016_Travels_bluray -- bd project 2017-06-09
6/9/2017 3:05:58 PM.882:   VideoMode: NTSC   Temp Dir: D:\Hegedus Videos\2017 Video Files\
6/9/2017 3:05:58 PM.882:   dll version 6.0.10.20
6/9/2017 3:06:00 PM.356:   Step 1 of 17, Encoding movie 1 ...
6/9/2017 3:18:21 PM.818:   Step 1 done
6/9/2017 3:18:21 PM.826:   Step 2 of 17, Encoding movie 2 ...
6/9/2017 3:28:32 PM.286:   Step 2 done
6/9/2017 3:28:32 PM.289:   ERROR: PrepareDVDVideoFiles() failed with errNo 5 - encoding failed
6/9/2017 3:28:32 PM.289:   !!! DBK error in BurnProject: 10 - movie encoding failed !!!

Comentarios

johnebaker escrito el 10.06.AM a las 09:46 horas

Are you following this tutorial to create the multi movie project?

Isolating the problem movie and object is going to take a while.

Create a new project and import 1 of the exported movies into a new project.
Using the Image recorder option in the burn dialog - burn the project.
Repeat for the other exported movies until you find one that fails.

Once identified then you need to locate the object which is causing the problem

The quickest way is as follows:

Load the failing movie into a new project
Remove all objects in one half of the timeline.
Export the timeline to .mts
If there is no failure then clear the timeline and import the movie again
Remove the objects in the other half of the timeline
Export again to .mts
Repeat the halving process on the half of the timeline that fails.
Eventually you should find the section where the problem is.

HTH

John EB

mike-h escrito el 10.06.PM a las 20:45 horas

Thanks. That's one way to try to find the problem. But the root problem is that the error message generated by the s/w should report more info about the error. Why have to hunt and peck to find the problem? That's just the sign of poor software. I've been using Magix products for years and have burned more than 100 DVD and Blu-ray disks and have been happy. But this problem is frustrating.

johnebaker escrito el 10.06.PM a las 23:11 horas

. . . this problem is frustrating . . . . . . . Why have to hunt and peck to find the problem? . . . .

I agree, however the problem is not necessarily the software's fault - in this particular issue the softwae is obviousl OK with the movie 1 and has an issue with movie 2.

This would would indicate thatthere is an issue with movie 2 - ie it could an image or video object, which is from a source external to the program, that to all intents and purposes may appear OK when played or viewed in Windows, however when it requires recoding causes an issue.

. . . . That's just the sign of poor software. . . .

In general terms there are limitations on what can be logged, depending on factors such as the error reporting levels provided by third party modules which are incorporated into software and the Windows OS error reporting features, gaining an optimum balance between capabilities and logging requirements, keeping the soze of the software within reasonable bounds ie not ending up with bloatware, as has happened to some software, eg anti virus suites, in the past.

John EB

mike-h escrito el 15.06.AM a las 04:27 horas

mike-h escrito el 15.06.AM a las 04:29 horas

So now the problem GETS WORSE !! I finally, after 2 days of hunting and pecking, fixed movie 2. Now I'm trying to burn the Blu-ray disk with a project including the fixed movie 2 and I get the same error with movie 3. It's funny because this disk burning project succeeded in burning a disk a month ago, but I changed only the disk menu (none of the movie .m2ts files) and now I'm getting all these errors. This is frustrating.

And I'm sorry, but just because 3rd party s/w is used is no excuse for poor user support. You can always write to the log the context (i.e. name of the movie) before calling to the 3rd party s/w and can always trap the error returned for logging. That is 3 lines of code, not bloatware. Otherwise it's just poor s/w design.

johnebaker escrito el 15.06.AM a las 09:35 horas

. . . . but I changed only the disk menu . . .

What changes did you make to the disc menu?

This may also be related to an issue I am having - see this here and here.

John EB