One Synth Challenge #93: OBXD by DiscoDSP & 2DaT (mmGhost Wins!)

[z.prime]

Main takeaway... in Cubase 7, it looks like click the "hidden drop down arrow" on the obxd track you are using for your kick, then add a lane for the Osc2Pitch, click points. See Guenon's post. You'll want to zoom in a lot, since this is at the individual note level...

[ere2learn]

kick.fxp - try it down low at a1,EQ it for some body

https://app.box.com/s/bcyjzh6zh60pj7yyt1oq3rpsz529z5ol

[wagtunes]

Here's an explanation of automation from Steinberg for Cubase 7. There's some extra topics, but just pay attention to the automation section:

Got it, found it, in process of setting up.

However, if I am understanding this correctly, in order to get the desired effect on each kick activation, you essentially need to set up the pitch envelope for each individual kick instance. This becomes beyond tedious for a 3 or 4 minute track of music.

There has got to be an easier way.

[z.prime]

... you essentially need to set up the pitch envelope for each individual kick instance. This becomes beyond tedious for a 3 or 4 minute track of music.

There has got to be an easier way.

Well, I assume if you create a midi clip with one kick and automation, you can just copy it. You might need to copy a specific way to also copy automation settings (like using shift, ctrl, or something else, or a button that toggles copy automation or not). Bitwig makes this easier with clip-based automation, but sorry I don't know enough about Cubase, maybe someone else could chime in.

[ere2learn]

OB-Xd - kick EQd

https://clyp.it/02enb5zr

[Dragonsongz]

Stephen, spend 1 week on sound design. I mean good sounds. Don't even worry about making a song. Take a kick sample and other percussion and other sounds you want to hear, and tweak the hell out of the synth to get them as close as possible. Then spend 1 week on a song, and design more sounds for it. Then scrap it. Then spend the 3rd week on a song and design more sounds for it then scrap it. Then spend the last week actually making a song from the sounds you've accumulated, and add a few more where you need to with your new knowledge of the synth. If you put 100 hours in like that, it should show and you would probably finish top 5.

I know this wasn't directed at me, but I'm definitely going to do this this month.

[VELLISLAV]

Whaaat .....why u make u music life so complicated - no need of automation for something so simple as making a kick.Here is a free preset ,feel free to adjust the knobs d way u like it for ur specific needs - OBXD as any other vst synths is perfectly capable to make kicks.Da vi imam sound dizain umeniyata...

[Guenon]

Whaaat .....why u make u music life so complicated - no need of automation for something so simple as making a kick.

You are right. I must add, though, that it's extremely basic automation , taking way less than a minute to set up and copy/paste across a track. [In this case, it was an experiment in one way of quickly getting a consistent, meaty kick out of this thing, with a lot of control for the slope.] But thanks, also to ere2learn, for cool kicks!

My view on these kinds of basic DAW features: if someone doesn't know, for example, how to assign a synth parameter to an automation envelope in their chosen DAW, and can't do trivial edits with them, it's nevertheless very, very important to get comfortable with that sort of thing.

[ATN69]

Nice synth! ..It will be even more interesting at voting time I guess

[opoint]

Any Ableton users out there know of a way to "print" the parameter values to a clip? I've always wanted to do this, so that a clip would essentially be a preset itself, rather than going in and tediously adding an automation point for each param.

[3lu5iv3]

Whaaat .....why u make u music life so complicated - no need of automation for something so simple as making a kick.Here is a free preset ,feel free to adjust the knobs d way u like it for ur specific needs - OBXD as any other vst synths is perfectly capable to make kicks.Da vi imam sound dizain umeniyata...

Thank you.

[z.prime]

Any Ableton users out there know of a way to "print" the parameter values to a clip? I've always wanted to do this, so that a clip would essentially be a preset itself, rather than going in and tediously adding an automation point for each param.

what the heck?

[Guenon]

Any Ableton users out there know of a way to "print" the parameter values to a clip? I've always wanted to do this, so that a clip would essentially be a preset itself, rather than going in and tediously adding an automation point for each param.

what the heck?

If I interpret this correctly: a function to automatically imprint the state of parameters into a clip; sort of like manually adding an appropriate automation point for every parameter. So that, when you place that clip into a specific place in your project, the plugin state changes accordingly, to the values of the imprinted parameters.

Unfortunately, no, I don't think this is possible. I know it isn't in Live 8, but haven't seen/heard anything like it in Live 9 either. There are many reasons for this, one being the arbitrary number of values that make up the whole state of a plugin. Live can only access the parameters you have manually configured to be automation targets (and before this was implemented it could only access the 128 first parameters of a plugin declared parameter list , I think the upper limit of configured parameters is still 128 freely chosen ones, could have been updated though) -- it would be convenient if this worked automatically across those user configured parameters, yeah. But it would still be different from recalling an actual preset.

However, something done in Max 4 Live might work. A bit clunky, overall, though.

In any case, note that each clip can have a program change message associated with it. If you're using a plugin that can recall sets of parameters when receiving those, that's one way of doing something resembling this. A flexible "parameter imprint" thing could effectively touch parameters of all plugins residing on a channel (not just the instrument plugin), from one clip, so it's not exactly the same, but... anyway.

[opoint]

The only max device with a similar functionality I know of is Kapture which uses only volumes and sends as far as I know, or maybe perhaps ClyphX, which I haven't used in years.

[Guenon]

Yeah... I have a nagging feeling I've seen a plugin snapshot M4L thingy like this, but I can't find it. I've used M4L so seldom these days it's almost weird. The general clunkiness and stability issues were a turnoff, I guess. Should use it more, for creative harvesting of material in separate sessions, and then process that raw material further using other means. (Okayyy, not going any further off topic hah)