Showing posts with label hardware synths. Show all posts
Showing posts with label hardware synths. Show all posts

Tuesday, April 8, 2025

SOLUTION: Correctly Importing SampleRobot instruments to Waldorf Quantum and Iridium

 As a long-time user of SampleRobot and a recent owner of a Waldorf Iridium Core synthesizer, I was excited to learn that SampleRobot 6 has explicit support for the Waldorf Iridium and Quantum instruments. After working with the synth for several days, however, I encountered a number of unexpected roadblocks when attempting to import my own SampleRobot recordings into my Iridium Core that the existing documentation and tutorial videos didn't cover. After a couple days of research and experimentation, I have finally figured it out, and wanted to share my findings for future users.

Recent developments

So far I have only found one video describing the process of importing SampleRobot instruments, and it's the one Waldorf published to their YouTube channel, however that video glosses over a very important fact: If you follow their steps exactly as described, it will work at first- but only if you leave your USB drive or SD card inserted in the synthesizer. If you try to load any instruments you created without the original storage device connected, the synth will complain that it can't find the samples!

If you want to permanently import your SampleRobot instrument without having to leave the USB/SD storage connected, you must import the samples into flash memory, and create the instrument from there. But that leads us to another problem: YouTuber Tim Shoebridge has the most popular video that covers the process of importing samples into a Quantum or Iridium, and it is very good, but it was recorded before the 3.0 update to the Iridium system software, which changed how sample storage works. His steps involve using an "Import" action which no longer exists in current Iridium/Quantum software. That functionality has been combined with the pre-existing "Add" action, but the workflow is different from what you'll see in Tim's video.

My steps below will show you how to correctly (and permanently) import your SampleRobot instruments into your instrument, as of the 3.2.0 version of Iridium Core OS (January 16, 2024).

Importing the samples

These steps assume you have already recorded your instrument in SampleRobot and exported the project in "Waldorf Quantum and Iridium (*.map)" format. I am a heavy SampleRobot user, and have already written some guides on working with it. If you'd like to see some more info on using it to make instruments for Quantum/Iridium, let me know.

First off, after you export your instrument to Waldorf format, make sure that you copy the resulting files to your USB drive or SD card exactly as follows: The USB drive/SD card must have a directory named "samples" at the root, and that directory must contain one or more instrument directories, each one containing the instrument's samples and MAP file. There can be other stuff on the drive/card, but all your Waldorf files must follow the above directory structure.

In this image you can see we have a USB drive named "IRIDIUM" and it contains a folder named "samples" with a subfolder named "The Giant Piano" which contains all necessary samples, plus the MAP file.

Note: Because some physical buttons on these devices have the same text as some on-screen buttons on the touch screen, I will try to use the word "press" for physical buttons and "touch" for on-screen controls.
  1. Insert your USB drive or SD card into your synthesizer.
  2. Press the physical Load button on the synth.
  3. On the Load Patch screen, touch Init to create an empty patch.
  4. Press OSC 1.
  5. Touch Wavetable and then touch Particle to select the standard sampler engine.
  6. Touch Actions, and then touch Add.
  7. In the upper-left corner of the touchscreen, toggle to the correct storage device for your samples (USB Drive or SD Card).
  8. In the left pane of the touchscreen, touch samples.
  9. In the right pane of the touchscreen, touch the directory name of the instrument you want to import (for the instrument in my screenshot above, I'd touch "The Giant Piano").
  10. Leave the directory name selected (don't select any individual files), and then touch Add.
  11. An "Add Samples" dialog will appear, asking if you want to copy the files to internal flash memory. Touch Copy.
  12. The samples will be copied into the "samples" directory on the synth's internal "Samples" storage. (For example, my "The Giant Piano" directory now appears between the factory "Tanya Samples" and "Vocal chika" directories in my internal storage.)

Loading the instrument map

The MAP file contains all the information your Waldorf synth needs in order to place each sample in the correct pitch and velocity ranges.
  1. With your USB/SD storage still connected, press the physical Load button.
  2. On the Load Patch screen, touch Init to create an empty patch.
  3. Press OSC 1.
  4. Touch Wavetable and then touch Particle to select the standard sampler engine.
  5. Touch Actions, and then touch Load Map.
  6. Use the touchscreen to navigate inside the original directory that contained your samples on your USB stick or SD card, and touch the name of the MAP file. (In my example, I'd navigate to "USB Drive > samples > The Giant Piano > The Giant Piano.map".)
  7. Touch Load.
Your samples should now be mapped the way you set them up in SampleRobot.

Testing and saving the instrument

You should now have a very basic sample-mapped instrument. Use the pads or fire up your DAW to play around with it to make sure your velocity layers are mapped properly (if you used more than one layer) and the pitches are mapped across the keyboard as you expected. You can make the necessary changes in the Timbre page of OSC 1, on a per-sample basis if only minor changes are needed. If you find massive changes are required, it might be best to go back to SampleRobot and re-record. (Again, if anyone needs tips here, let me know.)

Your freshly-imported instrument has a "gated" envelope (extremely fast attack and release) and does not adjust volume in response to velocity changes. It WILL trigger the appropriate samples if you imported multiple velocity layers, but it won't adjust their playback volume without some modifications.

To change the amp envelope to attack/release like you want, press the Envelopes button, and then make the appropriate adjustments on the Amp tab. (For example, I increased the Release to 1.54 seconds for my piano instrument.)

To make the instrument adjust volume in response to different velocities, touch Mod Targets on the Amp tab and then dial in the appropriate "Amp VeloAmt" value. In my case, 80% gave me the best velocity curve for my MIDI controller and playing style.

When your instrument is ready to save, do the following:
  1. Press the physical Save button.
  2. Enter a name for your patch and fill out the appropriate attributes. (I put all my patches into an "ultimateoutsider" bank so I can find everything I've created quickly by just selecting that bank in the preset browser.)
  3. Touch the blank space beneath the Save and Cancel buttons on the touchscreen to bring up the patch number entry dialog.
  4. Type in a patch slot number as a starting point to find where to save your patch. At least on my unit, the first available patch slot was 164. You can use the selector dial to scroll through existing patch slots until you find a blank one.
  5. Touch the red Save button to store the patch in the current slot.
And that's it! I do hope I save some future Waldorf-owning SampleRobot fiends some time with these updated steps!

Sunday, August 23, 2015

Playing General MIDI Files on Ableton Live Part 4: Roland Sound Canvas (Hardware)

This is part 4 of a multi-part series on how to use General MIDI files with Ableton Live. The first part covers the basics of General MIDI and how Live handles MIDI files. These subsequent posts are step-by-step walkthroughs for a variety of instruments.


ABOUT THE INSTRUMENT

In this post we're going to use a hardware GM-compatible sound module, a Roland Sound Canvas SC-88. The instructions we follow for this are virtually the same for any GM-compatible hardware synth as far as Ableton Live is concerned. Some instruments might need to be put into a special GM mode in order to load the right patches, though. Consult your hardware manual if you're using a different synth.

USING THE INSTRUMENT WITH LIVE

  1. Create a new, empty Live set and press TAB to enter Arrangement view. (Session view technically works, but if your MIDI file contains time signature or tempo changes, Arrangement view is more appropriate.) Drag your General MIDI file from the Live browser into your Live set. If it's a Type 1 file, all the tracks in the file should end up on separate MIDI tracks in separate MIDI clips in the Live set.
     
    If it's a Type 0 file, Live will only import a single MIDI clip/track, regardless of how many musical parts the song contains. You will have to convert the file to Type 1 and start over. See the first article in this series to learn how to convert MIDI files.
     
  2. For each new MIDI clip that Live created, select the MIDI clip and look at its Pgm Change settings in the Notes panel of the clip view. Each imported track (except for maybe the drum track) should at least have a Program Change value selected.


    If the current clip is not a drum channel, and you see no Pgm Change setting, Live might not have properly detected program change events for that track. See the first article in this series to learn how to locate program change numbers in MIDI files.
    Note: If your MIDI file contains program changes that occur within the song (if a single musical part changes tones as the song progresses) you will have to split those MIDI clips into separate clips so you can set the correct program change value on each clip individually. MidiYodi tells you where in the song the program change events occur, so they should be relatively easy to locate in your Live set.
     
  3. Since we're working with hardware, there are a couple more things we need to check out before proceeding. First,  go to Options > Preferences > MIDI Sync and make sure that the MIDI Output port that leads to your hardware synth is enabled. My Sound Canvas gets its MIDI from Port 8 of my MOTU Midi Express 128, and I can see that the Track box for that port is set to On, so I know this is set up properly.
  4. Now look at the Audio tab of Preferences and click Input Config to confirm that the audio inputs that receive sound from your hardware synth are configured. My Sound Canvas is connected to input ports 9 and 10 on my interface, and I'm going to use them as a stereo pair, and I see that "9/10 (stereo)" is enabled, so we're all set.
  5. Go to Create > Insert MIDI Track to add a new empty track in your project, and then drag the External Audio Effect device from the Audio Effects category of the Live browser into the track's Device View area. (Don't use a track that already has a MIDI clip on it; doing so will cause headaches if you ever want to mute or solo individual tracks.)

    Important: Leave the Audio To field set to "No Output", but set the Audio From field to the interface inputs that your synth is connected to. In my case, that's inputs 9/10.

    Now, you might ask, "Why are we using a MIDI track instead of an audio track for this?" Well, you can use an audio track, but when you do that you have to worry about track monitoring, and how Live compensates for delays when recording at various monitor settings. I prefer to use Live's External Instrument and External Audio Effect devices instead, because they behave more like plugins and they automatically compensate for latency.

    Next, you might ask, "Why use the External Audio Effect device instead of the External Instrument device?" Well, that's because the External Instrument device requires to to select a MIDI output in order to be able to select an audio input. Since we're putting this device on a track that intentionally has no MIDI, the External Audio Device makes more sense here. Setting Audio To to No Output basically turns the device into a live audio input.

    One further note: Since the External Audio Effect device is only available in Live Standard or Live Suite, if you're using Live Intro, you WILL have to use an audio track for this instead, and make sure that track monitoring is set to IN to hear incoming audio, or (better yet) use your interface's direct monitor ability instead.
     
  6. For each MIDI track in your Live set that has a MIDI clip on it, change the Output Type setting to point to the track where you loaded your virtual instrument plugin, and change the Output Channel setting to the MIDI channel you want to use for that part. For the most part the actual channels you choose don't matter (so long as they're different from each other), however, you should only use channel 10 for your drum parts (parts that actually use the multi-sample GM drum layout).
  7. Now try playing your song!
    If you find that the Sound Canvas isn't loading the correct patches, or something just doesn't sound right, check these things:
    • Each MIDI clip (except perhaps the drum track) has a Program Change setting.
    • You are using the correct Program Change values (remember, they should be the MidiYodi value plus 1 because of how Live numbers program changes).
    • Make sure your drum track is routed to MIDI channel 10, and that you have a GM drum kit loaded on that channel in your plugin.
    • Your MIDI output ports and audio input ports are enabled in Preferences, and the correct ones are being used in your tracks.
    • You started playback from the very beginning of the song, since the program change events only fire at clip start. Click the Previous Locator button several times to make sure you're playing from the beginning.
      The Previous Locator button.
That's it for now. Go back to part one for links to the rest of the series, in case you missed anything.

Sunday, August 9, 2015

Using the Roland FA-06 and FA-08 as DAW Controllers

After several weeks of research, I decided on one of the Roland FA series music workstations to serve as my main MIDI keyboard controller. In this post I talk about why I picked the FA-06 over other keyboard options, what accommodations I had to make in order to fit it into my rig, and how the keyboard integrates with Steinberg Cubase and Ableton Live.

IT WAS TIME FOR A CHANGE

After putting up with minimalistic 49-key and 25-key MIDI controllers for the past few years due to limited desk space in my small studio, I finally decided it was time to move on to a bigger keyboard controller with more features. Until the beginning of Summer 2015, the desk where I did all my music work looked like this:

The old, cramped setup.
My desktop monitors and clunky computer speakers left me so little room that not only could I not fit a very wide (or deep) keyboard controller on the desk to begin with, but when I actually needed to use the desk for writing, I had to disconnect my Roland A-49 controller and rest it against the wall until I needed it again. Since getting a bigger desk (or room) wasn't really an option for me, I developed a game plan for transforming my desk into a workspace that could accommodate a bigger controller and hopefully even leave me a little more surface area than I had before.

Here's what I did:
  • I bought a couple of these Cheetah monitor wall mounts to float my two side monitors over my desk.
  • I bought a Dell S2415H 24-inch monitor to replace my Dell S2440L 24-inch monitor, because my S2440L unfortunately wasn't wall-mountable. Another advantage of the S2415H is that it has built-in speakers, which helped me eliminate the need for desktop speakers.
  • I also got a different Cheetah wall mount for the new monitor, since it was in a corner and needed to extend further than the other two. (A note on both models of Cheetah wall mounts: In order to fasten these to my three Dell monitors, I had to pick up some 20mm-long M4 machine screws and matching washers at a local hardware store. My monitors all have recessed mounting slots that required longer screws than were included with these mounts, and I used the washers as spacers to result in a tight fit.)
  • I also got some mounting hardware to hang my 7-port USB hub to the wall, hidden behind my right-most monitor, leaving my desk completely empty, except for my MOTU Track 16 audio interface.
  • Of course I immediately filled the new-found space on my desk with a luxurious Roland FA-06 Music Workstation.
Here's what it looks like now:

The new, spacious setup.
But, you might ask, why did I choose a full-on workstation instead of just a nice MIDI Controller with Cubase integration, like the Nektar Panorama or Roland A-800PRO? Well, that's what the rest of this post hopes to answer.

WHY I CHOSE THE FA-06


My primary reason for wanting to expand from a 49-key to a 61-key controller was to avoid the frequent octave transposing that I had to do on smaller keyboard controllers whenever I used Kontakt instruments or drum samplers that have a GM drum layout. But the more I looked into existing keyboard controllers, the more I realized there were a number of other things I was looking for as well:

  • Requirement: Something that could make sounds of its own. I wanted to be able to work out melodies or chords quickly without having to fire up Cubase and open a DAW project. Straight-up MIDI controllers don't have on-board sound, so I started to look at synthesizers, stage pianos, and workstation keyboards.
  • Requirement: Something that provided some level of DAW control- especially transport controls. When I recorded vocals, I used to put my Steinberg CC121 controller on a TV tray and scoot it next to my microphone stand so I could toggle cycle mode and re-record takes without knocking over the microphone or getting tangled in headphone and mic cables. Transport controls on a MIDI keyboard would put these necessary buttons within much easier reach when I'm set up for tracking vocals. Many hardware synths and stage pianos have some knobs and faders that you can map to different DAW or plugin functions when you're working with a computer, but very few bespoke synths have transport controls. This narrowed my search again to mostly workstation keyboards.
  • Requirement: Something with a reasonable pitch and mod solution. Ideally I'd prefer something with good-feeling independent mod and pitch wheels, but a solid and reliable joystick solution was acceptable. The Yamaha MOXF6, Yamaha MX61, and Kurzweil PC3K6 keyboards have independent wheel controls, so they were under serious consideration. The current KORG offerings have very flimsy looking little joysticks, so I had to scratch them off the list. Also, as nice as the keybed and Komplete integration of the Komplete Kontrol S61 was, I am no fan of those weirdo ribbon controllers it has, so that was out of the running as well. Roland has their own solution, a combo pitch/mod joystick, where both pitch and mod return to the center position when you let go of the stick. While I'm not the biggest fan of the stick, the Roland sticks are much more durable than I've seen in Arturia products, or what I fear the KORG sticks are like, so Roland was still a contender.
  • Nice-to-have: General MIDI support. Often when I'm laying down the initial MIDI tracks for a new project, I use General MIDI patches just because I know the GM sound set so well. It's super easy for me to dial up an acoustic piano here, fretless bass there, and just get my notes and chords down before I start trying to pick the best possible sounds for the job. All the Yamaha, Roland, and Kurzweil keyboards I was considering offered some level of GM support, in that they responded to the typical program changes with appropriate patches.
  • Nice-to-have: Aftertouch support. Of all the keyboards I've owned, I think only one ever actually supported aftertouch- and it was the CME Xkey 25- something just too small and physically shallow for me to do serious work on. I was curious to get a board with aftertouch support just to see what it might add to my work- but this was far from a must-have, since I'd gotten by for so long without it. Neither the FA-06 nor the Yamahas featured aftertouch; only the Kurzweils.
  • Nice-to-have: USB streaming/audio interface support. While this started out as a nice-to-have, now that I've got it, I don't know how I lived without it. Both the Yamahas and the Roland FA series have the ability to serve as an audio interface, meaning you can make them the primary audio device in your DAW. You can plug your headphones into the keyboard and hear both the internal sound and all your other instruments. This is great for me on hot summer days when I don't want to power up my entire rig, which generates a lot of heat. I can just pop a pair of headphones into the FA-06 and do everything I normally do (except record vocals), and the only things I need powered on are the keyboard and my DAW PC. This also means that I can record audio from the keyboard directly into the DAW without any audio cables. Everything can go over USB. The Kurzweil workstations have varying levels of USB connectivity, but they lack anything as sophisticated as the Roland and Yamaha offerings, so Kurzweil was kind of out by this point.
  • Nice-to-have: I'd like to have some actual "desk space" on my desk. Even though I'd freed up a lot of room, my actual working area was still kind of tight. The Yamaha MOXF6 (40.5"x14"x5") was basically the largest possible keyboard I could fit on my desk, so anything smaller with a comparable feature set was desirable. This tipped the scale in favor of the slightly shorter, slightly shallower FA-06 (40"x12"x4").

THE ROLAND FA WORKSTATIONS IN PRACTICE

There are plenty of good reviews already that cover the sounds and the sequencing/sampling capabilities of the FA-06 and FA-08, but I haven't seen anyone talk in much depth about what it's really like to use them as DAW controllers, or how well they integrate with specific DAWs like Cubase or Ableton Live- so that's what I'm going to focus on here.

There are some basic instructions for configuring the FA-06 and FA-08 for DAW control in both the Reference Manual and the Application Guide (available here), but they omit some important steps (and they don't cover Ableton Live setup at all), so first let's go over the steps required for Cubase and Live. From here on out, I'm just going to say "FA-0X" since the steps are the same for both the 06 and 08 models.

SETTING UP DAW CONTROL IN CUBASE

The following steps assume you've already installed the FA-0X driver for your operating system.
  1. Exit Cubase if it is already running.
  2. From the STUDIO SET PLAY screen of your FA-0X, press MENU, then select System and press ENTER.
  3. On the General tab of System Setup, make sure that the USB Driver option is set to VENDOR (MIDI+AUDIO).

    Note
    If you have to change it, you will be prompted to restart your keyboard after you select WRITE. (Please do that before continuing to the next step.)
     
  4. Press the DAW CONTROL button to bring up the DAW Control screen.
  5. On the DAW tab of DAW Control, navigate to the CONTROL MAP line and use the wheel to select CUBASE.

    Important
    Press WRITE and then select OK to store your selection. If you don't do this, the FA-0X will forget its DAW Control settings the next time you power up.
     
  6. If you want to use the FA-0X like a true MIDI controller, select the Controller tab in DAW CONTROL mode, navigate to the Local Switch option and set it to OFF. Now when you play notes on the keyboard, you will only hear the FA-06's internal synth engine in DAW Control mode if it is selected as an output device in your DAW.

    Note
    Don't forget to press WRITE to save your settings.
     
  7. Launch Cubase and go to Devices > Device Setup.
  8. Click the + button and select Mackie Control from the list. This adds a "Mackie Control" entry to the Remote Devices list.
  9. Select the new Mackie Control entry under Remote Devices and set both MIDI Input and MIDI Output to FA-06 08 DAW CTRL.
  10. In the User Commands section of the dialog, you can set custom commands for pads 1-8 of the FA-0X's Sampler section (F1-F8). I do not believe there's a way to make the FA-0X use the "Shift+F1-8" or "User A/B" user commands, so I just leave those blank.
    There are many dozens of commands to choose from.

    Note
    To customize what your FA-0X's knobs and S1/S2 buttons do, go to the Controller tab of the FA-0X while it's in DAW CONTROL mode, and specify which CC value each physical control should use. The S1/S2 buttons can work in Momentary or Latch mode. In Momentary mode, the button fires a single event of the selected CC with a value of 127 when you first press it, and then fires another event of the same CC with a value of 0 when you release the button. In Latch mode, the button toggles between sending a 127-value or 0-value CC event each time you press it, and only fires the event upon pressing the button- not when releasing.

  11. Super Important: Select MIDI Port Setup in the Device Setup dialog and uncheck the "In 'All MIDI'" boxes for FA-06 08 DAW CTRL and FA-06 08.


    None of the documentation I've seen so far explains the difference between the three kinds of ports the FA-0X keyboards present, but unchecking In 'All MIDI' for the DAW CTRL port prevents the assignable sampler pads from transmitting MIDI notes when you're trying to use the pads to issue DAW control commands, and unchecking the box for FA-06 08 prevents Cubase from recording duplicate notes, as described below.

    When your MIDI ports aren't set up right, Cubase will record duplicate notes for anything you play. This has different results depending on which synths or plugins you're using as a sound source, so you may not even realize it's a problem right away. Some plugins will cut notes short when this happens, others will actually leave notes stuck on, just like keys on an old fashioned typewriter get stuck when you press a bunch of them at once.

    If you record a MIDI clip without disabling the extra In 'All MIDI' ports and then open that clip in Cubase's List Editor, you'll see the extra notes quite clearly.
    The problem with duplicate MIDI notes is most obvious in the MIDI List Editor.
  12. Even in DAW Control mode with Local Switch disabled, your FA-0X keyboard still functions as a 16-part multi-timbral synth when it receives incoming MIDI messages from your DAW. You can choose a default studio set to use for whenever you enter DAW Control mode on the Studio Set tab of the DAW CONTROL screen of the FA-0X. On the same screen you can pick which presets to use on each channel of the studio set. Again, remember to press WRITE to save any changes you make here.

SETTING UP DAW CONTROL IN ABLETON LIVE

The following steps assume you've already installed the FA-0X driver for your operating system.
  1. Exit Live if it is already running.
  2. From the STUDIO SET PLAY screen of your FA-0X, press MENU, then select System and press ENTER.
  3. On the General tab of System Setup, make sure that the USB Driver option is set to VENDOR (MIDI+AUDIO).

    Note
    If you have to change it, you will be prompted to restart your keyboard after you select WRITE. (Please do that before continuing to the next step.)
     
  4. Press the DAW CONTROL button to bring up the DAW Control screen.
  5. On the DAW tab of DAW Control, navigate to the CONTROL MAP line and use the wheel to select USER.

    Important

    Press WRITE and then select OK to store your selection. If you don't do this, the FA-0X will forget its DAW Control settings the next time you power up.
     
  6. If you want to use the FA-0X like a true MIDI controller, select the Controller tab in DAW CONTROL mode, navigate to the Local Switch option and set it to OFF. Now when you play notes on the keyboard, you will only hear the FA-06's internal synth engine in DAW Control mode if it is selected as an output device in your DAW.

    Note
    Don't forget to press WRITE to save your settings.
     
  7. Launch Live and go to Options > Preferences.
  8. On the MIDI Sync tab of Preferences, choose MackieControl as one of the options under Control Surface, and then pick FA-06 08 DAW CTRL for both Input and Output on the same row. You might notice that when you do this, the "DAW CTRL" ports disappear from the MIDI Ports list in the lower part of this dialog.
  9. In the MIDI Ports section of the MIDI Sync tab, Make sure that the Input port labeled only FA-06 08 is turned Off, but all the other FA-06 ports are turned On.

    If you don't disable the FA-06 08 Input port, you will encounter a problem where Live accidentally records duplicate notes when you play parts on the FA-0X keyboard. This can result in strange behavior, such as musical notes "sticking" on the FA-0X (or in virtual instruments you're triggering from MIDI parts you recorded with the FA), or notes being cut short unexpectedly. Unfortunately, Live doesn't provide any way for you to actually see evidence of the problem in the user interface. However, if you export MIDI clips recorded in Live to another DAW or MIDI editor, you can see the duplicated notes that happen as a result of leaving the FA-06 08 Input port enabled. In the below screenshot you can see that Live occasionally created extremely short duplicate notes in two parts of this simple sequence.
    Duplicate notes in MIDI recorded inside Ableton Live when the "FA-06 08" Input port was left enabled.
  10. To customize what your FA-0X's knobs and S1/S2 buttons do, go to the Controller tab of the FA-0X while it's in DAW CONTROL mode, and specify which CC value each physical control should use. The S1/S2 buttons can work in Momentary or Latch mode. In Momentary mode, the button fires a single event of the selected CC with a value of 127 when you first press it, and then fires another event of the same CC with a value of 0 when you release the button. In Latch mode, the button toggles between sending a 127-value or 0-value CC event each time you press it, and only fires the event upon pressing the button- not when releasing.
  11. To customize what the Sampler pads do, go to the DAW tab of DAW Control mode and choose CC values and button modes for the User Pad 1-8 settings. These options only appear in the USER DAW profile of the FA-0X. (In Logic, Sonar, and Cubase, you configure the pad functions inside the respective DAW.) Unlike the Logic, Sonar, and Cubase profiles, where you can actually assign DAW-specific commands to the pads, in the USER profile you are limited to only assigning CCs. You also have the option to configure individual pads to operate in Momentary or Latch mode, like the S1/S2 buttons. And as always, don't forget to WRITE.

THE FA-06/08 AS AN AUDIO INTERFACE

If you put the USB Driver setting of the FA-0X into VENDOR (MIDI+AUDIO) mode, the keyboard will appear to your DAW as a 2-in/2-out audio interface.
But the FA-0X is no ordinary audio interface! Here are some things you should know about the interface functionality:
  • By default, audio from internal FA-0X instruments and effects, as well as incoming audio from the analog inputs and the USB audio connection all go to the FA-0X's MAIN outputs, and this output signal goes both to the keyboard's physical MAIN OUTPUT jacks as well as the input channels of your DAW. So, unless you change the default input and output routings, any sound your FA-06 generates, or any sound coming into its inputs can be monitored and recorded inside your DAW without anything connected to the analog outputs of the FA-06. To record the FA-06's output over USB, you simply create a stereo audio track in your DAW and set it to record the FA-06 08 IN and IN(R) I/O ports as a stereo pair.
  • The FA-06 has two kinds of analog inputs: The LINE jack is a 1/8" stereo constant-level input, and the GUITAR/MIC jack is a 1/4" mono input with adjustable gain. (All inputs are unbalanced.) There's also a GUITAR/MIC switch that boosts the GUITAR/MIC signal by an additional 25-30db when placed in the MIC position (this doesn't affect the LINE input). The signals from these two inputs are automatically mixed, and by default these input signals are further mixed with the FA-06's internal sounds, so despite only appearing as a 2-channel interface to your DAW, you can actually record three different sound sources simultaneously into those two channels, similar to recording the output of a small outboard analog mixer.
  • You can change how the various inputs and outputs are routed in various tabs of the System Effects settings.
  • You can avoid experiencing phasing effects in Cubase when working with audio tracks that have track monitoring enabled by enabling the Direct Monitoring feature in Device Setup > VST Audio System > FA-06 08.
  • On Windows, audio applications generally only let you select one audio device (interface) at a time, so if you're using the FA-0X as your audio interface, you won't have access to any of your other audio interfaces while inside your DAW. If you prefer to use a separate audio interface, just use the FA-0X's analog outputs and use it like a regular hardware synth; there is no native way to route its USB audio to another interface. 
  • Also, while the FA-0X keyboards are 16-part multi-timbral, they only have two analog output buses (MAIN and SUB), and only one of those buses is available to the audio interface mode at a time, which means that you can't use the USB mode to record separately mixable parts from the FA-06 into your DAW. (If you had a 4-input external interface, you could record two different stereo parts out of the FA-0X's MAIN and SUB outputs if you assigned them appropriately in your performance settings.) The Roland Integra-7 has twice as many analog outs (and even a digital output connector), so that's where to look if you need lots of separate output channels.
  • When I'm finished using my computer for the day, I turn off my FA-06 and put the computer to sleep. The only times I ever fully shut down or reboot my PC are when I'm making hardware changes or when I install software or updates that require a restart. I have found that sometimes my FA-06 stops functioning as an interface (Cubase and Live can't access it when I select it as an audio device), and the only way to make it work again is to reboot the PC. (Cycling power on the FA-06 doesn't fix it, and attempting to disable/re-enable the driver in Device Manager causes Device Manager to lock up... it appears to be a driver problem rather than a hardware one.) I don't have this issue with any of my other interfaces (including other Roland units), so I really hope Roland fixes this in a future driver update.
In my day-to-day work, I'm finding myself turning on only my FA-06 and using it as my interface while I compose or do audio editing. I usually only power up the rest of the rig if I need to record vocals or hardware instruments (my RME Fireface UFX has balanced mic and line inputs), and my poor MOTU Track 16 has hardly been getting any use at all. (I might retire it at some point, but am still hanging onto it for its digital I/O, which I sometimes use when sampling virtual instruments.)

Also, the way I have my patch bays wired, the FA-06 analog outs default to going into the UFX's analog inputs 1 & 2, and the UFX's main outs default to going to my studio monitors. So I can actually turn everything on and hear the FA-06 through my studio monitors without switching which interface my DAW is using or plugging in any additional cables.
Input from the FA-06 passes directly through the Fireface UFX's main outs, leading to the studio monitors.

I now only have to power up the minimum amount of gear in order to get a given job done, with a minimum of cord patching and audio device switching.

FA-0X INTERFACE LOW LATENCY PERFORMANCE

In terms of low-latency performance, the FA-06 interface is average. It's much better than the Focusrite Scarlett 2i2 or the interface mode of the Access Virus TI2 (both of which I used to own), but not as good as my MOTU and RME interfaces. Like all Roland interfaces I've used, the FA-06's drivers don't use the powers-of-two method for selecting buffer sizes, so in my tests I had to use the closest buffer size I could get: 288 samples.

I tested four different interfaces on my new DAW PC, running 64-bit Windows 7 at 44.1kHz and 256 samples (or 288 samples in the case of the Rolands). Here are the round-trip latency results, as reported by the Oblique Audio RTL Utility (lower numbers are better):

SOUND BANKS AND EXPANSION LIBRARIES

The FA-0X keyboards are much more than simple ROMplers. They support a variety of synthesis methods, and are, in some ways, deeply programmable. But with this power comes a fair amount of complexity. It actually took several weeks of actively using my FA-06 before I fully understood the different classes of sounds it supports, and how those sounds are managed.

There are five top-level categories of "tones" (patches) on the FA-0X keyboards, most of which come from the libraries of other Roland instruments, including the Integra and Fantom lines:
  • SuperNATURAL acoustic tones (SN-A): These are realistic, expressive acoustic instruments that can be customized in the Tone Edit menu.
  • SuperNATURAL synth tones (SN-S): These are more more traditional synthesizer patches that can also be deeply customized in the Tone Edit screen. These tones can comprise up to three oscillators, which can be either PCMs (samples) or traditional synthesizer waveforms.
  • SuperNATURAL drum kits (SN-A): These are high-quality, multi-sampled drum kits with a GM layout. These are fully customizable as well.
  • PCM Synth Tones (PCMS): This bank contains PCM/sample-based sounds. These tones comprise up to 4 layers of PCM sounds. There are several subcategories of PCM Synth Tones:
    1. Presets (PRST): Built-in PCM tones, apparently imported from the Roland XV series of synthesizers. These are user-editable.
    2. General MIDI (GM2): This is a full bank of small-footprint General MIDI patches. To my understanding, this is different from the Integra-7's HQ GM sound set. The FA-series GM2 set sounds very similar to that of my Roland SC-88 Sound Canvas. None of these tones are editable.
    3. Expansion slots 1 & 2 (SLOT1, SLOT2): These are virtual expansion slots where you can install special expansion sets made specifically for the FA-06 and FA-08, which are available at the Axial site. These patches are also freely editable.
  • PCM Drum Kits (PCMD): Drum kits from any of the aforementioned PCM subcategories show up here, and conform to the General MIDI drum layout. Any kits specifically associated with the FA-0X GM2 set are not editable, but non-GM2 presets and downloaded PCMD kits are editable.
Aside from the five types of tones, you can also record or import samples for use on the FA-0X Sampler pads. These samples are stored in a different part of memory from the PCM waveforms used in the various tone categories, and are thus ONLY available for use when triggered by the pads or the built-in sequencer. (As a disappointing side note, the pads do not transmit MIDI note data, so they can't be used to trigger external synths or drum samplers.)

The FA-0X keyboards offer a number of ways to import samples and patches:
  • For samples to use as loops or one-shots on the FA-0X pads, you can either record your own samples or import them from an SD card. 
  • You can download sounds for the Roland Integra-7 from the Roland Axial site, and import them as user presets via a complicated process that uses the included SD card. Sounds you import from downloaded Integra-7 libraries are imported as user presets in the SuperNATURAL synth tones (SN-S) bank.
  • You can download third-party sample packs for the Roland FA series at the FA-06 / FA-08 section of the Axial site. Importing these is an unusually complicated procedure which involves the SD card.
  • Also available at the Axial site are expansion sets designed explicitly for the FA-06 and FA-08 workstations. Instead of installing these via SD Card, you actually import these via USB thumb drive (using the special "FOR UPDATE" USB slot on the back of the unit). In order to import these sounds, you boot the FA-0X into a special mode, and then indicate which expansions to install in which of the two of the keyboard's virtual expansion slots. Sounds imported this way will appear in the PCMS category of sounds, grouped by expansion.
    FA-series libraries labeled "EXP-xx" are real expansion sets that go into the virtual expansion slots.
    The others are just mini sample packs.
    The process for importing expansion packs is very similar to the steps for applying system updates for the FA-0X keyboards.

FINAL THOUGHTS


After a couple of months of using my FA-06 on a pretty regular basis, I am still happy with my decision. The only other keyboard I know of that's really in the same league as the FA-06 in terms of features I was looking for is the Yamaha MOXF6, and while I'm sure it's a fine workstation, I doubt I would be more pleased with it than I am with the Roland. I'll wrap this up with a quick list of pros and cons.

WHAT I LIKE

  • Large and broad selection of high-quality usable sounds.
  • Much more programmable and customizable than I expected. This is no simple ROMpler.
  • Nice-feeling keybed.
  • Lovely, informative display.
  • Good set of physical controls.
  • DAW integration gives me quick access to transport controls and up to eight frequently-used Cubase features at a time.
  • Built-in audio interface enables me to compose and mix without having to power on my whole rig.
  • Axial library provides me access to a surprisingly large number of free new sounds.
  • General MIDI support. (I actually use GM when sketching out ideas!)

WHAT I DON'T CARE FOR

  • Keyboard doesn't support aftertouch (but neither did the competing Yamaha models). 
  • Disappointing implementation of the sampler/pads. I don't care too much about not being able to use my own samples in patches, but I wish I could at least assign MIDI note values to the pads so I could trigger an external drum sampler.
  • Need to use USB thumb drives and SD cards to import different kinds of material, when the keyboard has a USB connection to your PC already. Why not use the connection we already have?
  • Interface mode performs well when it works, but does not seem stable across multiple sleep/wake cycles. Sometimes have to reboot PC in order for DAWs to use the interface again.
  • I wish it had the Integra-7's "HQ GM2" General MIDI bank!


Sunday, January 20, 2013

Dumping MKS-50 Patch and Tone Data to MIDI Quest

Sound Quest MIDI Quest 10 XL is a powerful patch editor and librarian for vintage synthesizers, but depending on the specific synth you're working with, there are often a number of manual steps involved in loading data from your device into the MIDI Quest application. Here are complete instructions for getting all patch, tone, and chord data from a Roland MKS-50 into MIDI Quest 10. The steps for dumping data from an Alpha Juno 1 or Alpha Juno 2 are probably similar, just slightly simplified due to their lack of patch banks or chord memory.

The MKS-50 has two patch banks (A and B) and two tone banks (a and b). MIDI Quest can only deal with one bank at a time. So to load the entire set of patches and tones from your device, you’ll have to follow these steps twice, choosing the correct bank option each time. Also note that there are two patch and tone banks, but only one Chord Memory bank. You can skip that one the second time around.
  1. After confirming that your MKS-50 MIDI settings are correct in MIDI Quest, click the Get button. MIDI Quest will open a window that says: Roland MKS-50 Patch Bank
  2. On the MKS-50, press the DATA TRANSFER button, then use the PARAM controls to select Bulk*Dump (do not use Bulk-Dump) and use the VALUE controls to select the patch bank you’d like to load (P-A or P-B).
  3. Press WRITE. MIDI Quest will load the selected bank and the screen will now say Roland MKS-50 Patch.
  4. If you don't want to load an individual patch now, click Cancel in MIDI Quest and skip to step 6. Otherwise, press TUNE / MIDI on the MKS-50 and use the PARAM controls to select TX PATCH APR, then use the VALUE controls to select ON.
  5. Press TONE to exit the MIDI menu, then press PATCH, and then enter the number of a patch to select. (For example, 1, 1 will select patch A11, PolySynth1.) MIDI Quest will now say it is receiving Roland MKS-50 Tone Bank.
  6. Press DATA TRANSFER and use PARAM to select Bulk*Dump. Use VALUE to choose the tone bank you wish to load (T-a or T-b).
  7. Press WRITE. MIDI Quest loads the bank and then says it’s receiving Roland MKS-50 Tone.
  8. If you don't want to load an individual patch now, click Cancel in MIDI Quest and skip to step 10. Otherwise press TUNE / MIDI on the MKS-50 and use PARAM to select TX TONE APR, then use VALUE to select ON.
  9. Press PATCH to exit the MIDI menu, then press TONE, and then enter the number of a tone to select. (For example, 1, 1 will select tone a11, PolySynth1.) MIDI Quest will now say it is receiving Roland MKS-50 Chord Bank.
  10. Press DATA TRANSFER and use PARAM to select Bulk*Dump. Use VALUE to choose CM.
  11. Press WRITE. MIDI Quest loads the bank and then says it’s receiving Roland MKS-50 Chord.
  12. If you don’t care about loading a specific chord memory selection, press Cancel in MIDI Quest now. Otherwise, press TUNE / MIDI and use PARAM to select TX C.M. APR, then use VALUE to select ON.
  13. Press TONE to exit the MIDI menu, then press PATCH, and then enter the number of a patch to select. (For example, 1, 1 will select patch A11, PolySynth1.) Note- the patch you select must already have the chord mode you wish to upload applied to it. You only get one chance to select the patch.
  14. Use PARAM to select ASSIGN MODE, and then use VALUE to choose C.M.
  15. Use PARAM to select CHORD MEM NO. and then use VALUE to choose a specific chord slot.

Tuesday, January 15, 2013

How To Upgrade the Roland MKS-70 ROMs

The Roland MKS-70 Super JX is a classic Eighties synthesizer that packs the power of two Roland JX-8Ps into a single 2U rack module. While the MKS-70's sound is still sought after today, most units on the second-hand market have old ROMs that don't support the ability to send SysEx commands to both of the device's internal synth modules. This presents a problem for artists wishing to perform automation on complex synth patches or editing those patches via MIDI.

How to tell if you need to upgrade


First off, the MKS-70 contains three EPROMs: The main ROM (A), which is on the synth's assigner board, and the two module ROMs (B and C), located on its module boards (one board for each synth part). You need to have version 1.08 of the main ROM and version 1.06 of the module ROMs to be fully up-to-date.

While there is no way to see the module ROM version without cracking the synth open, you can see the version of the assigner board ROM by pressing and holding the VALUE button on the front of the unit while powering the device on. The ROM version will appear on the display for seven seconds.

If you have main ROM version 1.03 or earlier, you will need to replace all three EPROMs in order to get full SysEx capabilities. You may wish to do some more research on this, but general consensus is that if you have 1.04 or later, you only need to replace the assigner board ROM.

My MKS-70 had version 1.03 of both the assigner and module ROMs, so I had to replace all of them.

Where to get new EPROMs


As the time of this writing, there are several options available for obtaining the latest ROMs for your MKS-70.

Roland Service Center


Up until some time in 2012, Roland USA upgraded the EPROMs for free if you sent yours in to them and covered shipping costs. When I called them in early 2013, however, they said that they will now only accept full MKS-70 units shipped to them, and they will perform the upgrade at a rate of $80 per hour (in 15-minute increments), plus shipping. It may be different at service centers outside of the United States. If you wish to go this route, make sure you have your serial number on hand and call them at 323-890-3740. Their USA service center is in Los Angeles.

Burning your own


If you own an EPROM burner, you can upgrade your own EPROMs or burn new ones using ROM image files obtained from other users. Just search around on the most common synth forums and you're bound to find someone willing to share.

Obtaining replacements


You can also simply buy new pre-burned EPROMs to replace your existing ones. At the time of this writing, you can get these from several places:
  • Synth Parts (USA). Email the owner for details. (This is where I got mine.)
  • KiwiTechnics (New Zealand). Use the Contact form to contact the owner.
  • Vintage Planet (The Netherlands). ROMs listed separately or as a bundle.
  • eBay (worldwide). I've seen the ROM sets up here for various prices.

Replacing the EPROMs

I was very nervous about doing this, but it turned out to not be very difficult. Here's a walkthrough of my successful upgrade from 1.03.

Tools required

I used the following tools to perform the upgrade:
  • Phillips screwdriver
  • Small flat-head screwdriver
  • Pliers (needed these to unscrew some posts inside the machine)
  • IC extractor (you can use a small flat-head screwdriver if you don't have one of these)

Opening up the case

First off, with the synth disconnected and in a well-lit area, remove the single screw on the rear of the lid.

I removed the rack ears, but after having the device apart, it looks like it was unnecessary to completely remove them- however the forward screw on each side appeared to fasten to the front of the unit, so at least remove that one.

Next, remove the six circled screws on the bottom of the device. In my case, the lips on each side of the top cover appeared to be sealed to the bottom of the case. I used a small flat-head screwdriver to gently pop the seal and free the top cover.

Replacing ROM C

After turning the unit over, remove the top cover by sliding it toward the rear. The first thing you should see is the top module board, where ROM C resides. (Mine was clearly labeled, including version number.) Carefully replace the EPROM and then remove the four circled screws.

Replacing ROM B

Swivel the top module board out of the way (I supported it with a couple small boxes placed next to the synth) to reveal the second module board, containing ROM B. Replace the EPROM and then remove the circled posts. Mine were actually sealed to the board, and I had to use pliers to loosen them. I also disconnected the cable circled on the left to allow this board to swivel more freely.

Replacing ROM A

Swiveling up the second module board fully reveals the assigner board, home of ROM A. You might want to ask a friend to hold the module board out of the way, since at least in my case it didn't go up enough to stay in a fixed position- but I managed to replace the EPROM one-handed.

Putting it back together and testing

After checking that all your EPROMs are firmly seated, reconnect any cables and replace any screws you removed, then replace and fasten the top cover. After re-connecting your MKS-70, try sending SysEx to both synth parts in a patch that uses both tones. If you're a Cubase user you can easily do this with the MKS-70 MIDI device panel available at Cykong. Before the upgrade, the second virtual PG-800 in the panel did nothing, but now it adjusts the second tone. Yes!


Sunday, December 30, 2012

SOLUTION: MIDI Feedback Loop with Roland MKS-80

I was so stoked to hear my newly-acquired MKS-80, my first-ever in-person experience with the legendary synth. I hooked up the MIDI and audio cables, set up my device connections in Cubase, and started playing- but to my horror, instead of hearing glorious phat basses and creamy pads, I was assailed with loud, distorted, frenzied noise. My eyes darted over to the MKS where I noticed the MIDI MESSAGE light flashing on and off, even though I was no longer holding down any keys. This was bad.

I re-powered the unit and tried again, with the same results. Next, I tried it out in Ableton Live, and still nothing changed. Uh-oh.

Well, after a fair number of unproductive internet searches, I did some more experimenting and figured out that if I unplugged the MIDI Out cable, the unit worked fine. It appears that the MKS-80's MIDI Out port operates a little like a MIDI Thru port, and the behavior is the same regardless of what position the unit's MIDI FUNCTION switch is in. Luckily this is pretty easy to work around in both Cubase and Live.

In Cubase: On any MKS-80 MIDI tracks, open up the track inspector and change your MIDI Input Routing from "All MIDI Inputs" to your primary MIDI controller. In my case, I selected my AKAI MPK49.

In Live: On any MKS-80 MIDI tracks, change the MIDI From setting from "All Ins" to your MIDI controller.

Whew. What a relief!

Monday, November 12, 2012

Using the Blofeld Virtual Editor on Live and Cubase

I love my Waldorf Blofeld desktop synthesizer (), but due to how my room’s set up, I can’t reach its controls or read its display when I’m at my computer. I was very pleased to learn about the free Blofeld Virtual Editor for Windows that you can use to edit Blofeld patches from your PC.

The editor runs as a VST plugin in a DAW or VST host, but there’s one major drawback- the editor needs exclusive access to your Blofeld’s MIDI ports; if your DAW is configured to “see” the Blofeld’s ports, you won’t be able to use them in the editor. And an unfortunate side-effect of this limitation is that once you configure your DAW to let the editor control the Blofeld’s MIDI ports, you can no longer send MIDI notes to the device... so unless you’ve got one of the Blofelds that has its own keyboard, you won’t have any way to test out your patches while you’re editing them!

Turns out there is a way to use the editor AND send MIDI notes to the Blofeld at the same time. And here’s how to do it:

Before You Start
1. Download the Blofeld Virtual Editor from here.
2. Copy the DLL file into your 32-bit plugins folder. For example, on my system, I keep all my 32-bit VSTs in: C:\Program Files (x86)\Vstplugins
3. Load up your DAW and make sure you can load the plugin.
4. Make sure you have a USB connection to your Blofeld. Full functionality of the editor is only possible with USB.
5. Plug a 5-pin MIDI cable into an available MIDI OUT port on any MIDI interface or device you may have available, and plug the other end of the cable into the MIDI IN port in the back of your Blofeld. Both the Blofeld’s MIDI and USB ports should now be occupied.

Setting up the Virtual Editor in Ableton Live

1. Create a new Live Set and delete the initial Audio track, leaving just a MIDI track.

2. Go to Options > Preferences > MIDI Sync and make sure the “Waldorf Blofeld” MIDI Input and Output ports are set to Off. (The Blofeld Virtual Editor won’t be able to access the ports if Live is still using them.)

3. Find BlofeldVirtualEditor in your Plug-In Devices browser and drop it on the project’s MIDI track. If the plugin window doesn’t appear, click the little wrench on the BlofeldVirtualEditor device at the bottom of the screen.

4. In the Blofeld Virtual Editor window, select Waldorf Blofeld for both MIDI IN and MIDI OUT.

5. Click Get Patch in the bottom of the editor window. It should load the patch currently active on your Blofeld device into the editor.

6. Back in Live, create a new MIDI track and drag an External Instrument device onto it.

7. In the External Instrument device, set MIDI To to the physical MIDI port that will be sending MIDI notes to your Blofeld (in my example, I'm using the MIDI out from my Virus TI). Next, set Audio From to the audio input ports where your Blofeld sends its audio output. If you don’t see the desired port listed in the MIDI To list, you might need to make sure that port is turned on in the Track column of Options > Preferences > MIDI Sync. The same goes for the Audio ports, which are activated in Options > Preferences > Audio > Input Config.

8. Now, as long as the MIDI track is armed for recording, you can play notes on your keyboard controller while tweaking away at your blofeld patch in the virtual editor! (Be sure to read the PDF manual that comes with the editor, as it covers some things unrelated to getting things working in your DAW.)
Setting up the Virtual Editor in Cubase
1. Launch Cubase and start with a new, empty project.
2. Go to Devices > Device Setup > MIDI Port Setup and uncheck any boxes for the Blofeld MIDI ports so that the State column says Inactive, then click OK. (If you don’t do this, the Blofeld Virtual Editor won’t be able to communicate with your device.)

3. Go to Devices > VST Instruments and load BlofeldVirtualEditor into one of your VST slots. When Cubase asks if you want to create a MIDI track, click Yes.

4. In the MIDI Inspector of the newly-created track, click the Edit Instrument (keyboard) icon to open up the editor window.

5. In the Blofeld Virtual Editor window, select Waldorf Blofeld for both MIDI IN and MIDI OUT.

6. Click Get Patch in the bottom of the editor window. It should load the patch currently active on your Blofeld device into the editor.

7. Back in Cubase, add a new MIDI track to the project. Set the MIDI “Output Routing” to the MIDI port that’s physically connected to your Blofeld’s MIDI IN port. In my case, it’s the Virus TI MIDI port. Also set the channel to one that your Blofeld will recognize (1 should work). If you play some keys on your controller while this track is armed, you should see the MIDI activity light on your Blofeld blink- you won’t be able to hear anything yet.

8. Add an audio track to your project. For Input Routing in the audio inspector of the track, select the input bus of your Blofeld’s stereo outputs. I named my bus “Blofeld Audio.” If you don’t have a viable choice in the Input Routing menu, you will need to set up a bus for your synth in Devices > VST Connections > Inputs.

9. Click the Monitor (speaker) button on the Audio track, then select the MIDI track and play notes. You should be able to hear notes you play now, and so long as the MIDI track is armed you’ll be able to audition sounds as you tweak them in the editor. Don't forget to read the PDF manual for the Virtual Editor. It will cover the rest.