Muxman 0.13 released

mpucoder · 28th March 2005, 07:53

A great deal of work has gone into changing Muxman ifo generation from a simple "canned" set of tables to being compiled from a database. Unfortunately, the work isn't complete enough to allow the Navigation section to be user defined.

But this release does have 3 improvements:
Definable subpicture palette
Improved I-Frame encoder
Frame-accurate chapters (provided the chapter begins on an I frame)

Available from the Muxman homepage

Please consult the mxp documentation especially the new Settings Section

D3s7 · 28th March 2005, 16:53

Excellent advancements.... It won't be long before Scenarist is obsolete for what we need it for

Question: Will there be support to specify channels for audio/subtitles that's out of order.. IE: audio 1 = 84.

Scenarist requires you dummy 80-83 in order to do that.

Thanks

- D3s7

mpucoder · 28th March 2005, 17:26

Scenarist is just enforcing the specs, audio and subpicture stream numbers should be consecutive. Right now, and for the foreseeable future, Muxman will not allow manual stream assignments. When it does the specs will still be enforced by some mechanism.
At present, with only one title, the audio and subpicture stream numbers follow the value in the scp or mxp file. But once Muxman starts working with multiple titles per titleset the script file stream numbers will be relative to each segment, but not necessarily the same as the titleset. This will happen if two titles have different requirements, e.g. title 1 has one audio stream of 5.1 DD, while title 2 has one audio stream of 2.0 DD.

But - it should not be necessary to skip stream numbers. There are 2 places where absolute numbers, rather than symbolic names, are used in scripts. One is line numbers for the "goto" command. Muxman changes the way commands are defined into what resembles assembler source, complete with labels.
The other place where numbers are used is to specify a "stream" in the SetSTN command. I prefer to call this a track, as it is the number used to index a table in the PGC which then supplies the actual stream number. This number remains the same even if stream numbers are reassigned.

D3s7 · 28th March 2005, 17:32

Understood... and I'm not sure the attraction to it for authoring houses

The problem we run into in Scenarist is when a particular PGC/VOBID uses different stream assignments from the rest of the Title. Scenarist won't except those for mux (as can be understood) forcing us to dummy the appropriate streams. Not really a problem for PGC demuxes but for VOBID demuxes it can be an issue for Seamless cells

Seems more and more the DVD "Specs" are more "Recommended guidelines but feel free to break if you wish"

mpucoder · 28th March 2005, 17:47

Are you saying that there are titles which have one or more Vobs with different stream numbers than the rest of the title? This makes little sense - how does the player access a stream that suddenly appears in the middle of a title. As far as I know, and this is how I planned to implement in Muxman, all the segments (or "tracks" in Scenarist) must have the same video attributes, and have the same number and type of audio/sub streams.

I can understand a segment using different streams than others in the same titleset, this is commonl. Not in the same title, though, but a seperate title.

D3s7 · 28th March 2005, 17:57

unfortunatly, yes...

a few have "additional" audio tracks in one PGC -vs- another (same VOBID) - Finding Nemo for example, 80,81,82
PGC 1 uses 80,82 - PGC 2 uses 81 (example - not sure if that's the correct mapping) - demuxing this by vobid isn't an issue but 81 must be dummied on other assets in that PGC.

that's just one example but I've run across 4 or 5 movies like that. The problem is in order to dummy 81 across the other vobid's causes the cells to have to be linked non-seamless... Currently one of the solutions is to flip 82 and 81 so you have 80,81 on the main and the "extra" pgc uses 82

mpucoder · 28th March 2005, 18:23

Is this the R1 version? I'm not into buying animated movies (or G ratings - btw, why won't my V chip block the teletubbies, I want ONLY R!), but in this case I could make an exception if it demonstrates a DVD oddity.

D3s7 · 28th March 2005, 18:25

I've got 3 still files that I use for Scenarist that when trying to import them into Muxman 13 (tried 12 as well) it locks the interface hard... have to kill the process to get out of it.

Want me to email them to you?

mpucoder · 28th March 2005, 18:27

sure - muxman (at) mpucoder (dot) com (have to type it this way or I get a flood of email in Korean - have no idea what they're selling)

sweetness · 29th March 2005, 18:35

when i mux only a bmp or a m2v file(no audio no subs) muxman crashes(encountered an error message). ifoedit reports that there is no titleset tables when i do a get vts sectors(no video_ts.ifo is created)

in version 11c it muxed everything and the operation compete window pops up but muxman close once ok is pressed. ifoedit does not complain.

mpucoder · 29th March 2005, 19:23

What is the error message? What version of Windows? What does the Muxman log say?

sweetness · 29th March 2005, 19:49

the microsoft "MunxMan.exe has encountered a problem and needs to close. We are sorry for the inconvenience."

win xp sp2

it crashes once the progress bar is done.

tried v.12c and it does the same thing as v.11 it closes once ok is pressed.
v.13 crash all the time now with audio or not.

D3s7 · 29th March 2005, 20:01

Quote:

Originally posted by sweetness
when i mux only a bmp or a m2v file(no audio no subs) muxman crashes(encountered an error message). ifoedit reports that there is no titleset tables when i do a get vts sectors(no video_ts.ifo is created)

in version 11c it muxed everything and the operation compete window pops up but muxman close once ok is pressed. ifoedit does not complain.

I noted this issue myself and partially tracked it down to the installed version of comdlg32.dll....

version 6.0.2900.xxx seems to work fine where as 6.0.2800.xxx doesn't.
I was only able to test this theory on one machine but upgrading the dll seemed to resolve the issue - i assumed the newer dll was from xp sp2 but it may be from the .net 2003 extensions as well....

mpucoder · 30th March 2005, 00:38

I'm fairly certain this bug has been squashed by version 0.13c

@sweetness - Muxman is supposed to close when you click OK. That will probably change in the future when I'm certain that the program can run project after project without problems.

sweetness · 30th March 2005, 08:30

thanks tried out .13c and seems to work good.
also notice some dummy menus.

BTW creating 16:9 stills Display Mode=Only Pan Scan doesn't work, muxman displays 4:3. but P/S and LB or Only Letterbox works.

Sir Didymus · 30th March 2005, 08:37

Just to confirm 0.13c have solved the issue: no need to upgrade comdlg32.dll...

All the best,
SD

Zeul · 30th March 2005, 09:06

@SD
Are you working from a mxp project file? I have noticed that 0.13 has changed the scripting for pan. It was Display Mode=Only Pan Scan -> it is now Display Mode=Only Panscan.

sweetness · 30th March 2005, 09:18

@Zeul
yes thank you. i even check the site too, but missed that the space was gone.
oh ya wrong guy.

that's ok i get that all the time.

mpucoder · 30th March 2005, 09:27

That's true, I changed some keywords to be the same as Scenarist.

video display mode Only Pan Scan changed to Only Panscan (as noted above)

subpicture display mode PS changed to Pan in all combinations (Pan, Letter/Pan, Wide/Pan, Wide/Letter/Pan

Sorry for not drawing more attention to that. Also Uop can be specified in scenes (but not put into the vob - oops)

mpucoder · 30th March 2005, 09:52

btw, if you want a sneak peek at some stuff. Here's a sample of the vm commands syntax that will be used.
And here is the auto generated navigation currently built for you.

28th March 2005, 07:53	#1 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	Muxman 0.13 released A great deal of work has gone into changing Muxman ifo generation from a simple "canned" set of tables to being compiled from a database. Unfortunately, the work isn't complete enough to allow the Navigation section to be user defined. But this release does have 3 improvements: Definable subpicture palette Improved I-Frame encoder Frame-accurate chapters (provided the chapter begins on an I frame) Available from the Muxman homepage Please consult the mxp documentation especially the new Settings Section

28th March 2005, 16:53	#2 \| Link
D3s7 ScenAid Join Date: Mar 2003 Posts: 1,623	Excellent advancements.... It won't be long before Scenarist is obsolete for what we need it for Question: Will there be support to specify channels for audio/subtitles that's out of order.. IE: audio 1 = 84. Scenarist requires you dummy 80-83 in order to do that. Thanks - D3s7 __________________ ScenAid May just replace the dog as man's best friend http://www.scenaid.com

28th March 2005, 17:32	#4 \| Link
D3s7 ScenAid Join Date: Mar 2003 Posts: 1,623	Understood... and I'm not sure the attraction to it for authoring houses The problem we run into in Scenarist is when a particular PGC/VOBID uses different stream assignments from the rest of the Title. Scenarist won't except those for mux (as can be understood) forcing us to dummy the appropriate streams. Not really a problem for PGC demuxes but for VOBID demuxes it can be an issue for Seamless cells Seems more and more the DVD "Specs" are more "Recommended guidelines but feel free to break if you wish" __________________ ScenAid May just replace the dog as man's best friend http://www.scenaid.com

28th March 2005, 17:47	#5 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	Are you saying that there are titles which have one or more Vobs with different stream numbers than the rest of the title? This makes little sense - how does the player access a stream that suddenly appears in the middle of a title. As far as I know, and this is how I planned to implement in Muxman, all the segments (or "tracks" in Scenarist) must have the same video attributes, and have the same number and type of audio/sub streams. I can understand a segment using different streams than others in the same titleset, this is commonl. Not in the same title, though, but a seperate title. Last edited by mpucoder; 28th March 2005 at 17:49.

28th March 2005, 17:57	#6 \| Link
D3s7 ScenAid Join Date: Mar 2003 Posts: 1,623	unfortunatly, yes... a few have "additional" audio tracks in one PGC -vs- another (same VOBID) - Finding Nemo for example, 80,81,82 PGC 1 uses 80,82 - PGC 2 uses 81 (example - not sure if that's the correct mapping) - demuxing this by vobid isn't an issue but 81 must be dummied on other assets in that PGC. that's just one example but I've run across 4 or 5 movies like that. The problem is in order to dummy 81 across the other vobid's causes the cells to have to be linked non-seamless... Currently one of the solutions is to flip 82 and 81 so you have 80,81 on the main and the "extra" pgc uses 82 __________________ ScenAid May just replace the dog as man's best friend http://www.scenaid.com

28th March 2005, 17:26	#3 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	Scenarist is just enforcing the specs, audio and subpicture stream numbers should be consecutive. Right now, and for the foreseeable future, Muxman will not allow manual stream assignments. When it does the specs will still be enforced by some mechanism. At present, with only one title, the audio and subpicture stream numbers follow the value in the scp or mxp file. But once Muxman starts working with multiple titles per titleset the script file stream numbers will be relative to each segment, but not necessarily the same as the titleset. This will happen if two titles have different requirements, e.g. title 1 has one audio stream of 5.1 DD, while title 2 has one audio stream of 2.0 DD. But - it should not be necessary to skip stream numbers. There are 2 places where absolute numbers, rather than symbolic names, are used in scripts. One is line numbers for the "goto" command. Muxman changes the way commands are defined into what resembles assembler source, complete with labels. The other place where numbers are used is to specify a "stream" in the SetSTN command. I prefer to call this a track, as it is the number used to index a table in the PGC which then supplies the actual stream number. This number remains the same even if stream numbers are reassigned.

28th March 2005, 18:23	#7 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	Is this the R1 version? I'm not into buying animated movies (or G ratings - btw, why won't my V chip block the teletubbies, I want ONLY R!), but in this case I could make an exception if it demonstrates a DVD oddity.

28th March 2005, 18:25	#8 \| Link
D3s7 ScenAid Join Date: Mar 2003 Posts: 1,623	I've got 3 still files that I use for Scenarist that when trying to import them into Muxman 13 (tried 12 as well) it locks the interface hard... have to kill the process to get out of it. Want me to email them to you? __________________ ScenAid May just replace the dog as man's best friend http://www.scenaid.com

28th March 2005, 18:27	#9 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	sure - muxman (at) mpucoder (dot) com (have to type it this way or I get a flood of email in Korean - have no idea what they're selling)

29th March 2005, 18:35	#10 \| Link
sweetness member Join Date: Feb 2004 Posts: 346	when i mux only a bmp or a m2v file(no audio no subs) muxman crashes(encountered an error message). ifoedit reports that there is no titleset tables when i do a get vts sectors(no video_ts.ifo is created) in version 11c it muxed everything and the operation compete window pops up but muxman close once ok is pressed. ifoedit does not complain. __________________ some guides Last edited by sweetness; 29th March 2005 at 18:39.

29th March 2005, 19:23	#11 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	What is the error message? What version of Windows? What does the Muxman log say?

29th March 2005, 19:49	#12 \| Link
sweetness member Join Date: Feb 2004 Posts: 346	the microsoft "MunxMan.exe has encountered a problem and needs to close. We are sorry for the inconvenience." win xp sp2 it crashes once the progress bar is done. tried v.12c and it does the same thing as v.11 it closes once ok is pressed. v.13 crash all the time now with audio or not. __________________ some guides Last edited by sweetness; 29th March 2005 at 22:07.

30th March 2005, 00:38	#14 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	I'm fairly certain this bug has been squashed by version 0.13c @sweetness - Muxman is supposed to close when you click OK. That will probably change in the future when I'm certain that the program can run project after project without problems.

30th March 2005, 08:30	#15 \| Link
sweetness member Join Date: Feb 2004 Posts: 346	thanks tried out .13c and seems to work good. also notice some dummy menus. BTW creating 16:9 stills Display Mode=Only Pan Scan doesn't work, muxman displays 4:3. but P/S and LB or Only Letterbox works. __________________ some guides

30th March 2005, 08:37	#16 \| Link
Sir Didymus Registered User Join Date: Mar 2004 Location: Italy Posts: 864	Just to confirm 0.13c have solved the issue: no need to upgrade comdlg32.dll... All the best, SD

30th March 2005, 09:06	#17 \| Link
Zeul NuMenu4u Join Date: Nov 2002 Location: England Posts: 1,361	@SD Are you working from a mxp project file? I have noticed that 0.13 has changed the scripting for pan. It was Display Mode=Only Pan Scan -> it is now Display Mode=Only Panscan. __________________ NuMenu4u here

30th March 2005, 09:18	#18 \| Link
sweetness member Join Date: Feb 2004 Posts: 346	@Zeul yes thank you. i even check the site too, but missed that the space was gone. oh ya wrong guy. that's ok i get that all the time. __________________ some guides

30th March 2005, 09:27	#19 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	That's true, I changed some keywords to be the same as Scenarist. video display mode Only Pan Scan changed to Only Panscan (as noted above) subpicture display mode PS changed to Pan in all combinations (Pan, Letter/Pan, Wide/Pan, Wide/Letter/Pan Sorry for not drawing more attention to that. Also Uop can be specified in scenes (but not put into the vob - oops)

30th March 2005, 09:52	#20 \| Link
mpucoder Moderator Join Date: Oct 2001 Posts: 3,398	btw, if you want a sneak peek at some stuff. Here's a sample of the vm commands syntax that will be used. And here is the auto generated navigation currently built for you.

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