HELP! Why isn’t Synth1 Librarian sending patches to Synth1?

Someone reported a problem that I’ve never encountered before: they can’t get Synth1 to receive patches from Synth1 Librarian.

Synth1 Librarian sends patches to Synth1 via a temporary patch folder, which is located at %APPDATA%\Synth1.Librarian.64|32.net\TempPatches (the 64/32 depends on the bitness of the Librarian).  So the requirements to send patches are:

  1. Synth1 Librarian needs to point to the correct Synth1 DLL
  2. Synth1 Librarian needs to know Synth1’s INI file location
  3. Synth1 needs to point SoundBank00 to the temporary patch folder
  4. Synth1 needs “Select program from host” enabled

Synth1 Librarian should automate steps (2) to (4), but in some cases file permissions might prevent it from doing so.  To get around that issue, try running your DAW/host as Administrator.

When everything is configured correctly, the options in Synth1 Librarian and Synth1 should look like this (note the highlighted areas).  Whenever you select a Patch in the Librarian, you should see Synth1’s UI update:

Synth1 Librarian running inside SAVIHost on Windows 64bit Home Edition, with all the latest OS updates.

If you continue having problems, please report them using the comments, and I’ll do my best to fix them for a future release.

neutrino.sky

8 comments to “HELP! Why isn’t Synth1 Librarian sending patches to Synth1?”

You can leave a reply or Trackback this post.
  1. Pedro Otero - April 13, 2018 Reply

    Hello,
    This sounds like a Super tool…
    I am getting this error “4/13/2018 10:31 AM – Access to the path ‘C:\Users\Pedro\AppData\Roaming\Daichi\Synth1\Synth1.ini’ is denied.”

    How do I make that not denied. I am running with admin privileges and the folder where Synth1 is has admin options on.

    • neutrino.sky - April 15, 2018 Reply

      First we need to establish if Synth1 Librarian is the problem, or if there’s a bigger issue. Try this:

      1) Load up Synth1 VST in your DAW (not via the Librarian)
      2) Click opt, and change the ExtBank folder to a temporary location (e.g. C:\)
      3) Click OK
      4) Close down your DAW completely, so that Synth1 VST is unloaded from memory
      5) Now restart your DAW, and reload Synth1 VST
      6) Click opt, and check the the ExtBank folder

      If the value isn’t C:\, you’ve got some kind of Windows issue. Does your Windows user name contain accented characters? If so, that could cause problems.

      Also, check the file properties for Synth1.ini, and ensure that read-only isn’t checked!

  2. Pedro Otero - April 19, 2018 Reply

    What if it says “one or more errors ocurred”? Is there an error log??

    • neutrino.sky - April 19, 2018 Reply

      The message area is the only log in this version (the upcoming release has better logging capabilities). Does this error happen at startup, or later on? Reply with your messages, then I can see the timeline of activities.

  3. Pedro Otero - April 19, 2018 Reply

    4/19/2018 12:13 PM – Loaded.
    4/19/2018 12:13 PM – Found 0 patches.
    4/19/2018 12:13 PM – Building library…
    4/19/2018 12:13 PM – Unzipping patch archives…
    4/19/2018 12:13 PM – Importing banks…
    4/19/2018 12:13 PM – One or more errors occurred.

    Apparently after importing banks. What subdirectory is that??

    • neutrino.sky - April 19, 2018 Reply

      So the problem is in the import process. The Librarian creates a temp folder (under %TMP%).

      Here’s an idea: reduce your zipbank contents down to, say, 5 zips (ie move the other zips elsewhere temporarily). Check the contents of those zip files – they should have numbered files like 001.sy1 etc). Try running the import against this small set, and see if it works. If it does, try adding more zips until you find the offending one.

  4. Pedro Otero - April 19, 2018 Reply

    Yes, it worked. A big hint is to look at the size of the zip file. Some of them come with PDF files or mp3 files…
    Got it to work

    • neutrino.sky - April 19, 2018 Reply

      Glad you got it working 🙂
      The upcoming release has a more robust import process, so hopefully this won’t continue to be a problem.

Leave a Reply

Your email address will not be published.