Can't install VC1

[Sirber]

http://i11.tinypic.com/35clw1k.png

I installed:

* WMEncoder.exe
* wvc1dmo.exe (error)
* wmformat95sdk.exe
* wvc1dmo.exe (error)

:(

[shon3i]

try to install wmp 11

[Sirber]

Why would I need WMP11 to encode?

[buzzqw]

wmp11 include both decoder and encoder parts

wvc1dmo.exe cannot be installed without the WMFormatSDK 9.5

as i asked in a previus thread http://forum.doom9.org/showthread.php?t=118996 if you install wmp11 and wm encoder 9 series you can access to wvc1

BHH

P.S. i see that you want add a wvc1 capabilities to RealAnime, good, have you resolved the audio part when destination audio is multichannel ?

[Sirber]

wvc1dmo.exe cannot be installed without the WMFormatSDK 9.5 I installed WMFormatSDK 9.5 manually, with no effect.

P.S. i see that you want add a wvc1 capabilities to RealAnime, good, have you resolved the audio part when destination audio is multichannel ?RealAnime does only 2 channels output. Since my goal is smallest files, 5.1 is out of the question.

[buzzqw]

RealAnime does only 2 channels output. Since my goal is smallest files, 5.1 is out of the question.

gotcha...

ok, so you had installed sdk 9.5 and then wmp11 ... when you try encoding what error you got ?

BHH

[Sirber]

I tryed installing at home (where it fails) via VNC, but seems I had to reboot first. Gonna retry tonight.

If everything works as expected, RealAnime 5a5 will have it included (no addon), if all dependencies are detected.

Did you try VC1 on anime content?

[buzzqw]

no, i don't like anime.

but as far as i tested the quality is less then x264, and much slower...

I have add even wmv8, it's nice, fast, reactive, try it :)

BHH

[zambelli]

I tryed installing at home (where it fails) via VNC, but seems I had to reboot first. Gonna retry tonight.
If it doesn't work, can you check your wmvcore.dll version? That usually reflects the WMF SDK version.

[Sirber]

Still doesn't work. Fails at the end, installer doesn't say what failed.

In sys32 I have v11.0.5721.5145

[edit]

You've encountered error message 8007F01E while using Windows Media Player. The following information might help you troubleshoot the issue.
Cannot complete setup

Windows Media Player setup cannot be completed. Typically, this error occurs when you try to switch from one language version of the Player to another language version. For example, this error might occur if you have an English version of the Player installed on your computer and you try to install the Spanish language version of the Player on top of it.

If you are running Windows XP, try removing the existing version of Windows Media Player from your computer, and then installing the most recent version of the Player.

[zambelli]

Still doesn't work. Fails at the end, installer doesn't say what failed.

In sys32 I have v11.0.5721.5145

That's your wmvcore.dll version? Then you already have WMF SDK 11 installed. Do you have wmvencod.dll present on your system too?

[bond]

sirber, are you using windows 2000? if yes, m$' vc-1 advanced profile will not work

[Sirber]

I'm on XP SP2.

anyway, thx for the help. I'm giving up :)

[emmel]

That VC-1 codec pack on Nic's web pages installed cleanly on my XP/SP2.

[zambelli]

That VC-1 codec pack on Nic's web pages installed cleanly on my XP/SP2.
That's a beta release. Nic hasn't updated the runtime to the final release version. You can get it here: http://www.citizeninsomniac.com/WMV/wmfdist11.exe

I'm on XP SP2.
anyway, thx for the help. I'm giving up
You never answered my question. Did you ever have WMF SDK 11 (full or runtime) installed on your machine? A wmvcore.dll version of 11.0.5721.5145 would indicate that you did.

[Sirber]

@zambelli

sorry I haven't seen your post about wmvencod.dll.
Yes I have, version 11.0.5721.5145.

I'm trying wmfdist11.exe.

[zambelli]

sorry I haven't seen your post about wmvencod.dll.
Yes I have, version 11.0.5721.5145.
Well then you don't need the WMV AP beta codec - you already have the final version. That's why the codec installer doesn't let you install it. My VC-1 FAQ (sticky in this forum) mentions that.
I'm trying wmfdist11.exe.
You might want to do a system restore first to the point before you installed SDK 9.5. I'm not sure what kind of result one can expect from installing SDK 11, then SDK 9.5, then SDK 11 again - but it doesn't sound like fun. :) At least we know installing SDK 11 on top of SDK 11 is likely to fix things, not break them.

[Sirber]

the dmo pack still want 9.5 :S

[zambelli]

the dmo pack still want 9.5 :S
wvc1dmo.exe? That's a beta release, I told you so. Even the EULA at the time of the install mentions it's pre-release software. I'm not sure why you're attempting to install it on top of a more recent WMV encoder version. The latest WMV encoder release is in the v11 WMF SDK runtime.

[Sirber]

http://www.microsoft.com/windows/windowsmedia/forpros/encoder/default.mspx

that what you get when you search for wmencoder

[zambelli]

http://www.microsoft.com/windows/windowsmedia/forpros/encoder/default.mspx
that what you get when you search for wmencoder
It clearly says beta though. Also, the VC-1 AP sticky here describes the v11 SDK as having the latest and greatest build of the WMV9 encoder.

[weaver4]

OK, I am getting ready to install from scratch and I am really confused.

Do Install WMP11, and WMEncoder only? Or do I need to install the SDK95 and wvc1dmo too?

[Inventive Software]

Sticky at the top of this sub-forum is a good guide. :search:
http://forum.doom9.org/showthread.php?t=112634

[weaver4]

I saw the sticky. But, the sticky seems to disagree with Microsoft's MediaEncoder web page.

http://www.microsoft.com/windows/windowsmedia/forpros/encoder/default.mspx

That is why I am looking for some clarity.

[Inventive Software]

Agree with the sticky. Honest! :D

[zambelli]

I saw the sticky. But, the sticky seems to disagree with Microsoft's MediaEncoder web page.

That is why I am looking for some clarity.
I'm looking into that issue. We'll try to fix the wording as soon as possible.

[stegre]

Note: Changes in green are edits made after Zambelli's comments in the next post, in an attempt to make this post more useful without reiiterating the everything all over again.
___________

I looked into some of this myself, and I'd have to say everything Zambelli said in the both sticky thread and this one seems 100% correct, at least from my experiments. The words "New" and "latest" on that Microsoft web page (http://www.microsoft.com/windows/windowsmedia/forpros/encoder/default.mspx#WMVA) only refer to the stuff below it. They're technically incorrect statements only in the sense that these are now similarly handled by a new set of DLL's included in WMSDK 11 & I assume WMP 11.

Anyway here's what I confirmed w/ some additional details.


As Zambelli surmised, WMV9 AP Beta does indeed check the version of wmvcore.dll. If it's 10.x or lower it will install, if it's 11.x it won't. The two things that will get your wmvcore.dll upgraded to v 11.x are installing SDK 11 or, I assume WMP11.


Once that's done, you cannot "reduce" the version number of wmvcore.dll by any combination of un-installs of SDK 11 or re-installs of 9.5. Which is somewhat normal; install programs are generally not supposed to replace newer DLL's with older ones since that can break other apps. An XP "rollback" would work if you really wanted the contents of WMV9 AP Beta but there's not much reason you’d need to do that:

a) The SDK 11, and I assume WMP11, while they include different complement of DLL's (see below), do have the required DLL's needed to properly handle WVC1 (VC-1 Advanced Profile) properly. The WMV9 AP Beta package, while it provides a different "single format DLL's", also handle the format properly. SDK 9.5, for its part, as well as WMP10, do not include DLL's which handle the current WVC1 advanced profile - only the now deprecated so-called WMVA [ref here] (http://en.wikipedia.org/wiki/VC-1#WMVA)

b) But if you still, for some reason, want the contents of WMV9 AP Beta after you've installed SDK/WMP11, you can open the whole distribution package in WinRAR (believe it or not) and extract all the files, except the binary install code itself (the part that puts up that dialog box preventing you from installing it). So you can easily get the old "single format WVC1" encoder & decoder DLL's, an installation .inf (right click on it and choose "install"), the VBScript encoder thing, and some other stuff you probably don't need, even if you've already installed SDK/WMP 11. But as Zambelli's been saying, there's virtually no reason you should want or need any of those things if you have the 11.x stuff installed. There is actually one reason you might want a copy of "wvc1dmod.dll", having to do with MPLAYER (believe it or not), but I'll on check that more later and post anything I find in a more relevant forum when I do.
-------
And btw, here's a summary of the whole deal of what the two SDK packages do, as far as far as codecs themselves:


WMV9 AP Beta: Just adds and registers the single purpose DMO decoder and encoder DLL's, "wvc1dmod.dll" and "wvc1dmoe.dll" respectively. It puts these in windows/system32, runs "regsvr32" on them - and then they're available for all DirectShow apps.


SDK 11.0 /WMP11 Installation:
(I'll just discuss decoding here; I assume encoding changes are roughly analogous):

Dispenses with "wvc1dmod.dll" altogether, un-registering and I believe actually deleting the file itself. Replaces it with WMVDECOD.DLL (v11.x), which, besides taking over the handling VC-1 in (as fourcc "WVC1") in an equally compliant way, also handles additional fourcc's WMVA, WMVR, WVP2, WMV1, WMV2, WMV3, and WMVP.

Dispenses with codecs mp43dmod.dll, mp4sdmod.dll, and mpg4dmod.dll, and wmsdmod.dll and replaces them with MP43DECD.DLL, MP4SDECD.DLL, and MPG4DECD.DLL, WMVSDECD.dll for handling MP43, MP4S and MPG4, and MSS1, all respectively. The first three are all older Microsoft MPEG-4 codecs; the last one is a Microsoft "screen codec".

[zambelli]

As Zambelli surmised, SDK 9.5 does indeed check the version of wmvcore.dll. If it's 10.x or lower it will install, if it's 11.x it won't. The two things that will get your wmvcore.dll upgraded to v 11.x are installing SDK 11 or, I assume WMP11.
You are mistaken in your assertion that the WMV9 AP Beta (http://download.microsoft.com/download/3/4/c/34c55eb4-a89b-418c-8192-9c941a4e5596/wvc1dmo.exe) download is the SDK 9.5 package. It's not. The SDK 9.5 download is a separate download (http://download.microsoft.com/download/9/f/d/9fdfb288-b4bf-45fa-959c-1cc6d909aa92/wmformat95sdk.exe)and much like SDK 11, includes a myriad of WM components, not just a single codec.

The v11.x VC-1 DLL's are new & current, as mentioned, the ones in SDK 9.5 are v10.x, and I believe actually aren't even really VC-1, they are technically the deprecated beta WMVA format [ref here] (http://en.wikipedia.org/wiki/VC-1#WMVA), though they are set up to handle the fourcc WVC1.
Correct, but in line with my comment above, beware that what you think is the SDK 9.5 is not the real SDK 9.5. :) But your statement is correct in essence - the real SDK 9.5 does indeed only include the outdated WMVA encoder, and not the VC-1 conformant WVC1 encoder. The beta AP download (wvc1dmo.exe), on the other hand, is fully VC-1 conformant.

SDK 9.5: Just adds and registers the single purpose DMO decoder and encoder DLL's, "wvc1dmod.dll" and "wvc1dmoe.dll" respectively. It puts these in windows/system32, runs "regsvr32" on them - and then they're available for all DirectShow apps.

Out of curiosity: what made you conclude that the wvc1dmo.exe package is the SDK 9.5 runtime? I'm just wondering whether I need to clarify the explanations in the FAQ in any way. I thought the FAQ explained the differences fairly well, but I suppose I could always improve the language.

which, besides taking over the handling VC-1 in (as fourcc "WVC1") in a more compliant way
Once again I have to point out that WMV3 is also a part of VC-1, Simple and Main Profiles namely.

[Inventive Software]

What would make sense is having WVC1 as a fourCC for Simple, Main and Advanced Profile content, so it keeps (at least) MS VC-1 support simpler (to an extent). ;)

[stegre]

shoot, you're right zambelli, my post is really screwed up for a several reasons, some just typos confusing the two packages, at least one major thing I was wrong on. Indeed, my own statement "...SDK 9.5 does indeed check the version of wmvcore.dll.." makes no sense in terms Sirber's original question: it implies you get the dialog "you must have SDK 9.5 installed" when you try to install SDK 9.5. Now that'd be a catch-22! Anyway, I'm at work now, I'll clarify and write a concise summary tonight, and do it a bit more carefully.

[stegre]

Zambelli -

I've edited by previous post as indicated - see if it seems more accurate to you now (again, I agree everything you're saying is indeed accurate). My main confusion, to answer your question, was not that SDK 9.5 and WMV9 AP Beta were the same, but I thought that the former was the full programmer's release package - but including the functionally same binaries as the latter (i.e., that latter was the like a mini "redistributable" of the "full" SDK 9.5). That assumption was, as you point out, entirely incorrect.

BTW, the reason why one might still want to extract "wvc1dmod.dll" from the "WMV9 AP Beta" is that if it's placed in your system32 dir, the current Windows binary release of MPLAYER will automatically use it and properly handle WVC1 nicely. Otherwise it defaults to its built-in ffmpeg lib decoding of VC-1, which seems very buggy. You do not have to run "regsvr32" on the DLL for this to work, which means it will be "invisible" to all DirectShow apps, though the DirectShow apps would choose "wmvdecod.dll" anyway, even if both were present and registered, due to a priority difference. Alternatively, you can put "wvc1dmod.dll" in MPLAYER's "codecs" dir, but the dir has to be renamed "bincodecs" for some reason. And no amount of editing (that I could accomplish) of MPLAYERS's "codecs.conf" file will convince it to use the newer wmvdecod.dll - again, not that it actually matters, but it'd be one less codec to have to keep around. But any further discussion of this belongs in the MPLAYER forum, so I'll stop talking about this here.

- Steve