Visualization window disappears if main window moves off initial display

[brianredbeard]

When running in a multi-head environment the Aural visualization window fails to appear if the main window has been moved to a secondary monitor. It does not matter if the window is toggled via the keyboard shortcut or via "View -> Visualizer Window".

This is occurring on Ventura 13.4

[kartik-venugopal]

Thanks for the bug report. I will look into it when I return to working on the project (away for a little while).

Cheers, Kartik

[kartik-venugopal]

Hi, I am unable to reproduce this issue on Ventura 13.3.1. Can you please list the exact sequence of steps, so I can be sure I'm not missing anything from your failure scenario ? Thanks!

[brianredbeard]

In Ventura 13.5.2 (22G91) I was able to reproduce as follows:

First, to demonstrate the normal behavior:

1. Start Aural.
2. Using the "View" menu bar at the top of the screen, activate "Visualizer Menu" ( Visualizer window appears )

Next, to demonstrate aberrant behavior:

1. Start Aural.
2. Drag the Aural to a different display
3. Using the "View" menu bar at the top of the screen, activate "Visualizer Menu" ( Visualizer window does not appear )

[brianredbeard]

In fact, when trying to reproduce this (multiple times, each of which succeeded), i generated the following crash report:

aural.dump.txt

[kartik-venugopal]

Hi, I've looked at the crash report, but was not able to gain much insight from it. Also, I've been unable to reproduce on both Ventura 13.5.x and now 13.6.

Couple of ideas:

1 - Aural log file.

• With Aural NOT running, go into your Music folder and under the "aural" subfolder (where all the app state and log are stored), delete "aural.log".
• Launch Aural and then run the error scenario with the visualizer to produce the crash (don't do anything else with the app, so that the log doesn't get bloated with unnecessary info).
• Grab the newly generated "aural.log" from the same location: ~/Music/aural/aural.log, and share it here with me.

2 - If the log file doesn't yield anything useful and if you are willing to try a little experiment, I can build a special app bundle for you augmented with some extra debugging statements put in, to generate extra log info to see at what exact point the crash occurs. Then I can share that app bundle with you, then you can repeat the above procedure and share the new log file with me. This will definitely provide good insights into where the crash occurs and possibly why.

[kartik-venugopal]

Also, can you please share details about your 2 displays: Manufacturer, model, resolution, etc. Which one is main and which one not ?

Is it a laptop connected to an external display ? Or an iMac / macMini ?

Or, at least, whether or not the 2 displays are identical in terms of resolution or not ?

[kartik-venugopal]

Hello, without any further info, I am unable to reproduce this issue, so I am closing it for now.

If you can provide more info, I'd be happy to look into it further.

Cheers!