GUI Rendering delay causes artifact pulses on Widgets

[MobileRez]

Problem

While using the Open BCI Gui with the Time Series, Band Power, & Head Plot widgets I would get random artifact data in the device across all channels and all configurations. This is also duplicatable when just using the head plot widget.

Noticed there is no system setting to set recourse priority with the APP, this is causing it to not be able to access all the resources it needs, not sure if the fact its build with java has any impact with that, though would explain the unreasonable high demand on resources.

EDIT 7/3/18
Added Links to images showing reported issue.
Photo of Device and wired electrodes
Photo of GUI W/ reported bug noise
Photo of Closeup of bug on all channels

Expected

No artifact nose is GUI from rendering issues, able to control System Resource priority from software as later versions of Win 10 do not let you set it from task manager therefor you cannot access all system resources as needed.

Operating System and Version

Windows 10 Pro x64
Version: 1709
Build: 16299.431

GUI Version

3.3.1

Running standalone app

Running in OpenBIC GUI

Type of OpenBCI Board

Cyton running firmware v3.1.1

Are you using a WiFi Shield?

No - But I would like to.

[andrewjaykeller]

Okay so this is all because of the headplot :(

Did you try changing the smoothing at all? I think the headplot needs to be rewritten!

[MobileRez]

Yes and no setting I could use on that Head Plot graph could help smooth things out. I know most people would call my surface book (1) with performance base old by now but its got some decent power too it and a decent graphics card as well so it should be able to handle this rendering... that must be some really bad code...

[retiutut]

There is evidence on my computer to support @andrewjaykeller's conclusion. On a Mac, Headplot single-handedly drops the GUI frame rate from 60 fps to < 30 fps! Here are the screenshots to document this.

At one point got 15 fps and lots of packet loss showing in Processing console. I moved the Cyton + dongle closer together. After, getting 23-26 fps with Headplot active with all smoothing settings. It's possible the strange spikes are associated with packet loss.

Here's an example where I put the dongle behind some metal on my desk to cause packet loss while running Headplot:

[retiutut]

@paquettejp You are experiencing packet loss related to the WiFi shield and Cyton, hardware related. Issue is described in detail already. #231 The team is definitely aware of this and we are still working on a plan of action, up to designing new hardware.

This issue here is likely caused by Headplot widget being greedy, so not related to packet loss.

[retiutut]

@paquettejp the issue here, about Headplot FPS, is definitely on the table to be fixed soon!

For now, try closing other programs, especially your web browser, if possible.