dvdlab compile.aux error

Discussion in 'Video to DVD' started by leechness, Jul 25, 2006.

  1. leechness

    leechness Member

    Joined:
    Jul 25, 2006
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    11
    okay so i have made an avi file into m2v and mp2 files using tmpgenc using the same template i always use to successfully make my dvd's. However this time i get this "Runtime C++ Compile.aux error" from dvdlab. Doint the dummy test compile seems fine, but when doing an actual mux, it gets hung up while placing navigation menu. I know its ironic to think its not my nav links, but the fact is that i have already tried to redo the whole project in dvdlab creating new links and new chapters. I still get the same error at the same spot. Also tried freeing up space on HD which i have well enough to work with (30Gigs). File system is NTFS. Tried uninstalling and re-installing the dvdlab. I can't seem to find what the problem is since dvdlab has quite a poor support of telling why the error occured in this situation. If anyone found a solution for this i would be utmost gratefull for some tips.

    Thankx in advance.
     
  2. leechness

    leechness Member

    Joined:
    Jul 25, 2006
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    11
    well i found out that it has something to do with the audio track. I still can't figure it out, but narrowed the issue down to the audio track since it compiles fine without the audio, or using other audio tracks in place of its orginal. Strange enough as it sounds the audio is without a doubt 48000kh 5.1 as it orginally came with the avi file. I tried the Mp2 file which was encoded with the avi into m2v. That didn't work. I tried the original ac3 48000kh file being directly demuxed from the avi itself and still refused to work. I begin to wonder if its because the video is originally a two part and joined that is causing this odd error or whatnot, but i have done a joint before without this error before going about the same exact method i have done this time around. I have recoded this audio back and forth from mp2,mpa,ac3,lcpm wav, all at 48000kh and none seems to work at all.


    okay so i found the edit button.

    At anyrate for the rest of the folks out there who runs into this issue or those who already has and have not yet found an answer to this i will tell how i got passed this issue. It may or may not work for everyones situation, but it did for me so ill just put it out there.

    At first i really thought it was my audio since it was able to compile all the way through without the audio file. But then when i took the two halves and encoded them seperately and insterted them into dvdlab, i noticed that one of my encoded streams had 0-gop and the other has the actual time frame for gop (which should be correct). How or why that happend i have no clue, it must have been done during the avi was being split by the encoder or avi splitter, or it just doesnt like my setting of gop in tmpgenc (accidently setup my pframe to 8 instead of 5).
    Anyway, i found and used "womble video wizard". I didn't need it to re encode the file or any of that nature, but simply to use its "GOP fixing tool"; the "re-write GOP" tool that comes in dvdlab did not fix the problem.
    After getting it fixed with Wombles video Wiz, the mpeg file now has opened GOP instead of closed GOP (too bad theres no way around that. Maybe its a bug or something the programmer just didnt care to introduce into this program), but that matters not. DVDLab can complain all it wants about that, it hurts nothing at all.
    Now that GOP has been fixed, DVDLab Pro compiles all the way through like a charm. Hope this helps someone out there as well.

    oh and to use Wombles Mpeg Wizard's GOP fixer:
    import the mpg/m2v/mpv video file into the program.
    From the menu bar (might be dislocated from the main interface) and click Tools->MPEG GOP Fixer. choose the third option down "fix GOP size errors for DVD GOP size compliance ( read + encode + write )". Although i doubt it really does the encode part since it went super fast and the quality pretty much stayed the same.

    Now as far as why dvdlab didnt complain about that or why it didnt report that GOP was the issue here. I have no idea, maybe someone else can explain this situation to us all.
     
    Last edited: Jul 26, 2006

Share This Page