Migrating virtual Instruments, FX and so on.,.

Author
Post
Essentials Only Full Version
trashman1965a
Max Output Level: -90 dBFS
  • Total Posts : 3
  • Joined: 2016/04/17 15:59:16
  • Status: offline
2017/11/27 09:58:19 (permalink)

Migrating virtual Instruments, FX and so on.,.

Hey Folks,
 
Rather than have another discussion on when/if/where to migrate, I would just like an answer to the question of migrating content/plug ins/instruments etc. to another DAW.
 
Is it as simple as copying the folder with the DLL's? Is there a concise list of what bundled content with Sonar Pro 2018 can be used elsewhere?
 
I bought Sonar Professional on Steam and really I want to clean up the install (it seems stuff is all over the place) and move it to a common folder, using any included content that was bundled where possible in another DAW. Then uninstall Sonar when I am ready to move.
 
Can this be done with Steam installs? I can download nothing directly from Cakewalk - I get the things like Addictive drums where the serial/activation is not through Cakewalk is easy enough and have tried pointing another DAW at the VST folders I could find and seems a lot are there, but if I uninstall via Steam, presumably these folders will also go?
 
I have no need to migrate projects - just bundled content.
#1

3 Replies Related Threads
    JClosed
    Max Output Level: -77 dBFS
    • Total Posts : 690
    • Joined: 2009/12/19 11:50:26
    • Status: offline
    Re: Migrating virtual Instruments, FX and so on.,. 2017/11/27 11:16:52 (permalink)
    Well - Keep in mind that not all virtual instruments and FX plugins will work outside Sonar. As an example - The standard BreverB that is bundled with Sonar, will not work in any other DAW. The same goes for instruments like Truepiano and DXi instruments/effects.
     
    However - there is a lot of stuff that will work very well in other DAW's. I do not advise to move the dll files to another location. Sometimes they are linked to entries in the registry in Windows (or have links to tables in the same directory), and stop working reliably when moved. If you really want to move those plugins to another location it is better to de-install them and then re-install them in the preferred location.
     
    In general it is best just to add the location/directory of the plugins in the application you are using. In Cubase it is just as simple as adding that location in the VST setup screen. The only application that can be a bit tricky is Ableton Live, because it only adds one location for all plugins. A simple solution is to make a link from the Cakewalk VST location to the location Ableton Live is pointing to.
     
    I cannot offer any help with Steam installs, because I simply have no idea where everything is located using that platform, sorry.
    #2
    trashman1965a
    Max Output Level: -90 dBFS
    • Total Posts : 3
    • Joined: 2016/04/17 15:59:16
    • Status: offline
    Re: Migrating virtual Instruments, FX and so on.,. 2017/11/27 16:40:45 (permalink)
    Thanks, but this is specifcally about Steam which is a different scenario.
     
    Starting to form the conclusion that there is no easy way to use the bundled content without having Steam and Sonar installed, which is not what I wanted to achieve.
     
    Any other thoughts?
    #3
    Cactus Music
    Max Output Level: 0 dBFS
    • Total Posts : 8424
    • Joined: 2004/02/09 21:34:04
    • Status: offline
    Re: Migrating virtual Instruments, FX and so on.,. 2017/11/27 17:05:19 (permalink)
    Normally most plug ins go to either Cakewalks VST folder or a lot of 3rd party go to Steinbergs VST folder. SOme ,like AIr instruments seem to get lost and I always have to go dig for them. 
    I can't see that Steam would install Sonar any different then using CCC. If it does then you might need to contact them and find out what will happen now that Sonar no longer is sold. 

    Johnny V  
    Cakelab  
    Focusrite 6i61st - Tascam us1641. 
    3 Desktops and 3 Laptops W7 and W10
     http://www.cactusmusic.ca/
     
     
    #4
    Jump to:
    © 2024 APG vNext Commercial Version 5.1