Andrew Zonenberg comments

Results 160 comments of


                                            Andrew Zonenberg

SPIRV linking (and other fedora isms?)

Should be fixed by https://github.com/ngscopeclient/scopehal-docs/pull/104 and some prior fixes

Add preferences for which Vulkan device to use

Depends on #457 . This might require some retooling of the preference class, because we need to consider what happens if the user adds/removes a GPU after a preferences file...

ngscopeclient: use VK_EXT_memory_budget if available

Also potentially interesting: VK_EXT_memory_priority, VK_EXT_pageable_device_local_memory

Improve Primus/Optimus support

We still need to look into how PrimusVK manages power. Do we have the ability to power the dGPU on/off on cue? Is data lost / are handles invalidated when...

Accessibility: Some (core) functionality is only accessible through unclear methods like middle clicking or double clicking specific GUI features. Users might not find or have the ability to access the functionality because of this.

A two-button mouse with scroll wheel is currently documented as a minimum hardware requirement. We can work on adding additional ways to access some of this functionality such as keyboard...

Channel 1 waveform in glscopeclient differs from oscilloscope screen, timebase settings differ

Max memory depth in the Siglent driver is I think 12.5M; the waveform download on Siglent scopes is incredibly slow with deep memory so we add an early-out to avoid...

Intensity grading: weight alpha value for each segment by length of segment to better emulate a CRT

This should be configurable by preference or even per viewport, definitely not a global always-on setting.

Signal to Noise filter (Measurment/Statistic?)

@602p is can we close this now that SNRFilter is now merged?

GPU accelerated rendering of protocol decode event bubbles

In ngscopeclient, we build the decode bubbles every frame in immediate mode, then submit a batch to the GPU. Better, but still not as fast as it should be (vs...

Allow historical waveforms to be displayed in the plot, used as filter inputs, etc.

This also depends on #283: historical waveforms used in math have to be pinned automatically so they can't be deleted when history rolls off the end.