Vienna Symphonic Library Forum
Forum Statistics

202,736 users have contributed to 43,304 threads and 259,489 posts.

In the past 24 hours, we have 5 new thread(s), 12 new post(s) and 53 new user(s).

  • Copy Dorico Template to another Computer

    Hi, I have a computer and a laptop. Is there an easy way to copy the templates between computers?

    Also, when I open the Dorico Demo Project files, I get an error message, because my templates doesn't have the exact name, as the ones in the project. Wouldn't it be good to have standard template files and custom template files, to reduce these problems?


  • Hello HeiPet!

    This easiest way is probably to save the same template on both computers with Dorico Wizard.

    I'm not sure if I understand your other problem. You can always apply a Dorico playback template and then save your project. The next time you open your project, you shouldn't get an error message about a missing template.

    Best regards,
    Andi


    Vienna Symphonic Library
  • Hi Andi,

    I try to describe my concern again. My problem is not about my own system, but about exchanging projects with others or with other computers in my setup. I have created several VSL Templates using the Vienna assistant. There is also a playback template for Studio Special Editions 1-4. But when I open one of the files from "VSL_For_Dorico_Demo_Project_Files_v1.2", I get the following error message:

    I would be easier if there would be a mechanism for standard template names in the Dorico Wizard.


  • last edited
    last edited

    On Windows you could probably manually copy the .json files for your VSL templates from one computer to the other.

    These can be found in:

    %appdata%\VSL\Vienna Assistant\Dorico Presets

    ex. C:\Users\myusername\AppData\Roaming\VSL\Vienna Assistant\Dorico Presets

    I have not tried it but I expect copying the json files from that folder to another system where you want to have the same Vienna Assistant Dorico Wizard settings will give you the same Vienna Assistant Dorico Wizard Templates. You would still probably have to generate the template in the assistant by hitting the button, because just copying over the json will not likely cause the Vienna Assistant to generate the actual Dorico template, but all of the settings should be there and correct so it should just be a matter of hitting the button in the interface.


  • Hello HeiPet!

    You can ignore the error message that you get when loading the demo project. This project has been made with an old playback template. You don't need this template for loading the project though. All instruments and expression maps get loaded as saved in the project. The template is not needed for that.

    "Standard template names" wouldn't make any sense in my eyes, because the configurations of the users are all highly individual. That's why we have invented the Dorico Wizard. It helps you to make individual templates for the libraries that you have registered.

    Best regards,
    Andi


    Vienna Symphonic Library
  • As Andi mentions the project loads correctly when you get this message and plays back correctly but when you afterwards save the project and open it again, I am nearly 100% sure the message pops up again the next time you open the project. Maybe that could be avoided by some clever status check when saving without valid playback template.


  • Hello Mavros!

    It's not in our hands what Dorico displays or does if a playback template is not there. You can always apply one of your playback templates. Then the error message will not come up anymore.

    Best regards,
    Andi


    Vienna Symphonic Library
  • Hi Andi, of course this is a Dorico issue. The Doirco playback templates the VSL wizard produces work very well.

    It becomes more complicated when using VEP Pro instead of directly loaded SY players. You can save an end point with several carefully prepared VEP instances for the full orchestra, save it and link it to a new playback template however when you then "apply and close" Dorico seldom produces the same setup as you started with. Dorico apparently is not able to.save and retrieve 16 channel VEP instances correctly and in most cases creates multiple versions of the same instance in the rack for the players.

    This is of course also a Dorico issue but maybe of interest to discuss between VSL and Steinberg.

    The best way to avoid this is to start with a project template with all instruments allocated to the VEP instances instead.


  • @Mavros said:
    It becomes more complicated when using VEP Pro instead of directly loaded SY players. You can save an end point with several carefully prepared VEP instances for the full orchestra, save it and link it to a new playback template however when you then "apply and close" Dorico seldom produces the same setup as you started with. Dorico apparently is not able to.save and retrieve 16 channel VEP instances correctly and in most cases creates multiple versions of the same instance in the rack for the players.

    This is a known issue in Dorico and one that has been discussed at some length in the Dorico forum. The problem is most visible when using independent voice playback within a given staff. There is a workaround (it's complicated and requires editing xml files, but does work). You can see a long thread discussing this here:

    https://forums.steinberg.net/t/dorico-independent-voice-playback-improvement/830676

    That thread points to another thread which identified the problem for me so that I could design a workaround. The second thread also indicated that Steinberg is aware of the issue and has assigned a bug tracking ID. See the thread here:

    https://forums.steinberg.net/t/dorico-not-saving-irv-channels-in-endpointconfig-xml/766494

    By the way, it is also possible to solve this problem by using Project templates rather than Playback templates. There are tradeoffs doing this but it may be simpler to deal with. Project templates don't require editing xml files. But you also cannot reassign a project template if something goes wrong in the middle of editing a file. So you need to be cognizant of that and save often so that you don't have to recreate edits in a long editing session. Credit to Paolo_T for pointing this out. I don't have a link handy for this reference.