Configuration Persistence
[The feature associated with this page, Windows Media Format 11 SDK, is a legacy feature. It has been superseded by Source Reader and Sink Writer. Source Reader and Sink Writer have been optimized for Windows 10 and Windows 11. Microsoft strongly recommends that new code use Source Reader and Sink Writer instead of Windows Media Format 11 SDK, when possible. Microsoft suggests that existing code that uses the legacy APIs be rewritten to use the new APIs if possible.]
None of the write-enabled properties described in this documentation are saved by the Windows Media SDK. Each application that uses the SDK must provide its own persistence procedures as needed and invoke the appropriate set method upon each instance of the SDK. In this way, configuration changes made by one application do not affect another application. For example, changing the buffering time in one player does not affect another player.
The one exception to this rule is for the credentials information. If the application indicates, in its return from the AcquireCredentials call, that the user ID and password information must be persisted, the SDK saves this information.
Related topics
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for