Everything you need to know about our product install, setup steps, configuration and usage of various features
MAKE THE CONNECTION, AGAIN
Set your JP Device ID
First, set the Device ID  from the Editor interface. Device ID value can be modified from the main edit view.
Device ID should be set to 17, but if you have multiple JPs, it is a good practice to have them all on different ID. This will protect the other units from accidental data overwrite and value changes.
Set your JP Model
Select appropriate JP model  so that the communication works as expected. If you have wrong model selected, you will get unexpected time-outs and data is not transmitted to the hardware as expected.
- JP-8000 users should select JP-8000.
- JP-8080 users should select JP-8080.
Data packages are different between models as JP-8080 has additional parameters which are transmitted, requested and written by the hardware vs JP-8000.
Parameter differences between models
Select your JP Model  from the “top bar” of the user interface to access parameters which are available for your hardware model. Some parameters are grayed out based on the selection made. I.e., Voice Modulator parameters are available for JP-8080 users only. In example below, you can see Voice Modulator appearing  when JP-8080 is selected as active model. Also, Oscillator 2 has extra modes (inputs and noise), Multi-FX (chorus) has additional options for Distortion FX etc. More about model change further below.
SET MIDI PORTS
Select ports with Standalone Application
If you use the Standalone Application, click “Roland JP-80×0 Editor ” from top bar and choose Preferences . This will open Preferences dialog  where you can set MIDI Input Device and MIDI Output Device.
On Windows machines, the same dialog can be opened from File menu.
Remote Keyboard Input port
If you have an external MIDI controller you want to use with the Editor to trigger notes and tweak knobs with, you can select MIDI IN from the Editor top bar. This port won’t work with the synth itself and is only used for triggering MIDI events.
This port is only visible with Standalone Application.
NOTE: Audio Device Settings in the preferences dialog does not have capability to transmit audio in this stage. Choose Audio Drivers, but keep in mind that audio has to go through Audio Jacks to console or sound card inputs.
Select ports with Plug-in
Select MIDI IN , where your Virus MIDI Out is connected in at.
Select MIDI OUT  port which will send data to your Virus MIDI Input.
HARDWARE CHECK / PING
After setting MIDI OUT, our Editor will start scanning for the hardware. If there is no immediate response, the Editor will attempt 3 more times. If there is no response, you might get a “Connection Timed Out” message. If so, double check your hardware settings and make sure your cables are good!
NOTE: MIDI ports for plug-in are set from the main window while Standalone Application MIDI ports are set from the Editor Preferences.
Editor Control Display will say “Editor is ready to go!” when response is received from the JP.
You can optionally enable Device ID probing function, which will check for the Device ID for you. This is good IF you have only one Virus model in your setup. Function can be enabled from Utilities  menu -> Editor Preferences  -> Enable DeviceID Scanning .
NOTE: If you have Device ID set to 17 on the JP and 17 on the Editor, our Editor will find your JP if everything else is configured properly.
SYNCHRONIZE DATA FROM HARDWARE TO THE EDITOR
This is the final step before you can start making your own adjustments IF “Enable Hardware Auto-connect” is disabled from Utilities menu as explained in previous section! Click Sync Data From HW  button to synchronize active PERFORMANCE data from your JP to the Editor user interface. This needs to be done only when new instance is loaded so that the Editor and you know what was set in the hardware already.
After the “Sync data from HW” process is completed, you should check the GENERAL SETTINGS  view. Verify layer MIDI channels are what you expect them to be.
You can now pursue with your own editing tasks, patch manipulations and experiments as you wish!
NOTE #1: Be patient and do not disturb the data flow with any knob movements or so. This will ensure the data packages are being sent and received as expected and you are not going to receive any SysEx error messages!
NOTE #2: All layers should ideally have individual MIDI channels to avoid control change conflicts. You can stack sounds together by setting the MIDI channel to same value, just keep in mind that control changes affect both layers!
STORE DEFAULTS IN FILE
You have the option to store your Editor defaults from the Utilities menu if you don’t have more than one JP in your setup. This is good when you insert a new instance of our Editor in a new project – Everything is setup the way you wanted.
Click Utilities  menu, select Editor Preferences  and click Save all settings as Defaults . After doing so, every time the Editor is loaded, your preferred settings are already applied. You can remove the defaults option by revisiting the same menu and select “Clear Editor Defaults”.
If you ever encounter any issues with defaults loading wrong data or the Editor crashes while loading defaults, you can disable this function from “data location”/Roland JP-80×0 Editor PREFS.txt by changing line loadcustomdata:true to loadcustomdata:false – save and exit and load your session again!
ADVANCED MIDI SETTINGS
You can control which messages gets processed and which do not. Open Advanced MIDI Settings window by clicking ADVANCED MIDI SETTINGS button in the Editor user interface.
You can block messages being processed from DAW or from the Synthesizer itself. Settings seen in the image below are default values.
Advanced Incoming MIDI settings
Allow certain MIDI messages to pass into the Editor processor within Incoming MIDI setting section. Green check mark means it will be processed and when there is no check mark, it will be bypassed. Process DAW messages  and Process Hardware messages  has their own set of data “filters” [3-9] available as follows:
-  Control Changes
-  Program Changes
-  Note Messages
-  Pitch Bend
-  Poly Aftertouch
-  Channel Aftertouch
-  System Exclusive
-  Part LEDs tracks incoming MIDI and SysEx messages
When green check mark is on, incoming data from DAW and Hardware ports is monitored and LED indicator will flash when data is coming in. When check mark is off, outgoing data is being monitored.
Check LEDs Off function to disable.
Note #1: If you disable Control Changes and System Exclusive messages from Hardware port, the Editor might stop responding to hardware knob movements completely.
Note #2: In Standalone Application use, Remote Keyboard MIDI Input data is handled in Process DAW messages section.
Advanced Outgoing MIDI settings
In Outgoing MIDI settings section, you can adjust few options to fine tune the Editor behavior.
Send note MIDI data from Plug-in:
- Directly to Hardware  = Send all MIDI related command directly to hardware from the MIDI output port.
- With attempt to match DAW buffer setting  = experimental attempt to sync with DAW time.
NOTE: If the Editor MIDI note handling is out of time, we would advise NOT to adjust these settings at all. Check your DAW user guide to figure out how to delay or advance your MIDI note timing / delay compensation.
MIDI Clock (experimental)
We are experimenting to add general MIDI clock to the Editor by standard feature. This might crash on some systems on a specific setup, so be cautious when experimenting with it.
Check Send Sequencer Start / Stop Commands  if you want to send MTC start and stop commands.
Check Send Continuous MIDI Clock information  if you want to sync MIDI clocked Effects and Arpeggiator to the Editor tempo information.
NOTE: The clock with the Editor might be inaccurate, so if you have another solution to sync clock information from your DAW to the hardware, use that instead.
User Manual contents
Introduction to our Editor, what it can and can not do
Checking wiring diagrams, Hardware and MIDI settings + registration guide
Successfully establish the connection to your Hardware
Hardware functions and our custom functions explained in great detail
Basic layout and guide how to use the Patch Librarian
Deeper analysis of the Patch Librarian Menu functions
Why there is no sound? Why no connection? Time to troubleshoot!