Error in Build 5000

[ttyner]

I receive the following Error Message when attempting to process any file. Build 3600 worked just fine on this
machine: Two week old AMD Phenom 9850, 4 Gig Corsair memory, Windows XP PRO.
The following Error Message is from an attempt to process the last
mkv file that was processed with build 3600. I also tried an AVI with the same result.

The LOG file is 8.37 MB and appears too large to include


Version: SVCD2DVD 2.5
Build: 2.5.5000.0

Type: System.AccessViolationException

Source: SVCD2DVD

Message: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

InnerException:

StackTrace: at x3284ccece41ee22b.xd3764d4f1e921081.AuthorDVD(xc76 139390a97debb xd2637df501625a82, x81974c36d7fdf1e1 xb4ee5c1758e9e983, Int32 xdc4f66b5011a3c9d, String[] x738d70b20493db82, Boolean x6b20cb17e8070d92, Boolean x3c21da9f928aac10)
at x3284ccece41ee22b.xd3764d4f1e921081.x2e6504f39decc 498()
at x3284ccece41ee22b.xd3764d4f1e921081.xf81783e1b359f fc3()
at System.Threading.ThreadHelper.ThreadStart_Context( Object state)
at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

[silicon101]

Having noticed there was a new version, I "updated" to the latest build. It was an unfortunate decision on my part as now SVCD2DVD is unusable. I'm new to the forum as honestly the program has always worked. I would gladly revert to a prior version however I did not save an old installer and don't see where it can be downloaded. At this point I'd like to get SVD2DVD working again or see a new version released that is stable. FWIW, I'm running WinXP with all the latest updates including .NET.

Version: SVCD2DVD 2.5
Build: 2.5.5000.0

Type: System.AccessViolationException

Source: SVCD2DVD

Message: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

InnerException:

StackTrace: at x3284ccece41ee22b.xd3764d4f1e921081.AuthorDVD(xc76 139390a97debb xd2637df501625a82, x81974c36d7fdf1e1 xb4ee5c1758e9e983, Int32 xdc4f66b5011a3c9d, String[] x738d70b20493db82, Boolean x6b20cb17e8070d92, Boolean x3c21da9f928aac10)
at x3284ccece41ee22b.xd3764d4f1e921081.x2e6504f39decc 498()
at x3284ccece41ee22b.xd3764d4f1e921081.xf81783e1b359f fc3()
at x3284ccece41ee22b.xd3764d4f1e921081.x12cbe7a4e46ac 9ae()
at System.Threading.ThreadHelper.ThreadStart_Context( Object state)
at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

[ttyner]

Don't worry, Silicon; ChrissyBoy will take care of it and probably very promptly. He always has. He gives the best support in the computer world. Still, it's a good idea to save the installation file from the previous version before updating.

[ChrissyBoy]

The LOG file is 8.37 MB and appears too large to include

Can you zip it up and attach (or email me)?

Previous builds can be sent via email if you would like - just email me. However if there is an issue, it would be good to nail it!

[ttyner]

LOG file sent via e-mail. Also attached here

svcd2dvd_log.zip

[Parkerboi76]

I get a similar error message when I perform a 2 Pass encode.

However when I use the default settings which use a Single pass the program works fine without any errors.

This is the error message I get when 2 Pass is seleted is listed below,

Version: SVCD2DVD 2.5
Build: 2.5.5000.0

Type: System.AccessViolationException

Source: SVCD2DVD

Message: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

InnerException:

StackTrace: at x3284ccece41ee22b.xd3764d4f1e921081.AuthorDVD(xc76 139390a97debb xd2637df501625a82, x81974c36d7fdf1e1 xb4ee5c1758e9e983, Int32 xdc4f66b5011a3c9d, String[] x738d70b20493db82, Boolean x6b20cb17e8070d92, Boolean x3c21da9f928aac10)
at x3284ccece41ee22b.xd3764d4f1e921081.x2e6504f39decc 498()
at x3284ccece41ee22b.xd3764d4f1e921081.xf81783e1b359f fc3()
at x3284ccece41ee22b.xd3764d4f1e921081.x12cbe7a4e46ac 9ae()
at System.Threading.ThreadHelper.ThreadStart_Context( Object state)
at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

[silicon101]

If it matters, the above error I received was also generated using two pass encoding as that is what I use exclusively.

[ChrissyBoy]

Yes. This is a 2 pass issue... It has been an issue for several builds now and i will be removing the option as 2 pass isn't required anymore. Can you just uncheck the option for now and i will get a new build out as soon as i can.

[ttyner]

Will do. Thanks.
I have not had a problem in any of the previous builds
with two pass processing.

[Cool Breeze]

Yes. This is a 2 pass issue... It has been an issue for several builds now and i will be removing the option as 2 pass isn't required anymore.

Are you saying there is NO increase in quality using 2 pass encode? Is this because of improvements to ffmpeg? Have we been wasting our time selecting that option in previous builds, more specifically the last build?

I have not had a problem in any of the previous builds
with two pass processing.

X2

[silicon101]

I'm also curious as to the removal of two pass encoding as I use that exclusively. Previously I had noticed a difference between single and two pass, so may I now inquire why two pass encoding is no longer an option? Having used about every DVD authoring program out there, I honestly believe that SVCD2DVD consistly produced the very highest quality DVDs. Not to take this thread off topic but my main usage is the conversion of my HD recordings to SD homebrewed "superbit" DVDs. My entire reason for using SVCD2DVD is to acheive the highest picture quality possible so please understand my concerns regarding the removal of two-pass encoding as an option. I am glad to hear that the reason for the build 5000 error has been found but now I would like to hear more on this topic.

[ChrissyBoy]

Ok I have fixed this issue. I thought it was a repetition of an older problem with 2 pass encoding but in fact it was a bug introduced in the last build.

Build: 2.5010 resolves this issue.

As to 2 pass in general... I have left the option in place. If people are using the feature – then I makes no sense for me to remove it! However the whole point of 2 pass encoding is to distribute the bitrate more effectively. FFmpeg has improved its ability to do this on a single pass. Personally I can’t see any difference between 1 and 2 pass encoding (but I do wear glasses!)

As always – thanks to all for flagging this issue.

[ttyner]

Thanks for the prompt fix, ChrissyBoy.
But then you have taught me to expect such

[silicon101]

Chrissyboy,
Thank you!