Note input pitch lag with big files

Dorico
,
1

First: I know that I represent kind of extreme case but nevertheless this kind of lag was not present in my “previous notation program” which was inefficient in terms of the processor usage. I am working with MacBook Pro 14-core M3Max with 36GB RAM so the computer speed or lack of RAM should also not be an issue.
This only happens with very big files:

  1. Full score, Galley view, Write mode, Caret active, Pitch before duration active
  2. Change pitches either with keyboard letters or MIDI kbd.
  3. The grey dot by the caret changes place with more than 0,5 sec lag. Audio feedback has the same lag.

I also searched this forum and found some tip to turn on “Lock Layout”. Did that: absolutely no effect on this.

The file size is around 12MB, full-scale opera, around 1 hr 40 mins ready by now. 5 flows.

This lag is present BEFORE I enter duration. When I have caret active and change pitches- they change with lag.
This behaviour affects entering longer scales with notes having the same duraton. I am using MIDI keyboard and the sequence [C-4-D-4-F-4-G-4 etc] gets me often double notes with the same pitch so I have to deliberately slow down my note entry, which shouldnt happen.

Any ideas besides: write only chamber music?

1 Like
2

What audio library are you using? Large sample libraries will have some impact.

It’s true that big files will get slower as they grow.

3

NotePerformer bare, without external sample library.
I understand the lag with larger files when I perform some operations that require calculations based on the material that has been entered (calculating layout aspects for example). But in this case there are no layout issues or generating data based on previous music. Just caret active and change pitch = significant delay. Nothing entered yet, no changes in score.

4

This might be helpful: Processing slowness

My experience is the same—entry of almost any item becomes very slow with large projects.

1 Like
5

Thanks, @jjm_335 , I checked the application.log.
I was wrong, changing pitch takes ONLY between 151-161 ms. It is not 0.5 seconds but it gets in my way often.

Lock layout 4193 ms, auto-save 6ms,

1 Like
6

Processing the command to set the input pitch in pitch before duration input should be pretty quick, and I would expect it to be quicker than you are finding it to be. Inputting the note itself when you hit the duration key could certainly take 100-200ms in a large project, but setting the pitch should feel quicker. If you want to send me your project and let me know where in the project you are working, I can profile it when I get a chance and see what’s happening.