View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0013496 | MMW v4 | General | public | 2016-09-06 14:22 | 2019-11-27 14:07 |
Reporter | rusty | Assigned To | |||
Priority | immediate | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Fixed in Version | 4.1.15 | ||||
Summary | 0013496: WMA and WMV encoding isn't working after Windows 10 Anniversary build 1607 upgrade | ||||
Description | MMW can't convert any format to WMA Lossless LOG File and sample track are on FTP | ||||
Additional Information | CRM-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 | ||||
Tags | No tags attached. | ||||
Fixed in build | 1822 | ||||
duplicate of | 0013475 | closed | michal | MMW v4 | WMA and WMV encoding isn't working after Windows 10 Anniversary build 1607 upgrade |
related to | 0013517 | closed | Ludek | MMW v4 | Provide useful error message when WMA/WMV encoding fails due to Windows 10 Anniversary Update |
related to | 0013866 | assigned | michal | MMW v4 | New WMA encoder, used from Win10 build 1607, does not support 2-pass encoding |
related to | 0013867 | closed | michal | MMW v4 | New WMA encoder, used from Win10 build 1607, does not support progress and termination |
related to | 0016148 | closed | michal | MMW 5 | WMA settings dialog is missing |
|
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). |
|
First version implemented in build 2034. It supports 1-pass CBR and VBR encoding. |
|
Remaining issues: 1) 2-pass encoding 2) implement some encoding progress 3) analyze and fix WMV encoding |
|
Update - 3) it seems, WMV encoding is working as expected, it was probably test error. |
|
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). |
|
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? |
|
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 |
|
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. |
|
Remaining issues tracked here: 0013866 - 2-pass encoding 0013867 - missing progress and termination |
|
Verified 1822 |