Creation of DVD was not successful:

[mem01]

Firstly apologies, I know there are similar threads around with this type of error but my search did not turn up the exact same thing and I am afraid I am not knowledgeable enough in this specific area to diagnose if a similar problem would mean I could use a similar solution.

I have backed up a number of original DVDs using AnyDVD and CloneDVD Mobile (latest versions of both) typically using generic MP4 and keeping the native resolution. I have just one DVD which fails at every attempt and I cannot work out why

I have attached a screen shot of the error and a text file of the Details. I hope this is what someone will need to help me a little.

Many thanks in anticipation
Mark

[FurryGuy]

Asking for feedback

Looks like even more DVDs are having problems with creating MP4 files. You could upload an AnyDVD log file of the DVD to help the developers, though they are already working on a solution.

[Frank]

This error

>> ParseVideo, #672 : Garbage in input queue: 21 01 00 00
Location: ParseVideo, #675, V:78031, A:97540, S:0

won't get fixed in this version 1800 and has been a known problem for a while which is why we released several beta versions to improve the performance.

Some inches away from the new thread button you see this:

CloneDVD mobile 1.8.0.6 beta

http://sandbox.slysoft.com/beta/Setu...mobile1806.exe

So please get that and give it spin. We will have the next update coming very soon I've been told.

[mem01]

Thanks I will give the beta a try and let you know.

[mem01]

Unfortunately it seems to have failed with the beta too so I let it send the report to Slysoft. I will just have to give up on that DVD for now

Thanks again for the help and I will try again when the next full release comes out.

[Frank]

The movie is HORRIBLE_BOSSES.

I see the log from Chameleon arrived so ....

This error has been identified previously so your DVD is just another with this strange authoring:

__ensure( C == 0x00000100 || C == 0x000001B3 || C == 0x000001B7 ) is in the log and this is being worked on.
Fernando tells me there is a good chance that the next engine update will fix this. We expect to release an update very soon.
Sorry for any inconvenience.

EDIT: 29 July - I've been informed the coming public release first week of August will address this.