A short note to inform you that Nandub 1.0 rc1 is now available. As usual, you
will find it on http://www.nandub.org/
From the readme.doc :
I feel that the feature set is now fairly complete and the only feature I'll
add will be the support of OpenDivX when it'll be available. In the meantime,
I'll correct the bugs which will (most probably) be reported.
*** Added : support for a secondary audiostream. You can now mux 2 audiostreams
with Nandub. I didn't test many combinations, but things like 2x VBR MP3, 2x
AC3, VBR MP3 + CBR MP3 (as WAV), etc, are possible. Due to the amount of
code added, it would be very surprising that no bugs arise...
*** Added : upon request, max compression level for keyframes have been
reintroduced, but, in order to avoid any nasty side-effect and to preserve
source code maintainability, it will only work in a specific situation :
first, you must have collected scene changes information in the first pass
and second, the setting will be taken into consideration only if inferior to
the other max CLs. So, it won't affect one-pass encodes and quality control
mechanisms (AntiFreeze/AntiShit) won't respect it either.
Now, let me make myself _very_ clear : if you get any kind of dropped frames
problems with this feature enabled, I won't freakin' care ! Don't use it,
period ! It's disabled by default (31), just don't touch it. Also, don't
even think about requesting a 100% enforcing of this setting, it's coded as
a "best effort" and I won't go any further than that.
*** Solved : there has always been a problem with subsets and ranges in Nandub.
It should work ok from now on, provided you follow the simple rules
described below. For those who don't know what ranges and subsets are, a
brief explanation. Let's assume we have a source which frames range from 0
to 99999. When you select frames from 48000 to 50999, you have defined a
range, which size is 3000 frames. Now, as soon as you hit the 'Delete' key,
*poof* the range disappears and you have now a subset, which size is 97000
(100000-3000). So :
- if you need to completely disregard some portions of the video-source
(like ignoring commercials in a TV capture), you will use subsets, in both
passes. (erm, before you ask, yes, the same ones <big grin>)
- if you want to reencode a segment of the video, or if you want to do a
small test on a segment (see if your 2nd pass settings are ok), you will use
ranges, in the 2nd pass only.
Last note: for those of you who have complicated needs like use 3 appended
AVI files as source and cut a couple commercials in these files, you'll
probably have far less problems by feeding Nandub with a small avisynth
script (that's what I do myself)
*** Changed : upon request, the 'Always on top' setting of the status window is
now saved across encodes, that is, if you check it in the first pass, it
will be checked in the 2nd as well (unless you restart Nandub in between)
*** Changed : when you load an external AC3 audio source, a message box pops up
with the various details of the AC3 file you selected. This box will now
last for 10 seconds maximum, so that it doesn't stop a 'Two Passes...' or a
job in the middle of the task.
*** Cosmetic : Since I know VirtualDub, I've always been extremely annoyed by a
tiny visual bug. When the video tab of the status window is partially
covered on its right side, the visible portion of the graph isn't correctly
updated. I've finally found out where it came from (yeah, I know, I should
go get a life instead of tracking bugs like this one... *sigh*)