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. |
9th February 2005, 17:11 | #81 | Link |
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 953
|
@SeeMoreDigital:
Yes. These applications (may) demux audio by cell-id. This way some audio header info is missed and MuxMan (correctly) complain about. A proper way to demux audio is following the PGC; give a try to PgcDemux (by Jsoto): http://forum.doom9.org/showthread.php?s=&threadid=84778 An alternative solution is to manually add one (or more) "silence frames", having the right header info set, to the demuxed audio, but then you have to take into account of the added audio delay. The "silence" tool is available at the Jsoto Home Page. A third solution (maybe it is the primary workaround...) has been reported to adopt some audio manipulation suite (do not remind which one specifically), to import the file and to export it to a new (or to the same) format, with the heading info properly set... Cheers, SD Edit: Got it! I finally remind where a similar discussion started: http://forum.doom9.org/showthread.ph...hlight=silence Last edited by Sir Didymus; 9th February 2005 at 17:49. |
10th February 2005, 22:04 | #82 | Link |
Registered User
Join Date: Sep 2002
Location: Germany
Posts: 352
|
@mpucoder
in case you remember: we talked about optionally supporting nonstandard GOP lengths. (relaxed check of GOP lengths). You asked what GOP lengths i usually encounter with DVB recordings. My results so far are that i have not encountered GOP lengths > 20. So imho it would be great if muxman accepts video files with GOP lengths greater than the standard DVD length of 15 (18). maybe a checkbox for enabling the relaxed check will do. or muxman simply outputs a warning afterwards if GOP lengths are > 15 (18) instead of refusing the video. Greetings, Malcolm |
10th February 2005, 22:12 | #83 | Link |
Life's clearer in 4K UHD
Join Date: Jun 2003
Location: Notts, UK
Posts: 12,219
|
Thanks very much Sir Didymus
By-the-way, has anybody had any luck muxing PAL Mpeg1 video with MuxMan... Can it do this? Cheers
__________________
| I've been testing hardware media playback devices and software A/V encoders and decoders since 2001 | My Network Layout & A/V Gear |
|
10th February 2005, 22:20 | #84 | Link |
Moderator
Join Date: Oct 2001
Posts: 3,530
|
@Malcolm - the next version, which is in alpha testing now and available from my forum, has quite a few changes in this regard. In order to support field_pictures the GOP tables were expanded to 36 entries (max for NTSC) and the limit set to 36 regardless of tv standard or picture_structure (field or frame). Muxman is only concerned about table overflow now.
btw I think (but have no samples) the longer gop's in DVB are the result of field encoding during high motion. But whatever the cause, version 12 should handle it. |
10th February 2005, 22:21 | #85 | Link |
Moderator
Join Date: Oct 2001
Posts: 3,530
|
I haven't tried PAL mpeg1, but NTSC mpeg1 works OK. The only thing to watch for is the PAR - Muxman will accept 3 or 8 for PAL, 6 or 12 for NTSC. It will not accept square pixels (1).
Last edited by mpucoder; 10th February 2005 at 22:23. |
10th February 2005, 22:59 | #89 | Link |
Wewkiee
Join Date: Feb 2002
Location: kashyyyk
Posts: 2,269
|
is it possible to have muxman align audios.. right now it puts one audio after each other (as well as each video) but if you have an audio that does not match the duration of the video it goes with, the next video/audio sequence will be out of sync. an option to have a non-seamless connection between the pairs so audio always matches would be cool. obviously this means having a way to determine 'pairs'. anyways.. food for thought
__________________
...yeah...but...why on earth would I compare apples with apples? |
10th February 2005, 23:09 | #90 | Link | |
Life's clearer in 4K UHD
Join Date: Jun 2003
Location: Notts, UK
Posts: 12,219
|
Quote:
When I mux PAL Mpeg1 I get this: - Cheers
__________________
| I've been testing hardware media playback devices and software A/V encoders and decoders since 2001 | My Network Layout & A/V Gear |
|
|
11th February 2005, 00:20 | #91 | Link |
Registered User
Join Date: Oct 2004
Location: PAL land
Posts: 211
|
@SeeMoreDigital
That has nothing to do with the MPEG-1 format itself. Your file simply has GOPs that are too long. The DVD Video Standard limits a GOP length to 15 frames (for PAL). That is very common with DVB, for example. What you need to do is to re-encode the oversized GOPs (so you replace an oversized GOP with two smaller GOPs, so that the DVD Video specification are met). I use Cuttermaran + TMPGEnc to do that with DVB Streams. The Geek |
11th February 2005, 11:02 | #92 | Link | |
Life's clearer in 4K UHD
Join Date: Jun 2003
Location: Notts, UK
Posts: 12,219
|
Quote:
So does this mean I'm going to have to re-encode the entire Mpeg1 stream then. Meaning another bounce down in quality I guess when the DVD Video Standard was being created for PAL content, making the GOP length 25 frames instead of 15 would have been "too easy" and obvious.... But I have to admit I'm somewhat of a newbie when it comes to DVD structures. Cheers
__________________
| I've been testing hardware media playback devices and software A/V encoders and decoders since 2001 | My Network Layout & A/V Gear |
|
|
11th February 2005, 11:46 | #93 | Link | |
Registered User
Join Date: Oct 2004
Location: PAL land
Posts: 211
|
Quote:
I never said anything about re-encoding the DVD compliant GOPs, too. Obviously, they don't have to be re-encoded, as they are already DVD compliant Now it depends on how many oversized GOPs you have in your MPEG-1 Stream. If every GOP is too long, well, then yes, you have to re-encode the whole thing. DVB recordings only have a few of them. I've done that with 4 King of Queens Seasons from DVB-S, that are about 90 episodes (a few are still missing). I think 15 oversized GOPs in one episode was the maximum I've seen so far, all other episodes had around 10. Using a high bitrate (6500 kbps), I don't see a quality loss. A GOP is short, and DVB-S ain't block-free anyway. With a low bitrate I was able to see the difference, but with 6500 I am not. The Geek |
|
11th February 2005, 15:36 | #94 | Link |
Moderator
Join Date: Oct 2001
Posts: 3,530
|
Or you could use version 0.12, either when it comes out or the alpha version from my forum. This version addresses two problems related to DVB - GOP size and field pictures. Actually I think they are the same problem, that is the large GOPs are the result of field (vs frame) encoding for high motion, but I have no examples. The next Muxman doubles the table size to accomodate field encoding to 36 and removes the tv standard based limit.
As for the DVD standards, they do not discriminate. The number of frames is based on time, 0.6 seconds to be exact (25x0.6 = 15, 30x0.6 = 18, the NTSC limit) |
11th February 2005, 15:44 | #95 | Link | |
Registered User
Join Date: Oct 2004
Location: PAL land
Posts: 211
|
Quote:
In my example, with 80 king of queens episodes, sometimes the intro has no oversized gops at all, and sometimes it has one or two. And the intro is always the same. On the other hand, you can encode field based MPEG streams with max. 30 fields in a GOP. The Geek |
|
11th February 2005, 15:56 | #96 | Link |
Moderator
Join Date: Oct 2001
Posts: 3,530
|
This is why I thought occasional field encoding might be the culprit. The actual limit is 30 (or 36 for NTSC) fields, regardless of picture_structure. And a GOP can contain a mixture of field and frame encoded pictures. But until version 0.12 there was no code to recognize and properly multiplex field encoded pictures, so the internal table limit was set to 18 pictures (regardless of type).
In version 0.12 it does not matter what the tv standard limit is, so long as there are no more than 36 pictures per GOP - it still has to protect against table over-indexing. |
11th February 2005, 17:08 | #97 | Link | |
Registered User
Join Date: Sep 2003
Posts: 1
|
Re: MuxMan 0.9 released
Quote:
|
|
11th February 2005, 19:39 | #98 | Link |
member
Join Date: Feb 2004
Posts: 346
|
MuxMan keeps rejecting BMP files.(0 file accepted, 1 files rejected)using version 0.11c
does the BMP have to be 720x480?or does it resize it? i'm i doing something wrong? thanks
__________________
some guides |
11th February 2005, 21:03 | #100 | Link |
member
Join Date: Feb 2004
Posts: 346
|
yes, thank you
i thought i did that but the preset in photoshop was NTSC D1 720x486. didn't see that. should have selected NTSC DV preset.
__________________
some guides |
Thread Tools | Search this Thread |
Display Modes | |
|
|