In wtware 5.8.62, local chrome should run on Raspberry Pi 4.
Firstly thank you too the wtware guys for their hard work getting this out to us! Initial testing so far the results are a fantastic with a significant improvement over the RPi3 b+.
My test environment is a Windows 2016 pooled session collection, 16CPU's with 32GB of ram, no vGPU.
I configured my clients with fairly default settings as you would expect, network boot, 50ms sound buffer, 200ms redraw_delay, 32bpp, hw sound use a USB sound bar (plugged into the USB3.0 port). I use a mix of combined USB port power (2A max) for some and the official RPi 2.5A 5.1v power supply for most of the other RPi3+'s.
Using the 3 model B+ I could get youtube to play in windowed mode with around 30fps @ 1080p, full screen is unwatchable. Everything else from word processing to basic multimedia and editing is great.
With the RPi4 4GB version booting off SD (will network boot when supported) same settings, booted 30% quicker than RPi3+, no issues. Once in Windows desktop everything was very crisp with zero jitter or artifacts. YouTube played perfectly and yes, full screen works! No problems at all!
Please note I am only using a 2.5A power supply, I assume there was still power available and that the CPU wasn't throttled due to no power warning however a full 3A may improve things down the track.
This basically means I'm replacing all our RPi's with 4's however I'm waiting on the 2GB version to test first, I suspect very close results to the 4GB version. I will test the 1GB version tomorrow and update on experience, I'm not confident on seeing big improvements though!
Hi Fraal,Fraal wrote: ↑Tue Aug 06, 2019 4:46 pmOne last thing to add, I configure the remote desktop settings to use lossless video setting however I have also configured it to detect network bandwidth and compress based off bandwidth, meaning some client sessions the video is pixelated and goes to lossless when image is static. Not a great experience when watching videos however the end result is a video with audio in sync and no lag\jitter. I will change host config to full lossless and then should see some changes, I'm hoping windows mode videos are perfect lossless with sound in frame sync, full screen yet to comment!
Thanks for testing, can´t be long till I follow in your footsteps How did you configure the bandwidth and compress based off bandwidth?
Now for a silly question: How do you shutdown rpi once it´s booted into the remote session? I assume Windows Shut Down pulldown menu will shutdown the host computer?
Why do not the configurations work in the configuration file? as described here http://wtware.com/docs5/configfile.html not, with the restart always the standard templets and not the after configured (see below) although after the restart, according to the web interface, the configuration file is the changed?
configuration before the change
Code: Select all
server=192.168.xxx.xxx rdpcompression=off domain=domain.de keyboard=de language=de,default M2_display=1280x1024, 1 ntp=192.168.xxx.xxx timezone=W. Europe Standard Time display=1680x1050, 0 screenswitch=Win-Ctrl-N video=hyperv_fb(F) connection
Code: Select all
turnoffmenu=on connection displayname=w8_jd server=192.168.xxx.xxx rdpcompression=off domain=domain.de keyboard=de language=de,default display=1920x1080, HDMI M2_display=1280x1024, 1 ntp=192.168.xxx.xxx timezone=W. Europe Standard Time screenswitch=Win-Ctrl-N video=hyperv_fb(F) connection displayname=Chaos_sw server=192.168.xxx.xxx domain=domain.de keyboard=de language=de,default display=1920x1080, 0 M2_display=1920x1080, 1 ntp=192.168.xxx.xxx timezone=W. Europe Standard Time screenswitch=Win-Ctrl-N video=nvidiafb(F) connection displayname=andere RDP Sitzung server=--new-- chrome_language=de domain=domain.de keyboard=de language=de,default display=1680x1050, 0 M2_display=1280x1024, 1 ntp=192.168.xxx.xxx timezone=W. Europe Standard Time screenswitch=Win-Ctrl-N video=hyperv_fb(F)