With the release of 7.6 FP3 in September 2015 came a new graphics-policy "With video codec for compression, "with the new settings:
1. Use video codec, if available. , (Default)
2. Non-video codec use
stood with the introduction of 7.9, a third option is available:
3. Use video codec, if preferred. ( new standard )
Confused? Probably. But after you're done reading this blog, hopefully everything will be clear, and I would have helped answer questions such as:
- W has to do these policies
- D I o this policy to set anything other than the standard?
First, a little a few years ago, Microsoft has made some changes to the way Windows graphics are done in the history ...
. Vista introduced DWM, a compositing window manager can use GPU acceleration and provide a truly engaging experience. Traditional GDI-based applications were still supported, but the exchange of GDI had removed begun.
This meant that we [Citrix] had, GDI, also. Our Legacy ThinWire graphics mode is essentially a GDI-based remoting solution with some very clever optimizations that ICA established itself as a pioneer in remote protocols. But in the new bitmap world only Windows 8 and Windows Server 2012, these optimizations had little or no effect and it became clear that a new solution was needed.
In XenDesktop 7.0, we ThinWire Advanced. This additional adaptive H.264 (a.k.a "Deep Compression"), which previously required HDX 3D Pro, the arsenal of codecs in the Thin Wire Super Codec. At the same time we have ThinWire default prefer using H.264, the receiver-user has supported it (Windows Receiver 3.3 or higher). For recipients who did not support H.264 - for example old thin clients that can not be updated - assuming Thin Wire Advanced mode a "compatibility". We also retained for use with Windows Server 08 Legacy ThinWire GDI optimized [R2] and Windows 7 or XP.
isuse of the Thin Wire of H.264 in the special are some very clever techniques used to make sure the text remains sharp and crisp. However, this comes at a price, and if Legacy ThinWire compared (on a legacy version of Windows), the scalability of the server is generally lower and the bandwidth usage is generally higher. In addition, the original compatibility mode also came at a considerable cost of increased bandwidth usage and server CPU utilization.
occasionally require server-side video rendering Thanks to our multimedia redirection technologies, only many Citrix customers, and can not be used 3D graphics applications. For such customers to take advantage of full-screen H.264 have not justify their costs. Recognizing this project "Snowball" was born. The challenge? To develop experience a non-H.264 solution maintaining the same amazing server scalability and bandwidth characteristics and the same great user that customers with legacy GDI-based Windows enjoyed in this new world of DirectX and fully composited desktops.
[1945001Mit] After this ThinWire Compatibility Mode has been said from the soil rehabilitated by Thin Wire adapt (or beat) server scalability and bandwidth usage of legacy. This we have in 7.6.3 and informally called this progress "Thin Wire Plus". What is even more impressive that we were doing this, a receiver / endpoint upgrade without requiring. So no need to worry about the old thin clients which can not be upgraded, we have 10 remoted Windows to eight years old 800 Mhz receiver hardware 11.x simply going well!So to recap , Thin Wire with H.264 was the "default" no-policy setting in XenDesktop 7.0 for modern Windows and this remains the case in the 7.6.3 Long Term Service Release (LTSR). However ThinWire without full-screen H.264 encoding - also known as compatibility mode known -. It is less expensive and very often a better choice
Up 7.6 FP3, there was no way for the administrator a preference to express compatibility mode to use. So, how does ThinWire the mode selection map on the "Use video codec for compression" policy?
"With video codec for compression"
It became clear that in addition to the revised compatibility mode implementation, we needed a way for the admin a preference to express with full-screen H.264 these instead of the then-default ThinWire mode to use. Thus we have the "Use video codec for compression" policy, the change is essentially this selection with the help of two policy settings: ". Use video codec, if available"
- "Do not use." Using Thin Wire with H.264 (default no-policy setting)
- - - Use compatibility mode
At this point you might be wondering, " If the new compatibility mode looked so good, why does Citrix default in 7.6.3 as Thin Wire with H. 264 "leave
There is a simple answer to this question: we wanted more data. At Citrix, we take great care when changing the default settings under consideration. Many customers use default values and the behavior under the covers can turn sometimes very disturbing. We wanted to be absolutely sure that the new mode is performed as well as we had seen internally before considering a change to the standard Thin Wire graphics mode.
Now that the time has come, and after a lot of positive customer feedback improved server scalability and lower bandwidth usage reporting, we have the switch. In 7.9, we have a new approach to politics:
- (no-policy setting default)
is Today "Use video codec, if preferred." this literally cards "do not use" in the setting does not make, rather than "do not use", so why do we have added a new setting and default? Quite simply, we want to allow future versions of the product, to make the decision automatically, rather than the administrator expects one or the other to choose
There are an exception to this - again based on lack of information - the. I will discuss next. want
when I would choose to "Use video codec available when."?
In other words, " when would I want my users with full-screen H.264 given ThinWire ?"
There are some workloads provides for Thin Wire with H.264 best performance. In particular workloads with video or large moving images on WAN links are better performance generally. As a video codec, H.264 images to be supplied at low bandwidth excellent with good quality. For this reason, when the XenDesktop VDA installed 3D Pro mode in HDX, it is prefer to use Thin Wire with H.264, unless by "Visual Quality" policy overridden.
Another reason a Thin Wire with H 0.264 prefer is for devices that can decode H.264 efficiently. For example, based on the recently announced Citrix Ready Raspberry Pi Thin Client on the Pi 3 has H.264 hardware decoding functions and enables easy work of full-screen 1080p Server rendered video - can keep the server available! However, for most workloads, Thin Wire compatibility mode is still the better choice. In fact, at this year's Synergy conference in Las Vegas, the Sandbox Citrix had 1080p 30FPS desktop and 3D app demos on the Pi _not_ with H.264!
Summary
As requested, here is a table summarizing the above:
| XA / XD version | "with video codec for compression" default policy | Which mode do I get |
| 7.0 - 7.6 | n / a | Thin Wire & H.264 (*) |
| 7.6.300 - use 7.8 | , if available | Thin Wire & H.264 (*) |
| 7.9 | use if preferred | Thin Wire compatibility (TW +) |
(*) Only selected when the receiver is new enough. Otherwise Thin Wire compatibility is selected instead.
My advice
"is used if preferred." In most cases, the "Use video codec for compression" policy should not change need from him default. In this as-ensures Thin Wire compatibility for all Citrix connections is selected, and is optimized for scalability, bandwidth and excellent image quality for typical desktop workloads. For intensive 3D / host rendered video workloads - especially on a WAN - you can this policy of trying to "use, if available," and see whether the user experience improves
Where could this go in the. Future?
Today, identifies the Adaptive Display Technology in Thin Wire moving images (video, 3D in motion) and is considered aggressive JPEG compression to deliver a smooth user experience. What would happen if Adaptive Display has been improved to use H.264? Overall, the impact on the scalability of the server would be lower, because the use of H.264 selectively would (only when the user watched a video, and only for the part of the screen). Certainly some interesting possibilities ...
0 Komentar