Muxman version 0.12 released

[SeeMoreDigital]

It's already possible to use Muxman to add/join multiple de-muxed .m2v and .ac3 streams (from .vob files) into a single stream


Cheers

[mpucoder]

What your other programs are seeing is the end_of_sequence that appears after each video file. If each file does not have an end_of_sequence, one is added otherwise the video verifier reports an error (due to the unexpected jump in the GOP timecode).

Since the stated purpose of Muxman is to make DVDs, this means it is not a bug.

If you want to join video files together for another program you should be using a video editor. They are designed to produce an entirely new sequence.

[Jeffster]

Thanks for the explanation.

[Gusy]

what kind of bitmaps does muxman support when using .sst files? I've been using 4 bit BMPs but it would be nice if I could use other kind of bitmap (higher palette BMPs or file types).

[mpucoder]

4-bit rgb or rle, Windows or OS2 format. Other color depths could have been supported, but I saw little sense in that since they get reduced to 4 colors.

[Trahald]

Originally posted by mpucoder
What your other programs are seeing is the end_of_sequence that appears after each video file. If each file does not have an end_of_sequence, one is added otherwise the video verifier reports an error (due to the unexpected jump in the GOP timecode).

Since the stated purpose of Muxman is to make DVDs, this means it is not a bug.

If you want to join video files together for another program you should be using a video editor. They are designed to produce an entirely new sequence.

with the install of batchencodem2v i have it comes with revpulldown.exe i modified from pulldown and it has a flag -ignoresequenceendcode which will remove all endcodes and add one to the end. (rev)pulldown naturally redoes timecodes which will help also.

[CoNS]

mpucoder, what do you think about my suggestions about importing subtitle colours from ifo (like ReJig does, very useful feature), and setting forced subtitle and/or audio stream?

[katjarella]

Dear mpucoder,
something is wrong with your chapter assignment. After multiplexing, the target chapters don't match the source chapters. And yes, I checked the MPEG for the presence of I frames at those places.

   Original,IfoEdit,DVDMaestro     |         Muxman 0.12/0.13pa         |  Muxman Scene List
[Pos: 00:00:07.07] [Frames: 182]   | [Pos: 00:00:07.07] [Frames: 182]   | Scene Time=00:00:07:07
                                   |       ***                          | 
[Pos: 00:20:33.11] [Frames: 30836] | [Pos: 00:20:33.11] [Frames: 30836] | Scene Time=00:20:33:11
[Pos: 00:22:14.18] [Frames: 33368] | [Pos: 00:22:15.08] [Frames: 33383] | Scene Time=00:22:14:18
[Pos: 00:29:26.12] [Frames: 44162] | [Pos: 00:29:26.12] [Frames: 44162] | Scene Time=00:29:26:12
                                   |         ***                        | 
[Pos: 00:44:02.09] [Frames: 66059] | [Pos: 00:44:02.09] [Frames: 66059] | Scene Time=00:44:02:09
[Pos: 00:50:13.02] [Frames: 75327] | [Pos: 00:50:13.17] [Frames: 75342] | Scene Time=00:50:13:02
[Pos: 00:54:17.22] [Frames: 81447] | [Pos: 00:54:17.22] [Frames: 81447] | Scene Time=00:54:17:22

I repeated this test several times, and almost always got different results.

Furthermore, sometimes the duration is parsed improperly during import. Could it be possible to change the handling to frames, or add the possibility to manually enter a frame count?

Thanks Katjarella

[mpucoder]

The accuracy of chapter placement has been on my todo list at a low priority for some time now. Chapters can start only at a new VOBU, and currently the VOBU planning logic does not take into account desired chapter points when deciding which gops go where. More than likely the desired I frame is in the middle of the preceeding VOBU.

Duration is very sensitive to a statement that preceeds it, the standard declaration. As another user found out the hard way, syntax is very important (to all statements, but this one is hard to catch). The statement must read:
Standard=PAL
without any spaces to be interpretted correctly, otherwise NTSC is assumed. The statement affects parsing only, as it is overridden later by the file properties. This is what makes it hard to notice, as the final product will say PAL if PAL sources were used.

edit: also wanted to make clear that at this time duration cannot be used to shorten motion video, it's only use is to hold video.

[CoNS]

A possible bug in MuxMan beta 0.12d:

I've used MuxMan about a dozen times now, with great results. Very fast and reliable tool. Only, on this last disc I tried, the subtitle stream is somehow not included in the output. I've tried twice, no luck.

It's a plain and simple case, like the other ones I tried: A single NTSC video file, one audio stream and one subtitle stream. The video and audio stream is demuxed from an original disc using PgcDemux, from which I also import celltimes. The subtitle stream is custom made by me. MuxMan checks "LB" for the video stream, and I select "LB" and "Wide" for my subtitle stream and of course specify language etc.

When I play the output in my software player (MPC), the subtitle stream is selectable in the navigation, but no suppic is displayed. At first I thought it was because of a wrong vertical positioning setting in my subtitle creation tool (SubtitleCreator by Paddington), but I've created hundreds of subtitles before this one with the exact same settings. I've checked that the subs I'm using are not out of sync. I've also checked that the .sup file created by SC actually does contain the bitmap subs as it should.

And when I try to demux the output created by MuxMan using PgcDemux, I tells me that there're no subtitle streams present, which is why I suspect MuxMan causing the problem.

One thing is different from all the other discs I've muxed using MuxMan: My audio stream is a .mpa file (MPEG, DD2.0), and thus the original disc and MuxMan places the stream as #C0, not #80. All the other discs I've muxed in MuxMan have had ac3 audio. Could this be causing the problem?

mpucoder, please let me know if you need any further info. In the meanwhile I'll try muxing it with IfoEdit and check if the subs are there...

BTW, mpucoder, whaddayathink of my suggestion about adding support for import of ifo colours? And perhaps a setSTN precommand?

[mpucoder]

I just tried an .mpa and .sup and the subs do disappear, so there is a bug (most likely, since .mpa and subs share a common header, that the subs are in the wrong stream)

All the stuff you are waiting for is coming, pre-release 0.13 imports colors the Scenarist way - ie by the .scp or .mxp files. Commands, navigation, highlight is all in the works, but requires replacing the canned ifo file generator with a compiler.

[CoNS]

Yep, my subs work with IfoEdit...

About import of subtitle colours: I don't have experience with Scenarist. Is it going to work like ReJig (and SubtitleCreator), where you can simply point to an .ifo file, and the program will read and use the subtitle colours from it? This way works very well in the aforesaid programs, I think.

EDIT: Is the prerelease of v0.13 available at the present time?

[mpucoder]

The colors get set by modifying the DefaultPalette. In mxp it looks like this:

Section=Settings
{
	Item=Palette
	{
		Name=DefaultPalette
		Color 0=0, 0, 255
		Color 1=255, 0, 0
		Color 2=0, 0, 0
		Color 3=255, 255, 255
		Color 4=0, 255, 0
		Color 5=255, 0, 255
		Color 6=255, 255, 0
		Color 7=0, 125, 125
		Color 8=125, 125, 125
		Color 9=225, 225, 225
		Color 10=125, 0, 0
		Color 11=0, 125, 0
		Color 12=0, 0, 125
		Color 13=222, 0, 255
		Color 14=222, 125, 0
		Color 15=125, 0, 125
	}
}

Pre-releases are available to members of my forum. 0.13 will be released on Monday.

Version 0.12e fixes the problem with mpeg audio and subpictures along with a fix to 4:3 video attributes (they were not spec, but DVD players don't check)
Available at the Muxman homepage

[buzzqw]

i had a problem too .. with subtitles

till 0.12b i used to vsrip subtitles, then with vsconv transform this idx/sub in a sst file and many bmp.

but with the change of 05/03/04 (0.12c) "conversion rules are now working in sst files"

my subtitles isn't visible. i suppose it get muxed ( i can see this in muxman log) but i cannot see more

i use vsrip/vsconv bundled with latest scenaid (1.5.0.20)

here the muxman log:

MuxMan version 0.12e
Opened script file D:\dvdmagic\zdvd.mxp
Accepted video d:\dvdmagic\movie_dvd.m2v size = 177620896
Accepted audio d:\dvdmagic\audio.ac3
Opened sub 1 file d:\dvdmagic\ita.sst.
Pixel_Area values 0 573 are incorrect, using default of 0 572.
09:28:22 Begin multiplex.
Maximum audio duration 28480 fields.
new graphics buffer size 414720.
09:28:23 starting video file number 1.
SeqEnd at A96479C.
Bytes remaining in buffer = 0.
09:28:52 End multiplex.
Bitrate - avg: 5300631, min: 3304106 (lba 59158), max: 8028160 (lba 58864).
Shortest GOP has 14 fields, longest GOP has 30 fields.
Fields: 14202, VOBU: 475, Sectors: 91894.

here is the start of my sst file

st_format 2
Display_Start non_forced
TV_Type PAL
Tape_Type NON_DROP
Pixel_Area (0 573)
Directory D:\dvdmagic
Subtitle ita
Display_Area (0 2 719 574)
Contrast (15 15 15 0)

PA (0 0 255 === )
E1 (255 0 0 === )
E2 (0 0 0 === )
BG (255 255 255 === )

SP_NUMBER START END FILE_NAME
Color (14 15 16 13)
Contrast (0 0 0 0)
0001 00:00:00:04 00:00:00:05 ita_0001_v001_c001.bmp
Contrast (15 15 15 0)
0002 00:00:01:24 00:00:04:13 ita_0002_v001_c001.bmp
0003 00:00:04:18 00:00:07:18 ita_0003_v001_c001.bmp
0004 00:00:07:23 00:00:10:07 ita_0004_v001_c001.bmp

Thanks

BHH

[mpucoder]

This is a common syntax error with many rippers, SubRip and vsrip among them. And it wouldn't work right in Scenarist, either. The conversion rules, which are the relational operators following the color values, must be seperated by a blank. ie

PA (0 0 255 === )
E1 (255 0 0 === )
E2 (0 0 0 === )
BG (255 255 255 === )

should be

PA (0 0 255 = = = )
E1 (255 0 0 = = = )
E2 (0 0 0 = = = )
BG (255 255 255 = = = )

This is so common that Muxman includes a statement to tell it what generated the sst file. In version 0.12 only SubRip1.17.1 is recognized, and the syntax and logical errors corrected. Version 0.13 will also recognize vsrip and treat each character as a new rule.

[buzzqw]

A big Thanks !!!

BHH

EDIT : will muxman autodetect/autocorrect this error or user must place somewhere in sst a note as for SubRip:"To correct for this, add the following line in your sst file as the second line:
Generator SubRip1.17.1 25257" ?

I hope for an automatic solution...

tahnks anyway

BHH

[mpucoder]

In 0.13 if you add "Generator vsrip" the conversion rules without spaces will work. I really would like all the sub ripping programs to correct these and other errors, though, as these scripts DO NOT work unmodified with Scenarist.

[buzzqw]

D3s7 has corrected vsconv !!!

http://forum.doom9.org/showthread.ph...844#post630844

now vsconv create a correct sst file (watch down in post)

would be possibile (in command line mode and gui) order to muxman from what ifo must copy subs color (if isn't to much to ask) ?

Great work Mpucoder ! thanks to you and D3s7 !

BHH



st_format 2
Display_Start non_forced
TV_Type PAL
Tape_Type NON_DROP
Pixel_Area (0 573)
Directory d:\dvdmagic
Subtitle 2
Display_Area (0 2 719 574)
Contrast (15 15 15 0)

PA (0 0 255 = = = )
E1 (255 0 0 = = = )
E2 (0 0 0 = = = )
BG (255 255 255 = = = )

SP_NUMBER START END FILE_NAME
Color (14 15 16 13)
Contrast (0 0 0 0)
0001 00:00:00:04 00:00:00:05 2_0001_v001_c001.bmp
Contrast (15 15 15 0)
0002 00:00:01:24 00:00:04:13 2_0002_v001_c001.bmp