Skip to content
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

WVisualWaveform #2 becomes corrupted after coming out of full screen mode #4928

Closed
mixxxbot opened this issue Aug 22, 2022 · 13 comments
Closed

Comments

@mixxxbot
Copy link
Collaborator

Reported by: deftdawg
Date: 2008-03-02T08:27:29Z
Status: Invalid
Importance: Medium
Launchpad Issue: lp197555
Tags: linux, waveform
Attachments: [Screen shot of visual corruption](https://bugs.launchpad.net/bugs/197555/+attachment/219382/+files/Screen shot of visual corruption), [Waveform corruption on OS X](https://bugs.launchpad.net/bugs/197555/+attachment/219702/+files/Waveform corruption on OS X)


System: Core2, Kubuntu Gutsy, Nvidia Proprietary 169 Drivers, Compiz-Fusion and Emerald (Compiz window decorator)

  1. Open Mixxx
  2. Hit Escape to open full screen mode
  3. Hit Escape to leave full screen mode

The Deck B WVisualWaveform widget becomes corrupt and 10% at the top of the screen becomes corrupted (it shows movement matching playback on Deck B)

Exit mixxx the video corruption disappears.

See attached screenshot

@mixxxbot
Copy link
Collaborator Author

Commented by: deftdawg
Date: 2008-03-02T08:27:29Z
Attachments: [Screen shot of visual corruption](https://bugs.launchpad.net/mixxx/+bug/197555/+attachment/219382/+files/Screen shot of visual corruption)

@mixxxbot
Copy link
Collaborator Author

Commented by: deftdawg
Date: 2008-03-02T08:30:32Z


This behavior is not observable on an eeePC running Xandros with an Intel i810 video chipset and no compiz.

@mixxxbot
Copy link
Collaborator Author

Commented by: asantoni
Date: 2008-03-02T16:07:23Z
Attachments: [Waveform corruption on OS X](https://bugs.launchpad.net/mixxx/+bug/197555/+attachment/219702/+files/Waveform corruption on OS X)


On OS X, when you go into fullscreen and come back you also see the WVisualWaveform widget get corrupted, as per my screenshot.

At this point, I'm in favour of putting all effort into rewriting WVisualWaveform from scratch.

@mixxxbot
Copy link
Collaborator Author

Commented by: wesley
Date: 2008-03-02T17:15:51Z


I agree with asantoni
the visual waveforms are causing a lot of weird issues that are very hard to track down and solve
I think it's better to start from scratch... we should write our ideas for this thing on a wikipage probably..
anyone wants to start?

@mixxxbot
Copy link
Collaborator Author

Commented by: deftdawg
Date: 2008-03-05T00:50:18Z


FYI, I noticed this also happens if I "window-shade" mixxx (i.e. double click on the taskbar to roll up the app window)

@mixxxbot
Copy link
Collaborator Author

Commented by: deftdawg
Date: 2008-06-23T04:27:39Z


This will be fixed in trunk when rryan's GSoC code merges sometime after 1.6.0... :D

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2008-07-18T03:02:24Z


Can you see if you can reproduce this now that the new waveform code has been merged into trunk? The bug might not be fixed by the re-write because it could have to do with how we use QGLWidget. (which is roughly the same)

@mixxxbot
Copy link
Collaborator Author

Commented by: deftdawg
Date: 2008-07-18T04:49:15Z


Reproducible with trunk by minimizing and restoring in Compiz-Fusion.
Window-shading also produces the problem (rolling up window into title-bar).

Full screen / restore does not cause it though.

@mixxxbot
Copy link
Collaborator Author

Commented by: deftdawg
Date: 2008-07-18T12:09:12Z


Occurs even if you don't load any tracks.

Does NOT occur with SIMPLE waveform (minimize, shade, fullscreen = all okay in simple waveform).

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2008-07-18T17:07:57Z


I asked in #qt and they said that many apps are reporting corruption with QGLWidgets related to Compiz. The interesting part is that it only seems to occur on waveform 2, which gets its GL context from waveform 1. We can try disabling context sharing and see if that fixes the problem.

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2009-04-16T19:00:34Z


In Bug #⁠338353 I disabled context sharing. ironstorm : do you still have the machine that had this problem? Are you able to reproduce this?

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2018-02-02T23:06:34Z


This on is incomplete for long, I close it now.

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Invalid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant