SFC-OB MIDI Controller
“
Specifications:
- Product: SFC-OB USB-MIDI Controller
- Compatibility: Class-compliant with USB-MIDI support
- Plug and Play: No drivers required
Product Usage Instructions:
1. Installation and Start-up:
The SFC-OB is a class-compliant USB-MIDI device, so no drivers
are needed. Simply plug the controller into your computer’s USB
port. Ensure that your USB ports provide sufficient power for all
connected devices.
2. USB-MIDI Troubleshooting:
Refer to the specific troubleshooting instructions provided in
the manual for both MAC and Windows systems.
3. Using the Controller with Plugins:
Before starting, ensure that your software is up to date. The
SFC-OB sends CC MIDI messages to control synth parameters. Make
sure the plugin is set up to receive MIDI messages from the
controller.
Assigning MIDI CCs:
Each plugin has a unique MIDI mapping system. Consult the
plugin’s manual for instructions on assigning MIDI CCs.
4. Plugin Modes:
The controller’s layout is designed to work with various
OB-styled plugins. Plugin modes are available to ensure
compatibility with different interfaces. Refer to section 12 in the
control panel to change the plugin mode.
5. Arturia OP-Xa 2-way Communication:
The controller synchronizes with the plugin based on the MODES
switch options. Ensure proper settings for seamless communication
between the controller and the plugin.
6. DiscoDSP OB-Xd Mapping Preset:
Use the included XML mapping preset in the plugin menu for
instant mapping. Follow the instructions to set up the OB-Xd plugin
with the controller.
7. DUMP Switch:
Use the DUMP switch to align the controller’s state with the
plugin interface. This helps maintain synchronization between the
controller and the plugin.
8. SHIFT Switch:
The SHIFT switch allows access to an alternative MIDI channel
for controls. Hold down SHIFT while adjusting a control. Note that
SHIFT is not latching.
9. LEDs Brightness:
Adjust the brightness of LEDs by holding down the SHIFT button
and turning the PORTAMENTO TIME potentiometer. The preference is
saved in the controller’s memory.
Frequently Asked Questions (FAQ):
Q: Do I need to install drivers for the SFC-OB?
A: No, the SFC-OB is class-compliant and does not require any
additional drivers.
Q: How do I troubleshoot USB-MIDI connectivity issues on
Windows?
A: Refer to section 4 in the user manual for troubleshooting
steps on Windows systems.
Q: How can I change the plugin mode on the controller?
A: To change the plugin mode, refer to section 12 in the control
panel of the user manual.
“`
SFC-OB User Manual
24 April 2025
1. Intro
Thank you for purchasing the SFC-OB MIDI controller. A considerable amount of effort and passion has been put into this product to make it the best it can be. It is built to last and withstand intense usage on tour and in the studio. SoundForce has an excellent track record for its controller line, with many units built and very liLle registered issues and repairs. I hope you will have a great experience using this device and that it will inject some fun in your music. Many thanks for your support. I am interested to get your feedback and requests: nicolas@sound-force.nl
2. InstallaQon and start-up:
The SFC-OB is a class-compliant USB-MIDI device which means that no drivers are necessary. The controller should directly be recognized by your computer when plugged-in. USB devices should preferably be connected directly to the computer USB ports. Please make sure that your USB ports/hubs are providing enough power to every single device in your configuraQon.
To use the controller with your DAW and plugins you need to make sure that the controller is setup in your DAW. In some DAWs, Logic for example, it’s automaQc when you plug it in and you don’t need to do anything. In others, you might need to turn on an opQon in the preferences. Please refer to your DAW manual for details. The controller is sending by default MIDI CC messages and can be mapped to plugins using their MIDI mapping funcQons. To specify which instance of a plugin you want to control, simply route the MIDI to the right track. This is usually down by scrolling (or clicking) from one track to another and thus pu[ng a specific track in “record-arm”. In some DAW, you can specify which MIDI devices are used on a specific track, so you can filter per device and someQmes also per channel. Please refer to your DAW user manual for specific details.
3. USB-MIDI TroubleshooQng on MAC:
If the device turns on (red LEDs are on and you can change the switches posiQons) but it is not recognized by the computer, please go through this guide completely. Please also try another USB cable, USB port and if possible another computer or OS. Before ge[ng in touch for support, please confirm that the device is sending out MIDI correctly (or not) using a MIDI monitor (in google Chrome you can use the control panel app). If it does send MIDI messages as expected then the problem should be in the DAW and plugin configuraQon, make sure the controller is setup in your DAW and that the plugin is mapped.
4. USB-MIDI TroubleshooQng on Windows:
If the device turns on (red LEDs are on and you can change the switches posiQons) but it is not recognized by the computer there is most likely an configuraQon or OS related issue. Please try another USB cable, USB port and if possible another computer or OS. Before ge[ng in touch for support, please confirm that the device is sending out MIDI correctly (or not) using a MIDI monitor (in google Chrome you can use the control panel app). If it does send MIDI messages as expected then the problem should be in the DAW and plugin configuraQon, make sure the controller is setup in your DAW and that the plugin is mapped. Remember that Windows allows only 1 connec5on at the 5me between a USB-MIDI device and a so>ware. Make sure all other MIDI applicaQons are closed before you are trying to connect the controller to your DAW.
5. Using the controller with plugins
Before you get started, always make sure that you have the latest version of the so^ware you want to use with the SFC-OB.
The SFC-OB sends CC MIDI messages to take control of the synth parameters. Therefore the plugin needs the right MIDI mapping and MIDI needs to be routed to the plugin’s track. There is no magic connecQon between the controller and plugins, the MIDI needs to routed like a USB-MIDI keyboard for example.
Every plugin has a specific MIDI mapping system, so please refer to your plugin’s manual to start assigning MIDI CCs.
6. Plugin modes
The controller front panel layout was designed to fit as many OB-styled plugins as possible. As there are differences between different plugin interfaces (specifically the amount of posiQons in certain switches), plugin modes are needed to make the controller compaQble with each plugin.
The original 1.0 factory firmware supports 4 modes:12 · Arturia OP-Xa (default out of the box) · GForce OB-X · Sonic Projects OP-X PRO-II/DiscoDSP OB-Xd · Synapse Obession
To change the plugin mode, see the control panel secQon 12.
7. Arturia OP-Xa 2-way communicaQon
Thanks to Arturia’s ingenious XML controller mapping system, a greatly improved integraQon with the latest Arturia OP-Xa (VcollecQon 9 and above) plugin can be accessed thanks to a simple and easy copy file(s). The controller can receive sysex data from the plugin when presets or instances are changed in the DAW. On the controller side, the data is loaded to the interface and the controller can update the front panel. It can also request the sysex interface data on demand if needed, this is necessary when a DAW will not trigger certain events correctly. This integraQon works thanks to Arturia’s XML system that was implemented for their own line of MIDI controllers. This funcQonality won’t be available for other plugins unless developers program special funcQons to implement this. Special thanks to Marie from Arturia for taking the Qme to explain me how it works.
Set-up: First make sure that the SFC-OB is in the Arturia plugin mode (see secQon 6). To start using this integraQon, download, unzip the support file. Check which version you are using in the Arturia ASC and choose the right folder. Follow the instrucQons in the README file. There are 2 versions released in 2024 that caused problems and cannot be supported. Only the versions specified in the README files are supported. A^er copying the XML file(s), restart the plugin if it was open and then in the plugin interface click on the cogwheel, then in the MIDI tab choose the SFC-OB in the MIDI controller dropdown. This will auto-map the plugin to the SFC-OB default CC map and turn on automaQcally the 2-way integraQon.
Behaviour to expect: The controller will synchronise to the plugin in the following situaQons:
· when a new plugin instance is created · when the standalone version is opened (if the SFC-OB is checked on in the Audio MIDI Set-
Qngs) · when changing presets · when switching tracks/instances · when requesQng it using the SYNC switch on the controller The plugin will also send a single sysex message when a plugin control is moved or touched using the mouse as well. When the sysex interface data is sent to the controller, the firmware will ingest it and the LEDs will be changed to mirror the plugin status. The pot data is also ingested and they are 3 behaviors possible, see below in the MODES switch opQons.
DAW specifics: Switching instances happens differently in every DAW so please refer to your DAW’s manual and documentaQon to do this. Usually, it involves selecQng another track, making sure that the arm record funcQon goes with it and also insuring that the new plugin GUI opens. Please note that switching tracks (using the Arm Recording switch) to open a new instance in Ableton is problemaQc. The previously opened GUI is not properly closed and thus the funcQons in the plugin framework are not triggered correctly when a new instance is opened. This is not a problem related to Arturia so^ware or SoundForce controllers. The easy workaround for this is to firstly switch tracks, then to manually request the sysex data transfer from the plugin to the controller with the SYNC switch.
Remote control switches: From the controller, you can change the presets with the DOWN and UP arrow switches. You can also manually request the sysex synchronizaQon from the plugin to the controller with the SYNC switch. This is especially handy if you noQce that the sysex transfer is not triggering when switching tracks/instances, for example in Ableton as menQoned above. The DUMP switch allows you to synchronize in the other direcQon, from the controller to the plugin. The controller will dump its full interface data into one packet sent to the plugin. The MODES switch will define the behavior in case of discrepancies between a plugin pot-posiQon and a controller pot-posiQon with the goal of avoiding juming values.
MODES switch op5ons: When the received pot data from the plugin differs from the actual pot posiQons on the controller, disconQnuiQes can appear if this is not dealt with. Similar to Ableton take over modes, they are 3 opQons that can be set with the MODES switch:
· Jump: the controller will send instantly its new physical pot value and the pot in the plugin will do a jump
· Pick-up: the controller will only send new pot values a^er the controller-pot has reached the plugin-pot posiQon. The LEDs on top of the DOWN and UP arrow switches will blink to let you if you need to go down (DOWN arrow blinks) or up (UP arrow blinks)
· Scaling: the controller will rescale the values sent to the plugin elasQcally so that a move on the controller matches the range of a move on the plugin control. Only smooth transiQons are created. As soon as the control reaches one extremiQes (0 or 127), the scale is back to the normal 1:1 proporQon.
This preference is saved in the controller and loaded when the device is plugged in.
8. DiscoDSP OB-Xd mapping preset
The DiscoDSP team has included an XML mapping preset in the plugin menu to get instant mapping with just one mouse click. Press the red MENU switch -> MIDI -> SFC-OB. The OB-Xd is an amazing plugin with a free non-commercial license opQon. Most of the classic OB-style parameters are available and those will be automaQcally mapped when using the preset.
9. DUMP switch
When the plugin window and the state of the controller are different, it is someQmes preferable to “push” the state of the controller to the plugin interface. That way nothing is jumping around when you start moving the controls and it helps ge[ng the controller and plugin synced up when you get starQng. The DUMP switch is reading every control and sending a pack of CC messages to the plugin.
10.SHIFT switch
The SHIFT switch is unlocking an alternaQve MIDI channel for the pots. Simply hold down the SHIFT switch and turn your desired control. Please note that SHIFT is not latching, which means you need to hold it down.
11. LEDs brightness
Holding down the SHIFT buLon, you can change the LEDs brightness turning the PORTAMENTO TIME pot. This preference is saved in the controller and loaded when the device is plugged in.
12. Users pots and switches
Please note that there are extra USER pots and switches that you can map to whatever you want. For example, an external reverb plugin wet/dry or an FX return fader level in your DAW.
13.Control panel
The Control Panel is a Google-Chrome app that allows you to save CC maps and select the plugin mode.
As firmware v1.0, the SFC-OB has 4 modes: · Arturia OP-Xa · GForce OB-X · Sonic Projects OP-X PRO-II/DiscoDSP OB-Xd · Synapse Obession
Each mode has a different interface behavior that will fit the desQnaQon plugin or hardware as much as possible.
You can click on each control and change the CC message number. In some situaQons, certain CCs are highjacked by DAWs and hard routed to specific funcQons, so some edits are necessary.
How to use the control panel:
· First plug in your SFC-OB · Then open the control panel in Google Chrome latest version · The device should be recognized and the message “Connected to SFC-OB” will be displayed
on the le^ middle container. The firmware version will also be displayed. · Choose your desired mode in the “plugin mode” dropdown menu and click “Send plugin
mode” · If desired click on a switch/pot/ in the front panel image and change its CC number in the
le^ field. When you are done with your changes, click “Save values”
You can save a MIDI map on your computer: · click Export as text · click in the filled text field · copy and paste that list of comma-separated numbers · save that on a text file on your computer
Similarly, you can copy a saved text field from a text file and paste it in the control panel text field. Then click “Load text to panel”.
You can go back to the factory CC values with the “Reset to factory values” switch. This will cause the controller to reboot and erase the saved data.
14.Default start-up state of the controller
To change the default start-up state of the switches, you can SHIFT press the DUMP switch. A^er it is saved for the first Qme, it will be loaded by default at start-up. It’s loaded but not sent out at start-up, if you’d like to send it out as a packet use the DUMP switch.
Documents / Resources
![]() |
SoundForce SFC-OB MIDI Controller [pdf] User Manual SFC-OB, SFC-OB MIDI Controller, SFC-OB, MIDI Controller, Controller |