|
|
WMA: MMW clearly detect that WMA Codec can't be Initialized by system and it can be interpreted as codec missing, thus using missing codec is logical choice and use specific page to explain what happened. If MS fix issue and or we create new codec for WMA it will not throw same error and codec will be initialized correctly. |
|
|
|
In this case, the codec dll is initialized/loaded normally, all needed functions and system libraries exist. The problem occurs at the very beginning of encoding process, when trying to create WM writer. So the only way to detect this is try to start encoding. I think, the error message, that encoding failed because of possible problem with OS version (or directly with system codec in this OS version), could be enough (or the description on web will be localized sooner?). In fact, the codec is not missing, it is "only" not working correctly for WMA encoding and returns error code ("No such interface supported"), where it should not. E.g. for tagging or WMA decoding it works.
If MS fix this, it simply start working again. |
|
|
|
Anyway, maybe opening web page (like http://www.mediamonkey.com/mediamonkey-wma-encoding-failed) with some KB article would be better, we can update it as soon as we know some solution, e.g. if installation of some MS hotfix will help. |
|
|
rusty
2016-09-16 13:37
administrator
~0045677
Last edited: 2016-09-16 13:38
|
OK, so it would be something like this:
---------------------------------------------------------
Error
---------------------------------------------------------
Conversion (WMA - <OS Name> <Version>): Not Supported
[Help] [OK]
---------------------------------------------------------
Where [Help] links to http://www.mediamonkey.com/mediamonkey-wma-encoding-failed
Note:
- no new strings are required in this proposal
- the link and accompanying article have been implemented.
|
|
|
|
Updated string to the following since there's a : in the Conversion string:
Conversion: WMA (<OS Name> <Version>) - Not Supported! |
|
|
|
Fixed in build 1810. |
|
|
|
Original fix and dialog showing Verified 1810
Reopen as after that dialog MMW show list of failed tracks with generic info "?????.wma was not created successfully" I would also append string from error dialog to be more verbose and clear "?????.wma was not created successfully WMA (<OS Name> <Version>) - Not Supported!" |
|
|
peke
2016-09-19 22:08
developer
~0045698
Last edited: 2016-09-19 22:09
|
as pointed Selecting 10 files and initiating WMA encode shows 10 Dialogs that WMA is not supported and 10 Dialogs of failed creation.
More verbose String is lower priority.
|
|
|
Ludek
2016-09-20 10:23
developer
~0045701
Last edited: 2016-09-20 10:40
|
Yes, this was definetely bad.
Fixed in 1811. Only one single log is shown for all files at the end of whole conversions (with the Help button).
Note that the [Help] button goes to http://www.mediamonkey.com/mediamonkey-wma-encoding-failed , but it should be for common convert failures (not only WMA related). But this is just about updating the KB article.
|
|
|
rusty
2016-09-20 14:01
administrator
~0045707
Last edited: 2016-09-20 14:53
|
OK, so since the error page is now generic (i.e. it redirects to a kb article that summarizes all encoding problems) we should use a more generic redirect such as http://www.mediamonkey.com/mediamonkey-encoding-failed and rewrite the KB article as a generic article that links to individual articles re. encoding failures.
|
|
|
|
OK, changed to http://www.mediamonkey.com/mediamonkey-encoding-failed in build 1811 |
|
|
|
Verified 1811 |
|
