Post to Twitter |
Comments (1) |
Views (9057) |
Recently I published a video blog post about RAVE (Remote Audio & Video Extensions), the technology behind SpeedScreen Multimedia Acceleration. RAVE supports high quality playback of media streams that can be decoded by a media player that uses DirectShow or DirectX Media Objects (DMO). A question came in from the field asking how a customer can determine whether SpeedScreen Multimedia Acceleration is functioning. So here are some handy tips for verifying whether RAVE is working or not. In addition, you'll find a helpful troubleshooting article in our Knowledge Center.
The quick answer is that you can probably tell by the quality of the video playback since RAVE delivers a user experience on par with running the media player locally. But here are some other telltales. When RAVE is working, a black rectangle will quickly flash by as the video begins to play. Server CPU usage will be much lower than if the video were being rendered on the server (for comparison, you can disable SpeedScreen Multimedia Acceleration on the console and try playing the same video). Searching for "FilterInt" in ProcessExplorer will show that DLL loaded by the media player's process.
Are there any enhancements that you would like to see to make it easier to discover that an additional codec needs to be installed on the client (or even on the server to support server-side rendering as a fallback)? For example, one possible enhancement would be for SpeedScreen Multimedia Acceleration to record RAVE events in the Windows Event Log.
Derek Thorslund
Product Strategist, Multimedia Virtualization
Comments (1)
Jul 30, 2008
Simon Bramfitt says:
Derek On RAVE enhancements I think you've got the most important enhancement i...Derek
On RAVE enhancements
I think you've got the most important enhancement identified already. The ability to inform admins of missing client-side and server-side codecs is a must, and just to be clear this means not just a single generic error msg, but a clear statement of what and where the missing codec is including the FQDN of the client device.
A second ehancement might be to give admins the ability to disable server-side rendering through the management console.
Add Comment