Differences

This shows you the differences between two versions of the page.

--- assignments:a1 [2018/09/25 13:03] – bil
+++ assignments:a1 [2018/10/03 16:59] (current) – bil
@@ Line 1: / Line 1: @@
 ====== Assignment 1 ======
+{{:assignment1.pdf|Assignment 1 Description}}
 The links you will need to complete Assignment 1 are below:
@@ Line 12: / Line 14: @@
 [[https://docs.juce.com/master/tutorial_create_projucer_basic_plugin.html|Create a basic Audio/MIDI plugin, Part 1: Setting up]]
+[[https://drive.google.com/file/d/1VsXdBBPL9-2nJEMXZr5B_2z6d1CNwHk4/view?usp=sharing|Audio Plugin Host Executable (Windows)]]
 [[https://docs.juce.com/master/tutorial_plugin_examples.html#tutorial_plugin_examples_arpeggiator|The Arpeggiator Plugin]]
@@ Line 17: / Line 21: @@
 [[https://docs.juce.com/master/classes.html|JUCE API]]
+{{:assignments:startersource.zip|Starter Source}}
 ==== Providing MIDI input to your plugin ====
 You should use the Audio Plugin Host to test your MIDI plugin while developing your assignment solution (see instructions above on setting up the Audio Plugin Host).
+The Audio Plugin Host comes with a keyboard that can be used to provide input events (your computer keyboard can be used to provide simultaneous events for arpeggiation).
-In order to provide MIDI input **on Windows** do the following:
+If you'd like to provide input externally **on Windows** follow these [[instructions]].
-Download and install:
-  - http://vmpk.sourceforge.net/#Download
-  - https://www.tobias-erichsen.de/software/loopmidi.html
-On loopMIDI:
-  - Check the + in the Setup tab to create a new port
-On vmpk:
-  - Edit -> MIDI Connections
-  - Uncheck “Enable MIDI input”
-  - Under Output midi connection select “loopMidi port”
-On AudioPluginHost:
-  - Options -> Change Audio Device settings
+==== Debugging your plugin ====
-  - Check “loopMidi Port” in Active midi inputs
+Configure your debugger to run the Audio Plugin Host. In Visual Studio, it’s under Project Properties > Debugging > Command. Make sure Attach is set to “No”.
+When you start debugging in Visual Studio, it will open an instance of the plugin host. Use it to load your plugin. Now debugging works for your plugin just as it does normally, i.e. you can set breakpoints etc.