Muxman version 0.12 released

mpucoder · 27th February 2005, 20:43

Available here
New features:
full support for field pictures
8 subpicture tracks
import Muxman or Scenarist project files (scripts)
export Muxman project files
batch mode / command line processing

katjarella · 27th February 2005, 21:53

Dear mpucoder,

unfortunately, something doesn't work with subtitles. The following error message appears:

Code:

Opened sub 1 file F:\temp\muxman\sourcen\TEMP\SUBs\Mai01-Mai04_TEST.sst.
Pixel_Area values 0 572 are incorrect, using default of 0 572.
Display_Area Y values 2 574 are incorrect, using default of 2 574.
F:\temp\muxman\sourcen\TEMP\SUBs\\Mai01-Mai04_0001.bmp adjusted start time is negative (SubRip delay too high). file skipped.

Here is my SubScript:

Code:

st_format       2
Display_Start   non_forced
TV_Type         PAL
Pixel_Area      (0 572)
Display_Area    (0 2 719 574)
PA              (0 0 0 - - - )
E1              (255 0 0 - - - )
E2              (0 0 255 - - - )
BG              (255 255 255 - - - )
SubTitle        0020
Directory       F:\temp\muxman\sourcen\TEMP\SUBs\
#############################################################
SP_NUMBER     START        END       FILE_NAME
#############################################################
Contrast   (15 15 15 0)
Color      (2 1 7 1)
0001       00:00:10:00  00:00:48:00  Mai01-Mai04_0001.bmp
Color      (2 1 1 1)
0002       00:01:00:00  00:01:20:00  Mai01-Mai04_0002.bmp
Color      (2 1 7 1)
0003       00:01:40:00  00:02:00:00  Mai01-Mai04_0003.bmp
Color      (2 1 1 1)
0004       00:02:02:00  00:02:40:00  Mai01-Mai04_0004.bmp

Furthermore, I noticed the following issue: Until version 0.11, I was able to use the VOBs with dvdauthor, too; unfortunately, since version 0.12 this does not work anymore.

Thanks for v.12 ... Katjarella

mpucoder · 27th February 2005, 22:15

NTSC subpictures are supposed to have an even number of lines, unfortunately the check doesn't care which tv system is used. It doesn't change the output, though. I have removed the check and replaced the zip file without a revision number change. Also the delay should be correct now.

All the tests run on Muxman (which are now automated thanks to project files) showed no changes in output. The exception, of course, is field pictures which were wrong before.

One thing about your sst script - the contrast line will be skipped. Any line following a line with all "#" will be skipped.

mpucoder · 27th February 2005, 23:08

I was thinking more about the skipping line. Originally any unrecognized line, like the with SP_NUMBER in it would have caused a syntax error. But the parser now just ignores anything it does not recognize. So I will be changing the parser to treat a line of all "#" as just a single line comment.

There is one thing that should be corrected in your script, for both Muxman and Scenarist. And that is the conversion rules. These are the symbols that follow the color values, eg PA (0 0 0 - - - )
the - - - are the three conversion rules. The only characters Scenarist allows are < = > &, these define the relationship between the stated color and that in the bitmap. - has no meaning and will be replaced with & by Scenarist, meaning if the bitwise AND of bitmap color and value from the script is non-zero then that is a match.
Muxman right now does not process the rules in an sst file (it assumes = = =), so you get away with it. But that will change (I missed it this time), and you may be surprised at the subpictures.

katjarella · 27th February 2005, 23:12

Ok, mpucoder...

The Original Scenarist Script:

Code:

***
 Item=Video {
	 Place Holder=No
	 Name=TESTSTREAM
	 Resolution=PAL
	 Drop Type=Non-drop frame
	 Data Start Time=00:00:00;00
	 Data End Time=00:01:19;24
	 File=F:\temp\muxman\sourcen\TEMP\TESTSTREAM.m2v
	 Width=720
	 Height=576
	 Is Encoded=Yes
	 Encode Type=MPEG 2
	 Size=720 x 576
	 Aspect Ratio=4 : 3
	 Picture Structure=Frame Structure
	 GOP Size=15 frames
	 GOP Structure=N/A
	 Bit rate=9800000
	 Average Bitrate=6000000
	 Minimum Bitrate=4000000
	 Bitrate Type=Variable
	 Icon Time=00:00:00;00
	 Line21 Switch1=No
	 Line21 File1=
	 Line21 Switch2=No
	 Line21 File2=
 }
***
 Item=Sub-Picture {
	 Place Holder=No
	 Name=Mai01-Mai04_0001
	 Resolution=PAL
	 Drop Type=Non-drop frame
	 Data Start Time=00:00:00;00
	 Data End Time=00:00:10;00
	 File=F:\temp\muxman\sourcen\TEMP\SUBs\Mai01-Mai04_0001.bmp
	 Width=720
	 Height=576
	 Is Encoded=Yes
	 Screen Size=Size {
		 X=720
		 Y=576
	 }
 }
***

and the Muxman Script:

Code:

***
 Item=Segment {
	 Name=Segment_1
	 Display Mode=4:3
	 Item=Video Stream {
		 Coding Mode=Mpeg-2
		 Standard=PAL
		 CC Field 1=No
		 CC Field 2=No
		 Item=Video Play {
			 File=F:\temp\muxman\sourcen\TEMP\TESTSTREAM.m2v
			 Size=10024552
		 Duration=Actual
		 }
	 }


 Item=Sub-Picture Stream {
	 Stream Number=1
	 Language=en
	 Language Extension=1
	 Display Mode=unspecified
	 Item=Sub-Picture Play {
		 File=F:\temp\muxman\sourcen\TEMP\SUBs\Mai01-Mai04_0001.bmp
		 Start=00:00:00:00 (0)
		 Forced Start=Yes
		 Time Code=PAL
		 Duration=00:00:10:00
		 Origin=0,0
		 Display Area=0,2,719,574
		 Color 1(Pa)=000000 & & &
		 Color 2(E1)=ff0000 & & &
		 Color 3(E2)=0000ff & & &
		 Color=2 1 7 1
		 Contr=15 15 15 0
	 }
 }
***

and The Error: Sub stream 1 sst tv_type disagrees with video

But in Scenarist, the same SubScript works flawlessly.

Matthew · 27th February 2005, 23:21

Fantastic to see project file/cli support. Although I think it's a huge shame that it's not possible to just specify an sst, instead of each individual subpicture and it's attributes. This would make auto generation of project files so much easier for people like me.

Also, in case you didn't know, the project file extention (mxp) seems to match that of the macromedia extension manager (which is installed with dreamweaver).

mpucoder · 27th February 2005, 23:56

You can use an sst or sup file, it looks like this:

Code:

		Item=Sub-Picture Stream
		{
			Stream Number=1
			Language=en
			Language Extension=1
			Display Mode=Wide/Letter
			File=D:\MuxSrc2\cu.sst
		}

Maybe a different extension?

mpucoder · 28th February 2005, 00:00

@katjarella - I think I fixed the tv standard problem. Any fixes after this will get a new revision.

Matthew · 28th February 2005, 00:00

I take back what I said. Pure awesomage

Yes, maybe you should change the extension, only because dreamweaver is so popular. Perhaps mmp? You can input possibilities at http://filext.com and see if they are already taken by well-known apps

mpucoder · 28th February 2005, 00:04

I'll check that out.
After you load a script with an sst it gets expanded, so saving the project will be in the format that lists each file.

katjarella · 28th February 2005, 00:05

Quote:

Originally posted by mpucoder
@katjarella - I think I fixed the tv standard problem. Any fixes after this will get a new revision.

Ok, Thanks... I wait in the MPUCoder's DVD Forum Index » Muxman Alpha // Download Center

mpucoder · 28th February 2005, 00:09

The fix is online now. And any fixes will be public. It's just that from now on I will give them revision numbers (letters, actually). A new series of alpha's will start Monday.

I'll have some documentation online about the project file soon. There is one other not-so-obvious thing you can do. Scenarist does not allow more than one motion video file in a track (segment to Muxman), instead they use a "concatenation file list" in a file with the .cfx extension. Muxman will import and expand these.

Matthew · 28th February 2005, 00:33

I tried 2 ssts via the GUI and the results were funky - the background was black instead of transparent for a start.

The ssts were saved from a sub/idx using SubResync/vsconv.exe. Here's one of them"

st_format 2
Display_Start non_forced
TV_Type NTSC
Tape_Type NON_DROP
Pixel_Area (0 477)
Directory .
Subtitle saved
Display_Area (0 2 719 479)
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 (9 4 15 3)
Contrast (15 15 0 15)
0001 00:01:39:02 00:01:41:25 saved_0001.bmp
0002 00:01:42:24 00:01:46:23 saved_0002.bmp
0003 00:01:47:16 00:01:49:15 saved_0003.bmp

mpucoder · 28th February 2005, 01:04

I see contrast there twice, first with background transparent, second is opaque. All the statements before a bitmap entry replace the previous value(s).

jsoto · 28th February 2005, 01:15

A BIG thanks. I'll give it a try in CLI mode..
jsoto

Matthew · 28th February 2005, 01:25

Quote:

Originally posted by mpucoder
I see contrast there twice, first with background transparent, second is opaque. All the statements before a bitmap entry replace the previous value(s).

Deleting the contrast line above the BMPs resolves the transparency issues but the colours are still wrong. I have little idea about the tech specs for ssts, but Scenarist does treat them properly.

mpucoder · 28th February 2005, 01:29

You still have to put the colors into the PGC manually. sst files have no color information.

The next version will add a lot more to what a project file can do, including setting the CLUT, but just this version required 110 keyword/context combinations. This was to get it to the same level as the gui.

Matthew · 28th February 2005, 02:14

Of course, forgot about the palette. Muxman's default palette differs from Scenarist's and presumably gabest produces ssts to fit the latter's default.

But that aside, I'm having issues with some other subs. The bmps on these are unusual, compared to the typical blue background, red text and white outline. They consist of a black backround and a small white box around the text area, and the text is red with a blue outline.

Scenarist handles these just fine using the inputted sst, Muxman doesn't, the background is white etc. It would appear Muxman detects what the background is differently from scenarist.

st_format 2
Display_Start non_forced
TV_Type NTSC
Tape_Type NON_DROP
Pixel_Area (0 477)
Directory H:\test\subs2
Subtitle test
Display_Area (0 2 719 479)
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 (3 10 3 3)
Contrast (0 0 0 0)
0001 00:00:00:00 00:00:00:01 test_0001.bmp
Contrast (0 15 15 0)
0002 00:00:30:08 00:00:35:26 test_0002.bmp
0003 00:02:54:25 00:02:57:18 test_0003.bmp
Contrast (0 0 0 0)
0004 00:03:32:27 00:03:32:28 test_0004.bmp
Contrast (0 15 15 0)
0005 00:03:40:13 00:03:46:17 test_0005.bmp
0006 00:03:55:08 00:03:56:29 test_0006.bmp
0007 00:04:01:07 00:04:04:20 test_0007.bmp
0008 00:04:17:08 00:04:18:17 test_0008.bmp
0009 00:04:23:17 00:04:25:25 test_0009.bmp
0010 00:04:49:19 00:04:51:16 test_0010.bmp
0011 00:04:51:22 00:04:53:06 test_0011.bmp

mpucoder · 28th February 2005, 02:37

Re-read your post. Could you send one of the bitmaps to me - muxman (at) mpucoder (dot) com

Muxman actually has no rule for the background - if a pixel is not P, E1, or E2 it is BG. What else to do with a pixel that matches nothing?

Matthew · 28th February 2005, 02:47

I've sent you the sample. It's a good testing set because of all the subtitles I've saved using the vobsub tools I've never seen the bmps come out like that.

27th February 2005, 20:43	#1 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	Muxman version 0.12 released Available here New features: full support for field pictures 8 subpicture tracks import Muxman or Scenarist project files (scripts) export Muxman project files batch mode / command line processing

27th February 2005, 22:15	#3 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	NTSC subpictures are supposed to have an even number of lines, unfortunately the check doesn't care which tv system is used. It doesn't change the output, though. I have removed the check and replaced the zip file without a revision number change. Also the delay should be correct now. All the tests run on Muxman (which are now automated thanks to project files) showed no changes in output. The exception, of course, is field pictures which were wrong before. One thing about your sst script - the contrast line will be skipped. Any line following a line with all "#" will be skipped. Last edited by mpucoder; 27th February 2005 at 22:58.

27th February 2005, 23:08	#4 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	I was thinking more about the skipping line. Originally any unrecognized line, like the with SP_NUMBER in it would have caused a syntax error. But the parser now just ignores anything it does not recognize. So I will be changing the parser to treat a line of all "#" as just a single line comment. There is one thing that should be corrected in your script, for both Muxman and Scenarist. And that is the conversion rules. These are the symbols that follow the color values, eg PA (0 0 0 - - - ) the - - - are the three conversion rules. The only characters Scenarist allows are < = > &, these define the relationship between the stated color and that in the bitmap. - has no meaning and will be replaced with & by Scenarist, meaning if the bitwise AND of bitmap color and value from the script is non-zero then that is a match. Muxman right now does not process the rules in an sst file (it assumes = = =), so you get away with it. But that will change (I missed it this time), and you may be surprised at the subpictures. Last edited by mpucoder; 27th February 2005 at 23:12.

27th February 2005, 23:56	#7 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	You can use an sst or sup file, it looks like this: Code: Item=Sub-Picture Stream { Stream Number=1 Language=en Language Extension=1 Display Mode=Wide/Letter File=D:\MuxSrc2\cu.sst } Maybe a different extension?

28th February 2005, 01:15	#15 \| Link
jsoto Just a Member Join Date: Nov 2002 Location: Spain Posts: 2,067	A BIG thanks. I'll give it a try in CLI mode.. jsoto __________________ Web sites with my tools http://download.videohelp.com/jsoto http://jsoto.posunplugged.com/

27th February 2005, 23:21	#6 \| Link
Matthew jdgljlfljg Join Date: Jan 2002 Location: Tony Abbott's electorate Posts: 1,394	Fantastic to see project file/cli support. Although I think it's a huge shame that it's not possible to just specify an sst, instead of each individual subpicture and it's attributes. This would make auto generation of project files so much easier for people like me. Also, in case you didn't know, the project file extention (mxp) seems to match that of the macromedia extension manager (which is installed with dreamweaver).

28th February 2005, 00:00	#8 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	@katjarella - I think I fixed the tv standard problem. Any fixes after this will get a new revision.

28th February 2005, 00:00	#9 \| Link
Matthew jdgljlfljg Join Date: Jan 2002 Location: Tony Abbott's electorate Posts: 1,394	I take back what I said. Pure awesomage Yes, maybe you should change the extension, only because dreamweaver is so popular. Perhaps mmp? You can input possibilities at http://filext.com and see if they are already taken by well-known apps

28th February 2005, 00:04	#10 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	I'll check that out. After you load a script with an sst it gets expanded, so saving the project will be in the format that lists each file.

28th February 2005, 00:09	#12 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	The fix is online now. And any fixes will be public. It's just that from now on I will give them revision numbers (letters, actually). A new series of alpha's will start Monday. I'll have some documentation online about the project file soon. There is one other not-so-obvious thing you can do. Scenarist does not allow more than one motion video file in a track (segment to Muxman), instead they use a "concatenation file list" in a file with the .cfx extension. Muxman will import and expand these.

28th February 2005, 00:33	#13 \| Link
Matthew jdgljlfljg Join Date: Jan 2002 Location: Tony Abbott's electorate Posts: 1,394	I tried 2 ssts via the GUI and the results were funky - the background was black instead of transparent for a start. The ssts were saved from a sub/idx using SubResync/vsconv.exe. Here's one of them" st_format 2 Display_Start non_forced TV_Type NTSC Tape_Type NON_DROP Pixel_Area (0 477) Directory . Subtitle saved Display_Area (0 2 719 479) 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 (9 4 15 3) Contrast (15 15 0 15) 0001 00:01:39:02 00:01:41:25 saved_0001.bmp 0002 00:01:42:24 00:01:46:23 saved_0002.bmp 0003 00:01:47:16 00:01:49:15 saved_0003.bmp

28th February 2005, 01:04	#14 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	I see contrast there twice, first with background transparent, second is opaque. All the statements before a bitmap entry replace the previous value(s).

28th February 2005, 01:29	#17 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	You still have to put the colors into the PGC manually. sst files have no color information. The next version will add a lot more to what a project file can do, including setting the CLUT, but just this version required 110 keyword/context combinations. This was to get it to the same level as the gui.

28th February 2005, 02:14	#18 \| Link
Matthew jdgljlfljg Join Date: Jan 2002 Location: Tony Abbott's electorate Posts: 1,394	Of course, forgot about the palette. Muxman's default palette differs from Scenarist's and presumably gabest produces ssts to fit the latter's default. But that aside, I'm having issues with some other subs. The bmps on these are unusual, compared to the typical blue background, red text and white outline. They consist of a black backround and a small white box around the text area, and the text is red with a blue outline. Scenarist handles these just fine using the inputted sst, Muxman doesn't, the background is white etc. It would appear Muxman detects what the background is differently from scenarist. st_format 2 Display_Start non_forced TV_Type NTSC Tape_Type NON_DROP Pixel_Area (0 477) Directory H:\test\subs2 Subtitle test Display_Area (0 2 719 479) 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 (3 10 3 3) Contrast (0 0 0 0) 0001 00:00:00:00 00:00:00:01 test_0001.bmp Contrast (0 15 15 0) 0002 00:00:30:08 00:00:35:26 test_0002.bmp 0003 00:02:54:25 00:02:57:18 test_0003.bmp Contrast (0 0 0 0) 0004 00:03:32:27 00:03:32:28 test_0004.bmp Contrast (0 15 15 0) 0005 00:03:40:13 00:03:46:17 test_0005.bmp 0006 00:03:55:08 00:03:56:29 test_0006.bmp 0007 00:04:01:07 00:04:04:20 test_0007.bmp 0008 00:04:17:08 00:04:18:17 test_0008.bmp 0009 00:04:23:17 00:04:25:25 test_0009.bmp 0010 00:04:49:19 00:04:51:16 test_0010.bmp 0011 00:04:51:22 00:04:53:06 test_0011.bmp Last edited by Matthew; 28th February 2005 at 02:25.

28th February 2005, 02:37	#19 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	Re-read your post. Could you send one of the bitmaps to me - muxman (at) mpucoder (dot) com Muxman actually has no rule for the background - if a pixel is not P, E1, or E2 it is BG. What else to do with a pixel that matches nothing?

28th February 2005, 02:47	#20 \| Link
Matthew jdgljlfljg Join Date: Jan 2002 Location: Tony Abbott's electorate Posts: 1,394	I've sent you the sample. It's a good testing set because of all the subtitles I've saved using the vobsub tools I've never seen the bmps come out like that.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode