Terradici vs Remote Boost

Hello Logik Friends,

I got an email from someone at HP who was curious to hear thoughts about Terradici vs Remote Boost. Since HP is acquiring Terradici he was interested in hearing the strengths and weaknesses of each product, from the user’s perspective.

Please leave your comments here and I’ll pass them along!

Terradici PCoIP client seems to work pretty well. Fairly snappy depending on your ping to the machine you’re using. Obviously tearing during playback and other streaming related issues would be great to improve.

They should also sort out some simple keyboard preference settings for Tech Ops/IT to map keyboards for OSX and Windows, so config-wise things are simpler, and keys are mapped so that if you have a Mac Flame and you PCoIP into a remote Linux Flame, the experience should have parity. At one shop all the scroll/pause/prntScrn keys work well but the shift-alt noodle toggle doesn’t work, or vice-versa at another. I think it was an issue when multiple modifier keys were held and another is toggled. (Holding shift & pressing alt to cycle F/B/M noodles for example)

One of the big Terradici advantages over Remote Boost is having an OSX client, where I needed to run VMware to run Linux for Remote Boost

ive used both extensively.

  • HPZ has a easier licensing model, makes it easier to deploy for smaller studios

  • Teradicis documentation completely sucks, its complete and utter garbage, there are even wrong in places.

  • teradicis product naming and whats behind it is extremely confusing, CAS+, CAC, pcoipUltra. all the things.

  • HPZ resolution matching never works well, teradici can do this just fine.

  • Teradicis workstation cards have paid firmware updates and generally dont work well, I mean if you dont disable dithering on the host it craps out? Why?!

-Teradici PcoipUltra if setup with a broker and UDP works very well, although you dont have many settings/ all hidden through GPO and other funky
config things… not good for small

-Teradici pcoip ultra is apparently 4:4:4? again no documentation just marketing blah blah.

-Teradici has a mac Host , although I havent tried it out.

In general I feel like HPZ is good for smaller studios and Teradici is good for larger ones.

They both need some useabillity improvements, Its not the technology behind it thats lacking, but the documentation and administration.

Lets hope ho doesnt pull a autodesk… at least we still have parsec …

1 Like

About Parsec…

Finn sums it up pretty much.

HP is easier.
Teradici is better image quality.

1 Like

Teradici performed a little better than ZCentral, but seemed to break if someone breathed too hard.
I have way less downtime on ZCentral. The biggest drawback of ZCentral is that if I want to use my 3440x1440 Ultrawide from home, the remote monitor has to unplugged with a DisplayPort dongle in its place. Makes it harder to easily switch a machine from Local to Remote.

That can be fixes, with a headless mode in the nvidia settings and a custom EDID , I had the same issue with my ultrawide

You can extract your home EDID and inject it into the Xorg, works a treat.

1 Like

@finnjaeger is this the procedure in the manual?

no took me a while to figue it out with a bunch of testing and scouring nvidia-xconfig … Ill try to find it and post it here, think Inhave posted this in the facebook forum back in the day

and here it is backup your xorg … i dont know what flame does here and if it matters for some I run cinnamon / CentOS and HPZ

====== HEADLESS RGS ======
First create /edid.txt , use values below or make your own

Single screen:

nvidia-xconfig -a --allow-empty-initial-configuration --use-display-device=“DFP-0” --connected-monitor=“DFP-0” --custom-edid=“DFP-0:/edid.txt”


nvidia-xconfig -a --allow-empty-initial-configuration --use-display-device=“DFP-0, DFP-2” --connected-monitor=“DFP-0, DFP-2” --custom-edid=“DFP-0:/edid.txt; DFP-2:/edid.txt”

after this run:

init 3 && init 5

you might need to switch around DFP-X numbering , cant be anything real screens are connected to it seems,

you can get a EDID text file using nvidia-config on Linux on a machine with similar monitors connected. there are also windows tools.

Sample EDID thats supports most common used resolutions, also ultrawide 3440x1440

00 FF FF FF FF FF FF 00 10 AC AA A0 4C 33 4D 30 2F 1B 01 03 80 50 21 78 EA FD 25 A2 58 4F 9F 26 0D 50 54 A5 4B 00 71 4F 81 00 81 80 A9 40 D1 C0 01 01 01 01 01 01 E7 7C 70 A0 D0 A0 29 50 50 20 CA 04 1E 4F 31 00 00 1A 00 00 00 FF 00 46 31 54 31 57 37 42 4B 30 4D 33 4C 0A 00 00 00 FC 00 44 45 4C 4C 20 55 33 34 31 35 57 0A 20 00 00 00 FD 00 30 55 1E 59 20 00 0A 20 20 20 20 20 20 01 9E 02 03 22 F1 4D 90 05 04 03 02 07 16 01 14 1F 12 13 5A 23 09 07 07 67 03 0C 00 20 00 38 44 83 01 00 00 9D 67 70 A0 D0 A0 22 50 50 20 5A 04 1E 4F 31 00 00 1A 9F 3D 70 A0 D0 A0 15 50 50 20 8A 00 1E 4F 31 00 00 1A 58 4D 00 B8 A1 38 14 40 94 2C B5 00 1E 4F 31 00 00 1E 3C 41 B8 A0 60 A0 29 50 50 20 CA 04 1E 4F 31 00 00 1A 56 5E 00 A0 A0 A0 29 50 30 20 35 00 1E 4F 31 00 00 1A 00 00 00 25

To revert this when wanting to use the pc locally you will need to run this to reset xorg back to default after turning on monitors

nvidia-xconfig -a

and then

init 3 && init 5