Spring Creators Update

This post has nothing to do with new versions of Windows 10, except perhaps for the delay in getting it published. I don't know what the story is with 1803 or 1804 or whatever it turns out to be, but I'm sure Microsoft are working hard to prepare it for release.

I'm also sure it will be packed with features that I, as a "Creator", don't give a sh*t about. Just like the last "Creator" release.

So, what's new this month? Quite a bit, actually:

  • I installed Reaper 5.77 and watched most of Kenny Gioia's video tutorials;
  • I migrated one of my "works in progress" from SONAR into a Reaper project.

This was actually pretty straight-forward, considering. Creating the empty project in Reaper was trivial - all the VST instruments and effects are available, and I haven't used very many plugins that are locked to SONAR-only.

The MIDI data can be exported as a MIDI Type 1 file, which keeps the tracks distinct and retains the time offset of each clip. Be warned, however, that muted clips will be exported as unmuted. So there is some preparation required of separating the tracks so that muted and un-muted are on different tracks.

Then, you can open a .mid file in Reaper in a separate project tab, and select all clips in a track and paste them into the new project, positioning the paste point at the start of the timeline.

.WAV data is migrated differently, using SONAR's export as Broadcast Wave feature. Again, muted clips need some special handling if you want to retain them, because they will be exported as silent (empty) clips.

I plan to continue working on this project in Reaper and see how it goes.

What else happened?

Uh, okay. I'll be honest and say, up until this moment, I'd never heard of BandLab. They seem to be some kind of cloud-based music collaboration outfit. But apparently their pockets are big enough to allow them to expand their market and include a "real" digital audio workstation in their product range.

Releasing it as a free download for registered users? That's... quite cool.

So:

  • I created a BandLab account;
  • Installed the BandLab Assistant;
  • Downloaded and installed the new "Cakewalk By BandLab" DAW.

It just worked. After tweaking some of the VST search paths, that is. Any project I chose to load up, opened without errors and played back correctly. However, it was about this time I realized it was 64-bit only.

Up until now I've been using the 32-bit version of SONAR, exclusively. All my VST plugins were 32-bit and things just worked, so I left it that way. If I was going to go ahead with Cakewalk By BandLab (from now on I'll just call it Cakewalk), I would have to do a little work. 32-bit plugins are loaded and used, but there's a translation layer involved that, ideally, I didn't want to use.

  • I installed SONAR Platinum x64, including the bundled VST plugins, ensuring to check the [x] 64 bit box instead of the [ ] 32-bit one.
  • I opened the Plugin Browser in Cakewalk and made a note of all the 32-bit plugins, categorizing them as "installed but never use" and "installed and definitely used"
  • I re-installed all the "definitely used" plugins and selected the 64-bit version where possible
  • I removed all obsolete 32-bit VST files into a "retired" directory so that they would no longer be detected by the DAW

This left me with a pretty small list of 32-bit VST plugins that I've used historically and wish to keep on hand :

Instruments:

  • Taurus (these days I have a patch on the Novation PEAK...)
  • 4Front Rhodes (still has a nice compressed tone, I could replace but it sounds good as-is)
  • esLine String (I will replace this with the Arturia Solina V probably)
  • MinimogueVA (these days I have a patch on the Novation PEAK...)

Effects:

  • VC-64 Vintage Channel Compressor (I can replace this eventually)
  • LFX-1310 (Used for "vintage radio voice" and I could replace it eventually)
  • Amplitude 3 (just in case I've used it on a Bass track)
  • Glimmerverb (a really really nice shimmer reverb, could replace but hard to duplicate)

With the 64-bit upgrade process completed, it's back to business as usual. I'll stick with Cakewalk for most projects, for now, but I'll continue using Reaper for that one project, just to see how it goes.

I have a back-log of tasks to work through, and first up is re-recording some solo synth lines in "Listen", using the Novation PEAK hardware synthesizer, which is awesome.

A Reaper video for everything - mapping Sonar features

Kenny Gioia may be one of the primary reasons the Reaper Digital Audio Workstation (DAW) is so popular. For any specific feature you can name, there is apparently a YouTube video by Kenny that demonstrates and explains it. He has. An odd way. Of speaking. That is disconcerting at first. But after a while, you get used to it, and I find it very easy to absorb the information Kenny is relating.

For my own benefit, I'm going to keep an index of videos I've found useful when researching how to map a specific SONAR feature to Reaper's functionality. At least, that was my intention when I started.

Master Bus, and Track vs. Buss in general:

Track Folders:

Routing:

Working with external MIDI sound modules:

  • External Keyboard or Synth in Reaper (except this isn't working for me yet!)
  • Update: It *does* work but I have no idea what I did. Maybe the input monitor button was involved? Must research further.

Arrangement, Markers, and Time-base Rulers

Automation:

Time signature changes:

Take management, and comping:

Customizing the editing experience:

Vocals:

Driving a multi-timbral VSTi with multiple tracks (e.g. Split tracks for drums)

"Fit to improvisation":

Drum Maps:

Groove clips and time-stretching:

Export to WAV (rendering a mix):

MIDI Editing

Noise reduction:

 

I should probably stop adding things to this list, because after a while it's just going to look like the complete index of Kenny's videos on his site, here.

Practice ‘til your hands hurt

I’m having some difficulty making progress compositionally on a couple of new pieces, so I decided it was time to go back to some mostly-recorded works and see what needed to be done to get them ship-shape for album #2.

I should probably document my manifesto for album #2, but one of the tenets is to go back to the first demos for each piece, and respect the original instrumentation, if it makes sense to do so.

For the piece currently known as “Listen”, the bass riffs were developed shortly after I acquired my Chapman Stick, and certainly the early demos all featured it. So why, I have to ask, does my current work-in-progress project use a regular bass instead?

So I take out the Stick case from the back of the closet, and give it a good cleaning and a new set of strings (standard 10-string tuning). Usually I spend a long time trying to find the perfect recorded tone, but this time it came together pretty quickly (see below).

Another tenet in my manifesto is to avoid building up tracks by stitching together multiple takes. I’m not normally a “one-take” kind of guy, so this means, practice. And in the case of the Chapman Stick, which I hadn’t seriously played for a couple of years at least, lots of practice.

Finally, I think I got it down. In one take.

Here’s a little video I made while (re)recording the bass:

https://www.youtube.com/watch?v=9mB38yCU6D0

The backing track is not final; it’s a special mix that keeps things simple and un-distracting.

Now, with respect to that tone, here’s how it is achieved in the DAW:

image

I’m recording a mono track (#6 in the picture) direct into computer’s audio interface via a Dual Channel PRO ST Preamp, to buffer and merge the two channels from the Stick into a single mono signal.

This mono signal is then routed in-the-box to an Aux Track “Stick FX” that contains an instance of Guitar Rig 4 virtual amplifier. A pre-FX Send duplicates the signal to a second Aux Track that allows me to mix in some of the clean, un-effected sound of the Stick.

Cakewalk is dead; Long Live SONAR

My Digital Audio Workstation (DAW) of choice is Cakewalk’s SONAR. In 2017, Cakewalk (formerly Twelve Tone Systems) were celebrating their 30th year in business. Over the years, the “Cakewalk” MIDI sequencer evolved to support digital audio and matured to became a very capable music production environment. Eventually the company took the name of its flagship sequencer, and the DAW continued under the “SONAR” name.

image

I first encountered Cakewalk Pro Audio in 1994 when my wife-to-be (long story) sent me a copy. I think it was version 5. It very quickly replaced Passport’s Master Tracks Pro * as my studio workhorse, especially after digital audio recording features were added. I’ve been a loyal, paid-up user ever since.

In 2008 the company was effectively acquired by Roland, which in 2013 subsequently sold their shares to Gibson.

In November 2017, Gibson effectively killed the company by stopping ongoing development and reducing the staff to the minimum required to keep the servers running.

We can guess that Gibson may have tried to find another owner for the company, and failed; or perhaps just decided that it was better to write it off as a loss for this financial year.

Either way, we’re not going to see any updates to the SONAR product in the foreseeable future, despite the fantasies being spun out by some on the user forum.

The company website still exists, and you can find links to “Buy SONAR” but they all eventually lead to the cease-of-business announcement and the statement that new purchases are no longer possible. Documentation and downloads of historical updates and resources are, for the moment, still available. You’d have to be an idiot to think that this will always be so, however.

So where does that leave folks like me?

  • Switch to another brand of DAW, immediately
  • Stay with SONAR for the time being

I think I’m totally in the second group. If I were to switch, it would be to PreSonus Studio One, because I already own it (I use it for the excellent Project page for mastering).

Negatives:

  • If you’re not happy with 2017.10, well, you’re out of luck waiting for changes.
  • A re-install will require access to online authentication servers (at least until a promised work-around is made available).
  • If you find an existing bug that doesn’t have a work-around, you’re out of luck getting it addressed.

Positives:

  • It’s not like SONAR is going to suddenly stop working;
  • No new features means no new bugs;
  • As far as we know, there aren’t any existing show-stopper bugs without workarounds;
  • Total mastery of the software is possible; current techniques won’t become obsolete;
  • We can finally create an up-to-date knowledge base of tips, tricks, and workarounds.

I don’t regret the time or money I’ve invested in Cakewalk SONAR up until this point. To throw up my hands and abandon it? That would be throwing away that investment. So for now, call me a happy SONAR user.

Onward, and create!

* Oh my goodness, they are still a Thing.

The VAXMIDI by Infinite Response

In 2015 a Kickstarter was created for a project called “VaxMIDI” – a MIDI keyboard controller with attractive features, including polyphonic note pressure detection or “aftertouch”, a feature that traditionally has been difficult and expensive to produce, and/or protected by patents.

The second really interesting thing about this project is that it would be shipped in kitset form, to keep costs to a minimum.

The folks behind this project were reputable (read more about Infinite Response and the VAX77 keyboard). Strictly speaking, I did not need another keyboard controller in my studio, but as an engineer/musician, the project intrigued me.

I backed the project at the top tier, in for a 8-octave unit.

After the project reached its funding goal, we had to wait for the kit to be developed and manufactured before eventually receiving our kits. I was in the second wave of beta testers, and early 2017 I came home to a large box on the front doorstep.

I took over the dining room table for several months, assembling and testing each of the four 2-octave units.

image  image

Each base is an extruded aluminum section with a complicated cross section, supplying rails for the keys to swivel and rest on, and a clever mechanism of hammers that are flipped up by each key, and pass a slotted blade through an optical detector.

The aftertouch sensor is a long slot that widens as the blade is pulled through the sensor as the key is depressed more firmly.

There is quite a few places where this can go wrong: The sensor strip (of 22 detectors) can be misaligned; the distance between the hammer rail and the sensor base can be too high or too low; the felt on which the key steel rests can be too high… all these things have to be just right in order to position the slots correctly for the note and pressure detection to work correctly.

Additionally, there are challenges in assembling each base into the chassis and connecting the system circuit boards so that it stays together in a robust and stable configuration. Also, there are bugs in the firmware such that spurious patch changes were being emitted during testing.

Bottom line: My assembled unit is back in its big brown box, in my garage, until such time as we get some updates on how to address these issues. It’s looking more and more as though they will not be forthcoming. I think the company has long burnt through their Kickstarter funding, and combined with family health issues, I don’t foresee this project coming to a good conclusion.

That’s sad, because it shows a lot of promise. Technically, I think it can work, but it is really sensitive to manufacturing tolerances, and the skill and ability of the assembly technician (i.e. me) to overcome them only goes so far.

Re-releases and Resets

You may notice that things have changed color since your last visit. I got tired of the blue and decided a change would be a good idea for the next phase of existence.

Steel Tree 2.0

Okay, the biggest news is that I have created a 2.0 version of the Fruit of the Steel Tree album, as a digital release on BandCamp. The songs are also available to stream on this site - I’ve updated the Production Notes and you can read about the changes there.

Album #2

Album #2 is taking longer than expected, due to reasons that aren’t worth discussing. I have one track 100% completed, and I’m working on a couple of others that have been around for years but have never been finished. I have another long piece in demo form, 70% of it anyway. And finally, another large piece that is in the process of being written and I’m feeling very challenged by it both compositionally and thematically and it’s been hard to make progress on it.

Bottom line: I’m not giving up. There’s too much here that I value to throw in the bin. In order to get Steel Tree finished, I had to get serious and “reset” my activity and treated it like a project, requiring management and discipline.

I need another reset, to not despair of how long things are taking and instead satisfy myself with continual, gradual progress. And also, I’ll blog about it. The studio diary lives again (hopefully).

Pardon the dust

…while we remodel. Actually, it’s exactly the same decoration but placed over a new framework – BlogEngine 3.3, an upgrade from 2.5. Some of the theme styles aren’t working as expected; and some of the plugins aren’t working yet. There may be minor changes.

It has been over a year since my last confession… what’s new, you may ask?

Gone quiet? Not really

OK, I'll admit there has been something of a hiatus but this site has been extra quiet because mostly I'm posting updates on Facebook instead.

Check it out: facebook.com/TheProdigalSounds

That said, I'm expecting to create a buttload of updates here in the near future.

A new arrival : Agile 53437 Bass

So here we have a lousy picture of an Agile Defiant 53437:

 

 It's not a trick of perspective; those frets really do fan out along the fingerboard. The bass B string has a scale length of 37", while the top G string is 34".

 

 

A work-around for Sonar's timeline editing behavior: Slippy Clips

Update Dec 2017:

In a recent update to SONAR, Cakewalk added a feature called "Ripple Editing". It doesn't actually help with the problem described below, which still exists in the 2017.10 release of SONAR.

Original Post:

So I have this project - "Working the Paradigm Shift" - that is mixed 7/8 and 4/4 time signatures. Cakewalk SONAR is largely a great product but I feel that it does let us down in the area of time line editing. Here's an example, and a work-around:

In this section of the project, I have a series of 7/8 bars followed by a 4/4 bar. Whilst practicing the keyboard solo, I realize that one of those 7/8 bars also needs to be 4/4 as well.

However, if I change Bar 24 from 7/8 to 4/4, all the subsequent clips change their musical position:

Notice the clips in bar 25,26,27 etc are now all offset. Clearly this is not what I want. I'm showing the click track here to make it very obvious what the problem is.

I don't know why this should happen. After all, the clips use the default time base of "Musical"; they are not locked to absolute time or anything tricky like that.

OK, so let's UNDO the time signature change, and try locking the clips first:

Nope, that still didn't work. In fact, even though the clips are "locked" to "Musical" time base, they still slip into the previous bar.

I don't think the clips should need to be locked at all; but even if they do, the SONAR documentation seems to indicate that the clips should not be changing their musical M:B:T position, if they are locked:

If the clip is set to the Musical time base, the clip's M:B:T position stays constant, and its Absolute position shifts. If the clip is set to the Absolute time base, the position does not move, but its M:B:T position shifts

So... this could be a bug, or perhaps I am missing something. I'll raise that with Cakewalk Support, but for now, here's the work-around:

Work-around:

1. Ensure that Bar 25 is set to 7/8, over-riding the default/previous bar time signature.

2. At Bar 24, insert 1 measure in the time line: 

Inserting a measure like this does not corrupt the subsequent clips' M:B:T position. This is expected and known behavior.

3. Change the time signature of the new Bar 24 to 4/4:

Observe:

  • The original bar 24 (now bar 25) is inheriting the 4/4 time signature from new bar 24;
  • The subsequent clips have changed their M:B:T position, as we would expect, given what we observed earlier.

4. Change the time signature of Bar 25 to 6/8:

This should cause the later clips to re-align with the bars, because 7/8 + 7/8  =  4/4 + 6/8:

Observe:

The "7/8" clip in bar 25 is wrong, but a) we don't care about it, and b) all the other subsequent clips are correctly aligned.

Now we can remove the "extra" 7/8 bar 25 from the time-line. This actually involves a known work-around for another issue, which is that you can't delete a bar from the time-line unless there is even data in the section you want to delete. Fortunately for us, we have a clip we don't need:

5. Re-size the "7/8" clip so that it is nicely situation within the bar boundary.

6. Ensure Snap-To-Beat (whole note is advisable) is enabled

7. Press Ctrl-A to select ALL TRACKS

8. Select the entirety of Bar 25, and select Edit > Delete Special from the menu.

9. Select all options, especially "Delete Hole" and "Shift by Whole Measures":

10. Click OK.

Bar 25 should now be removed, and now we have a Bar 24 in 4/4 and the rest of the project continues as it did before we started editing.

IN MY OPINION, THIS IS TOO DAMN COMPLICATED and should be addressed in a future version of SONAR. (Updated - see above)