We're pleased to announce Sibelius 8.7.2, a maintenance release of Sibelius and Sibelius | First. This update includes more than 70 improvements, mainly around Instrument Changes and multirests. We're also announcing macOS High Sierra support and a few smaller improvements to Sibelius | Cloud Sharing.
To find out more, check out the AvidBlogs.com post, here:
For those with a current subscription license or current upgrade plan, you'll be getting a notification from Application Manager. You will also be able to download the installers from your account at https://my.avid.com/products.
We hope you enjoy the new improvements in Sibelius 8.7.2!
Installed OK on laptop using Application Manager.
However, when doing the same on the desktop computer using Application Manager the install started OK & then stopped & gave the attached error message.
So I downloaded the whole installer from the Avid website and tried again - got the same message.
What should I do next?
--
Stephen Brown
'cellist, Musical Director, intermittent composer
Sib 8.6.1/7.51; NotePerformer 2.0; Win 10 Pro 64-bit; Core i7; 20GB RAM and Surface Pro 4; Core i7; 16GB RAM
> Installed OK on laptop using Application Manager.
> However, when doing the same on the desktop computer using Application Manager the install started OK & then stopped & gave the attached error message.
>
> So I downloaded the whole installer from the Avid website and tried again - got the same message.
>
> What should I do next?
I finally grabbed it directly from my Avid Account. Came down the line reasonably quickly, but the installation routine sat at Validating install for TEN MINUTES! And, no, there weren't a load of Windows updates going on behind it. Go figure? Anyway, sorted now. And the 'big computer' updated via Application Manager pretty slickly.
I note that 8.7.2 "includes over 70 improvements". The link above doesn't seem to list them all. If I upgrade:
Will I be able to select & alt-klik Double barline & rehearsal mark to a new location w'out the two objects pasting a measure apart? (works in 7.1.3 but not in 8.6).
Will I get my solid blue mouse pointer back to indicate that it is loaded for note input? (works in 7.1.3 but not in 8.6).
Will I be able to pin my Inspector panel w'out it slowing down editing to a unacceptable crawl?
1. No. If you have a multiple selection that includes a special barline and alt-click on a barline in 8.7.2, most barlines, including the double barline, will paste at the end of the bar, which is the behavior we have seen post-7.5.
The Add Rehearsal Mark Plus Double Barline plugin is still the best workaround I know of, though you could just copy the barline by itself and type ctrl-R. I know you have been having speed issues with plugins when the Inspector is pinned, but if the plugin is assigned to a shortcut and it runs normally, it should be faster and simpler than your paste.
2. I get a blue cursor in 8.7.2 if I type n to enter note input more of if I select a note or rest, then enter a note by typing. To me the same thing happens in 7.1.3. How are you getting the cursor in 7.1.3 that does not work in 8?
3. Most people are not getting slowed to a crawl when the Inspector is pinned, though some certainly are. It is probably worth upgrading to see if that still happens to you. As far as I know no explicit fix for that problem was reported, but sometimes just a rebuild fixes weird things.
> Will I be able to select & alt-klik Double barline & rehearsal mark to a new location w'out the two objects pasting a measure apart?
See Bob Zawalich's reply.
> Will I get my solid blue mouse pointer back to indicate that it is loaded for note input? (works in 7.1.3 but not in 8.6).
This was fixed back in July, in version 8.6.1.
> Will I be able to pin my Inspector panel w'out it slowing down editing to a unacceptable crawl?
I guess that one reason that no fix has been announced for this is the lack of any recipe for reproducing the problem, so that it can be diagnosed by the developers. It just does not happen as you describe it on any machine that I have tried, and apparently it does not happen on the vast majority of other users' machines either. There might be something about the configuration of your particular Windows system that is causing this. If you can find a recipe that reproduces your problem on other users' machines, then a solution would be much closer.
By the way, what do you mean by "pin my Inspector", given that there is no "pin" operation for the Inspector in Sibelius 8.x?
--
Sibelius 8.7/7.5.1/7.1.3/6.2/5.2.5, PhotoScore Ult 8.8.2, Dolet 6.6 for Sibelius, Windows 10 64-bit 16GB. Desktop, and Microsoft Surface Book.
Thanx, Bob & Robin for your replies. Robin, I realize there is no actual pin facility now for the Inspector. I meant that I have this awful sluggishness in 8.6 if I keep the Inspector open. I'm still having to do all my editing in 7.1.3. I have no confidence that 8.7 will be any better to work on.
First of all, congratulations on speeding up the reassignment of instruments in the mixer desk: prior to 8.7.2 I could not load all the Orchestral Tools libraries and play and edit an entire score without having to wait one minute between edits. Now you've reduced that to two seconds. It's a revelation!
There's still a bug to report though.
I've defined commands in the playback dictionary that shift the track ahead by a number of ticks to compensate for playback latency. Such as "ah00" (ahead by 0 ticks) and "ah25" (ahead by 25 ticks).
The problem is that shifting the time using the playback dictionary does not shift articulations and expressions: only the notes.
The image I've attached illustrates this: the first tenuto note will play staccato, and subsequent notes will play tenuto, because the keyswitch occurred after the start of the first note. This was present in previous versions too, it's not new to 8.7.2.
Glad you're seeing an improvement to the latency. Can you email me the score along with details of the playback configuration (which plugins you're using etc.) and we'll see what we can do.
I sent that file along to you, hope you got it. It happens on NotePerformer too, and could be demonstrated in just one musical phrase.
Actually, I'm not seeing a huge improvement in the latency now I look closer: I was just using a different file which had less problems.
It seems that it's still deciding to reallocate all the mixer instruments when just one articulation on one track changes and then you click on a note to get out of the edit. Can't it just do the track that was changed? This would be the mother of all improvements!).
So, when it reassigns, the latency seems connected to (a) the number of playback devices, and (b) the number of individual sound IDs (i.e. when there are lots of single note articulations, it takes a lot longer).
It's like for every articulation change or edit it decides to cycle through each sound ID in every track for each playback device. Since the latency is much worse when you have strings of single note articulations, I have to assume that it's not doing a sort of unique sound IDs in a track: just brute force ploughing through the tracks (which means two sound ID changes for every single-note articulation, even if two notes have the same making).
There has to be a more efficient way of doing this: even just restricting the calculation to the affected tracks or even just having an option to turn this behaviour off ("fast edit mode") so that the recalculation is done only on playback? Please please please?
Also, would it be possible for it not to send a sound ID reset if it detected the next note was the same Sound ID? At the moment I have mixed articulations and when replicated across the orchestra it just overloads everything and the sound cracks up, simply because it's sending too many sound ID resets.
I know that I can stop that happening by replacing the individual articulations with expression text, but that gets very messy very quickly. Alternately, how about expression text that turns off the reset between notes?
Or the ability to specify a base articulation for a section that is returned to after a different articulation? At the moment if you've specified "staccatissimo", then the moment a staccato hits, the next note isn't staccatissimo, it's [reset]. i.e. making expression text more "sticky".
Could anyone explain why I cannot hear audio from a Sibelius score I created in 8.7.1 after
upgrading to 8.7.2
I read something about sound not being heard after this update on Mac OS Sierra would
this mean I need to move to Mac OS High Sierra how would it affect me if working along
with ProTools HD 12.8.2
> Could anyone explain why I cannot hear audio from a Sibelius score I created in 8.7.1 after upgrading to 8.7.2
Please start a new thread of your own for this request for help, and provide more and better details.
> I read something about sound not being heard after this update on Mac OS Sierra would
> this mean I need to move to Mac OS High Sierra
You do not need to perform any system upgrade in order to use 8.7.2; and there is no difficulty with 8.7.2 if you do a system upgrade. 8.7.2 is the first version of Sibelius to be officially supported by Avid on macOS High Sierra.
There is a difficulty with any version of Sibelius installed on any version of operating system if the file system (whether APFS or not) is case-distinguishing. That will not happen to you by accident: you would have to try very hard to make it so.
--
Sibelius 8.7/7.5.1/7.1.3/6.2/5.2.5, PhotoScore Ult 8.8.2, Dolet 6.6 for Sibelius, Windows 10 64-bit 16GB. Desktop, and Microsoft Surface Book.
At least, I did find a workaround for the latency while editing thing: you turn off "play note while editing" in the options (which is pretty much the "fast edit mode" I referred to).
I tried to updated but on my avid master account I didn't find where to download it. can you help me please? when I hit the link I get the image I attached here. I still have a subscription till 29.12.17 but it doesn't seem to work for me.