hi again.
i have another super n00b question about using my microkorg.
i have found and edited a patch so it's pretty close to what i want to hear. the only things i can't figure out are how to make the sound blast at full pelt right when i touch the keys instead of it gradually coming in (i tried fiddling with the attacks but it didn't work) and also the sound sustains when i lift my fingers off the keys, and i can't seem to figure out how to fix this. i'm wanting the sound to stop when i remove my fingers.
i know, i know, probably silly or simple to alot of you, but i'm still learning! as before, any help would be wicked and muchly appreciated.
fuzzbot.
microkorg n00b question - 2
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
You apparently fiddled with the wrong Attack and Release. Find the right one and it will do what you expected. There can be 4 EGs in use in any one program. There's a filter EG and an amp EG for each timbre, and there's two timbres. So you're doing something wrong down there (that's what she said.) The initial state of a program is to play the sound full blast and to cut it off immediately when a key is release, as you can demonstrate by doing an InitProgram. So something is causing the slow attack and delayed release.
thanks, i seem to have played with the only attack/decays i can find which are on filter eg and amp eg, i also tried playing with the delay just in case it worked (???).
don't suppose you'd have any advice on what other things i should be trying specifically. (i literally just look and see which parameters have the word 'attack and decay' next to them and then turn them down, and there's only those two i mentioned that have it.) anything would help and thanks!
don't suppose you'd have any advice on what other things i should be trying specifically. (i literally just look and see which parameters have the word 'attack and decay' next to them and then turn them down, and there's only those two i mentioned that have it.) anything would help and thanks!
As I said, you have two sets of EG, one for each timbre. You are probably editing the ones on the wrong timbre. Pick the other timbre.
There also could be other settings that affect the level of the patch, such as LFOs and virtual patches that are assigned to affect the amp level or the filter cutoff point. One of the disadvantages of modifying a patch that someone else has created is that they might be using aspects that you don't understand, so it can be more difficult that creating your own patch from scratch - using the InitProgram to start from the default settings and a very simple tone.
So you may indeed have to go through every single parameter to see what they all do in order to determine what may be causing the behavior that you describe. That isn't a bad thing - since you probably should learn what they all do, and having a patch "misbehave" is a good exercise that can be motivating. When you eventually figure out what caused the problem, I'll bet you will remember it.
One approach you can take is to start stripping everything that you can from the patch that may be confusing the issue. Turn off all the effects. Disable virtual patches. Open up the filters by changing the cutoff point. Adjust the mix settings between OSC1, OSC2 and Noise to get rid of any of these sources that aren't in use. Keep stripping until to get to the heart of the issue and to simplify it. Then after you discover the problem you can add everything back.
There also could be other settings that affect the level of the patch, such as LFOs and virtual patches that are assigned to affect the amp level or the filter cutoff point. One of the disadvantages of modifying a patch that someone else has created is that they might be using aspects that you don't understand, so it can be more difficult that creating your own patch from scratch - using the InitProgram to start from the default settings and a very simple tone.
So you may indeed have to go through every single parameter to see what they all do in order to determine what may be causing the behavior that you describe. That isn't a bad thing - since you probably should learn what they all do, and having a patch "misbehave" is a good exercise that can be motivating. When you eventually figure out what caused the problem, I'll bet you will remember it.
One approach you can take is to start stripping everything that you can from the patch that may be confusing the issue. Turn off all the effects. Disable virtual patches. Open up the filters by changing the cutoff point. Adjust the mix settings between OSC1, OSC2 and Noise to get rid of any of these sources that aren't in use. Keep stripping until to get to the heart of the issue and to simplify it. Then after you discover the problem you can add everything back.
)That's a great attitude. It really can be a lot of fun to explore the depths of a synth engine, particularly if you approach it with the right attitude.
Programming a synth doesn't have to be a chore or an inconvenience, any more than sharpening a chisel is to a sculpter or mixing paints to a painter. You can think of programming as a martial art. Right now you are working on your white belt, but all black belts started with a white belt, so you are just at the beginning your training and learning the skills that you will use to attain higher levels of ability. This is your "wax on, wax off" phase.
Programming a synth doesn't have to be a chore or an inconvenience, any more than sharpening a chisel is to a sculpter or mixing paints to a painter. You can think of programming as a martial art. Right now you are working on your white belt, but all black belts started with a white belt, so you are just at the beginning your training and learning the skills that you will use to attain higher levels of ability. This is your "wax on, wax off" phase.