Skip to content

Commit

Permalink
Merge pull request surge-synthesizer#63 from esaruoho/patch-3
Browse files Browse the repository at this point in the history
logic->Logic, "I" = @kurasu, minor fixes
  • Loading branch information
kurasu authored Dec 11, 2018
2 parents a4a2c62 + 46f0d1d commit 6ce5bb6
Showing 1 changed file with 15 additions and 14 deletions.
29 changes: 15 additions & 14 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

This is the synthesizer plug-in Surge which I previously sold as a commercial product as the company [vember audio](http://vemberaudio.se).

As I'm too busy with [other](http://bitwig.com) projects and no longer want to put the effort into maintaining it myself across multiple platforms I have decided to give it new life as an open-source project.
As I (@kurasu / Claes Johanson) am too busy with [other](http://bitwig.com) projects and no longer want to put the effort into maintaining it myself across multiple platforms I have decided to give it new life as an open-source project.

It was originally released in 2005, and was one of my first bigger projects. The code could be cleaner, and at parts better explained but its reliable and sounds great. And beware, there might still be a few comments in Swedish.

Expand Down Expand Up @@ -85,16 +85,17 @@ Execute the Surge build-script.
./build-osx.sh
```

If you got Xcode-Select issues or are missing the Command Line Utilities, grab them.
If you got `Xcode-Select` issues or are missing the `Command Line Utilities`, grab them.

After the build runs, be it successful or not, you can now launch Xcode and open the `Surge` folder. Let Xcode do it's own indexing / processing, which takes a while.

The `surge-vst3 project` will now warn you to `Validate Project Settings`, meaning, more precisely, to `Update to recommended settings`. By clicking on `Update to recommended settings`, a dialog will open and you'll be prompted to `Perform Changes`. Perform the changes.

The `surge-au project` will also prompt to `Update to recommended settings` & `Perform Changes`, so, perform the changes.

At this point you can build an audio unit which links and passes validation, and you can build a VST which links but honestly we aren't sure
if it works. Help from someone who uses VST would be appreciated here!
At this point you can build an audio unit which links and passes validation.

You can also build a VST which links but honestly we aren't sure if it works. Help from someone who uses VST would be appreciated here!

To try the audio unit you will need to install and validate it. If you don't know how to disable and revalidate audio units, be
a bit cautious here. You can slightly mess things up. To make it easy there's a script which allows you to do this from the command line
Expand All @@ -103,29 +104,29 @@ a bit cautious here. You can slightly mess things up. To make it easy there's a
./installer-local-au.sh
```

This will update the build date, run a build, and if the build works, remove the version of surge in ~/Library/... and replace
it with the latest. It will then run auvaltool to make sure that the audio unit is properly installed (and so you should
see the build date and time on stderr in the auval output). Tips on how to develop
and debug using this are in
[this issue](https://github.com/kurasu/surge/issues/58). If you see
This will update the build date, run a build, and if the build works, remove the version of surge in `~/Library/...`
and replace it with the latest. It will then run auvaltool to make sure that the audio unit is properly installed
(and so you should see the build date and time on stderr in the auval output).

Tips on how to develop and debug using this are in [this issue](https://github.com/kurasu/surge/issues/58).

If you see

```
--------------------------------------------------
AU VALIDATION SUCCEEDED.
--------------------------------------------------
```

then you have successfully built and installed the AU.
Then you have successfully built and installed the AU.

To use the AU in logic, mainstage, garageband, and so on, you need to do one more one-time step which is to invalidate your AU cache so Logic
rescans. The easiest way to do this is
To use the AU in Logic, Mainstage, GarageBand, and so on, you need to do one more one-time step which is to invalidate your AU cache so Logic rescans. The easiest way to do this is

```
mv ~/Library/Caches/AudioUnitCache ~/Desktop
```

Then restart logic. If everything works and starts up again you can delete the cache on your desktop. If it doesn't, well, then you have it.

Then restart Logic. If everything works and starts up again you can delete the cache on your desktop. If it doesn't, well, then you have it.

## Building - VST2

Expand Down

0 comments on commit 6ce5bb6

Please sign in to comment.