Log in

View Full Version : 64 bit transcoding downfall?


ppera2
21st December 2005, 15:48
After some search on WEB and here, seeing dead links and similar, I get some 64 bit stuff. XviD, AVISynth, DGDEcode and VeeDub (Virtual Dub).
Instead faster work I get slower work... 45 vs 65 fps with same settings. I replaced Lanczos resize with Bilinear - then get some 50-52 fps with 64 bit.
Pretty disappointing. It was 'standard' VOB to XviD transcode, with only resize.
Then I tried XviD to XviD conversion with resize. Speed appears to be same for 32 and 64 bit... Did I downloaded wrong versions/builds?

VeeDub is 1.6.3. AVS is 2.55 from june 9. If relevant, I'll post (for) others...

Is there some live place with 64 bit stuff, or it is still all in development phase (deep) ?

Mug Funky
21st December 2005, 15:58
most of it's still very much in development. i haven't even put x64 on my new machine yet, so none of this software's of any use.

IIRC most of the 64 bit versions are simply compiles that run the same stuff in the same way but with 64 bit turned on in the compiler. other stuff really is optimised, but not to it's full potential.

it's all still very new...

foxyshadis
21st December 2005, 16:31
Also, MMX is disabled in x64, and manually 32-bit optimized C has to be recoded for 64-bit. Although reports are that MMX may still work, it's officially deprecated and shouldn't be in x64 code. If you're careful to use only SSE-optimized functions, it should be about as fast (like xvid), but obviously with so many different pieces it's hard to guarantee. Sorry there's no better news. :\

celtic_druid
21st December 2005, 16:47
Could always try say mencoder on one of the numerous 64bit linux distros.

Latexxx
21st December 2005, 18:11
I wouldn't expect a fully featured and actively developed toolchain for 64-bit Windows untill Vista comes out. Mostly because 64-bit Windows XP is pretty much useless thanks to poor driver support and nobody selling it with new computers.

Sirber
21st December 2005, 18:21
if I move to 64bit it will surely be linux...

ppera2
22nd December 2005, 11:07
Could always try say mencoder on one of the numerous 64bit linux distros.

Yes. It is in plan. I have installed Mandriva 2006 free. Just need some reading before start...

I installed XP x64 because it was free - downloaded 180 day evaluation vers. from MS site, activated it via free phone call. Actually, drivers are mostly here, and work fine. Only thing what we have not are TV card drivers, but I found BTWincap 64bit, and it works fine with 64bit VDub and XviD.

squid_80
22nd December 2005, 14:00
Also, MMX is disabled in x64, and manually 32-bit optimized C has to be recoded for 64-bit. Although reports are that MMX may still work, it's officially deprecated and shouldn't be in x64 code. If you're careful to use only SSE-optimized functions, it should be about as fast (like xvid), but obviously with so many different pieces it's hard to guarantee. Sorry there's no better news. :\
64-bit compilers aren't allowed to use MMX, but the instructions still work. Any properly written C code should work properly under 64-bit, it's 32-bit assembly that is the problem especially if it's inlined since that's another thing not supported by the compilers. Also SSE cannot always match MMX, no matter what precautions are taken.

The slowdown reported by ppera2 is because I converted avisynth's resizing code from inline assembly to intrinsics. Blame MS for a) not supporting inline assembly and b) offering crap intrinsic functions as a replacement. Also the win x64 ABI hobbles most of the advantages offered by the 64-bit chip; linux is much better in this respect.

Is there some live place with 64 bit stuff, or it is still all in development phase (deep) ? I've been trying hard, but yet to see anyone else step in and offer anything for windows.

Sirber
22nd December 2005, 14:05
Blame MS for a) not supporting inline assembly and b) offering crap intrinsic functions as a replacement. It's Intel that wants to remove MMX and FPU, not M$.

squid_80
22nd December 2005, 14:14
It's Intel that wants to remove MMX and FPU, not M$.
MMX is part of the AMD64 instruction set, there's no reason to not support it for windows x64. Just like windows xp still supports 16-bit and FPU instructions (both deprecated but still in use by old programs). If Intel suddenly dropped MMX from their chips there'd be a lot of unhappy gamers.

Sirber
22nd December 2005, 14:26
If Intel suddenly dropped MMX from their chips there'd be a lot of unhappy gamers.That's why they drop it in the OS first ;)