pat

[pat]

The project page has instructions on how to use the scripts… if there’s something specific you’re stuck on, let me know and I’ll do my best to help 🙂

[pat]

IN-FREAKING-SANE

[pat]

My sample organization is terrible… but for finding the samples I do have, regardless of on-disk organization… AudioFinder is awesome – IF you’re on OS X. I don’t know what’s good on Windows 🙁

[pat]

Any chance of seeing some kind of read / unread posts indicator? That is super useful for catching up with new stuff.

[pat]

Sampleconstruct wrote:

Yeah, I could do with an Undo, but I have adapted to the workflow of saving almost every single editing step so if something fubars, I simply load the previous version of a given patch.

It’d be nice if there were a “save version” button so yiu can do this with one click, rather than save as and edit the name each time.

[pat]

Okay another update. I’m going to keep exploring the wavetable stuff so I wrote a Ruby script to do the wave-to-wave interpolation, as well as support randomly chosen waves from a directory. It’s just a first pass but I plan to evolve it into a decent command-line tool for constructing wavetables.

[pat]

Here’s the first script which builds a wavetable from a single audio file.

I created a second script that interpolates between two audio files to create the wavetable file. So far I’ve only tried it with some of the Adventure Kids Waveforms and it works really well.

[pat]

otristan wrote:

For the coarse tune, you can use the Pitch knob instead. Regarding start slice, you indeed need to patch the sample multiple time.

yeah I worked it out with the pitch knob last night. Is there some way for me to set steps on it so I can get exact pitch amounts? Like say I want to set a range of +/- 12 semitones, and I want to change the pitch in semitone increments using host automation. How would I do that?

[pat]

 

The point is that they’re not triggered by the same key. In fact you can use different samples. Here’s a setup that works:

• program-level multi envelope set to legato (layer envelope probably works just as well)
• layer setting = mono retrigger
• multiple keygroups in same layer, with grain position modulated by the envelope

I haven’t tried it with keygroups from different layers yet… I suspect they wouldn’t work since it relies on the mono retrigger layer setting

[pat]

I want to do a lot more than 2. I want to create a bunch of variations that I can morph between. I’m just using 2 to start because if I can get that working then I can add more.

[pat]

Well it does matter… if it’s a dummy keygroup, you can’t use one of the mono play modes 🙂  But you can if you use a dummy oscillator, or a dummy modulation (aka no extra keygroup or oscillator at all).

I’ve confirmed that if you set the modulation ratio to 0 you get no modulation… so you can modulate an oscillator gain w/ the layer / program envelope, ratio set to 0 and it won’t change the sound.

Here’s an example patch that uses this technique. It uses a program ADSR and modulates the oscillator’s gain w/ a 0 ratio (no modulation), and a reverb chain’s return level. The way I’ve configured the ADSR, you’ll hear the initial attack with reverb, then the reverb will fade and it will be completely dry, and when you let go of the key the reverb will fade back in.

I’m starting to get the hang of navigating around list view too. Neat. Thanks to you both for explaning so much of this stuff!

[pat]

Okay so I did a bit more experimenting with this. I think it can be done just a bit simpler and more straightforward…

1. Create your keygroup and add a layer delay like normal. Set the wet amount where you want it
2. Create a second oscillator within the same keygroup, and disable it
3. Create your layer envelope w/ legato trigger mode, and route it to the disabled oscillator’s gain
4. Modulate the wet amount with the envelope, and set the ratio slider to -1.00 (don’t press the invert button)

This did the trick for me. Frankly I’m not sure why the layer envelope has to trigger an oscillator for this to work, but it does. In fact I think you can do it without a dummy oscillator at all.

1. Create keygroup & add layer delay
2. Assign a new layer envelope to the oscillator’s gain, set the ratio to zero
3. Assign the layer envelope to the delay wet amount, set ratio to -1

This does it without any extra keygroups or oscillators. It just adds a single, unused modulation on the oscillator gain. At least I think that’s what’s happening with a ratio of 0 (and that’s what it sounds like to me).

I don’t know how to upload patches otherwise I’d share an example.

[pat]

Oh yeah, sorry, I have a tendency to think about the next thing as soon as I get something sorted out.

You definitely helped me with the oscillator question, thanks.

“The next thing” I’m thinking of then is if I have three oscillators in a keygroup and I want to reuse those in a new program. I think it’s best to save it as a program, and then load the program in as a layer. Anyway I’ll keep experimenting.

[pat]

Sampleconstruct wrote:

Save the oscillator into your user library and then select it in the other keygroup -> create node -> choose anything -> then access your user library. One can only move keygroups to a new layer in the keygroup editor or copy/duplicate oscillators inside a keygroup via alt+drag.

Ah okay. I’m going to have to get into the habit of saving things into the user library.

So, let’s say I want to save a keygroup preset, which has three oscillators in it. I don’t think you can do that, can you? Basically you can save presets for individual modulators, or entire patch presets, right? So the way to save my three oscillators as a preset would be to save my program somewhere, and then load it in as a layer?

Whoa, duplicating oscillators with alt-drag is trippy! Turns out that’s in the release notes.

Thanks for the info 🙂

[pat]

Yes this is very confusing. Why can you assign modulators if they don’t do anything? I end up spending time and effort wondering, “Have I done something wrong, or is this a weird case that Falcon doesn’t support?”

[pat]

Oh interesting. I had never done it that way. I would just drag an oscillator over the keyboard, and then do it again – which creates two keygroups. I guess mono means it can only play one keygroup at a time… but multiple oscillators are allowed in a single keygroup as you pointed out. Thanks!

So, let’s say I have two keygroups, and I want to move an oscillator from one keygroup into another. Is that possible? Tree view shows the oscillators, but doesn’t have any cut / paste functions, or drag and drop. List view has cut / paste, but doesn’t show the oscillators.

[pat]

This was one of the first things I thought of as well… a ducking delay. Here’s the setup I tried (it doesn’t work):

* delay on layer

* modulate wet knob with a layer ADSR

I don’t know if I’m doing something wrong, but the ADSR doesn’t seem to affect the wet mix at all. Which if that’s the case, I don’t understand why I can add the modulation in the first place. But more likely I’m doing something wrong.

It’s… “interesting,” working around Falcon’s limitations (in an otherwise very powerful tool). I think it might be too complex for my brain at the moment 🙂