[VirtualDubMod] 1.5.10.2 released (updated) <2006-02-21>

[Suiryc]

As the subject say.

The changelog (not as long as in previous releases :p)


[VirtualDubMod 1.5.10.1]
Cyrius:
- Warn you when a subtitle don't have its duration set in a matroska file (instead
of throwing an error).
- Warn you if something really bad about timecodes happens when writing an mkv file.
- Fixed bug (1.5.4.1) where all streams would be muxed with a 1 frame interleaving.
- Fixed bug (1.5.4.1) where Matroska Segment size was incorrectly written.
- When editing an mkv file (without recompressing) the Aspect Ratio info is kept.
- Fixed bug where some large (>4GB) files wouldn't open.
- Fixed bug where the length of uncompressed audio streams would be wrong for OGM/MKV files.
- Fixed bug preventing Win 9x/Me users from saving sequence of images.
- Using Advanced filtering on more than one audio stream should work properly now.
- Fixed yet a few crashes when processing badly corrupted OGM files.
- Fixed bug where chapter information were incorrectly processed when muxing (would happen
when deleting a subset starting at frame 0).
- Fixed possible crash when processing corrupted MP3 VBR stream muxed in an AVI file by
Nandub or (really) old versions of VirtualDubMod.
- Fixed problem with AVI files containing an MP3 stream encoded using Dr. DivX.
- Fixed possible problem with AVI files containing MP3 VBR muxed with AVI-Mux GUI.
- Fixed problem (error -100, no video appearing in the preview windows) where XviD was
selected as decoder (instead of DivX) with OGM/MKV files containing DivX 5 video.
- Fixed broken code (resulting in problems when opening or muxing) in the DTS parser.
- Take into account the LFE channel in channel count for AC3 files.
- Readded the possibility to enqueue "Save WAV" or "Demux" as a job.
- Stream title is now written as stream name in AVI files.
- Copied VirtualDub 1.5.5 code to fix the focus stealing issues with the "Dubbing Status"
window. Also now this window remains hidden when using the /s commandline option.
- Fixed bug where some mkv files (with incorrect segment size) wouldn't open.
- Fixed bug preventing the "Audio" menu to popup under Windows NT4.
- Merged changes up to 1.5.10. Expect new exciting bugs now :>
- Removed ASF support in the code. There are better tools out there for ASF.
- Removed internal AC3 decompressing since fccHandler made an ACM codec for AC3.
- Added an option ("Adjust chapters ...") for chapters inside a stream. When enabled the
chapters time are adjusted according to the subsets (i.e. the chapters listed for a stream
are considered as the ones for the original full clip). When disabled the chapters are
only adjusted according to the start and end time of your selection (i.e. the chapters
listed are considered as the ones of the clip after you edited subsets).
- Warning (instead of errors) are triggered for some errors (when some data had no timestamp,
or when a frame had only a forward reference) inside Matroska files.
- A warning should be triggered when a VFR video stream is found inside a Matroska file.
Nb: in this case we strongly advise you to use another tool to safely process your file.
- Removed VDM specific items from the 'standard' preference windows. Use the 'VDubMod'
preferences window to setup those settings.
- Added a (track) "Name" comment in the availabe comment types. This set the track name in
AVI files (only shown by some players) and correspond to the track name in Matroska.

Belgabor:
- Included Toff's fix for the last chapter in matroska files.
- Added 'Insert Crop' in the Script Editor for AviSynth scripting. It sums up all
crops performed in the VDub filters.
- Two new options for the Script Editor. One activates single instance mode meaning
you will only have one editor window. The other one automatically pops up the script
editor when you open an avs file or loads it into an active editor window in single
instance mode.
- Fixed: Refresh [1.5.9]
- Fixed: Frameset transfer to AVS Editor [1.5.9]
- Fixed: Hotkeys in AVS Editor [1.5.9]
- Converted filename transfer to unicode.
- Partly fixed: AVS Templates (no unicode filenames and no multiple selection yet) [1.5.9]
- AVS Templates are now a part of the normal Open Dialog, replacing "Open via Avisynth".
- Fixed: tick settings not working if a file is opened via the MRU


As usual on SourceForge (http://sourceforge.net/project/showfiles.php?group_id=65889&release_id=201544).


Bugfix versions are available, see later in this thread.


Many important changes have been made in the code of VirtualDub since last release. So there may be many stupid bugs remaining ...

Enjoy

[stax76]

thanks a lot for your hard work. I did not test yet but got already a question, how is the VirtualDub code related to the VirtualDubMod code?

[Tuning]

Thanks Suiryc, Belgabor and other VDM team members.:)
Originally posted by Dolemite
thanks a lot for your hard work. I did not test yet but got already a question, how is the VirtualDub code related to the VirtualDubMod code?

Dolemite, everyone knows VDM is a derivative of Vdub. Hence code will be similar except in additions made for adding OGM/MKV/ac3/Ogg/SRT ( Many other additions which i don't exactly know :p )....etc support. It has a avisynth script editor too.:)

[stax76]

I have noticed VDM is derived from VD. I would like to know if and how the code is kept in sync

[ikarus]

@belgabor

1st:
I activated above mentioned Options in the preferences, saved and even restarted vdubmod.

this works well when using the file=>open menu,
but using drag'n'drop it won't. :(



------- dream section ---------

2nd: the import crop is very nice, but (referring to our initial chat in that other thread) in respect to usefulness to encode-addicts like me some other ideas (i hope you dont mind):

crop:
for cropping i use the "null transform" filter (since i use vdubmod only to determine my cropping and trimming values for my scripts), for your "Insert Crop" - Function i need to close both, the filter settings as well as the filterlist window and save the cropping values. this becomes unhandy when processing 10+ avs files in a row, since you'd have to reset these values for the new avs for each set cropping value manually.
if possible, it would be better to have an extra button in the cropping-settings window to set the current settings as crop values in the script, without having to save them to vdubmod filter settings before.

trim:
same as for crop, my suggestion would be 2 buttons in the cropping settings window for in/out, saving the values to in_x/out_x, and processing these on closure of the cropping settings or on pressing a third button (or each time an in/out - set is complete) to a valid trim line to the script.

these options would make it a perfect tool for me, maybe you like some of these ideas.
------------ end dream section ----------

best regards
ikarus

[Belgabor]

Originally posted by Dolemite
I have noticed VDM is derived from VD. I would like to know if and how the code is kept in sync
Thats mainly Cyrius' work. Its manual work, as far as I know using a three way diff.

[Belgabor]

Originally posted by ikarus
@belgabor

1st:
I activated above mentioned Options in the preferences, saved and even restarted vdubmod.

this works well when using the file=>open menu,
but using drag'n'drop it won't. :(



------- dream section ---------

2nd: the import crop is very nice, but (referring to our initial chat in that other thread) in respect to usefulness to encode-addicts like me some other ideas (i hope you dont mind):

crop:
for cropping i use the "null transform" filter (since i use vdubmod only to determine my cropping and trimming values for my scripts), for your "Insert Crop" - Function i need to close both, the filter settings as well as the filterlist window and save the cropping values. this becomes unhandy when processing 10+ avs files in a row, since you'd have to reset these values for the new avs for each set cropping value manually.
if possible, it would be better to have an extra button in the cropping-settings window to set the current settings as crop values in the script, without having to save them to vdubmod filter settings before.

trim:
same as for crop, my suggestion would be 2 buttons in the cropping settings window for in/out, saving the values to in_x/out_x, and processing these on closure of the cropping settings or on pressing a third button (or each time an in/out - set is complete) to a valid trim line to the script.

these options would make it a perfect tool for me, maybe you like some of these ideas.
------------ end dream section ----------

best regards
ikarus

1st: probably an oversight =)
2nd: I'll see what I can do.

[Suiryc]

Originally posted by Dolemite
thanks a lot for your hard work. I did not test yet but got already a question, how is the VirtualDub code related to the VirtualDubMod code?
As already mentioned VirtualDubMod is derived from VirtualDub. So both programs share the same core (GUI, stream, and dubbing systems). This core was unfortunately meant to deal with AVI (and e.g. only CBR audio). Starting with version 1.5.0 Avery Lee rewrote great parts of the code to make it cleaner, more efficient and less bug-prone. He made those changes keeping in mind that some people (like us) made mods of VirtualDub (he tried to make changes that still let us, sometimes more easily than in the past, mod it). And we all thanks him for that.

However the main code is still meant to deal with AVI (and CBR audio :p), so in some parts of the core we had to add some extensions (in other words hacks :p) : e.g. the stream and dubbing systems has been extended a bit to support more than one audio stream when muxing, and also to support VBR data.

Each time a new version is released we download the source code and merge the changes (from the previous version) in our code.
This is done by diffing the files in 3 folders : the previous version of VirtualDub, the new version of VirtualDub, and our own code.
This work has to be done manually because some modifications between 2 versions of VirtualDub can have been done in a file that we already modded (so we can't use any program to apply automatically the changes without risking to break our code).
If the changes belong to a part of the code we didn't modified, then all is fine we can copy and paste it in our code. However if the change belong to a part we already modified, then we have to merge it and adapt it to the our mods (which is sometimes difficult since the mods can have effects in other parts of the code).

Just to give you an idea of how difficult it can be, I will take as exemple the 2 latest versions we released (1.5.4.1 and 1.5.10.1).
The most difficult part in those versions (for us to merge) was the changes Avery Lee made in version 1.5.4 and 1.5.5 of VirtualDub.
For each version he mainly changed 80-95% of the code in 4-5 files representing more than 5000 lines of code.
All would have been fine if we already hadn't modified ourselves 80-95% too of the very same code for VirtualDubMod.
So we had to merge manually all this mess. For each merging it actually took me more than 24 hours of work (without break - cumulated time) to do this merging. No need to mention you better know what you are doing (i.e. understand what changes were made, how they affect VirtualDub behaviour, and so how we would have to apply them in VirtualDubMod to get the same behaviour without breaking our mods), and don't rush unless you wanna break the whole thing. And once the merging is done you need to test a bit to be sure you didn't left stupid bugs ...


@ikarus
For your dream it ma also be a good idea to mention it on a VirtualDub forum (http://virtualdub.everwicked.com) Avery Lee sometimes visit. Other people may benefit from what you ask.

[sh0dan]

:thanks:

[HarryM]

Capture mode is very unstable against to v1.4.13.
I newest version capturing crashing, in v1.4.13 all O.K.

[stax76]

great explanation:thanks:

[K-Dash]

Thanks for your good work.

[erratic]

Originally posted by HarryM
Capture mode is very unstable against to v1.4.13.
I newest version capturing crashing, in v1.4.13 all O.K.
Same problem here. As soon as I start capturing with 1.5.10.1 I get this error message:

Access Violation in capture routine.

VirtualDub has intercepted a crash condition in one of its routines. You should save any remaining data and exit VirtualDub immedialtely. If you are running Windows 95/98, you should also reboot afterward.

VDubMod 1.5.4.1 captures just fine. I have an ATI AIW 8500DV card, which I have to initialise first with a WDM capture app (I use VVCR for that). After that I can capture with VDMod 1.5.4.1 but not with 1.5.10.1.

[Leak]

When I load a video and use ALT-Tab to change to a different application, VirtualDubMod closes, but doesn't produce a crashdump or anything. If I play the video for a second or so before using ALT-Tab, it won't crash, even if I open another file in it.

Also, dragging a file into a newly opened VirtualDubMod window also kills the application. :(

np: Kid606 - Who Wah Kill Sound (Kill Sound Before Sound Kills You)

[HarryM]

Originally posted by erratic
Same problem here. As soon as I start capturing with 1.5.10.1 I get this error message:

Access Violation in capture routine.

VirtualDub has intercepted a crash condition in one of its routines. You should save any remaining data and exit VirtualDub immedialtely. If you are running Windows 95/98, you should also reboot afterward.

VDubMod 1.5.4.1 captures just fine. I have an ATI AIW 8500DV card, which I have to initialise first with a WDM capture app (I use VVCR for that). After that I can capture with VDMod 1.5.4.1 but not with 1.5.10.1.

I have totally similar problem with capture mode (see above).

[Leak]

Originally posted by Suiryc

[VirtualDubMod 1.5.10.1]
- Copied VirtualDub 1.5.5 code to fix the focus stealing issues with the
"Dubbing Status" window. Also now this window remains hidden when
using the /s commandline option.


Actually, I quite liked the status video being visible while VirtualDubMod does it's work; could you please make this new behaviour an option? If the main window would be minimized if started with /s that'd be more useful, as it's just a big window that doesn't do anything anyway while VirtualDubMod is working, and if it's minimized, it'll at least show the progress on the taskbar... :)

np: Monolake - Tetris (Momentum)

[North2Polaris]

Originally posted by erratic
I have an ATI AIW 8500DV card, which I have to initialise first with a WDM capture app (I use VVCR for that). After that I can capture with VDMod 1.5.4.1 but not with 1.5.10.1.
@erratic

How do you "initialize first" with a WDM capture app like VVCR?

Thanks.

[erratic]

Just run VVCR (or another DirectShow/WDM capture app) and then close it again. That's all. VirtualDubMod (1.5.4.1) should now work too (no problem with my AIW 8500DV anyway).

[hoola]

i am getting the same access violation crash error as stated above. this occurs when i try to capture, going back to previous version untill fixed.. thanks


running winxp pro sp1 and all pre sp2 hotfixes
tvwonder ve capture card / btwincap drivers

[dimitrius]

well, this is nice build.

I like the new menu setup while encoding (having 2 menus instead of 1 two-column). I think I might have noticed a bug:

When I open a video (any) at the bottom of the window I see the usual tick marks (in my case it's almost always a line since I open 90min+ movies) which is normal, if I cover this window fully with another window, then switch back to vdubmod window, the line dissapears and only two ticks remain (at the start and the end). It doesn't seem to redraw. I haven't tried it in VDUB so I can't say whos code has this problem. I have only used normal "Frames" tickmarks. This happens only after opening a video.

Another thing that's been there for ages I think is that neither vdub nor vdubmod seem to save options like vertical display (which I often use)

Does anyone actually use RealTime Profiler? or does anyone change dynamic compilation options? To me they seem to be superfluous options. Just a thought...

edit:
em, just read "Free Pies" thread, when I say "I think I might have noticed a bug" I mean 'I think I might have noticed a "a potential problem"' :)

[North2Polaris]

Originally posted by erratic
Just run VVCR (or another DirectShow/WDM capture app) and then close it again. That's all. VirtualDubMod (1.5.4.1) should now work too (no problem with my AIW 8500DV anyway).

I am trying to understand this. What does this do? Isn't VirtualDubMod still using the VFW wrapper?

[erratic]

Yes, VirtualDub(Mod) and AVI_IO use the wrapper.
http://www.doom9.org/capture/capturing.html
On my system they only work after running a WDM capture program, like VVCR or ATI MMC.

I use VirtualDubMod because VVCR creates AVI files with internal audio and video offsets (http://forum.doom9.org/showthread.php?&postid=407967#post407967). VFW capture apps don't do this.

[Suiryc]

I think the bug in capture mode is now fixed.
You can try the bugfix (http://sourceforge.net/project/showfiles.php?group_id=65889&release_id=177123) version.

[erratic]

Yes, after installing the bugfix version I can capture just fine with VirtualDubMod 1.5.10.1.

[unimatrixzer0]

When you click on "About VirtualDubMod" it crashes ;) lol

[Suiryc]

Yet another bugfix (http://sourceforge.net/project/showfiles.php?group_id=65889&release_id=177123) version.
This one fixes 'minor' bugs when writing Matroska files, so I recommand you to dowload this version if you make Matroska files. It also fixes some other issues (the ticks in the trackbar, some problems when decompressing audio in specific cases).

[mkanel]

I'm using the recent bugfix release of VirtualDubMod 1.5.10.1 build 2389. If I use the Save As (F7), or or Preview output from start (ctrl-F5) functions with an AVS file they work unless I have refreshed the AVS editor.

Example: I open a very simple AVS such as AVISource("D:\Capture.avi")
Everything works fine until I open the script editor. Just pressing F5 for refresh is enough to cause the problem. Now if I try to save or preview from the start the dub box flashes on the monitor and then disappears.

I've swapped 1.5.10.1 with 1.5.4.1 a couple of times and get the same results, 1.5.4.1 works fine.

That's for all the hard work, in general I like the new release.

Mike.

[Suiryc]

Originally posted by mkanel
I'm using the recent bugfix release of VirtualDubMod 1.5.10.1 build 2389. If I use the Save As (F7), or or Preview output from start (ctrl-F5) functions with an AVS file they work unless I have refreshed the AVS editor.

Example: I open a very simple AVS such as AVISource("D:\Capture.avi")
Everything works fine until I open the script editor. Just pressing F5 for refresh is enough to cause the problem. Now if I try to save or preview from the start the dub box flashes on the monitor and then disappears.

Ahah, true.
Seems like a little bug is remaining there. Actually when you refresh it set the selection start on the first frame, but also the selection end on this frame. i.e. it selects 0 frames to be processed ^^;
Will fix that ASAP.


Fixed in our CVS. You will have to wait a bit for the next bugfix to get it :p

[cweb]

Originally posted by Suiryc
Yet another bugfix (http://sourceforge.net/project/showfiles.php?group_id=65889&release_id=177123) version.
This one fixes 'minor' bugs when writing Matroska files, so I recommand you to dowload this version if you make Matroska files. It also fixes some other issues (the ticks in the trackbar, some problems when decompressing audio in specific cases).

Thanks for the update!

[Leak]

Originally posted by Suiryc
Fixed in our CVS. You will have to wait a bit for the next bugfix to get it :p

Not to pester you (I hope), but even the bugfix version shuts down the moment I switch to another application using ALT-TAB (as I often do) after loading an AviSynth script. It doesn't do this if I don't use the keyboard (i.e. clicking on the taskbar or another application's window), and it doesn't do this after letting the file play for just a second before using ALT-TAB.

I can't be the only one experiencing this, can I? *wonders*

(Seems to me as if something only got half-initialized since starting playback solves it, but why it would break on ALT-TABbing is beyond me... :confused: )

I'm using Windows 2000, the latest bugfix version (Dec 9th) of VDubMod and AviSynth 2.53 on a P4 2.4GHz with the following script:


MPEG2Source("e:\DVD\WitchHunterRobin_1\WitchHunterRobin_01\VIDEO_TS\Video.d2v",cpu=0,iPP=true,idct=6)

a=last
b=last.ConvertToYUY2()

a=a.Telecide(order=1,guide=0,gthresh=5,post=1,hints=true,back=0,vthresh=15,show=false)
a=a.KernelDeint(order=1,sharp=true,twoway=false,threshold=3,map=false)
a=a.Decimate(cycle=5,mode=0,show=false)

b=b.ConvertFPS(23.976).ConvertToYV12()

a.Trim(0,3984-1) + b.Trim(3984,6144-1) + a.Trim(6144,32400-1) + b.Trim(32400,0)

Crop(4,4,712,474)

UnDot()
MipSmooth(preset="AnimeHQ",temporal=0,temporal_chroma=0)
TemporalSoften(4,4,8,15,2)

LanczosResize(640,480)


As soon as I ALT-TAB away from the application window to Mozilla for instance, it just vanishes without any error messages (with no "Application Popup" message in the Windows event log, either). The same behaviour doesn't occur when I use version 1.5.4.1, which I have installed in a different directory.

np: Kid606 - The Illness (Album Version) (Kill Sound Before Sound Kills You)

[Suiryc]

No such problem here :/
Could you try to delete the settings in the registry ?
Launch regedit and delete [HKEY_CURRENT_USER]->[Software]->[Freeware]->[VirtualDubMod].

Note that this will reset all your preferences to default values.

[Leak]

Originally posted by Suiryc
No such problem here :/
Could you try to delete the settings in the registry ?
Launch regedit and delete [HKEY_CURRENT_USER]->[Software]->[Freeware]->[VirtualDubMod].

Note that this will reset all your preferences to default values.

Well - that did the trick. I dunno for the life of me why that would cause such strange behaviour, but it seems the config information in the registry isn't exactly upwards compatible... :)

Not that I can't redo the configuration in about 30 seconds... ;)

EDIT: And while I'm on a roll anyway - it's quite useful that you can start playing the video using SPACE, but I can't find a key to stop playing using the keyboard, but I guess that's quite handy. How about making hitting SPACE again stop playback if the video is currently playing?

2nd EDIT: Actually, I just found out what made it crash - if I disable "Display output video" either in the preferences or in the options menu prior to opening the video file (as I always do, as I'm only ever using Fast Recompress in conjunction with AviSynth), it crashes. If I turn the output pane on, it works.

I guess that should help to track the cause down... :) (And actually, the same thing happens in the original VirtualDub 1.5.10, now that I've tried it - OOPS. Well, gotta go file a bug report against that as well.)

np: Triosk Meets Jan Jelinek - Mis-Leader (1+3+1)

[zurv]

Is there a 64 bit complied version of it yet? :)

It will give me a reason to install the winXP-64. (i have an AMD 64 chip...) I'd be happy to report any bugs/speed diff with it :)

[geoffman]

Originally posted by zurv
It will give me a reason to install the winXP-64. (i have an AMD 64 chip...) I'd be happy to report any bugs/speed diff with it :) The current windows XP 64 bit version will not run on an AMD 64 CPU, it was specifically made for Intel's Itanium 64 bit CPU's, which uses a totally different architecture than X86.

Rumour has that Microsoft is building a 64 bit version of XP for X86 CPU's, dunno when it's going to be released though.

[zurv]

Its been in beta for some time. pretty stable now for everything but some 3d games. It should be out *soon*

[geoffman]

zurv, longhorn is in beta too, but it's not scheduled to be released until 2006! ;)

EDIT OOPS I meant alpha PDC build, I feel so stoopid now! :o s

[Suiryc]

Hi everybody. A little gift (http://sourceforge.net/project/showfiles.php?group_id=65889&package_id=69373&release_id=177123
) for you :) (the new one is build 2407 ;))

Cyrius:
- Fixed: (1.5.10.1) an input file containing audio would remain opened even
after "Clode video file" (thus preventing from deleting the file).
- Fixed: (1.5.10.1) crash when starting capture.
- Fixed: (1.5.10.1) ticks in the trackbar. Now have the same behaviour than
VirtualDub (when in "Frames" mode).
- Fixed: (1.5.10.1) not enough space was reserved for the KaxSeekHead at the
beginning of Matroska files. Added warnings (logs) when this happen.
- Fixed: duplicated references when writting 2 KaxSeekHead in Matroska files.
- Fixed: (1.5.10.1) logs shown 2 times when saving a Matroska file.
- Fixed: issues when decompressing AC3 (1.5.10.1) or audio using ACM.
- Fixed: issue with the input audio filter (graph) that would stuck the dubbing.

Since last bugfix (build 2389):
- Fixed: (1.5.10.1) problem with empty selection when doing a Refresh.
- Merged latest version of VirtualDub Sync by Andreas Dittrich (1.5.4, Sync 1.04)
- Fixed: livelock that could appear in some specific cases (the program encountered
a problem and is aborting the dubbing, but a livelock prevent it to properly end
the dubbing as well as showing you the error causing the problem).
- Fixed: issue when processing the very beginning of some AVI with MP3 VBR (this
problem would cause the previously fixed livelock).
- Added: 'Delete' key deletes entries in the stream, comment & chapter lists.

As explained by Belgabor in this thread (http://forum.doom9.org/showthread.php?s=&threadid=67292) SourceForge recently made possible for people to donate for projects.
For this system to be enabled the admins of a project must all agree, and we (ChistianHJW, Belgabor and myself) all agreed on donating 100% of your donations (http://sourceforge.net/project/project_donations.php?group_id=65889) to the Open Source community (see details on the page) :) :thanks:


Merry Christmas ^_^

[acrespo]

I found a problem and I don't know if it is a avisynth or virtualdubmod error.

I opened a AVS in virtualdubmod. At the same time this AVS is opened in notepad. After open in virtualdubmod, I change some filters settings (Convolution3d("animeHQ") instead Convolution3d("animelq") for example) and when I choose "Refresh" in Edit menu, the audio was gone. The only way to audio open again is open AVS file from File/Open menu, the refresh function can't open audio again. Sometimes it's not occuring after the first AVS change, but in the second or thrid.

This problem is occuring in virtualdubmod 1.5.4.1 too.

[avexplorer]

I can't use the script editor with Vdubmod 1.5.10.1 (even the latest release - build 2407 :( ). Vdubmod 1.5.4.1 was working fine...

Loading a script with File->Open video file (.avs file) is ok, but when I click Tools->Script editor it always crashes. Please check the crashinfo.txt at SourceForge (http://sourceforge.net/tracker/index.php?func=detail&aid=858170&group_id=65889&atid=512619).

The only way I can see the script editor is when there is no .avs file loaded, but when I try to do something like open, save or revert, it crashes too.

I'm using Win98SE+AMD Athlon XP 2200+ with an Epox 8RDA+ motherboard. The Avisynth version is 2.53.

Is there anybody else having the same problem ? :confused:

[Snakeisthestuff]

Hi i have exactly the same problem. If i open the AVS Editor before i load an avs everything works. But after i loaded a simple avs and opened then the AVS Editor VirtualDubMod crashes with a typical close or details Windows error. I`am using VirtualDubMod 1.5.10.1 build 2407 and Avisynth 2.53.

System:
AMD 1600+
Win98 SE

[avexplorer]

Hi i have exactly the same problem. If i open the AVS Editor before i load an avs everything works. But after i loaded a simple avs and opened then the AVS Editor VirtualDubMod crashes with a typical close or details Windows error. I`am using VirtualDubMod 1.5.10.1 build 2407 and Avisynth 2.53. System: AMD 1600+ Win98 SE

I guess this is a Vdubmod 1.5.10.1 Win98SE bug...

Does this happen with anyone using WinXP ?

[stax76]

seems like the range encoding is broke, it encoded the range twice so output is twice as long/big

VirtualDub.Open("E:\\records\\MTV.avs",0,0);
VirtualDub.video.SetMode(1);
VirtualDub.subset.AddRange(0,22020);
VirtualDub.video.SetCompression(0x78766964,0,10000,0);
VirtualDub.SaveAVI("E:\\records\\MTV_FirstPass.avi");

[Leak]

Originally posted by Dolemite
seems like the range encoding is broke, it encoded the range twice so output is twice as long/big.

Try adding

VirtualDub.subset.Clear();

before your AddRange command; as of this version the whole file is selected by default IIRC.

np: B. Fleischmann - 02/00 (Welcome Tourist)

[avexplorer]

I've installed WinXP and the script editor crash is gone.

Is there anyone running Win98SE, Vdubmod 1.5.10.1 with no crashes using the Script editor? :confused:

[Belgabor]

Its probably an unicode issue. Didnt have time to look into it yet.

[stax76]

Try adding

VirtualDub.subset.Clear();


thanks, I'll try it and report back if it still don't work

[kilg0r3]

Currently it seems to be something like common sense in the xvid secrtion here that vdmod 1.5.10 is buggy with xvid. I must admit, however, that I do not know in what respect. Are those problems alreday fixed?

cheers!

[stax76]

also interesting to know is if Suiryc stopped working on VDM because of his new project

[gatormac]

Originally posted by kilg0r3
Currently it seems to be something like common sense in the xvid secrtion here that vdmod 1.5.10 is buggy with xvid. I must admit, however, that I do not know in what respect. Are those problems alreday fixed?

cheers!

I personally have found those statements to be false. I've been using VDM 1.5.10 and XVID 1.0 RC2 and now RC3 with no problems whatsoever.

Well, the only thing that might be considered a problem is how VDM handles certain shades of blue. I've encoded School of Rock using Gknot, VDM, and Xvid...everything looks great except for some points in the concert scene near the end where flourescent-type blue lights mesh with the dark background and fog....makes things look very pixelated.

The only reason I assume it is VDM is that eyeballing the video in Gknot it looks fine, but when I load the .avs file in VDM it looks pixelated (only where there is that flourescent blue on the screen). For some reason it doesn't look pixelated within VDM if I ConvertToRGB() on the last line of the .avs file, but the resulting .avi file still looks pixelated, but not quite as bad without the ConvertToRGB().

Its not a bitrate issue as I like to encode at 80% after running gknots compression test...my encodes usually run anywhere from 1 to 1.5GB. Everything else is pretty straight forward, I set XVID no QPEL, no GMC, no packed bit stream, MPEG, B-VOPs 2-1.50-1.00, MSP 6, VHQ 1, chroma motion on, Quants 2-31, trellis enabled. I like to keep things simple and hopefully compatible with standalones (whenever they make a decent one). My encodes all look great, this is the only exception. I even set that scene to a zone with a Q of 1 and it still looks pixelated (especially when they show the boy with the fog machine...look at his face...frames 140280 to 140370).

Is anyone else having this problem?

[Suiryc]

Originally posted by Dolemite
also interesting to know is if Suiryc stopped working on VDM because of his new project
Nope.
I am just lacking free time at the moment.

@gatormac
Maybe it's an issue regarding the colorspace. VDM may display YV12 while GKnot may display YUY2 or maybe even RGB (dunno how it works there).