View Issue Details

IDProjectCategoryView StatusLast Update
0013496MMW v4Generalpublic2019-11-27 14:07
Reporterrusty Assigned To 
PriorityimmediateSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version4.1.15 
Summary0013496: WMA and WMV encoding isn't working after Windows 10 Anniversary build 1607 upgrade
DescriptionMMW can't convert any format to WMA Lossless

LOG File and sample track are on FTP
Additional InformationCRM-916-27953
OMX-279-82372
TYR-986-33076 confirmed
HJB-691-86801 confirmed
https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/95cccc74-efae-43c6-a169-bf534cd6f32b/wmcreatewriter-is-not-working-after-windows-10-anniversary-update-1607?forum=windowssdk
TagsNo tags attached.
Fixed in build1822

Relationships

duplicate of 0013475 closedmichal MMW v4 WMA and WMV encoding isn't working after Windows 10 Anniversary build 1607 upgrade 
related to 0013517 closedLudek MMW v4 Provide useful error message when WMA/WMV encoding fails due to Windows 10 Anniversary Update 
related to 0013866 assignedmichal MMW v4 New WMA encoder, used from Win10 build 1607, does not support 2-pass encoding 
related to 0013867 closedmichal MMW v4 New WMA encoder, used from Win10 build 1607, does not support progress and termination 
related to 0016148 closedmichal MMW 5 WMA settings dialog is missing 

Activities

rusty

2016-09-06 14:23

administrator   ~0045575

Per offline discussion, Michal is working on this for MM5 and will backport to MM4 (0013475) IFF no fix is forthcoming from MS (release timing 4.1.14 vs 4.1.15 tbd depending on implementation effort).

michal

2016-09-26 11:22

developer   ~0045769

First version implemented in build 2034. It supports 1-pass CBR and VBR encoding.

michal

2016-10-20 16:59

developer   ~0045975

Remaining issues:
1) 2-pass encoding
2) implement some encoding progress
3) analyze and fix WMV encoding

michal

2016-10-21 07:11

developer   ~0045982

Update - 3) it seems, WMV encoding is working as expected, it was probably test error.

rusty

2016-12-16 15:46

administrator   ~0046571

Last edited: 2016-12-16 16:00

Although 0013475 was technically resolved, it introduced UI problems that need to be fixed -- it exposes 2 distinct WMA encoders to users instead of a single set of configs that apply in all cases. This results in 2 sets of problems:
1) Users don't know what encoder to choose
2) If the user has settings on the original encoder, they're lost if they upgrade to a system that only supports the newer encoder

So this really must be fixed. The options could be:
a) Only enable the new encoder on systems where the old doesn't work.

b) Use the new encoder in all cases, assuming we can fix the remaining issues described at 0013496:0045975

In both cases, only a single set of configs should be used (i.e. the fact that we've switched encoders should be transparent to the user).

peke

2016-12-21 12:23

developer   ~0046686

Last edited: 2016-12-21 12:25

As talked on IM We have changed wording to "WMA (Win 10)" to remove confusion and till we find more stable permanent approach.

Maybe we should also add that info in error dialog so that user is pointed where to make switch?

rusty

2016-12-21 14:42

administrator   ~0046691

The "WMA (Win 10)" text sounds like a better interim measure.

I don't think there's a need for any additional info in the error dialog since afaik, the error dialog links to the kb article which indicates the solution.

Assigning back to Michal for resolution of 0013496:0046571

michal

2017-01-04 16:16

developer   ~0046832

Transparent use fixed in build 1822.

It will use old encoder on older systems and new encoder plugin from Windows 10 build 1607. New encoder plugin takes settings from the old plugin by default and converts them to its new format automatically. It adjusts values appropriately, in case of not supported format, i.e. makes 1-pass from 2-pass, or CBR from ABR, or replace some other unsupported values with the nearest supported.
Note, new encoder has slightly different config dialog, but it should not be problem.
During testing you should test also related autoconversions.

michal

2017-01-04 16:29

developer   ~0046833

Remaining issues tracked here:
0013866 - 2-pass encoding
0013867 - missing progress and termination

peke

2017-01-10 19:51

developer   ~0046902

Verified 1822