After upgrading to 5.1.20, i have a section of a piece that does not recognize the transition to arco. the project works successfully on a computer using the prior version (5.1.0.2068). if i put the arco back in it does work but clearly there is some kind of issue.
We’ll need more information to be able to investigate. Please provide a minimal example that will allow us to reproduce the issue.
the best thing is for me to send the project but it is too large to attach. if you can give me a way to send it, i will send the un-upgraded project and provide the specific mm’s
Can you make a copy and only include the section that demonstrates the problem, cutting away the rest to reduce file size?
pizzicato issue.dorico (3.4 MB)
select strings only then start at mm56. when you get to the arco at 62 you will hear arco in the prior version but not in 5.1.20 where it will remain pizz.
If I delete and re-apply the arco technique, then it works correctly.
In fact, if I just move the Arco left and then right again, that corrects it.
yes, i realized that, but this is a piece that has had hundreds of hours put into it and is now complete. there are other places in the same piece where this does not happen. i should not have to review all my completed work for issues like this.
I don’t seem to be able to reproduce this. Am I right in saying that all I need to do is:
- open the score
- make a selection in b.56 covering all the string staves
- press “p” to start playback, and listen until b.62
For me b.62 plays back arco in 5.1.21.
i am using 5.1.20, the latest released vsn.
- open score
- score is converted to 5.1.20
- start playing at 56 and issue shows up at the next arco
We released 5.1.21 this afternoon (in SDA) so that’s now the new version, although I don’t think any of the changes we’ve made there will have affected this.
What version of NotePerformer are you using?
I did think of that, but switching to iconica did not fix the issue…
However, having spent a lifetime in software I have learned one constant truth “software has a mind of its own”. So, why don’t we put a hold on this until 5.1.21 is released and I will try again. When do you think that will be available?
bernie
It’s already available.
You don’t believe in proofing?
I can reproduce the problem now. I will need to look into it some more, but I think the problem will only occur in the session when you open a project that was last saved in an older version. For me, even just opening the score, re-saving it in 5.1.20 (or 5.1.21) with a new name, and then opening the newly-saved version is sufficient to start the playing techniques playing back again. I’d be interested to know whether that’s also true for you.
(5.1.21 is already out.)
1 Like
Yes,
I tried that and had the same result.
Thanks,
bernie