Discovering Loopcloud 5.0 as a sample library manager

This maybe something that I had overlooked for too long: Loopcloud. For years the talk of the sampling library town, but I didn’t look at it until I got a demo of the new Loopmasters Loopcloud 5.0 version at the Amsterdam Dance Event this year. I also had looked at other sample managers like Algonaut Atlas, but that may be only drums oriented. Intriguing, because Atlas uses machine learning to recognize the types of samples. For me, up to now, a sample manager was simply a folder in Ableton Live to browse through. And I had always put Loopcloud away as simply a shop to buy samples with a subscription model.

How to work with the application

The Loopcloud application is a standalone application, but it integrates with your DAW through a Loopcloud plugin. You can only have it on one track in your DAW. All samples that you browse then play through that track. The idea is to start with a sample in the Loopcloud application. You can have random sorting to free your mind. Then use that to edit, slice, dice, sequence, mash up and add effects if you wish. You can drag the final result into your DAW as a sound file. Quite something different than finding a sample and then edit it in the DAW. All with the tune and tempo of your DAW. It nicely prevents you using kind of preset sounds over and over. Clever!

Loopcloud sample editor
Loopcloud sample editor

It means however, that you have to keep two applications open while working. For those of you with two monitors, maybe a no-brainer. But then again, it could just be that you already have a nice workflow with your two monitors and now you need to fit in yet another application. Anyway, there is an option to have the application dock to the sides of a window at about 20% of the width. Combined with scaling and other options, you might manage with one screen. The application sometimes forgets how you docked and scaled it.

Your library manager

Now about the library management. The moment you add your own samples to the Loopcloud application it starts scanning all the samples in it. It will try to find BPM and key information and it will try to read other information from the name of the sample or the loop. It will probably not correctly discover more complex information like the genre, loop or one-shot, or the exact instrument. All is then marked down as tags and you can start searching for things like key and BPM.

Loopcloud docked
Loopcloud docked

For this you need to click the button marked “Your Libary”. If you also want the detailed information of your scanned samples to be correct you will have to start tagging yourself. Its quite advanced, you can tag whole folders and batches of files. For a more in-depth dive into the tagging and searching you should dive into the tutorials.

Additional plugins!

But then when I found out Loopcloud as a sample manager, the tutorial also pointed me to Loopcloud Drum. A separate plugin that is actually a full sample drum instrument. It uses its own Loopcloud drumkit format and will open up a separate section in the Loopcloud manager. A strange find in a sample library manager. As a separate instrument it has its own format and its actually more of a pattern beatmaker with its own sequencer. A preset list of drum kits get activated that have been assembled from Loopcloud one shot samples of course.

Loopcloud Drum plugin
Loopcloud Drum plugin

I didn’t find any option to change the patterns in the beatmaker, other than with a mouse. You would also expect an option to edit drum kits and build your own. You can edit the mix of the kit and save that as a “user” drum kit, but I didn’t see any way to create a drum kit from your own set of one shots. Maybe this is in a future version, or in a Loopcloud subscription model that I didn’t explore. I was kind of on the lookout for tools to start making beats, other than with loops or Nerve, but this is not it yet.

Loopcloud Play plugin
Loopcloud Play plugin

And even more? The tutorial also points to the Loopcloud Play plugin. Yet another sample instrument, but this time melodic. As an instrument its quite basic, maybe so basic that you fall back into the preset trap again. There are about 7 knobs to turn and that’s it. Like the Drum instrument it has its own place in the library and again no way to choose the samples. You can save tweaks to the knob as “User” instruments. I think it needs work, as this is no match for Native Instrument’s Kontakt.

Closing out

Loopcloud has a quite intricate subscription model and not all of the features are available in all tiers. Specifically on using multiple tracks and the sample editing. However, if you just want to use it as a sample library manager you can even use the free subscription model tier. If you already own Loopmasters stuff it will automatically appear in your library. Even though it could do with more advanced detection of the samples that you load in the library, for me this was a great find and it surely beats the user folders in Ableton Live.

Its the impedance, stupid!

This is a short story about something that you take for granted in this high-tech age. That you can connect anything to anything and that it just works. This time I tripped over something that did not work and it reminded me harshly that there are classic electrical laws to take in to account: impedance matching. Even more embarrassing is that I am actually an electrical engineer that switched to computer science and music.

Zoom L-12 monitoring outputs
Zoom L-12 monitoring outputs

So these days I am working on my stage monitoring. Of course its at least my performers dream to have wireless in-ear monitoring, but then you will find that you have to invest at least hundreds of euros and you can easily go up to several thousands. This is why I started experimenting with a simple wired stereo in-ear monitoring system. The Zoom L-12 mixer/recorder that I am using has 4 mix outputs for monitoring so that is the starting point.

Lets try to set the impedance story straight without getting too technical. For that you can go to the wiki page about the subject. In short its about getting the energy from the output (a mixer) optimally to the input (headset, amplifier) of the connected device. Otherwise its kind of like fitting a wide garden hose to something that is too small. The electrical equivalent: the output impedance should be lower than the input impedance. As a rule of thumb you can expect for outputs:

  • 100 ohm to 600 ohm output impedance from line outputs
  • 0.1 ohm or less from an amplifier

And for input impedance:

  • 10K ohm input impedance or more for line inputs
  • An average of 32 ohms for headphones, but it can range from 8-600 ohm
  • Around 8 ohms for speakers

This only applies to unbalanced outputs and inputs. So that means jack plugs and speaker connections. The transformers used in balanced outputs and inputs will usually match without you having to worry about it.

Enough theory. It is always a good idea to start with the ‘zero’ option. Lets connect a simple Shure SE215 earphone to the L-12 monitoring output. It says ‘Phones’. Easy peasy. The sound comes out, but the lows are kind of missing. I just skipped over this this, because I just thought that this was the quality of the output from the L-12. Looking back this was not surprising. If you check the SE215 spec sheet you will find that with an average input impedance of 17 ohm this earphone is quite hard to drive!

A lot of energy is therefore lost, because the output impedance of the L-12 turns out to be 100 ohms. This output qualifies as a line output driver, expecting a high-impedance amplifier to pick up the signal. Actually connecting earphones to this connector is a bad idea! Listening however with a directly connected Sennheiser HD 280 Pro is a more pleasant experience. This is easily explained by its more friendly 64 ohm impedance. Energy is transferred not very efficiently (almost halved), but much more efficiently than with the Shure!

So then I first looked at the Behringer P2, a small active monitoring amplifier. It uses two AAA batteries. You can connect XLR or a stereo jack plug. Since the L-12 has stereo jack monitoring outputs, this seemed to be the way. When connecting it all and the SE215 the result was very disappointing. Like listening to overly compressed, pumping audio, with completely random frequency dips and a lot of noise. Another impedance mismatch?

I immediately blamed the Behringer P2. But when you scout for reviews, this device invariably comes out as top rated with a lot of very happy users. How is this possible? I still don’t know. Particularly vexing is that there is no specification of the input impedance of the P2. It must be that however. Because when I connect the balanced input to a balanced output, it all sounds fine. Possibly no-one uses the unbalanced jack of the P2.

This is why have fallen back to using the Thomann mini body pack 2. It allows me to use long cables and gives me volume control on the belt mounted device. The sound isn’t perfect, because the 100 ohm output still has to drive the SE215. I am still looking for that perfect wired monitoring solution. Any ideas?