-
Notifications
You must be signed in to change notification settings - Fork 616
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vispy flickering on Windows with real time data #2574
Comments
@djhoese Sorry to tag you directly but can you help us here? |
I can take a look tomorrow most likely. I tried the code and didn't notice issues on my Mac but I have access to a Windows machine now. |
Sure thank you |
Okay I played around with this more. If we're seeing the same thing, this is aliasing. I can see it on my Mac if using my external (4k) monitor. I'm not sure there's much you can do to fix it easily, but maybe others have ideas. You could start with changing the blending mode with There is a vispy demo of using shaders to plot high frequency signals that might be helpful. There are also some previous issues discussing MSAA, but unfortunately it's still not supported in vispy. Sorry I can't be more helpful. I will come back if anything else comes to me. |
Thanks for the help. I tried searching for things on my own as well. I integrated my code into PySide6. We had data coming in at 100 ms and faced flickering issues once we started windowing. As I debugged I realised if we plot just 1 in 10 times i.e every 1 second the flickering goes away. As I checked the examples.. ex03a_data_sources_timer, ex03b_data_sources_threaded_loop and ex03c_data_sources_threaded_events I realized that they too are being toggled at every 1 second either using Is this really a known constraint? Then we can convey the same to our customer and be happy with plotting data every 1 second. Maybe later you guys can fix this |
Cool. We have a limitation that we can only use PySide6 due to licensing limitations but that's ok. Could you help us where do you set the 'samples' method/parameter in Qt backend that you mentioned? Maybe we can try something similar in PySide6 if that exists. |
I don't think it's exposed in the API, but I could be wrong. I hard-coded the value here which should apply to both PySide and PyQt backends: vispy/vispy/app/backends/_qt.py Line 300 in 512a1ce
|
Ah ok will try it for my code as well. Who knows it might be a break through we need. |
Hi! Sadly this still remains a problem for us. I tried changing it to 16 and of course saw some improvement but sadly it still does not match our requirements. The configuration for our system is: Windows version CPU: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz 2.90 GHz Below is the output of "vispy.sys_info()": One key thing that I observe is egl is none. Is that the issue?
|
@djhoese Hi! Can you please look into this? We would really like to see the flickering getting stopped. We evaluated wide range of libraries for our project and based on client's requirements vispy seems to be the frontrunner. A bit of help from you or someone else would help us a great great deal. |
Sorry, I do not have time and do not have a Windows machine to test on...nor would I know how to fix this. My priorities: #2570 |
I am trying to create a real time application using vispy. Basically I need to maintain a window of 1000 data at a time. So once the data that I receive crosses 1000 I will try to shift the window as well as the x-axis using 'set_range' method. This is when the flickering issues start appearing. Below is the code for the same. I am executing the code on Windows 10 and my python version is 3.12.1.
Have also attached the execution logs for your reference
realtime_execution_logs.txt
The text was updated successfully, but these errors were encountered: