VideoHelp Forum




+ Reply to Thread
Results 1 to 3 of 3
  1. Member PBear's Avatar
    Join Date
    Sep 2002
    Location
    San Francisco Bay Area
    Search Comp PM
    Possible bug report (using v2.5.3300 in Vista):

    Was going crazy last night trying to compile a job and constantly getting the following (highly uninformative, it turns out) message and crash 80-90% into the "encoding title set" phase:

    Code:
    Version: SVCD2DVD 2.5
    Build: 2.5.3300.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(xc76139390a97debb xd2637df501625a82, x81974c36d7fdf1e1 xb4ee5c1758e9e983, Int32 xdc4f66b5011a3c9d, String[] x738d70b20493db82, Boolean x6b20cb17e8070d92, Boolean x3c21da9f928aac10)
       at x3284ccece41ee22b.xd3764d4f1e921081.x2e6504f39decc498()
       at x3284ccece41ee22b.xd3764d4f1e921081.xf81783e1b359ffc3()
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    I finally figured out that the problem was a combination of MPEG assets, copied from an SVCD, placed in a single VTS, some with dual-audio and some without.

    The original SVCD had four DAT files, two for the movie and two for extras. The movie has a second, commentary track, the extras have only a single audio track (the audio characteristics - frequency, bitrate, &c - of all the tracks would be identical, since all the assets were converted by SVCD2DVD before-hand to S2D files, yet the program would crash whenever trying to mux the single-audio assets into the VOB after successfully doing the dual-audio assets).

    Don't know if this is a bug or by design but, as soon as I separated out the extras into a separate VTS, the job compiled fine. If it's by design (or by nature of title set requirements), then the program should reject any non-compatible assets when the user tries to drag them into an already-populated VTS, shouldn't it?
    Quote Quote  
  2. Member ChrissyBoy's Avatar
    Join Date
    Feb 2003
    Location
    Yorkshire!
    Search Comp PM
    Your right - it should. I will look into this. To aid me - can you post the log of the run which caused the crash please?
    SVCD2DVD v2.5, AVI/MPEG/HDTV/AviSynth/h264->DVD, PAL->NTSC conversion.
    VOB2MPG PRO, Extract mpegs from your DVDs - with you in control!
    Quote Quote  
  3. Member PBear's Avatar
    Join Date
    Sep 2002
    Location
    San Francisco Bay Area
    Search Comp PM
    I couldn't figure out which log files pertained (I have about two dozen from yesterday), so I recreated the job tonight and here it is.

    Funny thing is, even though the crash occurs about 90% into the "Creating Title Set #1" procedure, the VTS_01 VOB files seem to be created successfully (the last one looks complete, through the end of the fourth input file), but the program crashes after that and before the menus (VIDEO_TS.VOB) can be created. Won't happen if I take the second two files with the single audio tracks out and put them in a different title set.

    svcd2dvdlog-20071110192035.txt
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!