I have installed the latest update and have not had any more problems, loading the instrument is fast and effective.
Only sometimes a Halion7 instance opens randomly, but it doesn’t affect the ability to work, so as far as I’m concerned it’s not a problem.
Thanks again for the support which is always great!
Hi @Italyuser , does that happen with every project with you or just particular ones? If only particular ones, could you please provide an example project file? If not, when it happens the next time, please do from the menu Create > Diagnostics Report and post the corresponding zip file here. Thanks
Thank you very much for your availability!
This is the starting project that I use as a template:
Scuole New.dorico (814.8 KB)
I created a new player, and Dorico created it successfully.
I saved and closed the project.
This is what happened when I reopened it. There are two instances of Halion7 and three of Halionsonic
Banquet hall.dorico (1.2 MB)
and this is the report diagnosic…
https://drive.google.com/file/d/1_ss89wg-l7hdtEgNxnhwWC5I_1IVrU7C/view?usp=share_link
Hi @Italyuser , thanks for the data, especially the project files. The second project indeed shows that it instantiated one HSSE, five HALion Sonic and one HALion 7 instances, so from the data perspective everything is okay.
However, I don’t know why so many instances are there.
Do you use custom templates in your projects?
Do you add single players or whole sections to your project(s)?
@dspreadbury , do you have any idea, of how this could happen with that many instances?
Not sure why it happened, but reapplying the Playback Template seems to cure it.
I usually reapply the Playback Template whenever I add a new instrument so long as I have an appropriate template for the VSTs used.
thanks for your attention.
I have several Dorico projects that I use as starting models depending on the uses. (these projects were created before I upgraded to Halion 7).
if I start from one of these project files without modifying or adding players everything is fine, but if I add a player (as in the second file I sent) the result is that when I save and reopen the file all those instances open.
Thank you Derek!
can you explain to me how i can do it?
Thanks for confirming. Could you then please just do that, start with one of your starting projects and add a player, then save and reopen. Then please create a new diagnostics report and attach here. Thank you very much
I can try tomorrow night, when I go back to the workstation where those files were created…
or tonight using the laptop I have with me (using the same starting project that I attached to the previous post), if there are the same anomalies
Take your time, there is no need to rush.
Great, thank you!!!
Hello, I did as you advised.
I opened one of my starter projects and added an instrument player (piano).
When I added the player a new instance of HS7 was opened, I saved and closed the project.
When I reopened it I got these instances:
4HS7
1 HS7 (present in the starting file)
2Halion7
I attach the initial project file:
Default.dorico (717.4 KB)
The saved project file:
TakeTrial.dorico (843.9 KB)
The diagnostic report file:
https://drive.google.com/file/d/1q4Ye3UJkwk6jRTstK2ha0IZJFQTFiJxF/view?usp=share_link
Thank you so much for your support and kindness!
I tried your solution, and it effectively rearranges the player sound assignment correctly.
Whatever choice I make regarding the reproduction model, Dorico always opens Halion7 anyway.
I also tried selecting the “Silence” model first and then HSSE, but Dorico opens a Halion7 instrument instead of HalionSonic7.
Not that it’s a problem, anyway thank you very much for your solution, it will be very useful to me in other contexts!
Hi @Italyuser , thanks for the data. I will have a look tomorrow and come back here.
Hi @Italyuser , so I had a look and indeed, I could also reproduce the behaviour that so many HALion instances got created. So I tracked this internally in our bug database.
When you do the workaround as proposed by Derrek, then always HALion 7 gets loaded, because your Dorico Preferences are set up that way. If you go in Dorico to Edit > Preferences and there to the Play tab, have a look at the 2nd and 3rd option. You are set up to use your “preferred” HALion plug-in and that is currently in your case HALion and not HALion Sonic. That’s why Dorico will always instanciate HALion 7 for anything new. You can leave the settings as it is, but you may also change it to HALion Sonic. Just as you like.
Thank you very much Ulf!!!
I’ll try It this night, thank you!
and thanks for listening to my problems
I’ve been looking at the files in this thread in connection with the entry Ulf has raised in our bug database. Neither our lead tester Richard nor I can reproduce the behaviour that you’re reporting, and looking at the project “TakeTrial” that exhibits the problem shows that there is a disconnect between the plug-ins the audio engine thinks it needs to load and the ones that Dorico itself requests. When this kind of problem occurs, the best course of action is to re-apply the default playback template, then re-save the project.
If you use these projects as templates, then I recommend you start a new project based on the template, then re-apply the default playback template, then re-save your project template. That should hopefully solve the problem for new projects you create in the future.
For any other existing project which behaves strangely, simply re-apply the default playback template, and you should find everything is OK thereafter.
It worked perfectly, I selected HSonic and it works great!
I did as you suggested and it works perfectly here too!
Thanks to all of you for the help, you are just amazing! 
