You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Self explanatory: The track edit window has no content.
Screenshot one: A multitrack project with several ust files. The Track editing window is not the active window in this screenshot.
Screenshot two: A brand new project, as a control variable to show that this error also occurs with new blank projects and new blank tracks when opening the track editing window. The Track editing window IS the active window in this screenshot, the colour of this active window is greyed out.
Explains how to reproduce the bug
Open OpenUtau on OSX15 on ARM64 architecture.
Create a new project or open an existing project.
Open the Track editing window / view.
OS & Version
macOS Sequoia / OSX15 | ARM64
Logs
As this is a display error, there was no log error generated or associated with the issue.
The text was updated successfully, but these errors were encountered:
This is a persistent and unfortunate known bug. It can be bypassed by resizing the window a little bit, but we're aware that's not exactly friction-less. Would you mind if I mention this issue and use crops of your screenshots on our Known Bugs page, for easy developer reference?
Acknowledgement
🐛 Describe the bug
Self explanatory: The track edit window has no content.
Screenshot one: A multitrack project with several ust files. The Track editing window is not the active window in this screenshot.
Screenshot two: A brand new project, as a control variable to show that this error also occurs with new blank projects and new blank tracks when opening the track editing window. The Track editing window IS the active window in this screenshot, the colour of this active window is greyed out.
Explains how to reproduce the bug
OS & Version
macOS Sequoia / OSX15 | ARM64
Logs
As this is a display error, there was no log error generated or associated with the issue.
The text was updated successfully, but these errors were encountered: