Komplete 10: Massive

While I could record wav directly using Reaktor (for example), for recording Massive I find I have to drop into my DAW (Reaper in my case), save to Midi, and render to wav or mp3 from there. But no issues on CPU overload with this one. Hm… while I haven’t yet checked, the overload might be because Reaktor’s output is direct to audio, not midi. Regardless, I can imagine that as I start to multi-track with more than a couple of the instruments across Komplete, I’ll find myself in need of a way meatier machine than a 5 year old I5 laptop with a single mechanical disk and 8GB of RAM.

Soundcloud quick sample here, using Bansuri in Orange. The number of synths or whatever name I should give them is again predictably massive. It must be tough thinking up new names for these.


Komplete 10: Reaktor 5

Working my way through the modules in Komplete 10…

So Guitar Rig, Kontakt, all went without a hitch. Reaktor: not the same experience. Note the “Processor Overload!” warning below. In fact this is not borne out by Task Manager, which went to a max of 60% or so. So I reduced sample rate from 44,100 whatever to 22,050 in an effort to stop the warning (with obviously a cost to the quality of the output).

On the positives, it is easy to record the output to wav file. See the trivial example on SoundCloud and another here.

Komplete 10: content

October 2016: Native Instruments now favour you using their PC app rather than the downloader, which didn’t have a proper home:

Now I’ve bought the thing, I will work my way through each of the modules, getting at least a cursory knowledge of how to use each of them:

  • Kontakt 5 –  August 2016, including factory content
  • Reaktor 5 – August 2016
  • Massive – August 2016
  • Absynth 5 – October 2016
  • Fm8
  • Battery 4 – October 2016
  • Guitar Rig 5 Pro – August 2016
  • Abbey Road 60s Drummer
  • Driver
  • Drumlab
  • Kontour
  • Monark
  • Polyplex
  • Rammfire
  • Reaktor Prism
  • Reaktor Spark
  • Reflektor
  • Retro Machines Mk2
  • Rounds
  • Scarbee A200
  • Scarbee Mark I
  • Scarbee Clavinet/Pianet
  • Scarbee Mm-Bass
  • Session Horns
  • Session Strings – September 2016
  • Solid Eq
  • Solid Bus Comp
  • Solid Dynamics
  • Studio Drummer
  • Supercharger
  • The Finger
  • The Giant
  • The Gentleman
  • The Grandeur
  • The Maverick
  • Traktor’s 12
  • Transient Master
  • Vintage Organs
  • West Africa

Given I bought the download version, directly from NI, so that I could install the modules piecemeal, I forget that I need to get the individual downloads from here, by downloading and installing Komplete_10_Downloader.exe.

Other thoughts related to the pictures below:

  • Given there are such a lot of checkboxes, a Deselect All option would have been jolly handy
  • Disk queue length of 50: this is running on my laptop with the 1 terabyte mechanical disk. I’m waiting for the right price on an SSD of that size (point being that Komplete is a massive install): I reckon around £150 will buy it on offer. I guess I need to judge my timing, as the GB pound’s lack of performance could easily see all items increasing in cost, and not reducing




Pester: starting to use it

I have started to move my PowerShell tests into Pester, and I like it. At the same time I have been using the PowerShell plug-in in VS Code, and I will not be going back (Well, right now, I still use the ISE for debugging, but I expect that might be available in VS Code at some time). Incredibly, Go To Definition exists, and works, taking you to a separate file if that is where the function is:

And you have any number of themes in VS Code (I’m using version 1.4.0 right now).

The PS plugin also has an automatic linter/hinter. For example, here it objects to the unapproved verb:

And finally just to show the Pester output from a passing and a failing test:

The code for the above is here (Utilities.ps1 and UtilitiesTest.ps1).

Azure ARM: MVA course

Useful ARM course here, for free.


Example they use on GitHub here.

Hm… I dumbly/deliberately pasted their example command line, knowing it would break, but not why:


New-AzureResourceGroupDeployment : The term 'New-AzureResourceGroupDeployment' is not recognized...

Fascinating. So they are using the Classic model.

If I now use


and not


, then I get this:


New-AzureRmResourceGroupDeployment : Could not find file 'C:\WINDOWS\system32\2VMsinVnetWithILB.json'

, which is fine.

So having cloned their repo, I then started using their example in anger.

Error 1: “GEN-UNIQUE is not a valid storage account name. Storage account name must be between 3 and 24 characters in length and use numbers and lower-case letters only.”

OK, so find and fix that:


Error 2:  “target”: “adminPassword”, “message”: “The supplied password must be between 8-123 characters long and must satisfy at least 3 of password complexity requirements from the following: \r\n1)
Contains an uppercase character\r\n2) Contains a lowercase character\r\n3) Contains a numeric digit\r\n4) Contains a special character.”

Same file – easy enough…

And after 5 minutes or so, I had a new deployment running in the Azure Portal. Great!


There is a Visualizer as well. I’ll dig into that another time. There is a new version… which looks a bit broken to me.

Azure and PowerShell: getting the status of the VM

If you run this, then you get a bunch of information… but not the key points about provisioning status:


$vmStatus = Get-AzureRmVM | Where-Object { $_.Name -eq "myvm1"} 
Write-Host $vmStatus.DataDiskNames 
Write-Host $vmStatus.DiagnosticsProfile 
Write-Host $vmStatus.HardwareProfile 
Write-Host $vmStatus.HardwareProfile.VmSize 
Write-Host $vmStatus.StatusCode 
Write-Host $vmStatus.ResourceGroupName 
Write-Host $vmStatus.Location 
Write-Host $vmStatus.HardwareProfile.VmSize 
Write-Host $vmStatus.StorageProfile.ImageReference.Sku 
Write-Host $vmStatus.StorageProfile.OsDisk.OsType 
Write-Host $vmStatus.StorageProfile.OsDisk.Name 
Write-Host $vmStatus.StorageProfile.OsDisk.Vhd.Uri

So the same command, but now specifying the resource name and vm name as arguments, gives this:

$vmStatus = Get-AzureRmVM -ResourceGroupName $rgName -Name $vmName -Status


And from there, we can drill in. For example:


That was a VM that is deallocated. This is how a running VM looks:




Azure: VM deallocation in PowerShell

… and implicit in that is Resource Manager, not Classic.

So interesting: if you execute this cmdlet against a running VM, then it becomes deallocated (as opposed to just Stopped):


That is, the default action is Deallocated.

If you now run the following, while keeping an eye on the Portal status, you see this:

That is, you can from a Deallocated state to a Stopped state. The key difference is the  [-StayProvisioned] switch.

This is useful for various PowerShell actions against Azure RM.

This is useful for the various sizes of VMs.