Hi! Just purchased Dorico 4 and so far I’m enjoying it…but…
When I hit ‘Play’ from the Transport it stalls for 1-2 seconds before actually playing back. This is on a very simple 5 bar, solo piano project. Actually, regardless of the situation, playback consistently lags by 1-2 seconds after hitting the ‘Play’ button. Not using any special plug-ins, just stock Dorico piano sound.
Welcome to the forum, ryanl !
Such a lag is not “normal” with Dorico, especially if you’re not using NotePerformer (which takes a 1s delay before play to calculate its phrasing). You should probably go to help menu, create diagnostic files and post them here so that someone from the team can help you further.
I’ve had a look through the log file and there’s nothing very unusual in there. You have a low buffer size which should help keep things responsive. However, I’ve compared the log to doing the same thing on my own machine and I get slightly different results. It looks like the play button is being pressed twice, so effectively it’s starting, stopping and then starting again. Do you have a very sensitive mouse, or are you double-clicking it? If you press space to play then is that fast?
Other than the from Paul mentioned repeated Start/Stop commands I also don’t see anything unusual in the logs, so I would investigate in line with what Romanos said. Those repeated start/stops must come from somewhere…
Hi @ryanl ,
I don’t see how a reinstallation should improve that behaviour.
However, you could do a little bit of research yourself.
E.g., the diagnostics report always contains the current Dorico log. You can extract the diagnostics report and then in the Dorico subfolder look for application.log. The log file can be opened with a text editor and with Ctrl-F you can search in there for ITransport::start. So normally, if you click the Play button that line shall only appears once. Then it is time to play around a bit. Compare what happens if you click with the mouse on the Play button or if you hit briefly the space bar. Do both actions produce the same output in the application .log?
Make longer or shorter clicks/key presses, does something change in the log?
Hi @Ulf I did some more digging around and the ITransport::start and stop appear to be behaving normally in the application.log file. In the file I uploaded you can see I let things play for longer to show a wider gap in the log file.
I’ve also looked up some videos on YouTube and it seems like playback on others’ systems also has a slight delay. I’m beginning to think this is normal, this slight delay. I’m used to MuseScore where Playback is literally instantaneous to when I hit Play.
Is playback instantaneous for everyone else here except me? I’m beginning to think I’m going mad lol. Dorico Diagnostics.zip (544.8 KB)
You are right that there’s a slight delay in Dorico that you don’t have in MuseScore. But honestly I got used to it — I even got used to the 1s delay from NotePerformer. I’m beginning to think there’s no problem on your system
Also found this thread with someone having the same issue.
@Ulf@PaulWalmsley Is this playback delay something that could potentially be minimized or completely resolved in future updates? It is somewhat of a hamper on an otherwise awesome piece of software. Thanks.
The delay can perhaps be further reduced, but it can probably not be completely eliminated. Depending on what you did immediately before you started playback, Dorico may have to recalculate some or all of the playback data for the project. There is not a one-to-one mapping between items you see in the score and MIDI data for playback – to take an obvious case, a trill or tremolo may need to generate multiple notes (and it has to determine what those notes should be, how many of them there should be, how fast they should be, etc. etc.). Similarly, to produce detailed playback using key switches, MIDI continuous controllers etc. following the settings of the current playback template is non-trivial. So unless you have not edited the score since you last played back, there will always be some amount of processing required.