Version 2.0.2 & 2.0.3 installers bug for content location

After attempting to upgrade from 2.0. to 2.0.2/2.0.3 the installers won't allow customizing the content location. All folders are greyed out when attempting to do this.

I've confirmed that version 2.0 will allow customizing the content location, but this functionality is broken (not disabled) in the latest updates.

In an email from support, they are suggesting the product doesn't support this. Has anyone gotten the newest versions to work?
2 people have
this problem
+1
This topic is no longer open for comments or replies.
  • Having same problem; when trying to select a different content location during the 2.0.3/2.0.2 install, all folders are greyed out and not selectable for all internal/external drives other than the OS drive. Seems like a bug. It's standard and common practice to install large instrument content and sample libraries to a separate non-OS drive.

    I ran a CRC32 checksum on the Transfuser and Velvet .big content files and they haven't changed from 2.0 to 2.0.3, so I let the 2.0.3 installer install the content to the default path on the OS drive, ran the authorizers, launched Pro Tools, instantiated Transfuser and Velvet, entered the config menus, changed the Content Location to the directory on my sample libraries drive where I had previously installed the 2.0 content, tested out several presets, deleted the 2.0.3 .big content files from the default path on the OS drive, and finally re-launched and re-tested the instruments. Seems to be working.

    Not sure yet how to best approach the new Strike and Structure installs and not sure what if any content has changed...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated happy, confident, thankful, excited

  • Same problem. I dont want to install this on my system drive, I have a drive especially created for Kontakt libraries and whatnot. Its absurd that we should be forced to install all this content to the drive we boot with, no exceptions.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated happy, confident, thankful, excited

  • Hello everyone,

    Here's a quick tutorial that I made that you can try with Velvet 2. Please follow my directions below.

    Velvet 2 content can be moved to an external drive for OSX.

    Click Finder, then Finder Preferences. Click Sidebar at the top. Then ensure that hard disk, external disks are checked under Devices. (if in doubt, check everything on this page). If these are not checked, customer's drives will not display in the sidebar as a valid location for content.

    Navigate to Applications> AIR Music Technology> Velvet folder. Locate the Velvet Data.big file. This is what to move. Do not move the presets. These are only configuration files. The sound libraries are contained in the Velvet Data.big file.
    Move this file to the external drive location. Remember to note this exact location.

    Then open Velvet in a host DAW. Click the Wrench on the bottom left next to the keyboard. Click the Content Location box, then navigate to the folder from the sidebar that contains your Velvet Data.big file. If the customer drives are displaying, then external drives aren't checked in Finder Preferences (see above). Click Choose once the correct location is chosen. Velvet may prompt you to restart the plugin. Save, close the project, then restart the project. The content will be located on the external drive.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated happy, confident, thankful, excited

  • I was able to move the Strike content from the Applications folder to an external drive, too, BTW. I'm hoping I can do the same thing with Structure, but we'll see...

    Just moved all the Structure content as hoped... OK, so forcing us to install to the system drive is a minor pain in the butt, at least it can be moved afterwards.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated happy, confident, thankful, excited

  • The install-and-transfer solution is not a good option. This requires installing big libraries onto the system SSD, which creates a lot of unnecessary writes (wear-amd-tear) to the SSD.

    Also, because I generally keep my smallish system drive half full, I have just enough room to install, move, and delete one library at a time. Once however, the library was too large for the system drive, meaning I could not install the AIR instrument at all before deleting other content from the system drive.

    This is a must-resolve problem in my opinion.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated happy, confident, thankful, excited

  • I’m frustrated
    Cannot install and transfer because my SSD boot drive is too small. This problems has not been fixed from my point of view...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated happy, confident, thankful, excited