VirtualDubMod 1.4.11.2 released

[Belgabor]

[VirtualDubMod 1.4.11.2]
Belgabor:
- Scintilla component for script editor. Be sure to get SciLexer.dll and AviSynthLexer.lexer
* Coloring for AVISynth keywords. Red denotes a fuzzy match (likely a type error).
Coloring for external keywords (plugin filters) is pending till i can get the info via
AviSynth. Same holds true for the implemenation of parameter hints.
* Completion with Ctrl+Space or Shift+Space
* Brace Highlighting. White on red denotes a mismatch.
* Ctrl+Shift+Alt-C/U Comments/Uncomments selected lines
* Ctrl-I Imports the Frameset (= the effective video stream created by selecting ranges and
hitting 'Delete'. I guess you get what I mean ^^) as Trim statements.
- Updated Sync to 1.03

Cyrius:
- Audio :
* fixed some bug/crash when previewing AVI with 2 audio streams.
* fixed bug causing all audio data being written in the same audio track (i.e. making
the secondary audio track and the generated AVI file useless).
* fixed bug (from Nandub) making impossible to use two audio tracks when deffering processing.
* "AVI information" window now contains information about the secondary audio stream in AVI.
* made a little change for the "Preload skew" tab in "AVI Information". Should be more
accurate than usual ;). In certain cases this value is however not really revelant :
-> for AC3 streams muxed in "Frame mode" (see below), you should only see 1536 samples
-> for MP3 streams muxed a la Nandub, you should see something around 1152 samples (or much
more if your file contains an ID3 tag). The more variable is the bitrate, the more will
vary the value around 1152.
In those cases it is the way the data are muxed that make this value irrevelant, but rest
assured that the real preload is neerer (if not equal) to what the user wanted when muxing ;)
* selecting "No audio" in Audio tab and "AVI audio" in "Secondary stream" tab let you save
the secondary audio stream when using "Save WAV".
* added a "Demux audio" feature that produce same output as "Save WAV" without the WAV header.
* while dubbing information about secondary audio stream are shown again (like in Nandub). When
writing an OGM output, the "Audio2 data" field also counts the other streams you are muxing.
* moved "Audio -> Secondary stream" to its own top-level menu : "Audio2".
* added a "Nandub VBR MP3 compatibility mode" when opening AVI files (disabled by default).
This should allow you to work on VBR MP3 streams as in Nandub.
Once again it is just for your convenience. I suggest you to use CBR streams in AVI files,
or to use OGM format for VBR audio ...
* added an "AC3 Frame mode" when opening AC3 files (disabled by default).
This should force VirtualDub to handle AC3 stream properly when cutting (i.e. not to cut in
the middle of a frame, but on frame boundaries). Seems to work on my test file.
I disabled both of these features by default because I cannot guarantee no side effect.
So : USE WITH CARE !!!
The fact you used those features or not is saved when using "Job List".
- Some minor GUI changes :
* made the Change Log / Release Notes window resizable (and a bit bigger by default)
* OGM Information use the same window than above (so resizable too, and Richedit now)
* gave VirtualDub icon to Hex Editor, RIFF Chunk Tree, Job List, OGM inputs / comments windows
and previous ones too :)
* file position (shown for OGM files) a bit more accurate and also shown for AVI files now
- Added "Go to last keyframe" (Ctrl+Shift+J) (Nandub feature) in Edit menu.
- Fixed an annoying bug (VirtualDub) with seeking to previous keyframe when being at the end of
the clip and having masked / deleted subsets.
- Fixed a bug (VirtualDub) causing audio being out of synch when saving a part of a clip
(not beginning at the first frame of the clip) where subsets have been masked / deleted.
- VirtualDubMod jobs are now located in VirtualDubMod.jobs instead of VirtualDub.jobs


Be sure to get the new dll package and the AviSynth lexer for full functionality!

Cheers & have fun
Belgabor

[Suzahara]

Very nice work, I like the new AVS features. The trim features especially help me on my TV caps where I cut out commercials, a lot easier than typing in all those frame numbers by hand.

[hakko504]

...and I take it you are already working on merging the new 1.4.12 into your Mod?

Nice work though, I haven't used the regular VD since your mod arrived.

Edit: Corrected spelling. What the hell is wrok?

[Koepi]

I can't get it to cmpile: the worst error is in the vorbis routines:

D:\data\PROGTEMP\Virtualdub\VirtualDubMod\Command.cpp(582): error: identifier "WAVEFORMATEXTENSIBLE" is undefined
if( (audioSelected->getFormatLen() >= sizeof(WAVEFORMATEXTENSIBLE))

What am I missing?

I want to spit out a version that suppresses the delay frames and doesn't write it into an avi (VidoSequenceCompressor, line 387 ff.:

if (pbiOutput->bmiHeader.biCompression == '05xd' || pbiOutput->bmiHeader.biCompression == '05XD'
|| pbiOutput->bmiHeader.biCompression == 'divx' || pbiOutput->bmiHeader.biCompression == 'DIVX') {
if (pbiOutput->bmiHeader.biSizeImage == 1 && *(char *)pOutputBuffer == 0x7f) {
bNoOutputProduced = true;
}
}

) ... Maybe you can put up a new compiled binary with that?

Thanks
Koepi

[Suiryc]

:)

There was a discussion about that in the XviD section (in this thread (http://forum.doom9.org/showthread.php?s=&threadid=38942)).
The XVID FourCC code will be added in the test (as you wanted to do here).

Otherwise I think you need the Platform SDK to get it compile correctly.

[Suiryc]

Some reports of blue tinted clips have been reported to us.
It may be related to the recent YV12 support added in VirtualDubMod.

Can someone confirm that using FastRecompress mode with DivX 5 or XviD leads to blue tinted clips ?

Thks, and sorry for the inconvenience :(

Some more info on the issue : it seems to happen when recompressing a DivX / XviD clip.

[JuanC]

I can successfully read and edit mpeg2 captures on a Pentium 3, but on my Pentium 4 I got odd results: the same ones you get when you select 64bit SSE2 MMX as your iDTC algorithm to create your D2V project in DVD2AVI and you try to read it within avisynth using the original MPEG2DEC (without the SSE2 implementation): a grey background with some scattered green dots in a regular pattern.

In fact, the d2v files generated by VirtualDubMod 1.4.11.2 are exactly the same except for the line "iDCT_Algorithm=5" in the P4 and "iDCT_Algorithm=2" in the P3.

Is there a way to manually select the iDTC algorithm to be used in VirtualDubMod?

BTW: I can't load these d2v files (generated by VDmod) using mpeg2dec2 into avisynth. It pops-up the message: "Avisynth open error: unrecognized exception" !?

[Bungholio]

ok, um i asked some1 about how to open either vobs or d2vs with Vdub, simply cause im familiar with encoding to divx from mpeg with this prog, adn they said that if i use avisynth i should b able to, furthermore that vdubmod would be even better. now um i managed to find your site at sourceforge, but ive had a few questions/problems...uhm firtly, do i use

VirtualDubMod_needed_DLLs_251102
or
virtualdubmod_needed_dlls_301002

secondly uhm, ive put all the avisynth files, and the .lexer in the vdubmod.exe folder, along with the 251102 dlls for now, and i cannot open either d2v or vob, so i really need some help, if i shouldnt be using vdub to go from dvd to divx, then ill go to gardianknot, but i was just wodnering if this could work, cause like i said im familiar with this prog. uhm so any tips would be greatly appreciated.

[Bungholio]

lol. omg guys, sorry, please ignore my problem with opening vobs in your program, i got it to open one, but if you guys have any tips, let me know, thanks :)

[Bungholio]

also, uhm it is not possible to open multiple vobs, this is a inconvience, but only a small one, i will have to join the avi's after. oh and, im having trouble getting the audio out of the vob, i dunno whats wrong. even if i was able to import with v-dubmod a wav or mp3 of the audio extracted with say dvd2avi, how can i control the sound being on the right place if i cant open multiple files? thanks. ill keep trying...

[lighty]

Originally posted by Suiryc
[BThere was a discussion about that in the XviD section (in this thread (http://forum.doom9.org/showthread.php?s=&threadid=38942)).
The XVID FourCC code will be added in the test (as you wanted to do here).[/B]

Ehhh- call me stupid but I don't get it- is XviD FourCC support already implemented or not?

[Suiryc]

Not yet.
It is in the CVS now, and will be available in the next release (along with VirtualDub 1.4.12 changes, which are also in the CVS now).

[lighty]

Ahhh... I cannot wait for it- I am tired of manual synching.

[Ookami]

A recommendation:

How about adding the "tagging" feature of Nandub? And is there a possibility to make it both WMP 6.4 and WMP 8 compatible?

Cheers,

Mijo.

[Suiryc]

Originally posted by Ookami
A recommendation:

How about adding the "tagging" feature of Nandub? And is there a possibility to make it both WMP 6.4 and WMP 8 compatible?

Cheers,

Mijo.
If you are talking of the "Title", "Author", "Copyleft" and "Comment" fields that can be filled when saving to an AVI, I can't make them available under WMP6.4 and WMP8 (I tried a lot of AVI tags but none was shown under WMP8).

[pulco-citron]

Originally posted by Bungholio
also, uhm it is not possible to open multiple vobs, this is a inconvience, but only a small one, i will have to join the avi's after. oh and, im having trouble getting the audio out of the vob, i dunno whats wrong. even if i was able to import with v-dubmod a wav or mp3 of the audio extracted with say dvd2avi, how can i control the sound being on the right place if i cant open multiple files? thanks. ill keep trying...


The trick to open multiple vob files is to open a .txt file instead. This vts_xxx.txt file must have been created with smartripper (2.34 and 2.41 tested)


Audio support is currently limited to extraction to disk (no "avi audio"). Afterwards you can load it with the audio menus if you want to keep the original AC3 or possibly after transformation with an external application.

Audio support works a lot better with .txt files than with .vob. This should be better for vobs in the next release (1.4.13.something).