|
|
| stephanV |
| Posted: Sep 7 2004, 02:46 PM |
 |
|
Spam killer ;)
Group: Moderators
Posts: 4348
Member No.: 8917
Joined: 18-February 04
|
from www.virtualdub.org
| QUOTE | VirtualDub 1.6.0 released
VirtualDub 1.6.0 is out the door, and besides being the first experimental release in a while, it has a major new feature: it is the first version to have a native 64-bit (AMD64) build. This build is pretty raw, is missing a bunch of features and optimizations, and doesn't do much yet that really shows "the power of 64-bit." (It's even compiled with a prerelease compiler, the DDK compiler. VS2005 beta 1 doesn't have a "go-live" license.) Nevertheless, it is a true AMD64 release, for those of you who must have a native release.
It took me about three days to get this release out the door, once I'd committed to absolutely nothing but showstopper bugs. It took me about two dozen tries to get it right, and each try is about 10 minutes to do a full rebuild (to make sure the final builds are correct and match source). Well, the AMD64 build is broken. Okay, we'll fix that. The crash handler bombs. Fixed that. Now the crash handler doesn't bomb, but it doesn't report DLLs properly. Fixed that. Oops, broke x86. Try again. Seems good... nope, UI is broken returning from capture mode. Fix that, try again... oh, frameserver's busted too. Okay, try AGAIN, one more time... about dialog says 1.5.10. ARRGH. Fix that, check it into Perforce, compile one last time.... Change log has a build number two below actual value.
Screw it, I'm not doing another build to fix that. Ship it.
I have no doubt that I left something stupid in the build, but considering the number of low-level changes in this build, some amount of breakage is to be expected. If you spot regressions, report them to me so I can fix them for 1.6.1. Please don't email me just to complain that your pet feature didn't make it in, though; I had to draw the line at some point.
I was typing a long, thorough explanation in Pivot for this part explaining all of the new features in VirtualDub 1.6.0, but I'm very angry because Internet Explorer ate it. I'll retype it later. |
some of the features added:
- in and output support for virtually every useful color depth existing
- fast recompress is in principle redundant as the filter chain will be skipped when not used, its there though
- internal DV decoder
- integrated JPEG in- and output support
remember: its experimental 
--------------------
useful links:
VirtualDub, Input plugins and filters, AviSynth, AVI-Mux GUI, AC3ACM by fcchandler, VirtualDub FAQ |
|
| Cyberman |
| Posted: Sep 7 2004, 04:13 PM |
|
|
Advanced Member
Group: Members
Posts: 2035
Member No.: 3477
Joined: 3-April 03
|
Indeed - these are good news.
What is this "triangular resize", does anyone know?
IMO, the best thing about the new release is that itīs till offering the same design as previous builds(well, except for the slider).
Thatīs something I fear with every new program - that the designers decided to totally change the design for no reason at all.
Anyway...
--------------------
Matroska/MKV ? |
|
| phaeron |
| Posted: Sep 7 2004, 05:06 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
A bit of a warning: The executable that got sent out has a bug that I already fixed: leaving the frameserver causes a wonked timeline. Something happened with the release script because the executable that got shipped is not the same as the last one that the compiler generated, but they have the same timestamp out of the linker (!). I don't know how bad the regressions are yet.
|
|
| phaeron |
| Posted: Sep 7 2004, 06:24 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
Never mind, the executables are the same... I just forgot a copy constructor. 
Triangular resize was another attempt at implementing an edge-adaptive interpolator; it underperforms compared to bicubic and I simply forgot to yank it before ship.
|
|
| meilin |
| Posted: Sep 8 2004, 01:41 AM |
|
|
Unregistered
|
thx phaeron,thx for your hard work:) |
|
| Wilbert |
| Posted: Sep 9 2004, 03:32 PM |
|
|
Advanced Member
Group: Members
Posts: 132
Member No.: 6270
Joined: 11-September 03
|
| QUOTE | | Another problem you'll run into is that 32-bit plugins can't be used, including video filters and Avisynth. Win64 does not allow a 64-bit process to load 32-bit DLLs. COM marshalling might be able to handle Avisynth but I doubt it; it's more likely that I will have to launch the 32-bit VirtualDub as a child process and use IPC to access 32-bit code. |
Yikes  Do I understand it correctly, that AviSynth doesn't work on a Win64? |
|
| phaeron |
| Posted: Sep 9 2004, 07:21 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
It works for 32-bit processes, but is not accessible to 64-bit processes. You could use it with VirtualDub.exe but not Veedub64.exe.
|
|
| stephanV |
| Posted: Sep 9 2004, 09:15 PM |
|
|
Spam killer ;)
Group: Moderators
Posts: 4348
Member No.: 8917
Joined: 18-February 04
|
For more explanation about the changes
also read the comments 
--------------------
useful links:
VirtualDub, Input plugins and filters, AviSynth, AVI-Mux GUI, AC3ACM by fcchandler, VirtualDub FAQ |
|
| mikesbytes |
| Posted: Sep 12 2004, 01:29 PM |
|
|
Unregistered
|
Whats the performance difference between VirtualDub.exe and Veedub64.exe |
|
| phaeron |
| Posted: Sep 13 2004, 12:10 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
@mikesbytes: Read the release notes.
@stephanV: I had hoped that people would post on-topic comments, but instead people posted the same random junk I get in my Inbox. I'll probably have to turn the comments back off.
|
|
| mikesbytes |
| Posted: Sep 13 2004, 03:32 AM |
|
|
Unregistered
|
Sorry, but I didn't find the reference to performnce. Am I looking in the wrong place. Could you please point me in the right direction - thanks for your help.
I'm about to buy a new PC to do a large amount of processing on and this sort of thing will influence the purchase, hence the question. |
|
| phaeron |
| Posted: Sep 13 2004, 03:50 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
| QUOTE |
AMD64 version
- The AMD64 build can only be run under a 64-bit version of Windows, such as Windows XP Professional x64 Edition. It cannot be run on 32-bit Windows even on a 64-bit capable CPU.
- Due to OS limitations, 32-bit drivers and filters cannot be accessed from the 64-bit version. This limitation may be lifted in a later version.
- Some functionality is unoptimized or missing in the AMD64 build due to unported code, most notably video filters and some of the bitmap conversion routines. Current AMD64 builds should not be used for benchmarking.
|
It would be very unwise for you to decide between a 32-bit-only and a 64-bit-capable CPU based on the current 64-bit build. That having been said, the Athlon 64 is a strong performer even on 32-bit code.
|
|
| mikesbytes |
| Posted: Sep 15 2004, 01:54 PM |
|
|
Unregistered
|
Thanks Phaeron, if you arn't into games, then video processing is only reason for most home users to consider, when selecting a cpu. I'm sure that in the long term, your development of the 64bit version will pay rewards. In the short term, non compatibility with existing filters will be a showstopper for most. For me, compatabitliy with Deshaker or an equilivant filter is a must, where equivilant filters to those like the MSU ones are sure to arrive quickly. |
|
| freako |
| Posted: Sep 25 2004, 05:25 PM |
|
|
Unregistered
|
thx   |
|
