Why would those be related? How something is displayed is a front end issue. A playback engine would be part of the backend. It seems bizarre for something in the front end to affect the backend.
The more I'm hearing about it, the worse this new playback engine seems. It seems to have performance problems (along with the software itself) on many systems, glitching and playing out of time. It takes time to even be available when you open a score (if the score has a lot of instruments). And now I find out it required a regression in the UI in order to work.
So far, the only way I can actually use it is to export the file to audio. It's rather disappointing how buggy and glitchy that this release seems to be.
The current playback engine is assuming single-instance usage.
Yes, this is not front-end; but you can front-end all you want if your backend can only handle one score at a time.
The good news is that this was known and work is ongoing to allow the playback engine to support multiple front ends within the same instance.
Comments
They vanished
They got promoted to windows.
The reason behind it is to enable the current playback engine implementation.
In reply to They got promoted to windows… by jeetee
Why would those be related? How something is displayed is a front end issue. A playback engine would be part of the backend. It seems bizarre for something in the front end to affect the backend.
The more I'm hearing about it, the worse this new playback engine seems. It seems to have performance problems (along with the software itself) on many systems, glitching and playing out of time. It takes time to even be available when you open a score (if the score has a lot of instruments). And now I find out it required a regression in the UI in order to work.
So far, the only way I can actually use it is to export the file to audio. It's rather disappointing how buggy and glitchy that this release seems to be.
In reply to Why would those be related?… by turkeypedal
The current playback engine is assuming single-instance usage.
Yes, this is not front-end; but you can front-end all you want if your backend can only handle one score at a time.
The good news is that this was known and work is ongoing to allow the playback engine to support multiple front ends within the same instance.
See #338910: Tabs behaviour change - Opening two scores on the same window