now if you are going to do a wave table like that you need to do it in 1bar so that when you change to the next bar it plays exactly after the previous bar this way you can have several bars that you modulate this is how i do it on a asr10 you have 6-8 variations and use the mod wheel to chop the breaksmojogigolo wrote:re the first point - to some degree it is present (but awkward). If you make a 'wavetable' thats actually a drum loop, then set the loop point to an 8th/16th/ whatever, you can trigger individual measures (but they loop on completion, meaning slower tempo from the original sounds all ugly and out of time).MadGav wrote:I wonder if this is actually a different module fighting to get out... kind of sample playback with a quantized start position. So you could load a loop, set the quantization to 16 "slices" then a trigger would kick playback to the position controlled by a slice input.mojogigolo wrote:id like to see a retrig on the grain oscillator (so it retriggers the 'frame' on input) - would allow for good reproduction of transients in tight timing without having to revert to tiny window sizes.
Martin
thats all a huge pain in the ass though.
so YES - more granular resequencing modules would be unbelievable - im sick of the quantising and thinking im putting into remixing loops with the current grain osc. You can go full scale autechre-style glitch with vaz, but thats not well reflected in the presets or docs.
also - hell yes to your new module above - perfect.
Top of your VazMod wish lists Easter 2011?
-
- KVRer
- 20 posts since 22 Apr, 2007 from uk
-
- KVRian
- Topic Starter
- 513 posts since 9 Nov, 2000
Have had a rethink... will add a Stages control (1-16), and reduce to 2 outputs: Output A will run from 1-16, Output B will run from 9-8 i.e. 8 steps off from A. So for up to 8 stages the sequences won't overlap. Also considering an option to disable looping so it could be used as a burst generator.shamann wrote:Perfect.MadGav wrote:How about this?shamann wrote:I'd love a pulse-driven gate sequencer module. I find the sequencer row at times a little awkward to work with, it'd be great to have an 8 or 16 step row of on/off buttons, like a single row of the Trigger Sequencer, but as a module, with clock in triggered on rising edge of the input signal.
Has outputs for each row and a 3rd for both rows (i.e. 16 steps).
Martin
[edit]Upon second consideration, would the addition of the option to specify sequence step length ( 1 to 8 ) be feasible? Could easily be done with an external Reset signal, but it would simplify to have it internal to the module.
[Edit] Also a Stage 1 output could be useful for i.e. stepping a switch to use multiple modules to make longer sequences.
Martin
-
- KVRist
- 441 posts since 30 Nov, 2002 from Sweden
Hi!
Maybe it's too late for easter-surprises now ...but I wonder if the 'Glide' could have a second mode, wich could be more discrete than the existing one. I find the glide a little bit too aggressive when used with fast envelope amp- and filterattack.
Best regards,
Kire
Maybe it's too late for easter-surprises now ...but I wonder if the 'Glide' could have a second mode, wich could be more discrete than the existing one. I find the glide a little bit too aggressive when used with fast envelope amp- and filterattack.
Best regards,
Kire
-
- KVRian
- Topic Starter
- 513 posts since 9 Nov, 2000
I could maybe do something if I could translate this into a concrete change in behaviour... any chance you can come up with an example patch to show off what you don't like?Kire wrote:Maybe it's too late for easter-surprises now ...but I wonder if the 'Glide' could have a second mode, wich could be more discrete than the existing one. I find the glide a little bit too aggressive when used with fast envelope amp- and filterattack.
Martin
-
- KVRist
- 441 posts since 30 Nov, 2002 from Sweden
Sure Martin!
Here's a little CS-80 improvisation just for you!
I like the glide, no doubt about it, but in some situations there's a need for a bit more discrete portamento. In this clip you can hear the glide going up and down heavily with only a value of 1.
http://www.box.net/shared/f2v1b58e4c
/Kire
Here's a little CS-80 improvisation just for you!
I like the glide, no doubt about it, but in some situations there's a need for a bit more discrete portamento. In this clip you can hear the glide going up and down heavily with only a value of 1.
http://www.box.net/shared/f2v1b58e4c
/Kire
-
- KVRian
- Topic Starter
- 513 posts since 9 Nov, 2000
I think you mean discreet? Not listened to the clip yet, but it sounds like the glide time slider is lacking resolution at the low end (i.e. the discrete steps are too far apart).Kire wrote:in some situations there's a need for a bit more discrete portamento. In this clip you can hear the glide going up and down heavily with only a value of 1.
Martin
-
- KVRian
- Topic Starter
- 513 posts since 9 Nov, 2000
I've just been trying this out... to get an idea of what is fast enough please can you try making portamento using a Slew Limiter B module with Rate set to 1. This will be a bit faster than the CV Converter Glide set to 1, but is it enough faster to make a practical difference? (Needing more just makes the change a bit more work...)Kire wrote:in some situations there's a need for a bit more discrete portamento. In this clip you can hear the glide going up and down heavily with only a value of 1.
Martin
-
- KVRist
- 441 posts since 30 Nov, 2002 from Sweden
Hi Martin!MadGav wrote:I've just been trying this out... to get an idea of what is fast enough please can you try making portamento using a Slew Limiter B module with Rate set to 1. This will be a bit faster than the CV Converter Glide set to 1, but is it enough faster to make a practical difference? (Needing more just makes the change a bit more work...)Kire wrote:in some situations there's a need for a bit more discrete portamento. In this clip you can hear the glide going up and down heavily with only a value of 1.
Martin
I'll try that tonight
-
- KVRist
- 441 posts since 30 Nov, 2002 from Sweden
Hi Martin!Kire wrote:Hi Martin!MadGav wrote:I've just been trying this out... to get an idea of what is fast enough please can you try making portamento using a Slew Limiter B module with Rate set to 1. This will be a bit faster than the CV Converter Glide set to 1, but is it enough faster to make a practical difference? (Needing more just makes the change a bit more work...)Kire wrote:in some situations there's a need for a bit more discrete portamento. In this clip you can hear the glide going up and down heavily with only a value of 1.
Martin
I'll try that tonight
I think it works fine as it is! No need to change this.
Would it be possible to have a modulation option for the detune-amount in the Multi-saw osc?
-
- KVRian
- Topic Starter
- 513 posts since 9 Nov, 2000
OK will extend the glide range to match 1 on the slew limiter.Kire wrote:I think it works fine as it is! No need to change this.
Would it be possible to have a modulation option for the detune-amount in the Multi-saw osc?
Adding detune modulation to the multi-saw osc should not be a problem.
Martin
-
- KVRian
- 507 posts since 15 Mar, 2002
would be great to see the glitch tempo pushed out to it can record more than 4 beats (8 would do, anything above would be a bonus).
also, pitch control on the glitch pitch would be good (the pitch of the recorded audio, not the frequency of the looping itself).
also, pitch control on the glitch pitch would be good (the pitch of the recorded audio, not the frequency of the looping itself).
come on you ..... lets have some aphex acid.
-
- KVRian
- Topic Starter
- 513 posts since 9 Nov, 2000
This is on my near-future list of things to look at, my first thought was "too RAM hungry", but there should be a reasonable trade-off possible.mojogigolo wrote:would be great to see the glitch tempo pushed out to it can record more than 4 beats (8 would do, anything above would be a bonus).
You mean dub delay kind of thing? Main limitation would be the the first period after the glitch is triggered is live audio so could not change speed...mojogigolo wrote:also, pitch control on the glitch pitch would be good (the pitch of the recorded audio, not the frequency of the looping itself).
Martin