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. |
24th September 2006, 15:02
|
#1 | Link |
|
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 865
|
BatchMux release 1.3 - a C/L Interface for MuxMan
Please do not consider the small program below as other else than what it is stated in the title: it is just a small Command Line middleware to launch MuxMan (the great authoring program of mpucoder) with some command line argument.
Link to release 1.3: http://www.mediafire.com/?kmtmsuvzmrb For release 1.3 the argument list is as follows: Code:
//
// ---------------------------------------------------------------------------
// -------- General Arguments ------------------------------------------------
// ---------------------------------------------------------------------------
// -arglist file_name, optional; if this mode (and argument) is used, no other
// arguments should be present; file_name should be a text file containing
// all of the other BatchMux arguments, ONE SINGLE LINE CONTAINING two
// strings ([arg] [val]) separated by spaces and optionally delimited by "
// -d destination_folder, mandatory
// -mxp target script_file, optional; default to C:BatchMux.mxp
// -l log_file, optional; default to C:MuxMan.log
// -muxman folder, place where to look for the MuxMan.exe file, optional,
// default NULL string, meaning the same folder where BatchMux is executed
// -palette palette_file, optional; PgcEdit compatible ascii file containing
// 16 colour entries (index, red, green, blue) adopted for redefining the
// default color palette used by MuxMan
// -preparer "32_char_string"; optional copyright string setting the DVD
// preparer field in the VIDEO_TS.IFO and VIDEO_TS.BUP files. Note: it is
// overridden by the -norun option
// -norun allows to open the MuxMan GUI, to load the script file and to stop
// -prio REALTIME | HIGH | ABOVENORMAL | NORMAL | BELOWNORMAL | LOW
// allows to launch MuxMan with a given execution priority, optional,
// default to NORMAL
// ---------------------------------------------------------------------------
// -------- Content Section Arguments ----------------------------------------
// ---------------------------------------------------------------------------
// ======== VIDEO ========
// -[SEGi]v[_j] video_file[s], mandatory; note: in all of the arguments with
// the "SEGi" prefix, the i index should be an integer value, in the range
// [2...999]; also, segments sequence should be progressive: e.g if segment
// 4 is missed, all segment arguments from 5 to 999, if present, are
// ignored; the [_j] extension, with j in the range [2..99], allows to join
// a file list (in a plain, sequential way), to compose the asset of the
// given segment
// -[SEGi]vidmode 4:3 | PS_LB | PS | LB display mode for the video asset,
// optional, if present and compatible with the actual video mode, it is
// honored, based on the authoring application rules; if not present, it is
// not included in the script
// -[SEGi]vduration[_j] ACTUAL | DEFAULT | hh:mm:ss:ff, duration of the video
// play item, optional; default DEFAULT. Duration=ACTUAL is valid for
// motion video only. For the last file of the list Duration=DEFAULT means
// until the audio track ends. For other positions in the list it means:
// 15 frames for stills (image or single frame mpeg); 5 sec. for stillshow
// video (multiple I frames with a sequence end code for each frame);
// actual duration for motion video
// ======== AUDIO ========
// -[SEGi]a1[_j] audio1_file[s] ... -[SEGi]a8[_j] audio8_file[s]; all
// optional; the [_j] extension, with j in the range [2..99], allows to
// join a file list (in a plain, sequential way), to compose the asset[s]
// of the given segment
// -[SEGi]a1lang xx ... -[SEGi]a8lang xx two characters language code for the
// audio assets, all optional; default unspecified
// -[SEGi]a1ext 0|1|2|3|4 ... -[SEGi]a8ext 0|1|2|3|4 language extensions for
// the audio assets, where 0 --> unspecified, 1 --> normal, 2 --> visually
// impaired, 3 --> director comments, 4 --> alternate director comments;
// all optional; default 1 - normal
// -[SEGi]a1delay xxx ... -[SEGi]a8delay xxx audio delays, positive and
// negative values, in ms, in the range [-300...300]; all optional;
// default 0
// ======== SUBPICTURES ========
// -[SEGi]s1 subpic1_file ... -[SEGi]s32 subpic32_file; all optional
// -[SEGi]s1lang xx ... -[SEGi]s32lang xx two characters language code for the
// subpic files, default unspecified
// -[SEGi]s1ext 0|1|2|3|5|6|7|9|13|14|15 ...
// -[SEGi]s32ext 0|1|2|3|5|6|7|9|13|14|15
// language extensions for the subpicture files, where 0 --> unspecified,
// 1 --> normal, 2 --> large, 3 --> children 5 --> normal captions,
// 6 --> large captions, 7 --> children captions, 9 --> forced,
// 13 --> director comments, 14 --> large director comments,
// 15 --> children director comments; all optional; default 1 - normal
// -[SEGi]s1dmode LB | PAN | LB_PAN | WIDE | WIDE_LB | WIDE_PAN | WIDE_LB_PAN
// ... -[SEGi]s32dmode LB | PAN | LB_PAN | WIDE | WIDE_LB | WIDE_PAN |
// WIDE_LB_PAN display modes and track assignement for the subpicture
// streams; all optional; default --> WIDE_LB if video A/R is 16:9,
// unspecified if video A/R is 4:3
// ======== HIGHLIGHTS =========
// -[SEGi]hlstart[_j] hh:mm:ss:ff; highlight start time, relative to start of
// video segment; default 00:00:00:00
// -[SEGi]hldurat[_j] hh:mm:ss:ff; highlight duration, relative to start of
// highlight; default 00:00:00:00
// -[SEGi]hlmnu[_j] menu_file; in PgcEdit mnu format; all mnu items may be
// overridden by other hl arguments (see below), if present
// -[SEGi]hlbset[_j] hh:mm:ss:ff; button selection end time, relative to
// start of highlight; default 00:00:00:00
// -[SEGi]hlbutm{l}[_j] NORMAL | LB | PAN | WIDE; display mode for group {l}
// buttons; l=1,2,3; default --> NORMAL, i.e. unspecified
// -[SEGi]hloffsbutnr[_j] 0..36; highlight start button number; default 0
// -[SEGi]hlnumselbut[_j] 0..36; number of buttons selectable with the remote;
// default 0
// -[SEGi]hlfselbutnr[_j] 0..36; force selected button number; default 0
// -[SEGi]hlfactbutnr[_j] 0..36; force activated button number; default 0
// -[SEGi]hlcsm[_j] color_scheme_file; in PgcEdit csm format
// -[SEGi]but{k}g{l}[_j] button_file; in PgcEdit gbv format, where {k} is the
// button ID and {l} is the group ID --> {k} == 1 ... 36 and {l} == 1, 2, 3
// ======== CHAPTERS, PROGRAMS, CELLS ========
// -[SEGi]celltc timecode_file; optional file containing timecode boundaries
// for the cells in the hh:mm:ss:ff - 11 char fixed ndtc format
// -[SEGi]cellfr framecnt_file; optional file containing framecount boundaries
// for the cells in the "usual" CellTimes format - plain frame indexes
// -[SEGi]progtc timecode_file; optional file containing timecode boundaries
// for the programs in the hh:mm:ss:ff - 11 char fixed ndtc format -
// program boundaries must be a subset of the cell boundaries;
// default (no timecode_file) --> 1 SINGLE PROGRAM for the segment
// -[SEGi]progfr framecnt_file; optional file containing framecount boundaries
// for the programs - plain frame indexes format - program boundaries must
// be a subset of the cell boundaries;
// default (no framecnt_file) --> 1 SINGLE PROGRAM for the segment
// -[SEGi]chaptc timecode_file; optional file containing timecode boundaries
// for the chapters in the hh:mm:ss:ff - 11 char fixed ndtc format -
// chapter boundaries must be a subset of the program boundaries;
// default (no timecode_file) --> 1 SINGLE CHAPTER for the segment
// -[SEGi]chapfr framecnt_file; optional file containing framecount boundaries
// for the chapters - plain frame indexes format - program boundaries
// must be a subset of the program boundaries;
// default (no framecnt_file) --> 1 SINGLE CHAPTER for the segment
// ---------------------------------------------------------------------------
// -------- Organisation and Navigation Section Arguments --------------------
// ---------------------------------------------------------------------------
// -hcn file_name; hard coded navigation with static, motion, single page or
// multipage menus; interim solution providing the placement of the last
// segment(s) in the VMG domain as different page menus
//
The program is someway limited in many aspects; for example - at least in the actual release - the number of segments is limited to 99. Both the organisation of the segments and the DVD navigation are hardcoded. Version 1.3 is supporting the creation of simple menus, static, motion, single page or multipage, placed in the VMG domain. The related navigation, for the moment, is hardcoded. Up to 255 cells, 99 programs and 99 chapters are supported. A set of reference examples, including all of the needed menu assets to build static and motion menus is here: http://www.mediafire.com/?z8fykh2rpbc Overall rationale for the existance of BatchMux.exe is based on the following considerations: 1. Simplicity and straight usage. Even though MuxMan 0.16.6 fully supports command line arguments, the usage of some authoring parameters is only possible by means of scripting. That's not a complex job. The compilation of a MuxMan script is possible (for instance) by loading in the GUI the needed assets files, by making some configuration of the DVD project an by saving the project itself. However the command line control provided by BatchMux is simple, and it should like to users not familiar or not interested in mxp scripting. 2. Enabling of automation for existing applications. The usage of MuxMan as a reference authoring application should be encouraged as much as possible. The quality of its output is significantly better respect to other authoring packages, getting rid - definitely - of "stuttering", "freezing" and other sad effects, mostly caused by some weakness of the adopted authoring packages. On the other hand, the direct integration of MuxMan as authoring engine into thirdy party applications, may turn out as being not possible or too complex, due to the need of creating the mxp MuxMan script. BatchMux.exe may be helpful in this scenario... Actually it made possible the development of the MuxMan plugin to author DVD inside the DVD2SVCD package, it was also adopted in FAVC of MrOdwin and inside AVSTODVD of MrC... Usage: run BatchMux with the above arguments... No argument, or -help for printing out the list of the CLI arguments... Cheers, SD Edit 11-09-2008: link update to release 1.3 Main changes: - Added sanity checks for the lenght of log file path and destination folder (both should not exceed 120 characters) - Added -progtc, -progfr, -chaptc, -chapfr switches to support the generation of programs and chapters in the DVD compilation - Bugfix. Corrected a mistake, introduced in version 1.2, concerning the wrong attribution of chapters in multi-title compilations Edit 25-08-2008: link update to release 1.2 Main changes: - Reference examples completely revised: now they include all of the assets to show the usage of BatchMux to build single page and multipage menus - First release supporting multipage menues, hardcoded organisation and navigation - Completely reworked the harcoded navigation for static and motion menus - Removed all -hcni switches; now the navigation is partially configurable by means of a proper cfg file - Added -hcn file_name switch, to support the configuration of the hardcoded navigation - Changed the default assignement, in the mxp output, of the -[SEGi]hlbset[_j] argument. Now it is set to -1, instead of 00:00:00:00; same as for the -[SEGi]hldurat[_j] argument - Radically improved the DVD navigation: now supporting prev&next title jump, the resume function and the titles are now all one-sequential Edit 21-07-2008: link update to release 1.1 Main Changes: - Added -prio argument, to set the exec priority of MuxMan.exe - Added -hcn3 and -hcn4 arguments to implement the menu navigation without the "PlayAll" button Edit 15-05-2007: link update to release 1.0 Main Changes: - First release supporting menues, hardcoded organisation and navigation - Added -hcn1 and -hcn2 argument to implement static and motion menus Last edited by Sir Didymus; 11th September 2008 at 08:46. Reason: 25-08-2008 Uploaded release 1.2... |
|
|
|
16th January 2007, 10:06
|
#2 | Link |
|
Registered User
Join Date: Jan 2003
Location: Land of the Long White Cloud
Posts: 179
|
Thanks SD, for sharing your helpful little program.
It has enabled me to create a DVD with multiple titles for the first time using MuxMan.  One thing I did notice was only the first title had a language code for the audio stream, the remaining titles didn't have one. I checked the .mpx file that was created and the audio language code was missing from all segments except the first one. It's not a problem, I just thought you might like to know. I don't think I did anything wrong, but here's my -arglist file: Code:
-d E:\tmp\test\out -muxman "C:\Program Files\Muxman" -l E:\tmp\test\BatchMux.log -mxp E:\tmp\test\BatchMux.mxp -v "E:\tmp\demuxed\video1.m2v" -a1 "E:\tmp\demuxed\audio1.ac3" -a1lang en -SEG2v "E:\tmp\demuxed\video2.m2v" -SEG2a1 "E:\tmp\demuxed\audio2.ac3" -SEG2a1lang en -SEG3v "E:\tmp\demuxed\video3.m2v" -SEG3a1 "E:\tmp\demuxed\audio3.ac3" -SEG3a1lang en -SEG4v "E:\tmp\demuxed\video4.m2v" -SEG4a1 "E:\tmp\demuxed\audio4.ac3" -SEG4a1lang en -SEG5v "E:\tmp\demuxed\video5.m2v" -SEG5a1 "E:\tmp\demuxed\audio5.ac3" -SEG5a1lang en |
|
|
|
|
17th January 2007, 19:28
|
#3 | Link |
|
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 865
|
Hey, Jeffster, thanks for the bug report...
It will be fixed in the next release... I am working to add highlight stream support and some possibilities to organise the segments in different domains, in order to support the building of menus inside BatchMux... In the next days I will PM you a beta release, just to fix the missed lang codes (and few other little bugs...)... Cheers, SD |
|
|
|
|
17th January 2007, 23:28
|
#4 | Link |
|
Registered User
Join Date: Jan 2003
Location: Land of the Long White Cloud
Posts: 179
|
Thanks for looking into it SD...
 It's nice that you will be expanding on the possibilities, because I find the mpx documentation a little daunting to get my head around, and it will be fun to experiment with adding menus also, at a later date. 
Last edited by Jeffster; 18th January 2007 at 02:09. |
|
|
|
|
10th November 2007, 08:36
|
#5 | Link |
|
Registered User
Join Date: Dec 2006
Posts: 59
|
whew i really like the batchmux, been working fine for me except that i cannot download from your link i gotten it by downloading from other package(?fl?av?c) just to get batchmux out and delete the package that bundle
i wondering if we are purchase higher version of muxman will it works? for the seamless? --------------------- i'm also wondering if PRIORITY for muxman could be set in CLI when batchmux call muxman? /belownormal /abovenormal ? |
|
|
|
|
10th November 2007, 14:46
|
#6 | Link | ||
|
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 865
|
Hi Anime! Thanks a lot for your nice words...
Quote:
Quote:
For the moment the support provided by BatchMux is still unable to exploit the whole capabilities of MuxMan 0.15. For the future I would like to continue on this path, by adding some organisational capabilities to BatchMux. I mean I would like to be able to use PgcEdit PGC description files in order to organise the c/l authoring (VM commands, placement of segments in given domains, better support for menues, and so on...). This stage will be complete when I will be able to fully disassemble a given (simple) DVD, manually, by using PgcDemux and PgcEdit alones, and then to reauthor it completely, by using BatchMux and MuxMan alones... The complex features of MuxMan 0.18 or even the 1.0 are far beyond this objective... So, for the moment, I can just say that the usage of MuxMan 0.18 or 1.0 is definitely encouraged. If you are planning to use MuxMan with its native GUI, the little investment in MuxMan 1.0 is worth its cost. The domain of BatchMux is the one of MuxMan 0.15, and its c/l capabilities are quite limited... It seems to me more logic to improve this stage, for the moment... Sorry for that... Concerning the priority, thanks for the suggestion! It seems to me a relevant feature to add. I will check if it is feasible. It seems it should... Cheers, SD Last edited by Sir Didymus; 10th November 2007 at 18:41. |
||
|
|
|
|
5th July 2008, 07:01
|
#7 | Link |
|
Registered User
Join Date: Dec 2006
Posts: 59
|
hello, Sir Didymus
is there any update for this? because i been wondering if able to feed fade wipe sst for muxman v0.16.6 free/Pro 1.1.3 -------------------------------- i'm a maestrosbt user, i have already use your batchmux more than 400+ dvd myself, excluding that i also spread your program with your BatchMux Usage.txt to others, for a 1 click adding subtitle to dvd solution the 1 click adding subtitle solution is now noble known as DIYSup http://www.google.com/search?hl=en&r...p&start=0&sa=N, can get some info from google which include a .sup and a batch, those people who own the dvd, just insert disc answer-to-bat where is your drive letter, and wait-result is a optional subbed dvd (with menu) you might not know that, batchmux is very important to me, i always going for how to make .sup better... so i like to have effect in sst possible sorry for my english, thanks for batchmux |
|
|
|
|
5th July 2008, 08:16
|
#8 | Link | ||||
|
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 865
|
Hi Anime!
Quote:
I mean: 1. The development on this little middleware for MuxMan is not stopped! 2. I am currently working on improving the support for more complex menues; the direction I decided to follow (i.e. to provide a completely general solution) turned our being too complex and I have been forced to stop and to rollback a lot of work already implemented... Now I am working on including a simpler solution in order to provide multipage menues, but the navigation will be still hardcoded... Quote:
It is PERFECTLY matchnig with the sort of things BatchMux should do. At the moment I don't know precisely how the fade-in and fade-out effects are created by maestrosbt. I have to learn about this and to check what is feasible with the free version of MuxMan. However I will work on this and I will be back to you as soon as I have something to try on the matter (but please consider that I can not promise when...)... Quote:
As I said before, I will work on the inclusion of some fade-in and fade-out effects in BatchMux... Quote:
 , so I understand your troubles...Thanks to you again for your nice words, and for putting up the thread: it was an opportunity for me to refresh the links in the first post that were not valid any more...  Cheers, SD Last edited by Sir Didymus; 5th July 2008 at 08:19. |
||||
|
|
|
|
15th July 2008, 04:14
|
#9 | Link |
|
Registered User
Join Date: Dec 2006
Posts: 59
|
@Sir Didymus
about the fade & wipe that muxman accepts.... the also the thing I'm trouble in... i don't know what muxman accepts from a SST, or actually say how must it written in SST for muxman to read. OLD Maetsrosbt doesn't have this effect option too as maestrosbt been stopped for years without any update in sourceforge the only solution is i comeout with what muxman want in that SST to enable effects if any of you guys know how to write a SST to let muxman read effects let me know please.... |
|
|
|
|
15th July 2008, 08:39
|
#10 | Link |
|
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 865
|
I am not an expert on the production of subtitle assets...
However it should be understood that there are different methods to control the level of transparency of the subtitles. Within the freeware version of Muxman (e.g. the one supported by BatchMux) the single possibility I see is to create the fade-in and fade-out effects, based on the sst format, externally, by hand, or [better] by means of a subtitle manipulation application such as Aegisub or Subtitle Workshop. The concept is that the individual pictures in the fade-in and fade-out sequence should be all repeated, just changing the transparency level of each one. This is not at all elegant or efficient from the authoring point of view, but I see no other possibilities working with the freeware version of MuxMan. In the sst format, the transparency level of a given subpicture is controlled by the "Contrast" parameter, with 16 levels of transparency, independently and individually for the four elements of the colour pallette (Enphasis1, Enphasis2, Pattern, Background): Code:
st_format 2 Subtitle data_name #Display_Start …. forced/non_forced Display_Start non_forced Pixel_Area (2 479) Display_Area (0 2 719 479) #color index value …. (E2 E1 Pa Bg) (1-16) Color (1 2 3 4) #contrast …. (E2 E1 Pa Bg) (0-15) Contrast (15 15 15 0) ... So, let's check if one (or both) of the Aegisub or Subtitle Workshop applications can do the job... Ah... And maybe, please let's continue the discussion on fade-in and outs in the other thread you started, in the same forum, in order to avoid multiple topics opened on the same argument... Cheers, SD Last edited by Sir Didymus; 15th July 2008 at 08:53. |
|
|
|
|
16th July 2008, 16:58
|
#11 | Link | |
|
Registered User
Join Date: Dec 2006
Posts: 59
|
Hi, Sir Didymus
it is about muxing now... i got a friend project on R2J DVD with 170 cell Title: R2J NTSC - Doraemon the Movie 15: Nobita and Tree Visionary Swordsmen batchmux.log PGC "VTS01_Ttn1_Pgc1" has 170 programs, limit is 99 Exiting due to errors, no multiplex performed. -------------------- is this batchmux limitation or muxman? -------------------- Quote:
to be able to performed subtitle to DVD, my pratice is SSA > SST (breaking effects stage) > Muxman there seems to no other workaround with effect subtitle to DVD ---------------------- or I'm trying to say that aegisub and subtitle workshop effect is not for Muxman Muxing.... Last edited by Anime; 16th July 2008 at 17:03. |
|
|
|
|
|
16th July 2008, 18:35
|
#12 | Link | ||
|
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 865
|
Quote:
I assume you have loaded into a BatchMux one project with a single video asset, and a chapter file with 170 chapter points. Is it correct? Please confirm if this is the case... Even though the maximum number of cells per pgc is 255, the approach of MuxMan (and of BatchMux) is to create for each video segment one cell and one program at each chapter boundary... In this specific case the suggestion I have is to try to change the approach you are using: BatchMux supports multiple titles, and if you never tested this feature, you will be impressed... So, instead of demuxing the original DVD by pgc, try to demux it by VOB ID. I assume you are using PgcDemux for the job, is it correct? Again, please confirm if this is the case... If you are lucky, you will obtain just two video files, two sets of audio files and two sets of subpictures, and two chapter files, each one with less than 99 chapters. These normally correspond with the two VOB IDs used for the two layers of the original DVD. Then, telling to BatchMux to generate a DVD with two titles, the error you have get should disappear... Quote:
As mpucoder reported, there in no support in the SST format for the effects of fade and wipe. In the SST format these can just be simulated. In the SUP format these effects are preserved, but then you (we) should look for a subtitle rendering application capable of outputting the subtitles in the SUP format... Cheers, SD Last edited by Sir Didymus; 16th July 2008 at 18:37. |
||
|
|
|
|
17th July 2008, 06:10
|
#13 | Link |
|
Registered User
Join Date: Dec 2006
Posts: 59
|
@Sir Didymus
we shared the custom subtitle.sup for specific DVD in my private forum we use automatic scripting created by my forum member and myself having scripting config DEMUX=V1P1P2, V3P1, V4P1P2P3P4P5 will process adding custom audio, subtitle to final dvd, user which use can sit back or go out to relax due to batching tons of DVD is also possible all automatic from taking each VTS & PGC according to config.demux then it demux from pgcdemux, that VTS.PGC looking for custom audio and subtitle.sup/sst and custom palette (optional config) to batchmux mxp passing to muxman passing to voblanker, that VTS.PGC for replacing extract .sup for sharing to other forum member using (optional config) --------------------- PGCdemux can demux VOB ID MUXMan can mux it voblanker, i cannot see a way replaing vob id... Last edited by Anime; 17th July 2008 at 06:21. |
|
|
|
|
17th July 2008, 08:21
|
#14 | Link | |
|
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 865
|
Quote:
Due to the characteristics of this particular DVD, I see only three possibilities: 1. Extract the chapters of your DVD using PgcEdit (output programs only option). Don't use PgcDemux. This way you will get less than 99 programs. Use VobBlanker in pgc replace mode. This will replace the first 99 cells (with the movie) and then will blank the other cells. It's not a clean solution, and the structure of the reauthored DVD will be different from the original one, but the movie should work, including the original menues, including the chapter menu. Instead of VobBlanker, you may use the function of VTS replacement of PgcEdit. This has the advantage of not appending void cells to the replaced title. 2. Movie only solution: e.g. not using VobBlanker after the MuxMan session. 3. Using VobBlanker to replace each one of the 170 cells of your compilation individually: VobBlanker have a function to replace cells. It's not a good idea, since the process is very hard to be automated, and it takes a significant amount of time to perform it manually. In addition it will introduce discontinuities at the cell boundaries... :-( Cheers, SD ======================================================== Edit 21.07.2008 Announcing release 1.1 I have just uploaded the new release 1.1 of BatchMux.exe. See first post of the thread for the d/l link. Two features have been added: 1 - the new argument -prio was added, in order to launch MuxMan as a task with the following possible priorities: REALTIME, HIGH, ABOVENORMAL, NORMAL, BELOWNORMAL, LOW. Default: NORMAL 2 - two new navigation arguments have been added to support the Menu Generation: -hcn3 (which is the same as -hcn1, but creates a DVD navigation without the "PlayAll" button) and -hcn4 (which is the same as -hcn2, without the "PlayAll" button). Last edited by Sir Didymus; 21st July 2008 at 09:12. Reason: Announcing release 1.1 |
|
|
|
|
|
27th July 2008, 21:26
|
#15 | Link |
|
Registered User
Join Date: Dec 2006
Posts: 59
|
hi, sir, thanks for the new 1.1 after 1.0 a year back!!!
thanks for keeping it upgraded! ~really thanks! ----------------------------- edited: to comment about 170 cell solving solution @170 cell dvd point 3 is out... since i don't think it is easy to subtitle 170 parts.. it might take ages... the reason taking out demuxed stuff is wanted to add subtitle to it i told my friend to comeout with do not use muxman.... but use ifoedit>author instead just for this type of DVD that much easier right? just click the gui a few click and forget about trying to solve "how to" in muxman... --------------------------- by the way a long time ago i PM mpucoder about bug that muxman failed to mux if path is way long i did estimate the amount of character that possibly fail muxman muxing, wondering did he solve that issue, or was it batchmux that cannot accept very long path? Last edited by Anime; 27th July 2008 at 21:40. |
|
|
|
|
28th July 2008, 10:14
|
#16 | Link | ||
|
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 865
|
Quote:
Quote:
In BatchMux there are by sure limitations, in many (and different) parts of the code... Most of the paths are limited to 256 characters... Could you send to me some examples of BatchMux scripts (or command line sessions) with samples of very long paths? |
||
|
|
|
|
28th July 2008, 17:48
|
#17 | Link |
|
Registered User
Join Date: Dec 2006
Posts: 59
|
oh, thanks sir for answering,
currently after i knew that there will be some error msg stopping project i dare not use too long path and always squeeze my brain how to come out with shorter ones, on either cutting down project folder title or short sup name using short forms this is an example which is still valid, maybe abit longer than that will return error after* muxman muxing D:\VAXVA_STUDIO\[DIYSup][DVDISO] BALDR FORCE EXE Resolution (2006-OVA) [R2][VAXVA]\VAXVA_DEMUX_VTS01_PGC1\* D:\VAXVA_STUDIO\[DIYSup][DVDISO] BALDR FORCE EXE Resolution (2006-OVA) [R2][VAXVA]\[VAXVA]_BALDR_4_PGC1x1_zh.sup about subtitle i not sure if there is a rule of restriction but i try to cut short till this which is also passed, C:\Documents and Settings\Administrator\Desktop\New Folder\dvd4-v1p4x3_zh_w_0014.bmp a few long ones (project name) which is still passed can be quite long in title Code:
[DIYSup][DVDISO] Aa Megami-sama Tatakau Tsubasa (2007-SP) [R2][VAXVA] [DIYSup][DVDISO] Black Lagoon 2nd Barrage (2006-TV) [R2][VAXVA] [DIYSup][DVDISO] JoJo no Kimyo na Boken (1993-OVA) [R2][VAXVA] [DIYSup][DVDISO] Kenko Zenrakei Suieibu Umisho (2007-TV) [R2][VAXVA] [DIYSup][DVDISO] Kono Aozora ni Yakusoku wo (2007-TV) [R2][VAXVA] [DIYSup][DVDISO] Night Wizard The Animation (2007-TV) [R2][VAXVA] [DIYSup][DVDISO] Pocket Monster MOVIE (1998~20XX-Movie) [R2][VAXVA] [DIYSup][DVDISO] Suzumiya Haruhi no Yuuutsu (2006-TV) [R2][HH_A] it happens that there is small crowd popularity after year+ of this type of muxing solution , and small crowd exist because batchmux is here , else i could hardly go this far today using 1click solution adding subtitle/audio to dvd, http://www.google.com/search?hl=en&r...p&start=0&sa=N one more thanks to batchmux! Last edited by Anime; 28th July 2008 at 18:07. |
|
|
|
|
25th August 2008, 19:57
|
#18 | Link |
|
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 865
|
Hi Anime!
Sorry for the someway long time before providing feedbacks on the problems you have found. I confirm that both the issues consisting in the limitation to 99 cells per segment and the unpleasant behaviours due to the usage of long paths in the filenames of the assets are present... I take the opportunity to announce the availability of release 1.2 of batchMux.exe (now it includes the support to multipage menues). See the first post in the thread for details on the matter. The next release(s) of the program will be focused on the working on, and fixing (if possible) the two problems you have pointed out. I am planning to focus on the matter in the next days/weeks/months... All the best, SD Edit - 27-08-2008. IMPORTANT. I discovered that the troubles with long path names are mostly due to a limitation of MuxMan... Both the Path Name of the destination folder and the Path Name of the log file should be less than 120 characters. The same limitation is apparently not present for the source assets, than can be as long as 255 characters. I have implemented a couple of sanity checks for the next release (1.3) of BatchMux.exe. In case the log file is exceeding 120 characters, then the error is non blocking, and the log file is reverted back to the default C:\BatchMux.log. In case the destination folder is exceeding 120 characters, then the error is blocking: BatchMux stops with an error message... Edit - 28-08-2008. After some further quick checks, it seems also the issue of the number of cells in the segments exceeding 99 can be solved. It will imply to change the way mxp script is produced, and to add some new switches (-progfr and -chapfr) in addition to the already available -cellfr. This way it will be possible to specify explicitely program points and chapter (PTT) points. These points should be placed at the cell boundaries, as defined by the -cellfr switch, allowing to group cells into programs and programs into chapters. The single segments will then better match with the DVD-VIDEO specs. Up to 255 cells, 99 programs and 99 chapters will be available for each segment. ...Starting from the next release 1.3... Edit - 11-09-2008. Release 1.3 is now available. Pick it at the link in the first post of the thread. It is mostly a bugfix release; the single (important) new feature is related to the support to 255 cells, 99 prgrams and 99 chapters for the MuxMan segments. Please consider the usage (and the results) of the previous -cellfr and -celltc C/L switches is changed. Last edited by Sir Didymus; 11th September 2008 at 08:51. |
|
|
|
|
24th September 2008, 13:49
|
#19 | Link |
|
AVStoDVD Dev
Join Date: Apr 2006
Location: Italy
Posts: 764
|
SD,
I have noticed that from release 1.2, the item "static memory usage" has increased. A couple of questions: 1. What does it exactly mean? I guess it is a kind of VOB vs elementary stream oversize percentage, but I need your confirmation...  2. I noticed that it increases a lot when there are many titles. How is it calculated? Bye |
|
|
|
|
29th September 2008, 20:02
|
#20 | Link |
|
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 865
|
Hi MrC!
No, no... It is just an internal parameter, only useful for statistics purposes. Within BatchMux the memory for the segments and for almost all of the "heavy" data is completely dynamic: whenever a block of memory needs to be allocated, it is issued a call to the OS (something like a "malloc"); this block is then freed when its not needed any longer. An exception is made for the strings (for instance the filenames of the source assets) and for the timecode structures (13 bytes are used for each timecode). These variables are stored within a local memory (its current size is LOC_STACK_SIZE = 131072 bytes). Timecodes are used mostly for defining the chapter points. Starting from release 1.2, with the introduction of the -chapfr and -progfr switches, the usage of the timecode structures went out as three times bigger than before. This is the reason for the increase you have observed in the parameter, which gives just the % of usage of the local stack. May I ask which level of occupancy you are seeing for the most complex projects with AVStoDVD? Cheers, SD Last edited by Sir Didymus; 29th September 2008 at 20:06. |
|
|
|
 |
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
