View Full Version : Windows Media Encoder x64 now available - with VC-1 support!
stephanV
22nd November 2005, 10:45
I always heard Apple used MP4 as a starting point for their MOV, not the other way. But I have no prove for this.
Of course you don't, because its simply wrong.
ASF [..] has very often problems with seeking, has a limited codec support.
Wrong and wrong.
The bigest disadvantage of ASF is that VirtualDub can't read it.
That's not any different for any other container but AVI and MPG.
Please don't spread fud.
Doom9
22nd November 2005, 10:48
I always heard Apple used MP4 as a starting point for their MOV, not the other way.You're mistaken, it's definitely the other way round. Think about it.. mov was available prior to MP4, prior to 2001 when MP4 was created.
Any ideas when the 32 bit version will be available and when the advaned profile options will finally be exposed to the end user other than having to hack the registry?
Wilbert
22nd November 2005, 11:03
That's not any different for any other container but AVI and MPG.
You know very well that VDub can't read asf, because Avery got a phone call from some company when it could. (The part you snipped from vlada's reply ...) For which other containers is this also the case?
bond
22nd November 2005, 13:05
Actually, it'd be more accurate to say that VC-1 is a superset of WMV9. WMV9 supports only simple and main profiles of VC1. WMV9 Advanced Profile supports the advanced profile of VC1.i assume wmav9 ap is not a totally new codec, but normal wmv9+ap features
like x264 high profile isnt a different codec than x264 main profile
And yes, you're right, Microsoft won't be the only company offering VC1 encoding and decoding solutions. Google for "VC-1 encoder" and you can already find existing non-MS implementations. i never found a proove that a company made its own vc-1 implementation. what makes you think that they are not simply using m$' codec?
Doom9
22nd November 2005, 14:14
well, if you follow the google advice, there are definitely other encoders out there.. just no desktop encoders. It's kinda hard to use software when you're making a hardware platform...
acidsex
22nd November 2005, 14:30
well, if you follow the google advice, there are definitely other encoders out there.. just no desktop encoders. It's kinda hard to use software when you're making a hardware platform...
No doubt and the hardware shit isnt cheap at all.
acidsex
22nd November 2005, 14:37
I may have missed the answer as I didnt see it when I looked back through the posts but does the x64 encoder provide any speed increases for encoding? 1080i advanced profile takes forever as it is. any speed up would be welcomed.
acidsex
22nd November 2005, 14:43
One other issue. I dont know if this was in the 32bit encoder, but during a one pass ADvanced Profile encode, the input looks crisp and clear and the blacks are rich. However on the output side (using the "next" display) the output side looks like it has a nasty film covering it (overlay???) So how do I get my output to have the same blacks as the input?
vlada
22nd November 2005, 16:56
stephanV, Doom9> I know MOV was here before MP4, but I thought there just might be more MOV versions. I was wrong. I wrote that I'm not sure about it and thank you fo clearing this up.
stephanV> What compressions other then MS-MPEG4 and WMV can be stored in ASF? How do I produce such a file? And you never saw an ASF file with seeking problems?
VirtualDubMod can read/write OGM and MKV too. For muxing/demuxing and cutting/joining of MKV and MP4 there are free tools. What about ASF?
But this is way off-topic. I was only trying to explain to zambelli, why it had sense to have a new container and audio compression formats. But at the same time, I see no use for VC-1 format.
Wilbert
22nd November 2005, 17:40
stephanV> What compressions other then MS-MPEG4 and WMV can be stored in ASF? How do I produce such a file?
Pretty much anything: http://forum.doom9.org/showthread.php?t=92136
stephanV
22nd November 2005, 17:40
You know very well that VDub can't read asf, because Avery got a phone call from some company when it could. (The part you snipped from vlada's reply ...) For which other containers is this also the case?
For none, but it is the same reason why VirtualDub doesn't support MPEG2. Even so, do not overestimate the asf "support" that VirtualDub had back then.
@Vlada:
stephanV> What compressions other then MS-MPEG4 and WMV can be stored in ASF? How do I produce such a file?
Basically any.
Here's a nice thread about a free ASF muxer for DirectShow --> http://forum.doom9.org/showthread.php?t=92136&highlight=asf+muxer
And you never saw an ASF file with seeking problems?
I basically have seen any file type with seeking problems. If this is fault of the file format is highly doubtful.
VirtualDubMod can read/write OGM and MKV too.
Reading MKVs with VirtualDubMod is quite problematic these days. And VirtualDub-MPEG2 can read ASF.
But this is way off-topic. I was only trying to explain to zambelli, why it had sense to have a new container and audio compression formats. But at the same time, I see no use for VC-1 format.
Yes it is way off-topic but then just don't use it and keep it at that. There are a lot of things that I consider useles and redundant for me personally, I'm certainly not commenting on all of them. :)
Since VC-1 is mandatory for the upcoming DVD standards, there's enough reason to show at least some interest in it IMO. The problem is that when something smells of MS (or M$ in cool terms) some people seem to always deem it necessary to show their dislike of it. It's a. not relevant and b. very boring.
Elias
22nd November 2005, 21:05
Since this thread ever so expectedly became another anti Microsoft the evil, evil company thread, allow me to contribute a bit of a reality check.
It's so funny it's almost sad that people think MPEG-4 ASP, AVC, AAC, or whatever, "was never pushed".
As anyone who knows a little about this group called the Motion Pictures Experts Group, you probably know that it is composed of some of the most powerful and influential multimedia companies in the world. Allow me to list a few:
AOL Time Warner, Apple, Ateme, ATI, Axis Communications, Canon, Casio, Cirrus Logic, Coding Technologies, DTS Inc., Envivio, ETRI, France Télécom, Fraunhofer, Fugi, Hitachi, Kawasaki Microelectronics, LG, Mitsubishi, Motorola, Nero AG, Nintendo, Nippon, Nokia, NVIDIA, Philips, Pinnacle, QUALCOMM Inc., Samsung, Sharp, Sonic Solutions, TDK, Telecom Italia, Thomson, Toshiba...
And many more.
If for a second you think MPEG technology is not "pushed" by anyone, welcome to Reality. Microsoft doesn't have to "payoff" any MPEG body. MPEG handles quite well on their own, thank you. The standardization is standardization for a reason, it doesn't come from thin air. All the persons and companies comprising the MPEG bodies are responsible for the fine technology available to you in its standardized glory.
The fact the Microsoft's technology, which is in no way a "ripoff" of MPEG technology as some love to state, basing their statements on nothing but "astounding similarity" (the kind that could say Vorbis is a ripoff of AAC since it uses so similar algorithms, as if MPEG is the only body allowed to use widely used algorithms) managed to pass the MPEG quality assurance means nothing but that, it passed.
So there you have a little reality check as opposed to "M$" disussion.Which is good. The more companies that are involved in MPEG, the more they make MPEG codecs suitable for open standards. I'd rather see 1 000 000 companies involved in a codec solution, than 1 alone controlling it.
acidsex
22nd November 2005, 21:14
Well, I suppose theres no way to set different variables for AP. Looked in the registry and there is no "scrunch" entry so shit has changed. Seems to be no way of using B Frames or lookahead and its definitely not available through the gui encoder.
I suppose this encoder should read x64 beta 1.
IvS
23rd November 2005, 04:28
The more companies that are involved in MPEG, the more they make MPEG codecs suitable for open standards. I'd rather see 1 000 000 companies involved in a codec solution, than 1 alone controlling it.
Exactly. The fact that the MPEG is not some puny group which can be "bought out" by a single monopoly (they themselves are the strongest possible "monopoly") means you can forget about Microsoft or any single company taking over and ruining things for everybody.
zambelli
25th November 2005, 02:40
So the x64 encoder is more advanced than the 32-bit edition? I can't believe Microsoft would alienate the millions of 32-bit users for the 64-bit minority.
Only in the ways listed in the original posting: VC-1 support and a new DRM module.
zambelli
25th November 2005, 02:45
Any ideas when the 32 bit version will be available and when the advaned profile options will finally be exposed to the end user other than having to hack the registry?
I can't give specific dates, but there are new versions of the encoder in the works. I'll get back to you on this one.
zambelli
25th November 2005, 02:50
i assume wmav9 ap is not a totally new codec, but normal wmv9+ap features
Well, a significant amount of work has been (and still is being) done on the VC1 implementation, so yes, although the basis of the codec is the same, it'd be unfair to say that it's just a repackaged WMV9 as shipped 3 years ago.
i never found a proove that a company made its own vc-1 implementation. what makes you think that they are not simply using m$' codec?
Because MS is stil tweaking its own implementation. :)
(Why does everyone adopt M$ but no one ever writes $ony, for example?) :)
Valeron
25th November 2005, 03:21
(Why does everyone adopt M$ but no one ever writes $ony, for example?) :)
Because it's not "cool" to write $ony here but M$. ;)
Valeron
25th November 2005, 03:22
I can't give specific dates, but there are new versions of the encoder in the works. I'll get back to you on this one.
Good news
bond
25th November 2005, 13:44
zambelli: are you working for microsoft?
Well, a significant amount of work has been (and still is being) done on the VC1 implementation, so yes, although the basis of the codec is the same, it'd be unfair to say that it's just a repackaged WMV9 as shipped 3 years ago.my point is to get away from marketing but point out the facts which imho are
1) vc-1 = wmv9, so this brandnew feature "vc-1 support" is actually no new feature
2) wmv9 ap is an extension of the normal wmv9 codec and not a new codec, like x264 high profile is not a new x264 codec, but an extension of x264 main profile, so to say "the same codec"
Because MS is stil tweaking its own implementation. :)
(Why does everyone adopt M$ but no one ever writes $ony, for example?) :) because, lemme quote the european commission:
Commission concludes on Microsoft investigation, imposes conduct remedies and a fine
...
the investigation concluded that the ubiquity which was immediately afforded to WMP as a result of it being tied with the Windows PC OS artificially reduces the incentives of music, film and other media companies, as well software developers and content providers to develop their offerings to competing media players.
As a result, Microsoft's tying of its media player product has the effect of foreclosing the market to competitors, and hence ultimately reducing consumer choice, since competing products are set at a disadvantage which is not related to their price or quality.
Available data already show a clear trend in favour of WMP and Windows Media technology. Absent intervention from the Commission, the tying of WMP with Windows is likely to make the market "tip" definitively in Microsoft's favour. This would allow Microsoft to control related markets in the digital media sector, such as encoding technology, software for broadcasting of music over the Internet and digital rights management etc.
More generally, the Commission is concerned that Microsoft's tying of WMP is an example of a more general business model which, given Microsoft's virtual monopoly in PC operating systems, deters innovation and reduces consumer choice in any technologies which Microsoft could conceivably take interest in and tie with Windows in the future."an example of a more general business model"
"foreclosing the market to competitors"
"controlling markets"
"reducing consumer choice"
and thats the official opinion of one of the highest bodies of the european union
IvS
25th November 2005, 18:04
Sure. We all know the EU is a very "respectable" body.
If you want to limit a company in such ways like preventing it from including very basic things like a multimedia player and codecs with its operating system and an internet web browser (....) you're not very OK in the head, or you're just looking for ways to get lots of money.
I can't quite remember WMA being popular. In fact I'd say the percentage of people using WMA as a primary format for audio files is immensely low compared to users of the "good old" popular MP3, which, by the way, Microsoft has included a decoder for in its operating systems since ages.
As for video files, I can't quite remember when WMV files have been popular. "DivX" seems to be a synonym for "digital video" amongst avarage users who don't know too much about codecs. As for online content, Microsoft, Apple and Real have succeeded in that field because all their offerings have been unfortunately more complete than MPEG based ones and were adopted by many companies.
How well do the European Union's arguments hold? Not too well at all I'd say.
Microsoft has no monopoly whatsoever in the multimedia field and that's the fact. And if you'd like to prevent it from having a useable operating system, you'd have to prevent all others too. Mac OS, Linux and various UNIX based solutions, all of them should have no multimedia support "out of the box." Why, that would be unfair!
zambelli
26th November 2005, 17:21
zambelli: are you working for microsoft?
Yes, I am. I don't work for the encoder team though, hence my delay in getting specific answers back to you. I also need to be careful I only discuss information which is already public - you know, standard business non-disclosure policy.
my point is to get away from marketing but point out the facts which imho are
1) vc-1 = wmv9, so this brandnew feature "vc-1 support" is actually no new feature
WMV9 (as released in WMP10) is only a subset of VC-1. Your old math teacher would probably object to you using an equal sign for that relation. :)
2) wmv9 ap is an extension of the normal wmv9 codec and not a new codec, like x264 high profile is not a new x264 codec, but an extension of x264 main profile, so to say "the same codec".
True, but considering the amount of work gone into WMV AP since the VC-1 proposal, you should at least consider this a codec update.
because, lemme quote the european commission:
"an example of a more general business model"
"foreclosing the market to competitors"
"controlling markets"
"reducing consumer choice"
and thats the official opinion of one of the highest bodies of the european union
And the special European Windows XP non-media version is now selling like hot cakes. ;) But seriously... You have to ask yourself: what's the alternative? How do you make an operating system in the 21st century without including video and audio playback capability? Can you imagine Apple shipping MacOS without QuickTime or iTunes? It's just simply not realistic.
(speaking as a private individual and not as an employee)
bond
26th November 2005, 17:52
Yes, I am. I don't work for the encoder team though, hence my delay in getting specific answers back to you. I also need to be careful I only discuss information which is already public - you know, standard business non-disclosure policy.good to know, its always nice of having people from companies around :)
what are you doing at microsoft?
WMV9 (as released in WMP10) is only a subset of VC-1. Your old math teacher would probably object to you using an equal sign for that relation. :)still till now available wmv9 was following the vc-1 specs too, which means m$ supports vc-1 since it released wmv9 so to say
again i see wmv9 advanced profile not as a new codec (and i am sure it isnt), but simply as new features added to wmv9, supporting full vc-1 (which doesnt mean that it didnt support vc-1 before)...
And the special European Windows XP non-media version is now selling like hot cakes. ;) But seriously... You have to ask yourself: what's the alternative? How do you make an operating system in the 21st century without including video and audio playback capability? Can you imagine Apple shipping MacOS without QuickTime or iTunes? It's just simply not realistic.
(speaking as a private individual and not as an employee) well this has been discussed already enough in other threads...
read my opinion there ;)
keel
27th November 2005, 15:38
VC-1 video codec. Windows Media Encoder 9 Series x64 Edition includes support for a fully SMPTE-compliant version of the new VC-1 video codec. SMPTE has not yet approved VC-1, how can you have a "fully SMPTE-compliant version"?
bond
27th November 2005, 15:39
SMPTE has not yet approved VC-1, how can you have a "fully SMPTE-compliant version"?because wmv9 = vc-1? :D
keel
27th November 2005, 16:01
because wmv9 = vc-1? :DNow, you know that's not true.
Sorry, sounds like the usual Microsoft PR to me. Exaggerate the truth.
Maybe some people put an $ in Microsoft but not in Sony because Microsoft is a convicted monopolist but Sony isn't.
bond
27th November 2005, 16:04
of course its true :p
keel
27th November 2005, 16:18
The king of MS combinations of facts and PR, of course, is amirm in avsforum.
If anone is really bored and needs something to read, and you don't know about it, there is an interesting HDTV thread on how MS got WMV9 (now VC-1) to be a contender
http://www.avsforum.com/avs-vb/showthread.php?p=6575755&&#post6575755
It looks like some of the codec battles are being fought in the trenches, for the hearts and minds of the cognoscenti....
Of course, I always welcome real facts that are not wrapped in hype, nor surrounded by copy/paste buzz from corporate PR releases.
Sirber
27th November 2005, 17:59
I can't encode from xvid files. Says I have no codec :confused:
unmei
28th November 2005, 10:54
wouldn't surprise me if you needed a DMO xvid decoder =)
stephanV
28th November 2005, 11:30
A 64 bit program normally must use 64 bit decoders.
zambelli
29th November 2005, 01:42
A 64 bit program normally must use 64 bit decoders.
Of which there are, like, 2. :)
Not 100% sure what the story is there, but in the meantime, Sirber, can you try passing the input through Avisynth or a similar wrapper that can output uncompressed YV12/YUY2 video?
Also, if you're using ffdshow, can you try enabling/disabling VfW vs. DShow versions of the Xvid decoder?
CruNcher
29th November 2005, 03:02
Alex Zambelli ?
zambelli
29th November 2005, 07:16
good to know, its always nice of having people from companies around :)
what are you doing at microsoft?
Thanks. I've been a Doom9 regular for many years, even before I joined Microsoft. I've been working as a test engineer on Windows Media Player since v9, on both desktop and Win Mobile. I'm actually scheduled to start working for the VC-1 team very soon so I'll try to watch this particular forum more closely in the future and chime in when necessary.
still till now available wmv9 was following the vc-1 specs too, which means m$ supports vc-1 since it released wmv9 so to say
Well, WMV9 SP+MP (as shipped with WMP9) was actually developed before VC-1 was drafted, so it's a chicken or the egg kind of question at this point. But the general idea is that if you develop a VC-1 compliant decoder, it ought to be able to decode video streams encoded with the existing WMV9 codec.
well this has been discussed already enough in other threads...
read my opinion there ;)
I'll actually stay out of that whole discussion because I'm a little biased. :)
bond
29th November 2005, 21:51
Thanks. I've been a Doom9 regular for many years, even before I joined Microsoft. I've been working as a test engineer on Windows Media Player since v9, on both desktop and Win Mobile. I'm actually scheduled to start working for the VC-1 team very soon so I'll try to watch this particular forum more closely in the future and chime in when necessary.great! :)
I know it may sound like semantical nitpicking, but WMV9 is an *implementation* of VC-1. Saying it's the same is kind of like saying a chocolate cake is the same thing as its recipe. You can't eat a recipe, can you? Someone else could make a cake based on that recipe, but it wouldn't be the same as your cake. Make sense? :) my words!!! vc-1 is the format, wmv9 an implementation of it
CruNcher
29th November 2005, 22:37
my words!!! vc-1 is the format, wmv9 an implementation of it
Jep with all the additional features that M$ didn't provided as amandments for AVC as they left the standard :P
HookedOnTV
29th November 2005, 23:58
Can you now encode AC3 5.1 to WMA 5.1? Never have been able to do this without converting to mono wavs then to multichannel avi then to wma.
acidsex
30th November 2005, 08:18
Heres a better question regarding the Adanced Profile for Zambelli.
Now lets suppose that content producers are encoding to VC-1 currently. Will the files we encode today be easily authored in the upcoming BLu Ray/HD-DVD or will we have to re-encode our content again at that time? What are the optimal settings from the VC-1 advanced profile that MS recommends that will ensure playback on the HD players that are due out? Lookahead? B frames? Default?
Furthermore, will MS ever release an app that allows the authoring of Menus instead of being forced to buy an entire encoding pc system from Sonic? I saw a demo of it and its quite clunky and heavily overpriced. Definitely not in the price range of idnependent producers or hobbyists.
zambelli
30th November 2005, 20:20
Now lets suppose that content producers are encoding to VC-1 currently. Will the files we encode today be easily authored in the upcoming BLu Ray/HD-DVD or will we have to re-encode our content again at that time? What are the optimal settings from the VC-1 advanced profile that MS recommends that will ensure playback on the HD players that are due out? Lookahead? B frames? Default?
Content producers encoding for HD-DVD/BD aren't using WME9. This encoder only produces ASF files, whereas for HD-DVD/BD authoring you need elementary video streams. Although it might be possible in the future to extract the video stream from an ASF file and mux it into an MPEG transport stream for HD-DVD/BD, I wouldn't count on that. So in other words - if you're looking to produce HD-DVD/BD compliant VC-1 streams today, don't do it with WME9.
Furthermore, will MS ever release an app that allows the authoring of Menus instead of being forced to buy an entire encoding pc system from Sonic? I saw a demo of it and its quite clunky and heavily overpriced. Definitely not in the price range of idnependent producers or hobbyists.
Menus for what? HD-DVD?
acidsex
30th November 2005, 22:18
Menus for what has been used on windowmedia.com.
I know MS put out the docs regarding how to code for menus but alot of content producers dont know javascript very well it at all.
To your earlier response, if this will not likely be possible, then what is the sense of encoding to WM9 HD today it it unlikely to be supported for HD-DVD authoring later? Does the Xbox360 even support playback of Wm9 HD files (w or w/o DRM)?
bond
2nd December 2005, 14:06
imho these wmv9 dvds were more about promoting that wmv9 can do hd, than to be a real format competing with hd-dvd/bluray
afaik these wmv9 dvd menus are some sort of html, so nothing really fancy (this has been discussed already)
wmv9 encoded today and these wmv9 dvds will definitely not be compliant with hd-dvd or bluray (the same way as h.264 encodes made today are not compliant). that is because the specs will definitely define in details how these streams will have to look like (gop structure aso) and we today simply dont know these specs
zambelli
3rd December 2005, 01:52
@Bond:
Correct on all counts. I'm guessing the WMV-HD discs will be phased out as soon as a dominant HD DVD standard emerges.
@Acidsex: (ouch)
What's the point of any encoder? :)
Doom9
4th December 2005, 02:20
@zambellin: I haven't heard from Dan yet.. if you know him, could you ask him if he got my mail regarding the next codec comparison and your participation in it?
CruNcher
4th December 2005, 07:15
Correct on all counts. I'm guessing the WMV-HD discs will be phased out as soon as a dominant HD DVD standard emerges.
If you could repeat that in the Standalone Forum and AVSforum for all the users that bought HD capable chinese players, because they thought your WMV-HD stuff is the new big mofo and try to explain them why all companies promoteing your WMV-HD DVDs as HD-DVD on the cover that would be cool ;) (but be carefull not to be sliced into pieces by the audience)
bond
4th December 2005, 12:26
haha :D
mrcorbo
4th December 2005, 22:38
If you could repeat that in the Standalone Forum and AVSforum for all the users that bought HD capable chinese players, because they thought your WMV-HD stuff is the new big mofo and try to explain them why all companies promoteing your WMV-HD DVDs as HD-DVD on the cover that would be cool ;) (but be carefull not to be sliced into pieces by the audience)
Do you actually believe anyone ever thought WMV-HD (in terms of commercial releases) was ever anything more than an intermediate solution until the real HD-DVD formats arrived?
zambelli
5th December 2005, 20:21
If you could repeat that in the Standalone Forum and AVSforum for all the users that bought HD capable chinese players, because they thought your WMV-HD stuff is the new big mofo and try to explain them why all companies promoteing your WMV-HD DVDs as HD-DVD on the cover that would be cool ;) (but be carefull not to be sliced into pieces by the audience)
Let's get one thing clear: I am on this forum mainly as a private individual, like I have been since the day I joined. The fact that I work for the company - you can consider that a nice bonus, not the other way around. What I say are my own opinions, particularly something explicitly worded as "I'm guessing..." To consider that anything but a personal opinion is an intentional misreading on your part.
Now, with that out of the way... What words publishing companies use to describe DVDs is largely is up to them. I'm not sure if Microsoft has any control over anything other than the WMV-HD logo. I've seen WMV-HD titles that are very accurate in their description of the HD content included on the DVD, clearly indicating that the WMV-HD is intended for playback on PC and PC only (see "Step Into the Liquid" description). Others, however, use very vague (and possibly misleading) words such as "DVD HD" and "HD DVD-ROM". I suspect these are just labels made up by marketing people who figure "HD" is the new buzzword that will help sell the DVDs.
I've heard of players by IO Data and Zensonic that allegedly play WMV HD content, but I'm unsure whether they're actually capable of playing released WMV-HD titles because that would involve supporting DRM in all its forms (some titles such as "Terminator 2" require over-the-Internet license acquisition). The WMV HD boast might be just their way of saying "we play WMV files and we're capable of decoding high definition resolutions". I don't know, I've never actually tried one of these players. If you have specific info, please enlighten me.
acidsex
13th December 2005, 18:59
@zambelli: Again, I may hav missed it in this thread but can you please clarify soem points for me.
1) How can the user define different features such as B frames or Lookahead using the x64 encoder? 32bit use can change the registry setting under scrunch. Under x64, scrunch is not there. So how does a user implement that?
2) Is it reasonable to expect some sort of speed increase when encoding using the x64 encoder over the 32bit version? If not, then can you please explain what the benefit of using the x64 encoder over the 32 bit other than Advanced Profile is available by defaul with the x64 even though you cannot currently tweak any specific features?
Thank you.
zambelli
13th December 2005, 22:23
1) How can the user define different features such as B frames or Lookahead using the x64 encoder? 32bit use can change the registry setting under scrunch. Under x64, scrunch is not there. So how does a user implement that?
Have you tried just creating the HKCU\Software\Microsoft\Scrunch\WMVideo key and putting Advanced Profile settings in there? I see no reason why it wouldn't work.
2) Is it reasonable to expect some sort of speed increase when encoding using the x64 encoder over the 32bit version? If not, then can you please explain what the benefit of using the x64 encoder over the 32 bit other than Advanced Profile is available by defaul with the x64 even though you cannot currently tweak any specific features?
Thank you.
The advantage is that the x64 version runs natively on 64-bit Windows without WOW64. You can expect performance benefits in some encoding scenarios, but not necessarily across the board. Just like with 64-bit versions of VirtualDub, Avisynth, Xvid, etc, the speed improvements are not revolutionary but they do exist.
Want to run some objective benchmarks and post the results?
Doom9
22nd December 2005, 19:35
So I'm wondering, has anybody tested the 64 bit encoder on a full movie? What kind of performance are you seeing?
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.