The issue of Dorico refreshing the document back to the very beginning every time you change between write/engrave or between part and full score — this is a constant overwhelming source of frustration and time wasting. I always have to memorize where I’m at in the score because Dorico won’t remember where I’m working if I need to change or edit anything. On a recent 22 minute orchestral score, I estimate this one glitch cost me probably 3-4 hours in extra time trying to scroll back to where I was. While we’re at it, having a way to push a button and just go to the beginning of a certain flow, this would be so helpful.
4 Likes
It usually only happens when the selection can’t be made in the incoming mode. This happens a lot with Condensing, because you can’t select condensed objects in Write mode/Page View.
But if you’re working in Galley or Fill View, you should see the selection maintained.
There are commands to go the Next/Previous flow, which you can assign keys to. I can then move through a project by tapping the keys I’ve assigned, to get to the relevant bit.
In addition to @benwiggy’s answer, you can also use the jump bar in GoTo mode to jump to a flow.
I have Shift+J set up to open the bar in GoTo mode, so something like Shift+J f3 Enter will take me to the start of the third flow.
1 Like
I don’t understand what you mean here about “incoming mode”. I will edit say measure 100 in write mode, then switch to engrave mode, and Dorico refreshes back to the beginning. Just today, I was entering in cues to an orchestral part at Rehearsal H. As soon as I started doing it, the software flips back (in galley mode) to Rehearsal C. This seems to be known issues as I’ve seen Dorico developers in this forum talk about “be sure not to use certain zoom levels like fit height or 2-page view, or else you’ll trigger this problem!”
2 Likes
This would seem to be a no-brainer type of feature given that work in Dorico is designed around flows. We can only hope this can be addressed post-haste. I wouldn’t mind if flows showed up as tabs in the display but this might not set well with some others.
I would also like to see Dorico remembering where I was last editing in a flow that is specific to Write and Engrave modes. It is often annoying that this is not the case.
1 Like
I’m not sure that I understand the delay on this. If Dorico can perform a trill with options, there really should be no issue with turns, mordents, inverted mordents and the like…the delay doesn’t make sense to me.
1 Like
Very simple: development time. It’s no secret that the team is smaller than it used to be (or at least: their resources are borrowed by other departments within Steinberg, which effectually diminishes the team). They have deemed that the development time vs. opportunity cost for this feature verses others isn’t high enough to get priority yet.
It’s a very well–loved theme here on the forum that “small” feature does not mean “quick and easy to code”. So be wary of making any assumptions in that department.
5 Likes
Hm, I can select something within a flow and get to the beginning of this flow by pressing the home key (on Mac).
So, as much as I do genuinely appreciate all of the great features and the F-inspired updates since I moved to Dorico in August 2024, I am a little taken aback by this type of response to coding errors, omissions or whatever-you-want-to-call them. This is part of the reason that the application beginning with “F” became so bloated over time such that fixing one thing broke another.
So, I haven’t personally created an application since compilable Basic and Assembly Language became obsolete to OOP, but I do believe practices are the same: garbage in = garbage out ( aka even a minor error or oversight in coding can lead to all kinds of unwanted issues in future versions that are not from a fresh start).
I had not previously been concerned about Dorico’s future prospects but now I am. That attitude is not good…
To be clear, you are responding to a user’s paraphrase. I think this is the actual post:
I read that as, “We’re aware that there’s an issue; here’s one way to avoid it.” Since the dev team is aware of the issue, I’m sure it’s on their backlog to be fixed.
2 Likes
IMVHO all software is buggy and the more a program tries to achieve the more the bugs pile up. The problem is when the bugs take forever to be fixed or, as you say, just lead to others. On both those scores the team at Dorico do really well - lots of fixes are done - and often - and the fixes tend to stick without causing a whole load of new ones. You can see from the replies here that the team are well aware of the issues and will be doing all they can to solve them.
5 Likes
I’d simply like to echo what has been said here: the team is exceptionally responsive and consistently exceeds expectations.
It can be frustrating to wait for an issue to be resolved or for desired functionality to be implemented, but when a member of the team confirms that something will be addressed, you can be confident that it will be.
2 Likes
Hmm. OK. It still should point back to the same measure whether the view real estate changes or not as bar (not measure) 100 is bar 100 irrespective of the view.
1 Like
Well, actually, providing you have something selected there, it does work… As usual, it’s a workflow matter. I understand that there are limitations and it would be better that there is no context where this kind of problem appears, but let’s be realistic and cope with those little issues (that the Team knows and has been constantly solving).
2 Likes
But neither you nor I know anything about how all of this is modeled under the hood, and therefore what’s involved in fixing the issue.
2 Likes
I guess one problem may be returning to a condensed page in Write mode where object is not selectable.
2 Likes
As a feature request, I would like to be able to step through note playback for a selected measure or sections of multiple instruments. Like you can step through notes of one instrument with an arrow key. Maybe asking too much but the Dorico people are awesome!