| User review:
|
This is a wonderful utility with an annoying bug (which does have work-arounds) which I'll report here for future reference. Hopefully mpucoder will spot and correct this in a future version.
In certain conditions there seems to be a problem with MuxMan's *vertical* (not horizontal) boundary checking which gets it into buffer under/overflow situations.
These conditions seem to be related to ab/presence of titleset menus and chapter buttons; there may well be others too. These conditions seem to determine which part of the MuxMan code checks and parses the subtitles, and not all parts seem to work equally well.
Input files used below have the following characteristics (initially, the source DV AVI container was encoded into an MPEG container with both audio and video to maintain sync, which were then demuxed into the below video file and audio file with AVIdemux):
Video file parameters:
File size: 63,404,529 bytes
Duration 00:01:08.55
Aspect ratio 4:3
MPEG2 720x576 25.000 fps 9800.0 kbps (1225.0 kbyte/s)
Audio file parameters:
File size: 1,107,456 bytes
Duration: 00:01:09.21
Format: AC3 stereo 48.000 kHz
Data rate: 128 kbits/sec
Subtitle file parameters:
.SST file and BMPs as rendered by MaestroSBT, 3 colours used, BMPs are correctly rendered 720 x 573 pixels x 4 bits/pixel files
.SUP file containing same subtitles as SST, rendered by Srt2Sup/Txt2Sup makes no difference
Multiplexing 1 movie file, 1 audio file and 1 subtitle file in either SUP or SST format with no titleset menu works correctly. Adding an empty titleset menu to this project still works, still with either subtitle format. Adding chapter buttons to the titleset menu (still using exactly the same SST subtitles as before) causes MuxMan to fail with the message:
SPU error, C:Documents and SettingsfvisagieMy DocumentsMy VideosHome Videos20061218 NamibiaSubtitlesTestMovie.avi.dv_datecodeBottomMixed_0001.bmp, encoded line exceeds 1440 bits.
SPU error, C:Documents and SettingsfvisagieMy DocumentsMy VideosHome Videos20061218 NamibiaSubtitlesTestMovie.avi.dv_datecodeBottomMixed_0001.bmp, encoded line exceeds 1440 bits.
Normally, this message would be issued for horizontal buffer overflow (too wide or too much colour depth in subtitle file) in other conditions. However, the BMPs are known to be correctly rendered as proven by successful multiplexing in the absence of chapter buttons and/or titleset menu. The BMP mentioned in the error message is the first of the subtitle bitmaps listed in the .SST file.
With chapter buttons in the titleset menu but using SUP subtitles instead, multiplexing succeeds.
Next, rendering the SST subtitles _incorrectly_ as 720 x 574 pixels x 4 bits/pixel BMPs, results in the .SST file specifying (for the physical BMPs):
Display_Area (0 2 719 575)
muxman.mxp still contains (as per the subtitle specification):
Display Area=0,2,719,574
Which differs from the physical BMP size of 720 x 574.
Using the same project with titleset menu and chapter buttons which failed with SST subtitles before, MuxMan now notices the above discrepancy and behaves a little more carefully - from muxman.log:
Pixel_Area values 0 573 are incorrect, using default of 0 572.
Display_Area Y values 2 575 are incorrect, using default of 2 574.
This results in MuxMan itself "clipping" the BMPs back to 720 x 573 during multiplexing, and all is well!
So the work-arounds for projects with titleset menus containing chapter buttons are:
* Use SUP subtitles if those work for you; otherwise
* If you require SST subtitles, create (and specify in the .SST file) BMPs that are 1 pixel too tall and let MuxMan sort it out from there. |
