KVR Audio

bjporter · Post by **bjporter** » Thu Sep 12, 2013 1:19 am

In case anyone missed it:

Making a Mono / Fury snare - PART 1

Introduction
You might be able to do it with 1 instance, but I almost always use 2, for more control.
Here's what it sounds like after Parts 1 & 2:
https://soundcloud.com/bjporter/a-littl ... fury-snare

Let's start with the first instance:

The Upper Layer (Click to enlarge)

This is what gives the snare its roughness, and snap. Start with the 'init' patch, and work your way from there. You need to lower all the oscillator volumes, and turn up the noise. Then to make it snappy, adjust the Voltage Control Amplitude envelope.

The Lower Layer (Click to enlarge)

This is what gives the snare its thump. Start with the 'init' patch again, and work your way to the picture. Lower all oscillators, except for oscillator #2, and make sure to set the Freq MOD knob, for pitch modulation. Also set the 2 envelopes, and the filter intensity correctly. The KBD track should be 0.

Your snare note should be between D3# and G3# depending on how you like it. That is between around 150 to 200hz.

Hope that helps

bjporter · Post by **bjporter** » Thu Sep 12, 2013 6:13 am

Making a Mono / Fury snare - PART 2

The Signal Chain
PLEASE READ PART 1! Basically the idea here is to group / bus the Upper & Lower parts, and apply some compression.

**Click Picture to enlarge / zoom**

The transient designer should give the lower part a bit more snap. The limiter gives the snare a lot more thud at the top end. The maximizers glue everything together and bring out a lot of the frequencies for more roughness (almost more acoustic / real). The EQ will remove unnecessary frequencies that should not be in a snare. When you maxmimize/compress/limit things, a lot of unneeded frequencies tend to come in. A very steep EQ high pass filter should be employed to remove these.

I'll add more information later. But that's just the basic idea of what I did. The maximization and limiting was VERY STRONG.

V'ger · Post by **V'ger** » Thu Sep 12, 2013 11:53 am

Great tutorial Bj

nitrowheels · Post by **nitrowheels** » Thu Sep 12, 2013 12:33 pm

nice tut and result BJ

e@rs · Post by **e@rs** » Sat Sep 14, 2013 11:07 am

On my machine, Mono/Fury acts like a great emulation of a really really broken Mono/Poly. In a normal situation I will go to the moon just to be as far from it as possible. But for this month we will make sweet sweet lovin'. Hope the child won't come out as ugly as the parents...

V'ger · Post by **V'ger** » Sun Sep 15, 2013 12:59 pm

V'ger · Post by **V'ger** » Tue Sep 17, 2013 3:04 am

So how's it going with those bassdrums then? Do bongos instead?

V'ger · Post by **V'ger** » Thu Sep 19, 2013 10:49 pm

By the way, this must be one the best opening weeks tech issues wise so kudos for a (seemingly

) solid product there Bjorn.

V'ger · Post by **V'ger** » Sat Sep 21, 2013 8:42 pm

In case you missed it, the rules have been clarified, see here: http://www.kvraudio.com/forum/viewtopic ... 90#5492890

nitrowheels · Post by **nitrowheels** » Sun Sep 22, 2013 6:30 pm

Hi, I just want to let you know that I remastered "September". I hope that you will like this renewed version and effort. Thank you.

https://soundcloud.com/nitrowheelsmusic ... -september

QuadrupleA · Post by **QuadrupleA** » Sun Sep 29, 2013 7:15 am

Just for fun (not a contest entry, but a one-synth Monofury track):

http://soundcloud.com/quadruplea/nes-contra-remake

psmacmur · Post by **psmacmur** » Sun Sep 29, 2013 4:49 pm

Not sure if this belongs here or in the Studio One 2.6 thread, but I've been having a vexing problem with the Mono/Fury OSC. I don't understand patch management within Mono/Fury, so I saved my patches as Studio One presets. However, when I load the project, or choose to create a MixDown, it resets the synth settings to something other than my saved patches.

For live playback, if I go through each Mono/Fury instance (there are 11 so far) and choose the studio one preset from the "Browser Presets" (top left) dropdown, it loads the patch correctly. However, like I said, I can't create a mixdown, as it resets to the wrong patch settings.

It might be too late for me, but has anyone figured out a workable patch workflow for Mono/Fury in S1?

Thanks!

bjporter · Post by **bjporter** » Sun Sep 29, 2013 6:05 pm

psmacmur wrote: It might be too late for me, but has anyone figured out a workable patch workflow for Mono/Fury in S1?

Thanks!

That's weird... In cubase I just load up MonoFury, change the settings, and that's it. I don't have to save any patch.

I'll look into this - but it might be best to ask this at the Studio One Support forums etc.

psmacmur · Post by **psmacmur** » Mon Sep 30, 2013 2:27 am

Thanks for that. Just as an experiment, I tried a new project tonight, with exactly the usage pattern you described: drag in mono/fury, tweak the parameters, save the song file (not patches), restart S1 and see what I hear. The knob settings look right, but while the sound is related to what I set, its different. E.g. volume sounds wrong, MG isn't on even though its set. Changing these controls brings the sound back to expected, but its like what I see on startup is not quite what I get.

Not knowing the VST API, I can't say whether such a bug is more likely the synth or the DAW, but since Cubase behaves correctly, it must be S1. Boo, and I bought S1 because it was so great for the Mausynth OSC and seemed to be the new hotness.

bjporter · Post by **bjporter** » Mon Sep 30, 2013 2:45 am

psmacmur wrote:Thanks for that. Just as an experiment, I tried a new project tonight, with exactly the usage pattern you described: drag in mono/fury, tweak the parameters, save the song file (not patches), restart S1 and see what I hear. The knob settings look right, but while the sound is related to what I set, its different. E.g. volume sounds wrong, MG isn't on even though its set. Changing these controls brings the sound back to expected, but its like what I see on startup is not quite what I get.

Not knowing the VST API, I can't say whether such a bug is more likely the synth or the DAW, but since Cubase behaves correctly, it must be S1. Boo, and I bought S1 because it was so great for the Mausynth OSC and seemed to be the new hotness.

That's terrible! wtf... Sorry to hear mate

One-Synth-Challenge 56: Mono/Fury - Chat & Gossip