Printable Version of Topic
Click here to view this topic in its original format
Unofficial VirtualDub Support Forums > News / Announcements > Virtualdub 1.6.5 Released


Posted by: phaeron Apr 4 2005, 04:57 AM
QUOTE

Build 23350 (1.6.5, experimental): [April 4, 2005]
  [features added]
  * Script: Added Sylia.Atoi(), Atol(), and Atod() functions to allow
    conversions from string to value.
  * Script: Added VirtualDub.Log(string) command to output to log output
    (or console).
  * Added vdub.exe launcher for basic command-line driven operation.
  * Added multiple undo/redo for timeline edits.
  * Added /? switch to list command-line options.
  * Added support for reading paletted BMPs.
  * Dub input format is now reported in the log.

  [bugs fixed]
  * Script: Binary operators sometimes promoted the wrong way, i.e. double +
    int -> int.
  * Script: The old form of the Open() command didn't choose the right
    driver when a specific driver was requested, due to sorting by priority.
  * Script: Fixed random crash when adding video filters after opening a
    video file.
  * Script: Fixed crash when issuing SaveWAV() command with no audio stream.
  * Capture: Fixed race condition induced random crash when RGB filtering
    and accelerated preview were both enabled.
  * Capture: Capture stats were not updated while frame dropping was
    occurring, which sometimes made it hard to diagnose timing problems.
  * Capture: Added adjustable limit on length of burst inserts when timing
    anomalies occur, to prevent the app from locking permanently on a very
    bad timing glitch.
  * Capture: Audio device was not auto-saved.
  * Capture: Fixed crash when attempting to capture with an unsupported
    video format (MPEG-1/2, interleaved DV, etc.).
  * MPEG-1 video decoder occasionally glitched due to a missing end tag.
  * Removed dumb debug code that was causing a "???" message box to appear
    when unrecognized command-line flags are seen.
  * Fixed display panes not always updating properly.
  * Fixed rare crash if an MPEG-1 open failed extremely early.
  * Fixed cases where the render start/end point wasn't updated properly
    when a selection bound was used to "push" the other, i.e. "set end"
    before start, or vice versa.
  * Paste (Ctrl+V) wasn't deleting the current selection before doing the
    insert.
  * Hex editor: Scroll bar thumb wasn't reset to top when loading a new
    file.
  * Fixed a bunch of busted paletted converters.
  * Fixed dialogs that had swapped OK/Cancel buttons.
  * Fixed conflicting accelerator for Audio > Conversion menu option.
  * Fast recompress mode now tests source format before UYVY and YUY2.
  * Y8 AVIs weren't accepted even though they could be generated.

  [regressions fixed]
  * Capture: "Hide on capture" now works.
  * Capture: Preview/overlay display commands toggle once again.
  * Priority drop-downs in preferences didn't have vertical scroll bars.
  * Top-down uncompressed RGB AVIs weren't handled properly.
  * Fixed busted non-MMX XRGB1555>XRGB8888 converter.


Posted by: stephanV Apr 4 2005, 09:16 AM
yay cool.gif

Posted by: stephanV Apr 4 2005, 08:48 PM
it would be cool if the "run video analysis pass" could be added to the joblist from the GUI smile.gif

bug:

maybe there is something wrong with YV12 decoder routines: i fed it 716x428 through a AVS script and it gave me this error:

VideoSourceAVI: uncompressed frame 0 is too short (expected 460528 bytes, got 459672)

It seems to me the expected value is wrong... using the Helix YV12 decoder and VirtualDub 1.5.10 it works fine. BTW, it seems to happen to all 716xXXX resolutions.

Posted by: phaeron Apr 5 2005, 03:25 AM
Whoops... wish you told me about that earlier. That means there is a routine that is attempting to compute bitmap pitch using normal DIB rules (scanlines padded to 4 bytes), which isn't true for YCbCr surfaces. 459672 is correct.

You should be able to work around this by disabling YCbCr support in Options > Preferences > AVI, in which case the input routine will use a VFW decoder like 1.5.10 did.

Posted by: stephanV Apr 5 2005, 08:49 AM
i just found out about it by accident while reading #x264... 716xXXX is not something i would normally use. wacko.gif

Posted by: i4004 Apr 8 2005, 07:44 PM
QUOTE
it would be cool if the "run video analysis pass" could be added to the joblist from the GUI

++

it would be cool if vdub would be easier to use for 2pass encoding in job control and batch processing modes, yeah. wink.gif
just ask this networked machine i have that's just sitting here and doing nothing.
smile.gif

that's right; 2pass x264; i can afford that as long as it's not hogging my primary machine for days.

Posted by: phaeron Apr 9 2005, 03:52 AM
Yeah, yeah, it's on my TODO list. Note that you can do it right now through scripts, if you're so inclined. Generate a script that does both passes, parameterize it for the filenames, and use the /i (invoke) command-line flag to run it.

Posted by: i4004 Apr 9 2005, 03:02 PM
i don't have a problem with scripts so i say
"thank you!".
(i better dload scripting reference now... )

btw. tried x264?
what do you say?
i say it's not bad; not bad at all!
(you do anime, so i guess you're not overwhelmed with it.)

Posted by: hannibalstgt2 Apr 9 2005, 04:14 PM
QUOTE (phaeron @ Apr 4 2005, 04:57 AM)
QUOTE

Build 23350 (1.6.5, experimental): [April 4, 2005]
  [features added]

  * Added support for reading paletted BMPs.
 

Hello,

can somebody explain to me, what paletted bitmaps are.
I am quite new to VirtualDub and English is not my mother language,
so the dictionary tells me rubbish.

Thanks

Wolfgang

Posted by: fccHandler Apr 9 2005, 07:26 PM
Bitmaps are arrays of tiny dots (pixels), where each dot is a different color. The colors are represented as the weights of the primary red, green, and blue components of light.

A "true color" bitmap stores a red, green, and blue value for each individual pixel. Thus a 24-bit true color bitmap can show any or all of 16 million possible colors, all the time.

A "paletted" bitmap contains a small list of only the most popular RGB colors, typically 256 of them. (An optimized palette can be made by analyzing the real colors in the image.) Then instead of storing 3 values (R,G,B) for every pixel, only one value (an index into the 256-color palette) is stored for every pixel. Thus the paletted array is 3 times smaller than the true color array, but its disadvantage is that it can never show more than 256 colors at a time.

GIFs are a prime example of a paletted format.

Posted by: hannibalstgt2 Apr 10 2005, 03:14 PM
Getting a little bit smarter every day.

Many thanks for the explantion of "paletted bitmaps".

Wolfgang

Posted by: Boulder Apr 13 2005, 02:32 PM
I finally got around to transferring some old VHS tapes on DVD biggrin.gif

Two over 3-hour captures, perfect a/v sync and no problems during capturing even when there were some dropped frames between recordings on the tapes.

What can I say -- except thanks!

Posted by: PrinceMyshkin Apr 13 2005, 03:46 PM
What is your capture card?

Posted by: Boulder Apr 14 2005, 04:16 AM
Hauppauge WinTV Stereo WDM, BT878 chip, the latest official drivers.

Posted by: Darkfalz Apr 14 2005, 05:10 AM
How "experimental" is it for just normal video processing?

Posted by: phaeron Apr 14 2005, 08:24 AM
I just updated the known bug list pinned post for 1.6.5 in the bugs section. The regression bugs to watch out for are the frameserver bugs and the MS MPEG-4 V3 format negotiation bug; other than that I do not know of any serious bugs in the edit module. I have already started to shunt features to a second branch and will probably make 1.6.6 a bugfix-only stable release unless I find a good reason otherwise.

Posted by: i4004 Apr 16 2005, 07:12 PM
avery...
going to 'capture filter' (to adjust settings of a driver) still turns off the preview.
rather annoying to go to some other capping app just to adjust brightnest/contrast, don't you think?
wink.gif

Posted by: phaeron Apr 16 2005, 07:41 PM
Yes, but not a bug. Not sure how I want to solve it. Easiest way would be to add a Capture Filter (with display) command, but that isn't very intuitive.

Posted by: fccHandler Apr 16 2005, 08:57 PM
Well what do you know... ohmy.gif

And I thought it was just my system acting screwy. I didn't realize that it was normal behavior. So why is the preview disabled during the dialogs, if I may ask?

Posted by: i4004 Apr 16 2005, 10:07 PM
QUOTE
Yes, but not a bug.

well, then all of your previous vfw versions have a bug as it's working ok with them.
tongue.gif

how to solve it?
helluva lot dshow apps out there that don't hide preview when one does need it.

Posted by: phaeron Apr 16 2005, 10:54 PM
Some capture drivers expose critical settings through their filter configuration dialogs that are inaccessible if the filter is active while the dialog is displayed.

i4004: Does the new version act differently if you use the devices in VFW mode? If not, it's not a bug.

Posted by: i4004 Apr 17 2005, 01:38 AM
http://prdownloads.sourceforge.net/virtualvcr/VirtualVCR-src-v2.6.9.zip?download

tongue.gif

ps/
in my post [Posted: Apr 16 2005, 09:12 PM] i didn't call it a bug.
it doesn't matter much if it's a bug or dshow quirk or something. i just said it's not working. and it should. like it's working in plenty of other dshow cap apps.

Posted by: DarrellS Apr 30 2005, 05:35 PM
Capture is broken for ATI Rage Theater users with the wdm-vfw-wrapper. Program freezes up when File/Capture is chosen and the audio from the TV tuner stays on (with or without the wdm-vfw-wrapper installed).

Bottom of page says ...

Connected to capture device: ATI Rage Theater Video Capture (Directshow)
The program freezes up so there is no way to change any settings, if any settings would fix the problem.

Video Capture works fine in VirtualDubMod and Virtual-MPEG2 using the wdm-vfw-wrapper but not on VirtualDub 1.6.5.

Posted by: phaeron Apr 30 2005, 07:42 PM
You're not using the WDM wrapper; you're attempting to use the WDM device directly. 1.5.10 couldn't do that. Selecting Microsoft WDM Image Capture (Win32) (VFW) is what you want to mimic the behavior of 1.5.10. Does that freeze up too?

Posted by: DarrellS May 1 2005, 04:29 AM
QUOTE (phaeron @ Apr 30 2005, 01:42 PM)
You're not using the WDM wrapper; you're attempting to use the WDM device directly. 1.5.10 couldn't do that. Selecting Microsoft WDM Image Capture (Win32) (VFW) is what you want to mimic the behavior of 1.5.10. Does that freeze up too?

I tried VDub 1.6.4, VDub 1.6.5 and VDubMod 1.5.10.1 before installing the wrapper (which took forever to find since most of the links I found were dead links, including the ones on this site) and all programs either froze up or told me that I didn't have a capture device.
I uninstalled VDub 1.6.4, installed VDub-MPEG-2 and the Wrapper and now I can capture with all except for VDub 1.6.5 which I'd like to try since it has the keyboard channel changer for the TV tuner.

I can't open any options in VDub 1.6.5 to select Microsoft WDM Image Capture (Win32) since the program freezes up when I click File, Capture. I could've sworn I saw that option in the other versions before but after installing the wrapper, all I see now in VDubMod an VDub-MPEG2 is the ATI Rage Theater Video Capture. I thought there were three options before

I am using Windows 2000 Professional SP4.

I was hoping that there would be more capture resolution options by using VirtualDub to capture but unless the Microsoft WDM Image Capture has more options, it doesn't look like it. Matter of fact, it looks like there are less. At least with the ATI Catalyst software, I can capture AVI at 400x300, 480x360 or 560x420 and more MPEG capture resolutions. With VirtualDub, my only options are low resolution or high resolution. No mid range resolution for TV capture.

Another annoyance is that the default capture framerate is 15 frames per second when broadcast TV is 29.97 and you have to change the framerate every time you go to try to capture. It has no problem remebering the resolution, just the framerate.

OK, I just looked under Device Manager and it shows Legacy Audio Drivers and Legacy Video Capture Devices ( which looks like the WDM VFW Capture Driver Win32 ) and it says that they are working properly.

Posted by: DarrellS May 1 2005, 04:40 AM
I installed VirtualDub 1.5.10 and no, it doesn't freeze up. Only VirtualDub 1.6.5 freezes up.

Posted by: DarrellS May 1 2005, 04:44 AM
QUOTE (DarrellS @ Apr 30 2005, 10:40 PM)
I installed VirtualDub 1.5.10 and no, it doesn't freeze up. Only VirtualDub 1.6.5 freezes up.

I reinstalled Virtualdub 1.6.3 and it freezes up too.

Posted by: DarrellS May 5 2005, 09:04 PM
Here are some screenshots.

user posted image

user posted image

user posted image

These are after installing the Wrapper. Before, I couldn't get any version of VirtualDub to capture. Now all older versions work but no 1.6.xx versions will capture.


Posted by: i4004 May 5 2005, 10:56 PM
well, i hate screenshots that make forum window not fit my 800x600 desktop.
smile.gif

see the vdub in registry;
http://i4004.net/i4004/vdub%20in%20registry/1.png
now, what if your saved 1.5.10 settings are making problems for 1.6.5?
i dunno, avery does.
if my suspicion is correct, then you should erase the vdub entry, and use 1.6.5 only from then on.
(i don't know, i didn't read all that you said here)


i was thinking how it would be cool to have some tool to easy extract (and then merge again, when needed) different vdub (cap) settings from and to the registry.
this would be replacement for the lack of capping 'profiles'.
but i didn't investigate possibilites too much as i already have 2 versions (redfish's versions has it's own spot in registry, as you can see) and that covers me nice.

why is vdubmod entry there, you ask?
well, i admit i tried it. i didn't like it. it is erased from hdd, but registry entry stayed. (i just erased it now. smile.gif )

mhm avery; did you see how blight solved this:
http://www.inmatrix.com/zplayer/highlights/multicopy.shtml
incredibly simple and good!
(i have 3 versions of zplayer installed. smile.gif )

i would love to see this in vdub.
3 instances for me right away.
<wink>
1lores, one medium res (as far as ffvfw mpeg4 goes...576x576), and last one full res mjpeg.

hell, this is a good suggestion to elegantly avoid the "profiles".

Posted by: phaeron May 6 2005, 03:56 AM
DarrelS:

If File > Capture hangs on entry, hold down SHIFT the next time you try. It prevents VirtualDub from activating the device that was used last time, which may be causing problems.

Can you list exactly which devices are under the device list in 1.6.5? We need to get 1.6.5 working on the Image driver first; comparing 1.6.5 on DirectShow with 1.5.10 on VFW is an apples-to-oranges comparison and is not helpful.

Posted by: DarrellS May 6 2005, 05:09 AM
QUOTE (phaeron @ May 5 2005, 09:56 PM)
DarrelS:

If File > Capture hangs on entry, hold down SHIFT the next time you try. It prevents VirtualDub from activating the device that was used last time, which may be causing problems.

Can you list exactly which devices are under the device list in 1.6.5? We need to get 1.6.5 working on the Image driver first; comparing 1.6.5 on DirectShow with 1.5.10 on VFW is an apples-to-oranges comparison and is not helpful.

Well I took i4004's advice and first deleted all Virtualdub programs except for MPEG-2 and then deleted all Virtualdub entries in the registry. I honestly wasn't sure there were any since VirtualDub can just be deleted instead of uninstalled.

I then reinstalled VirtualDub 1.6.5 without any other versions ( except for MPEG-2 ) or VirtualDubMod and am now am able to open capture without the program freezing up.

I couldn't get to the list of devices before but now I can.

Here is a screenshot

user posted image

Which option do I choose, Microsoft WDM Image Capture (Win32) (VFW)?

Posted by: i4004 May 6 2005, 05:21 AM
directshow

vfw is the wrapper (the stuff older versions had)

Posted by: DarrellS May 6 2005, 05:38 AM
QUOTE (i4004 @ May 5 2005, 11:21 PM)
directshow

vfw is the wrapper (the stuff older versions had)

Now that's where I'm confused. The program said it was connected to capture device: ATI Rage Theater Video Capture (Directshow) when it was freezing up.

Version 1.5.10 works fine with the ATI Rage Theater Video Capture (Directshow) device so I would assume that the newer versions would need the VFW one.


Posted by: DarrellS May 6 2005, 06:33 AM
I tried the Directshow device and it's the one that freezes the program. The VFW one works but although I can change the channel under Video, Source, TV Tuner, I can't figure out how to change channels with the keyboard and under Video, Video Sources, there are no sources.

Diplay, Capture Pin, Preview Pin, Capture Filter, Crossbar, Crossbar2 and Tuner are all greyed out

Posted by: DarrellS May 6 2005, 08:08 PM
I guess that I should just give up. I was able to capture video with version 1.6.5 but the audio was terrible. You could hardly hear what was being said from all the noise and static blairing out of the speakers.
None of the shorcuts work. I have to use the menu to start capture and the escape key to stop cature. Nothing else works. No F5 or F6 keys or no Left Click from the mouse to start and stop capture (which I would normally use). Oh yeah, and no Tuner control from the keyboard which is the only reason that I would use this program to capture along with the option to create custom capture formats.

The ATI Catalyst software seems to be the best option for All In Wonder/TV tuner cards.

Too bad you can't open .vcr files in VirtualDub since it seems to be the only capture that doesn't have the interlace lines and ATI/VCR looks alot better than the MPEG2 captures.

Nevermind, I figured out how to convert them to mp2. Great, I can use VDub-MPEG2 to edit.

Posted by: phaeron May 7 2005, 04:11 AM
DAMMIT i4004, you are not helping! I specifically asked him not to choose the DirectShow entry!

DarrellS, 1.5.10 does not use the ATI device in native DirectShow mode. It can only access drivers that show up as (VFW) in 1.6.5. What the Microsoft WDM Image Capture (Win32) driver does is act as a tunnel to the DirectShow device, so that's probably why you're getting confused. The ATI Rage Theater Video Capture (DirectShow) entry corresponds to direct access to the DirectShow driver by 1.6.5 and you need that mode for VirtualDub to be able to directly control the channels — not being able to get to that is why 1.5.10 couldn't programmatically change the channel, only bring up the dialog to do so.

I don't know why it's hanging on your system. I found a bug in the ATI driver that I thought I had worked around for the new code, but apparently it doesn't work for you, so the best you can do is use the VFW driver, which gives you the same functionality as 1.5.10. Sorry.

Posted by: i4004 May 7 2005, 05:27 AM
yes, i am helping;
QUOTE
The VFW one works but although I can change the channel under Video, Source, TV Tuner, I can't figure out how to change channels with the keyboard and under Video, Video Sources, there are no sources.


http://forums.virtualdub.org/index.php?act=ST&f=4&t=9232&hl=channel+changing&#entry38327

see?
smile.gif

btw. darrells, could you (please) try the version from my signature too? i would be interested to hear what happens with it.

Posted by: DarrellS May 7 2005, 06:02 AM
QUOTE
DarrellS, 1.5.10 does not use the ATI device in native DirectShow mode.


That's strange because it said it was using the ATI Rage Theater (Directshow) before I changed the settings for 1.6.5 and now 1.5.10 says it is using the WMD image capture (Win32) also.

QUOTE
The ATI Rage Theater Video Capture (DirectShow) entry corresponds to direct access to the DirectShow driver by 1.6.5 and you need that mode for VirtualDub to be able to directly control the channels — not being able to get to that is why 1.5.10 couldn't programmatically change the channel, only bring up the dialog to do so.


OK, I see. That's why everything is messed up. I'd try updating the driver again and installing a newer Catalyst software but I'm afraid I'll have to reinstall the operating system again like I had to the last time I tried to update the ATI driver. I tried to update the driver from Windows Update and it messed my operating system all up.

I downloaded the new driver for Windows 2000 from ATI but when I choose update driver from Device Manager, it can't find the driver when I show it exactly where it is. It tells me it couldn't find a driver and will keep using the one I have.

QUOTE
I don't know why it's hanging on your system. I found a bug in the ATI driver that I thought I had worked around for the new code, but apparently it doesn't work for you, so the best you can do is use the VFW driver, which gives you the same functionality as 1.5.10. Sorry.


Well, thanks anyway. It was worth a try. It will still come in handy if I decide to hook my VCR back up to the PC.






Posted by: DarrellS May 7 2005, 06:18 AM
QUOTE

http://forums.virtualdub.org/index.php?act...ing&#entry38327

see?


btw. darrells, could you (please) try the version from my signature too? i would be interested to hear what happens with it.


As Avery explained, there is no way for me to get to directshow so my keyboard and mouse funtions don't work.

I tried the VCR program but it is the same. I see the channel up and channel down options but nothing happens when I click them and the keyboard options have no effect.

Let me uninstall all the versions again and clean up the registry and I'll try it again.

Posted by: DarrellS May 7 2005, 06:31 AM
QUOTE
Let me uninstall all the versions again and clean up the registry and I'll try it again.


Nope. Same thing.

Posted by: i4004 May 7 2005, 07:05 AM
catalyst driver should be just the exe file you run.
it cannot be used via "update driver" of win.

hehe...i recently installed ati aiw128(bt829) to my 2nd machine. and i used vdub to cap.
didn't toyed with tuner, though.


as for 1.6.5, vfw mode and tuner...i misunderstood...sorry.


so try that last catalyst, and if it's still the same, go back to ati's mmc software to cap stuff.
at least we'll bring this saga to end.
smile.gif

Posted by: DarrellS May 7 2005, 06:16 PM
QUOTE
catalyst driver should be just the exe file you run.
it cannot be used via "update driver" of win.


Here is what I tried to download from Windows Update that killed my computer before.

user posted image

QUOTE
hehe...i recently installed ati aiw128(bt829) to my 2nd machine. and i used vdub to cap.
didn't toyed with tuner, though.


That's a totally different chipset so it will probably work.

QUOTE
so try that last catalyst, and if it's still the same, go back to ati's mmc software to cap stuff.
at least we'll bring this saga to end.


I couldn't understand the ATI website at all but I found a catalyst download at zednet for my card. It didn't help with my Virtualdub problems but my computer seems to be alot faster. I couldn't understand why my 3.2GB P4 w/512MB of DDR memory was running so slow. I have cable internet and it didn't seem much faster that dial up at times.

Thanks for all your help, even though it didn't help. smile.gif

You too, Avery.




Posted by: i4004 May 7 2005, 06:31 PM
QUOTE
I couldn't understand the ATI website at all but I found a catalyst download at zednet for my card.


http://www.ati.com/
-->click "drivers and software"
pick os, pick card, download catalyst.
(offcourse, first check if version you already have is same as the one you attempt to dload; no point in installing same driver twice)

ok, bye,bye now.
wink.gif

Posted by: DarrellS May 8 2005, 05:17 AM
QUOTE (i4004 @ May 7 2005, 12:31 PM)
QUOTE
I couldn't understand the ATI website at all but I found a catalyst download at zednet for my card.


http://www.ati.com/
-->click "drivers and software"
pick os, pick card, download catalyst.
(offcourse, first check if version you already have is same as the one you attempt to dload; no point in installing same driver twice)

ok, bye,bye now.
wink.gif

It would be nice if it was that easy but it's not.

It took me about 4 hours downloading and installing different versions (which I had to search for since they weren't listed under drivers and software) before I could find one that worked and didn't kill my TV tuner and it wasn't like the CD that came with my card or the update I did a year ago where everything was on one install program. Everything came in seperate downloads and installs.

The one I finally ended up with is Catalyst 4.3 and MMC 8.9. I'm still not satisfied with this version since it has less capture templates than the original version but at least I can use it until I can brave going back into the website and finding a version between the original (3.1 MMC 7.7?) and the one I have now.

Powered by Invision Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)