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. |
29th December 2004, 17:21 | #101 | Link |
Moderator
Join Date: Oct 2001
Posts: 3,530
|
At version 0.6 some io changes were made, and since then 3 reports of hanging during ifo creation.
So here is a special compile of version 0.7 that goes back to using buffered writes for ifo creation. Trahald, Sir Didymus, Koepi, and anyone else who experienced hanging please try this version and let me know. I'm also curious which OS (I'm assuming XP) |
29th December 2004, 17:56 | #102 | Link | |
Moderator
Join Date: Oct 2001
Location: Germany
Posts: 4,454
|
For now the result looks the same. I'll give muxman some more minutes though (it's at 99% CPU) to give it a chance to create video_ts.ifo|bup.
OS: Win2k SP4 + all security patches (german) source drive: 7.200 rpm/2mb 80GB maxtor u-dma 133 target drive: 7.200 rpm/8mb 160GB samsung u-dma 133 athlon xp 2.800+; nforce 2 ultra chipset. Regards Koepi P.S.: forgot to paste the log, maybe the underflows and/or remaining bytes in buffer are the problem here? Quote:
EDIT2: weird. now that I forced the program closing, vts_01_0.ifo|bup get the current timestamp instead of the creation time 15 minutes ago. Maybe that helps.
__________________
Koepi's new media development site Last edited by Koepi; 29th December 2004 at 18:06. |
|
29th December 2004, 18:26 | #103 | Link |
Life's clearer in 4K UHD
Join Date: Jun 2003
Location: Notts, UK
Posts: 12,219
|
Lord of the Ring's!
Those movies have run times that are measured in "parts of days" rather than in hours and minutes That said, it should provide MuxMan with "the ultimate test" Cheers
__________________
| I've been testing hardware media playback devices and software A/V encoders and decoders since 2001 | My Network Layout & A/V Gear |
|
29th December 2004, 19:05 | #104 | Link |
Moderator
Join Date: Oct 2001
Posts: 3,530
|
Well, since it is not the io routines, the next thing would be for people having this problem to make a profile and send it to muxman@mpucoder.com so I can hopefully reproduce it.
|
29th December 2004, 19:05 | #105 | Link |
Moderator
Join Date: Oct 2001
Location: Germany
Posts: 4,454
|
Obviously this is true, SeeMoreDigital
@mpucoder: Another thing I noticed - with mplex-based programs the vts_01_0.[ifo|bup] are 113kb in size. With muxman, they are 63kb. On my 2nd test with a lot more time not touching anything muxman still hangs in the same place. If I can help you in any other way to track down the issue? Regards Koepi
__________________
Koepi's new media development site |
29th December 2004, 19:23 | #106 | Link |
Moderator
Join Date: Oct 2001
Posts: 3,530
|
@Koepi - if you could run it again with "make profile" checked and then send c:\muxman.mxl to muxman@mpucoder.com that would help. Even if Muxman hangs the profile will contain enough information to reconstruct conditions up to the hang.
|
29th December 2004, 20:17 | #107 | Link |
Moderator
Join Date: Oct 2001
Location: Germany
Posts: 4,454
|
ok, mail is on the way (takes a little due to my max. 16kb/s uplink). My zip program refused to pack it, so it's full 1.2MB.
Cheers, Koepi
__________________
Koepi's new media development site |
30th December 2004, 08:07 | #109 | Link |
Moderator
Join Date: Oct 2001
Posts: 3,530
|
I found the problem, and man, is that one long movie. Although I don't like releasing so often, especially right after the last version made the news, this is important enough.
Version 0.8 is available here Fixes hang while building vobu_admap > 64K (movies > 2h16m) And although it hasn't happened yet, the same thing could have happened while building the time map for movies longer than about 4H30M. So that has been recoded as well. |
30th December 2004, 10:14 | #110 | Link |
Moderator
Join Date: Oct 2001
Location: Germany
Posts: 4,454
|
Success! I got the "summary" messagebox at the end and muxman closed. The resulting files are playing correctly. Forgot the chapter list in the first run but repeating that now, then burn the stuff and try it on my standalone.
mpucoder, one other suggestion though, if the input files aren't compliant and muxman won't accept them, can you spit out an according message too? I don't have my 18frames-per-(PAL)-gop file around anymore but that would be sure helping. Regards Koepi
__________________
Koepi's new media development site |
30th December 2004, 15:41 | #111 | Link |
Moderator
Join Date: Oct 2001
Posts: 3,530
|
MuxMan will diagnose the GOP size, and tell you when it encounters a large one. The bug was that if the first GOP is too large MuxMan attempted to calculate the average bitrate before showing the error message, resulting in division by zero.
The ironic thing is it crashed while trying to tell you. The program can easily handle 18 frame GOPs, they are used in NTSC. But a check was put in, mainly to prevent GOPs larger than 18 from crashing MuxMan (as that is the limit of one table). All files get checked somewhat before the multiplex. Video is checked to see if the required headers are present (also needed to see if it is MPEG-1 or MPEG-2, if Pan/Scan is present, and for closed-captions). Audio files are recognized by content, not file extension, so they get scanned a little. If the files meet the first checks the multiplex can begin. Any time MuxMan absolutely can not go on it will tell you why, but sometimes that will be very far into the multiplex as there is no pre-scan. Last edited by mpucoder; 30th December 2004 at 15:48. |
30th December 2004, 19:08 | #112 | Link | |
AviSynth Enthusiast
Join Date: Jul 2002
Location: California, U.S.
Posts: 1,267
|
Quote:
|
|
31st December 2004, 07:56 | #114 | Link |
Registered User
Join Date: Oct 2002
Location: Texas, USA
Posts: 8
|
While muxing one of my RTV recordings of a 8mm video, I got an error message from MuxMan 0.7 about 2/3 of the way through a 2 hour recording saying it had detected a GOP with more than 18 frames. I clicked the "OK" button, and MuxMan terminated gracefully.
I eventually traced the problem to a section of the original 8mm recording that was flaky. I edited that section out, and MuxMan was then able to successfully mux the entire recording. No problem to report, just wanted you to know that the NTSC GOP > 18 error handling is working as designed, at least in this situation. RF |
31st December 2004, 10:57 | #116 | Link |
Registered User
Join Date: Aug 2002
Location: Italy
Posts: 303
|
Check it out !!!
__________________
HYbrid Multimedia Production Suite project @ GitHub |
31st December 2004, 11:01 | #117 | Link | |
Moderator
Join Date: Oct 2001
Location: Germany
Posts: 4,454
|
Re: Check it out !!!
Quote:
Please do so. Cheers, Koepi
__________________
Koepi's new media development site |
|
31st December 2004, 21:10 | #118 | Link |
Registered User
Join Date: Oct 2002
Location: Texas, USA
Posts: 8
|
I had a 4 hour recording of the Olympics still, so I ran it through MuxMan. MuxMan 0.8 successfully multiplexed the video and audio streams into 6 VOB files, but the program abended with the error: "Can't open VOB file" and did not create any .IFO or .BUP files. Clicking on the "OK" button appeared to hang the program, and clicking "Close" results in the "Program Not Responding" error to appear.
This is all that's in the log file: MuxMan version 0.8 Opened video file M:\newdvd.m2v, 4294967295 bytes. Opened audio 1 file M:\newdvd.mp2. MP2 audio, frame size = 0x240. 11:58:49 Begin multiplex. Cell map size 50. |
3rd January 2005, 08:43 | #119 | Link |
EphMan
Join Date: May 2004
Posts: 737
|
I have two requests for a future MuxMan version:
1: Make the muxman.log file goto whatever dir the actual MuxMan.exe is located at, instead of defaulting to C: 2: Option to mux .m2v and .mp2 to a .mpg MPEG-2 video file instead of setting it up for authoring. Keep up the great work :-) |
3rd January 2005, 11:04 | #120 | Link |
Registered User
Join Date: Sep 2002
Location: Germany
Posts: 352
|
hi mpucoder,
i have another 2 requests for muxman: 1. please add an option to relax some DVD compliancy-checks. that means primarily GOP-length. resolution (e.g. 480x480, 480x576) would be nice too. i record DVB streams regularly and burn them to DVD. nearly all DVB streams have a few GOPs (<0.1%) with lengths > 18 (15). they all play fine on my dvd-player. IMHO it's a bit far from practical use if a muxer refuses *at all* to mux such streams. (again only MHO ) 2. ability to add more than 1 video file. there are 2 types of use for this: a) you have some mpeg files (e.g. 2 or 3 SVCDs) and you want them to play as a single film on the dvd. AFAIK playing all videos after another automatically can be done by adding some navigation commands in the .ifo file. b) you have some mpeg files (2 individual movies) that you want to select + play individually. greetings, Malcolm |
Thread Tools | Search this Thread |
Display Modes | |
|
|