Authoring - AVStoDVD fails at 95% to complete

[Mark97213]

AVStoDVD is such a great program, it's frustrating when it can't complete a project. I have tried several times, with as many different settings, to try and complete a project but each time, the end result is the same; AVStoDVD stops at 95% completion. However, I can run the project in ConvertXtoDVD and all goes well except it lacks the Menu capabilities that AVStoDVD has.

What could ConvertXtoDVD be completing that AVStoDVD does not want to complete?

Attached is the log from the last uncompleted project run through AVStoDVD:

[zoobie]

there's a avs2dvd thread here somewhere...the author may be able to help you
offhand, it sounds like one of the files is corrupt

[_MrC_]

@Mark97213

could you please post the BatchMux log file:

BatchMux log file <C:\Documents and Settings\End User\Desktop\Gum Sing Teason 1\Gum Sing Teason 1 Episodes 1-10 of 30\Gum Sing Teason 1 Episodes 1-10 of 30_0_BatchMux.log>



Bye

[Mark97213]

Apparently, this is all the BatchMux log contained:

Segment memory resources --> RELEASED
Local Stack memory --> RELEASED
File i/o structures --> DEALLOCATED

[davexnet]

Check out this thread. Some dude received the same error and it was due to some bad blocks (write error) on his HDD.
Have you tried running a disk check ?

http://forums.afterdawn.com/t.cfm/f-126/avstodvd_muxman_problem-881704/

[Mark97213]

I ran chkdsk and all seemed well. I'm really at a loss for this. I re-ran the project and again, the completion stops at 95%.

Batchmux log just contains nothing but what I previously wrote.

Any ideas?

[zoobie]

Using a dvd-rw, I'd start removing the clips towards the end one by one and see if it completes the operation. This is often the only way to determine what it's hitting when it stops.

[Mark97213]

I think I'll just abandon AVStoDVD and utilize a different Authoring program. When I have problems with AVStoDVD, I generally use ConvertXtoDVD which is successful 100% of the time BUT, it lacks Menu building capabilities.

Any recommendations for another all-in-one converter with two pass encoding capability that also has Menu building capabilities that they've have success with?

[davexnet]

Perhaps give AVI2DVD a try:
http://www.trustfm.net/divx/SoftwareAvi2Dvd.php?b2=1

Just out of interest, I noticed the version of muxman.exe included in AVStoDVD is version 15,
while the version available for download from videohelp.com/tools is 16.8.

I gave it a try (just replaced the version in \program files\avstodvd\muxman)
and it seems to work, however, I've got no idea why MrC left in the old version -
there may be a good reason.

[Mark97213]

I switched from .15 to the .16 version into the Muxman folder. Something curious; in the Muxman folder, there is also Batchmux 1.3 which says it's intended for Muxman .16, yet as you said, only .15 comes with AVStoDVD. I'll try another project with the .16 upgrade ans see how it goes.

[davexnet]

OK sounds good, hopefully if it's going to fail again, you'll get a better muxman.log than you got before.

[Mark97213]

Well, same result, stops at 95% completion. And I can't figure out why I get almost nothing in the Batchmux log:
Segment memory resources --> RELEASED
Local Stack memory --> RELEASED
File i/o structures --> DEALLOCATED

This just doesn't make sense.

[_MrC_]

@Mark97213

have you tried using another hard drive as output destination?



Bye

[davexnet]

Mark, have you made sure to deselect "delete temporary DVD assets files" and "delete AVStoDVD working files".
With these deselected, I get a file with a name like "DVD_2_MuxMan.log" in the A2D temp folder. Do you get this?

[Mark97213]

SUCCESS! Creating a Output folder in my 2nd HD seemed to do the trick as I have a 100% completion. Am curious as to why I couldn't use the working HD. Thank you Dave and MrC. I feel like I just rebuilt a mainframe!

[Mark97213]

Dave, yes, I did. I tried both deleting and keeping but I just couldn't get anything more in the log. Must be something I have configured elsewhere which is incompatible.

[davexnet]

Very interesting - I've used to do it on the main drive, never had a problem like this.
I find having the assets on one drive and author to another runs much faster at that step.

Glad to hear it's fixed!