Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > (HD) DVD, Blu-ray & (S)VCD > (HD) DVD & Blu-ray authoring

Reply
 
Thread Tools Search this Thread Display Modes
Old 27th January 2005, 22:40   #41  |  Link
mrslacker
Junior Slacker
 
mrslacker's Avatar
 
Join Date: May 2004
Location: End-World
Posts: 296
Small request: Could the "Input file list" dialog be made resizable or at least have a horizontal scroll for long file names? Thanks.
mrslacker is offline   Reply With Quote
Old 27th January 2005, 22:56   #42  |  Link
mpucoder
Moderator
 
Join Date: Oct 2001
Posts: 3,530
The cell times should add up in the next release (you can check its alpha version at http://www.mpucoder.com/Muxman/alpha/ use 11e or later)

This only happens with NTSC, and only with cells that have an odd number of fields. The PGC total is correct, the individual cell times can be short one frame.

@mrslacker - I never thought anyone would have a filename not fit, but I will enable horizontal scroll.
mpucoder is offline   Reply With Quote
Old 27th January 2005, 23:00   #43  |  Link
erdoke
Custom User Title
 
erdoke's Avatar
 
Join Date: Aug 2004
Location: Lat. 47.3350 | Long. 21.3850
Posts: 226
THX mpucoder, it seemed to be an administrative issue anyway for I had no problems with the playback.

Any plans on increasing the number of multiplexable subtitle number soon?
And subtitle color table support? At least to be able to copy colors?
__________________
Today begins the rest of your life...

Last edited by erdoke; 27th January 2005 at 23:02.
erdoke is offline   Reply With Quote
Old 27th January 2005, 23:02   #44  |  Link
mpucoder
Moderator
 
Join Date: Oct 2001
Posts: 3,530
What's really strange is I was testing subpicture pointers to make sure they were not spanning cells when the verifier spat out an error concerning cell elapsed time. So the problem got fixed before I read the post.

btw alpha 11e now processes sst files.
mpucoder is offline   Reply With Quote
Old 27th January 2005, 23:04   #45  |  Link
erdoke
Custom User Title
 
erdoke's Avatar
 
Join Date: Aug 2004
Location: Lat. 47.3350 | Long. 21.3850
Posts: 226
Quote:
Originally posted by mpucoder
btw alpha 11e now processes sst files.
Good news indeed.

Sorry, I edited my previous post while you were answering. Support of Muxman is really quick here.
__________________
Today begins the rest of your life...
erdoke is offline   Reply With Quote
Old 27th January 2005, 23:10   #46  |  Link
mpucoder
Moderator
 
Join Date: Oct 2001
Posts: 3,530
Those are a couple good requests. Muxman internally can process all 32 subpicture streams, it is only the GUI that is limited. The problem is what you're seeing now will become the demo for the full featured product, and I have promised never to take anything away from it. So I have to restrict it in some places. 3 seemed like a good number as it is the minimum you might need for a 16:9 movie.

The color tables is another story. Eventually the project file will carry it, and I'd like to avoid a whole bunch of little text files to import for each aspect of the project.
mpucoder is offline   Reply With Quote
Old 27th January 2005, 23:17   #47  |  Link
mpucoder
Moderator
 
Join Date: Oct 2001
Posts: 3,530
This is kinda pre-release info, but. I added a line to the sst file to allow Muxman to correct for the errors in SubRip 1.17.1 (and I have told Zuggy about them in this thread , but so far no fix)
the line looks like this:
Code:
Generator	SubRip1.17.1 25257
the number (25257 in this example) is the initial vobu_s_ptm value (SubRip does not account for this when computing times) which you can get from VobEdit, first NAV pack.
Other corrections made for SubRip are to get the pixel mapping correct.
mpucoder is offline   Reply With Quote
Old 28th January 2005, 10:12   #48  |  Link
bourtzovlakas
dvd.stuff.gr moderator
 
bourtzovlakas's Avatar
 
Join Date: Apr 2004
Location: Greece
Posts: 312
Hello,
Is it possible to add an option,to copy the color palette from the original IFO to the new IFO,created by Muxman?

Thanks
bourtzovlakas is offline   Reply With Quote
Old 31st January 2005, 18:58   #49  |  Link
mpucoder
Moderator
 
Join Date: Oct 2001
Posts: 3,530
Version 0.11 is now available here

New features:
added sst (Scenarist subpicture script)
added ini file, saves window position, log file name, and destination folder

other changes:
internal changes to prepare for CLI ability

bug fixes:
fixed problem accepting multiple video with Closed Captions
mpucoder is offline   Reply With Quote
Old 1st February 2005, 00:20   #50  |  Link
Matthew
jdgljlfljg
 
Join Date: Jan 2002
Location: Tony Abbott's electorate
Posts: 1,393
Good stuff.

But I just tried sst (PAL), saved from a sub/idx using subresync, and the subs did not appear. The entry is there in the IFO, but vobsub cannot find any subs. While this may be the fault of subresync, perhaps some sort of relaxation would be desirable I included the muxman log and the start of the sst.

Also, unless I'm mistaken, to use automatic pan and scan Scenarist requires the video to have an aspect ratio of 4:3. This is inconsistent with MuxMan.


----
MuxMan version 0.11
Accepted video H:\minoritychap1\minoritychap1.mpv size = 290610004
Accepted audio H:\minoritychap1\MINORITYCHAP1 AC3 T01 3_2ch 448Kbps DELAY 0ms.ac3
Opened sub 1 file D:\hjhj\minoritychap1.sst.
Pixel_Area values 0 573 are incorrect, using default of 2 574.
Display_Area Y values 2 575 are incorrect, using default of 2 574.
.\minoritychap1_0001.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0002.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0003.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0004.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0005.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0006.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0007.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0008.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0009.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0010.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0011.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0012.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0013.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0014.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0015.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0016.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0017.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0018.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0019.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0020.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0021.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0022.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0023.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0024.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0025.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0026.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0027.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0028.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0029.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0030.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0031.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0032.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0033.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0034.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0035.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0036.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0037.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0038.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0039.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0040.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0041.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0042.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0043.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0044.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0045.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0046.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0047.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0048.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0049.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0050.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0051.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0052.bmp height of 574 is less than the required height of 575. file skipped.
.\minoritychap1_0053.bmp height of 574 is less than the required height of 575. file skipped.
10:01:38 Begin multiplex.
Maximum audio duration 19360 fields.
10:01:38 starting video file number 1.
SeqEnd at 11525B50.
Bytes remaining in buffer = 0.
10:02:14 End multiplex.
Bitrate - avg: 6568652, min: 3969969 (lba 8649), max: 9011200 (lba 8385).
Fields: 19374, VOBU: 648, Sectors: 155348.
----
st_format 2
Display_Start non_forced
TV_Type PAL
Tape_Type NON_DROP
Pixel_Area (0 573)
Directory .
Subtitle minoritychap1
Display_Area (0 2 719 575)
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 4 14 3)
Contrast (13 15 0 15)
0001 00:01:18:16 00:01:19:20 minoritychap1_0001.bmp
0002 00:01:27:05 00:01:29:12 minoritychap1_0002.bmp
0003 00:01:29:17 00:01:31:13 minoritychap1_0003.bmp
0004 00:01:51:18 00:01:54:13 minoritychap1_0004.bmp
0005 00:02:25:23 00:02:28:02 minoritychap1_0005.bmp
0006 00:02:28:08 00:02:29:23 minoritychap1_0006.bmp
0007 00:02:44:05 00:02:46:21 minoritychap1_0007.bmp
0008 00:02:47:01 00:02:50:02 minoritychap1_0008.bmp
0009 00:02:50:07 00:02:54:22 minoritychap1_0009.bmp
0010 00:02:55:02 00:02:58:12 minoritychap1_0010.bmp
0011 00:02:58:17 00:03:01:07 minoritychap1_0011.bmp
0012 00:03:05:10 00:03:07:05 minoritychap1_0012.bmp
0013 00:03:08:09 00:03:11:10 minoritychap1_0013.bmp
0014 00:03:11:15 00:03:13:10 minoritychap1_0014.bmp
0015 00:03:13:16 00:03:17:24 minoritychap1_0015.bmp
0016 00:03:18:04 00:03:19:03 minoritychap1_0016.bmp

Last edited by Matthew; 1st February 2005 at 00:26.
Matthew is offline   Reply With Quote
Old 1st February 2005, 06:10   #51  |  Link
mpucoder
Moderator
 
Join Date: Oct 2001
Posts: 3,530
The maximum number of subpicture lines for PAL is 573, you lose two at the top, and one at the bottom. This means the biggest display area is 0 2 719 574
It's alright to use bmp's that are larger, you just have to determine which line(s) to lose.
In your case, since the bmp's have 574 lines, I would recommend:
Pixel_Area (1 573)
Display_Area (0 2 719 574)
And Muxman will accept them, cropping off the top line.

Muxman complies with the specs, so if this is what subresync produces, it should change.

Auto pan/scan and auto letterbox are methods of displaying 16:9 video on 4:3 displays. Scenarist and Muxman both require either:
a) 16:9 video and a Picture_Display_Extension header (specifies the horizontal offset)
b) Sequence_Display_Extension indicating display horizontal size of 540
mpucoder is offline   Reply With Quote
Old 1st February 2005, 08:00   #52  |  Link
Matthew
jdgljlfljg
 
Join Date: Jan 2002
Location: Tony Abbott's electorate
Posts: 1,393
Thanks for the subtitle tip, I'll try it later. I knew it was probably SubResync's fault, but it along with vsconv.exe (dunno if it has same problem) are major sst saving apps.

Re pan and scan, if video is encoded as 16:9 + panscan checked in CCE then Scenarist takes it as 16:9.

However, if it's flagged as 4:3 + panscan is checked then Scenarist detects it as "4:3 (Pan-scan)".

Now, MuxMan will accept stream 1 as pan-scan but not stream 2.

Some time back it took me bloddy ages to figure out why Scenarist wasn't detecting the panscan info, so I remember it very clearly.

Plus I just tried it as well.

Last edited by Matthew; 1st February 2005 at 08:10.
Matthew is offline   Reply With Quote
Old 1st February 2005, 13:47   #53  |  Link
Trahald
Wewkiee
 
Trahald's Avatar
 
Join Date: Feb 2002
Location: kashyyyk
Posts: 2,270
I modified pulldown.exe source to add a -ps flag (pan and scan) it modifies (or adds *which was a pita since pulldown wasnt coded to add stuff) the sequence_display_extension with width 540. i force AR to 2 (4:3) since my intent for the option was compliance with scenarist. scenarist likes the output and it works great.. just wondering is it really part of the spec to have 4:3 flagged or is it scenarist. ive heard there are p&s streams on pro dvds that are 16:9 flagged with p&s width. i would make it optional for the app
__________________
...yeah...but...why on earth would I compare apples with apples?
Trahald is offline   Reply With Quote
Old 1st February 2005, 15:09   #54  |  Link
mpucoder
Moderator
 
Join Date: Oct 2001
Posts: 3,530
The DAR and headers are used as clues. In Muxman auto P/S can be set even without the headers present (or cleared if they are present). The only problem is multi-file wants the files to match in regard to the headers. This perhaps should be changed, along with requiring all files to match in regards to closed captioning.

I know it may sound rigid, but in order to produce spec compliant output Muxman will be strict in the early stages of any feature. Later on I can find ways to correct minor problems, such as subpicture height. I also know that this is a widespread problem, but the spec (as quoted in the Philips Video Verifier User Manual) is clear.
Code:
X-co-ordinate values shall be in the range 0 to 719 inclusive.
Y-co-ordinate values shall be in the range 2 to 479 inclusive for TV system 525/60.
Y-co-ordinate values shall be in the range 2 to 574 inclusive for TV system 625/50.
btw, anyone can download the User Manual from Philips
mpucoder is offline   Reply With Quote
Old 1st February 2005, 15:26   #55  |  Link
mpucoder
Moderator
 
Join Date: Oct 2001
Posts: 3,530
I just found a section in the User manual about the sequence_display_extension. What it says is typically hard to understand. It's a chart, so I'll paraphrase it:
Code:
When aspect ratio is 16:9
horizontal size      display horizontal size   aspect ratio information
720 or 704                    720                            16:9
720 or 704                    540                              4:3

When aspect ratio is 4:3
720 or 704                    720                              4:3
352                             360                              4:3
Confused as to which aspect ratio they're talking about? So was I - I guess by "When aspect ratio..." means the VTS video attributes, and "aspect ratio information" means the sequence header value.

Muxman will accept video coded this way, the presence of either a sequence_display_extension or a picture_display_extension will flag the VTS as 16:9 with auto P/S. If neither extension is present Muxman then relies on the sequence header DAR.
mpucoder is offline   Reply With Quote
Old 1st February 2005, 20:54   #56  |  Link
Sir Didymus
Registered User
 
Join Date: Mar 2004
Location: Italy
Posts: 946
Quote:
Originally posted by mpucoder
... it is only the GUI that is limited. The problem is what you're seeing now will become the demo for the full featured product, and I have promised never to take anything away from it. So I have to restrict it in some places. 3 seemed like a good number as it is the minimum you might need for a 16:9 movie.
Cough, cough...
Well, I don't know if you may be open to a little tricky negotiation...

Cough, cough...
But it seems to me that in order to support three subpictures for a 16:9 movie, including wide screen and letterbox variants, we poor users, cough, cough, we need at least SIX entries for the subs in the GUI...



Edit: adding three more subpicture entries while keeping just three radiobuttons for the additional tracks may do the job...

Edit2: of course if you inadvertitely add some more than three radiobuttons, me think nobody would object...

Last edited by Sir Didymus; 1st February 2005 at 21:05.
Sir Didymus is offline   Reply With Quote
Old 1st February 2005, 21:59   #57  |  Link
mpucoder
Moderator
 
Join Date: Oct 2001
Posts: 3,530
Well, there's no more room for track select radio buttons, so it would have to change to a pulldown. Either that or remove the track selection altogether and do as Scenarist does - automatically assign streams to tracks. The same logic as Muxman already has for determining possible tracks (which is based on language and extension match plus display modes not assigned) would set the track number to the lowest available. You lose some flexibility, but it gets simpler looking.

I'm leaning toward automatic track asignment since that means no extension to the Scenarist-like script syntax for project files coming in the next release.
mpucoder is offline   Reply With Quote
Old 2nd February 2005, 00:56   #58  |  Link
Matthew
jdgljlfljg
 
Join Date: Jan 2002
Location: Tony Abbott's electorate
Posts: 1,393
@Trahald, unless I'm mistaken DVDAuthor (or mplex) expects 16:9 for PS, while DVDMaestro will take either 16:9 or 4:3 (in fact I think it might not even check for the PS info).

Anyway, suppose I'll just have to live with the 16:9 only thing, when CLI comes along. It just would have been nice for the same output to be usable in both MuxMan and Scenarist.
Matthew is offline   Reply With Quote
Old 2nd February 2005, 02:19   #59  |  Link
mpucoder
Moderator
 
Join Date: Oct 2001
Posts: 3,530
I'm not clear on what Matthew means. As long as the headers for PS are in the first GOP Muxman doesn't care what the DAR is. Either 16:9+PS or 4:3+PS will set the video attributes to 16:9 auto-LB auto PS (aka "both"). You should be able to intermix videos of both encodings in a multi-file list. What you won't be able to add to the list is 4:3 without the headers.
mpucoder is offline   Reply With Quote
Old 2nd February 2005, 03:37   #60  |  Link
Matthew
jdgljlfljg
 
Join Date: Jan 2002
Location: Tony Abbott's electorate
Posts: 1,393
Mea culpa.

I had a 4:3 (no pan-scan) m2v in the same directory as well so I probably added that by mistake

I had also tried an earlier release of MuxMan and thought that 4:3+pan-scan wasn't detected properly then either.

Fortunately I'm wrong It's really odd how one can do multiple tests, come back later and do it once, and realise they've been an idiot :P
Matthew is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 03:58.


Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2017, vBulletin Solutions, Inc.