|
stutter/rhythmicfx
|
View this Thread in Original format
| daverodger |
| what is the best way to create a stutter in a section of my track using logic??? automated plugin, cut and paste?? |
|
|
| daverodger |
| quote: | Originally posted by Enigmatic XTC
practice |
yes but what exactly should i be practicing??? :D |
|
|
| DigiNut |
By "best way" I am sure you mean "easy way" and rest assured there is no such thing. These edits are some of the hardest things in production to get right if you aren't BT or Hybrid.
Read the material that's already available (use the search), start experimenting, and don't expect results for at least a couple of sessions, possibly several depending on your current level of experience.
Usually a good stutter or glitch edit starts with some cut and paste (or something similar), but there's a lot more that has to be done, and you have to make sure you pick the right source material as well. There's definitely no automated plugin which won't sound like absolute crap (unless you can get the hang of something like crusherX, but I wouldn't really call that "automated", it's even harder to work with the manual edits). |
|
|
| thoughtlessjex |
You can use either way. If it doesn't need to be very detailed--just a quick, dirty edit--you may as well go for dblue Glitch, which is good for beginners doing quick edits, and gives you an introduction via actual use to how glitch effects are implemented rhythmically. It only subdivides to 16th notes, but it works well enough up to that point.
If you want some truly impressive edits, though, you should use anything and everything at your disposal. Cut and paste, automate filters, throw different effects on different slices, Throw different edits on different tracks, etc. It works best if you break it down to 32nd notes and smaller, because eventually, you reach the point where sounds can develop a pitch and timbre of their own. This is time-consuming and difficult, though, and it never really gets faster or easier the more you do it, so if you aren't trying to emphasize the glitch itself, then you should just save your energy and use a plugin. |
|
|
| Arudius |
I agree with both above statements...practice, and also keep at it. This may be a good start point, as it's what got me going and am now pretty intermediate with stutter edits:
1.) Always make sure your stutters are on zero-crossings so they don't "click", unless you want that purposely.
2.) Two effects that work well, are easy, and go a LONG way:
- pitch shift up/down with quicker stutters (32nd, 64th notes, etc)
- sweep a negative-feedback mod-delay (especially the one that comes in Logic) just for that small section.
Just to get you started. Happy stuttering, and also enjoy LiveCut, CamelSpace, a d Frohmage as personal recommendations. :) |
|
|
| DigiNut |
| quote: | Originally posted by thoughtlessjex
This is time-consuming and difficult, though, and it never really gets faster or easier the more you do it |
I don't know if I agree with that - after a while you start to develop a particular "style" of editing, for better or for worse, and you tend to use the same general workflow and plugin settings. Of course it isn't exactly the same for each edit, and it's highly customized to the individual producer so I think that providing blanket advice would be useless, but one could say the same about arranging a track. And in fact, I'd consider many glitch and stutter edits to be a lot like arrangement, but on a much smaller timeline. It does become more natural with practice, but it has to be a lot of practice.
I think the key point is that this type of editing is a skill and not a task, which is what people often don't seem to understand.
| quote: | Originally posted by Arudius
1.) Always make sure your stutters are on zero-crossings so they don't "click", unless you want that purposely.
|
Not necessary as a short envelope on the attack/release will solve this problem, and a bit of reverb/delay can easily fill in any gaps. |
|
|
|
|
