Menu

#468 Bad w64 file from HD Stream Extractor tool?

closed
nobody
None
5
2010-12-02
2009-07-21
Anonymous
No

Thanks for a great app! I came across a critical issue that I think may be a bug with MeGUI.

I go under Tools and use the HD Stream Extractor and set the output to type w64. The source audio is DTS-HD MA in a m2ts stream. It seems to extract the w64 file just fine. However when I go to remux this file with tsMuxeR, tsMuxer gets about 25% of the way through and then starts giving this error: LPCM bad frame detected resync stream. It then just gets stuck here and keeps showing this error over and over until I cancel it.

I have tried this with several titles that have DTS HD MA and in each case it fails with the same error, although for some titles it gets further along in the process (such as 33%) before the error shows up. For each title the error spot is identical on each run.

The reason I think this may be a bug with MeGUI is because I can successfully use the same source m2ts file with the Clown BD app and have it generate w64 for the audio. Then if I take that w64 and remux it with tsMuxeR it runs just fine. There are no errors and the title plays as expected. If I understand correctly both Clown BD and MeGui both use eac3to to create the w64 file. Since the output from eac3to works when created through Clown BD I am therefore thinking (perhaps wrongly?) that this is likely a bug with MeGUI.

If I had to take a total guess I would say the issue may be that MeGUI is actually creating a .wav file, yet calling it a .w64. I say this because I can reproduce this error every time if I try to feed a .wav file into tsMuxeR whether that .wav file is created via Clown BD or MeGUI. So I am thinking that maybe MeGUI is giving me file named .w64 (and I ask for a w64) but it may not be really generating a w64 and generating a wav instead.

For reference I am using eac3to 3.1.6 (latest release). As for MeGUI I am running release version 0.3.1.1040 but cannot recall (but I know its one of the latest versions, if not the latest). Thank you for looking into this.

Discussion

  • Nobody/Anonymous

    Also I meant to add that the w64 files I am extracting are greater than 4GB. Since the size may matter in reproducing this I wanted to add this information to the notes. Thank you.

     
  • Zathor

    Zathor - 2010-03-28

    Thanks for the report. Moved to the bug reports - I will try to reproduce it.

     
  • Zathor

    Zathor - 2010-09-03
    • status: open --> pending
     
  • Zathor

    Zathor - 2010-09-03

    Tried it with the recent eac3to (3.24) and MeGUI (0.3.5.8) and had no problems with muxing the w64 file with tsmuxer. Therefore I assume that the problem is fixed.

     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 90 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending --> closed
     

Log in to post a comment.

MongoDB Logo MongoDB