VirtualGL TurboVNC

[redge]

VirtualGL TurboVNC
inside UltraVNC coded with OpenCL API server/viewer would be amazing virtualizing usage of vGPU/vCPU

nativ DirectX between windows to windows should be better ?


for
Video/2D/3D application

[Rudi De Vos]

When i'm correct, opencl is an api like directx or opengl.
Your application needs to be compiled for opencl or directx...

A directx application can't use opencl and an opencl application can't use
directx....

What's the usage for opencl in vnc when all apps on windows now use directx ?

[redge]

new standard coding for access hardware ressource CPU/GPU as native via OS OpenCL API like MacOS.X and all application cad use it witout recoding.

cross plateform: like RFB
OpenGL/TurboVNC for cross plateform between Linux/Windows/Mac
OpenGL via VirtualGL
like Xrdp between Linux/Unix

main usage cross plateform: like RFB
Video/3D/2D application like google hearth/map/street, etc.. is actually very slow by remote

[Rudi De Vos]

Redge,

Applications need to rewritten for opencl.

When you write a game you can use different graphical egines.
DirectX, openGL, openCL

The 3 engines are not compatible, you make a game that use opencl or that use directx... not both.

OpenCL is cross compatible: Same source can be use on linux, apple,windows....

The gain for uvnc when opencl get installed as standard extra driver option on windows would be that you can use the GPU to encode/decode
images. When that time comes, we need to add new encoders that can be
processed by the GPU... ( jpeg ok, zlib nok)

[redge]

> The 3 engines are not compatible, you make a game that use opencl or that use directx... not both.

OK this i clear like startup
Google Earth DirectX
or
Google Earth OpenGL

> OpenCL is cross compatible: Same source can be use on linux, apple,windows....

> jpeg ok, zlib nok
I don't believe about zlib...
you can use software engine like codec H.264

read below:
There will be several initial ways RemoteFX will function once it's released, including:
Full software-based encoders on the host.
a GPU/CPU-based encoder (with extensions to Hyper-V to let GPUs be shared between multiple VMs).
A custom chip-based encoder, either on a plug-in card or built-in to the host.

Similar variations will exist on the client side, with traditional PCs being able to decode RemoteFX fully in software (either running on the CPU or, if available, the client GPU). There will also be options for chip-based plug-in cards to fully offload the decoding from the client CPU, and new lines of thin client devices with the decoding circuitry built-in to their hardware.

Microsoft has stressed that the RemoteFX codec is the same regardless of whether it's running in software on the CPU, the GPU, or a custom plug-in card. And any client/host combination of software, GPU, or plug-in card will work, because the data on the wire is the same regardless of how it was created or how it's being decoded. (I visited Microsoft's Silicon Valley Campus earlier this week and recorded a video demo of RemoteFX in action on several clients.)

As I briefly mentioned before, RemoteFX is just an enhancement to RDP's virtual channel that handles graphics remoting. It's not a replacement for RDP. This means that all the "other" RDP characteristics and capabilities are the same. (Same ports, same encryption, same printing and client device remoting, etc.) It also means that you don't have to have a RemoteFX-enabled client to connect to a RemoteFX-enabled host as the client and host will auto-negotiate their capabilities (or lack thereof) around RemoteFX just like any other RDP component.

reference:
http://www.brianmadden.com/blogs/brianm ... titor.aspx

[Rudi De Vos]

Current, you can only use a 2008 R2 server with SP1 as RDP host that
support RemoteFX.

The idea of MS is the have one big server with HyperV that allow low
hardware clients to connect. They return back to the good old days of the X-terminals. The advantage is that you only need one server with 1000$ video cards instead of having one in each client.

RemoteFX SERVER only works on a SERVER 2008 R2 SP1 with HyperV.
The RemoteFX wddm driver is something that you need to install in the
guest OS of the virtual server. Yes, you can use it for WIN7, but win7 need to be installed on a virtual server...

Possible this will change in the future, but during the Beta tests this was the only way it worked.