Seems like this kind of better access to “fire triggers” might be beneficial with the upcoming pedal style looper unit you mentioned might be in development? 
1 Like
The answer to your question is Yes. It is in development. 
5 Likes
No way. I love having those options.
1 Like
Same. I would only vote for an additional One Shot sampler if it had useful, one-shot specific parameters like retrigger or voltage control over the current sample (The Digitakt is a great model for an efficient one-shot workflow). Even then, I like having the option of loop vs. once on the larger Sample Player.
The addition of the loop vs. once option was my favorite workflow improvement in 0.3 so far! There was previously too much friction if I wanted to add multiple drum hits to a project.
EDIT: Another really nice One Shot option would be velocity. It would only read the velocity upon a trigger and keep the sample at that amplitude until the next trigger. This would save a lot of patching and would lead to easy articulations without worrying about amplitude-jump discontinuities when S+Hing the output VCA.
3 Likes
Hah! First I’ve heard this one!
1 Like
Hi!
I love the new version, great work!
I don’t know if this has been suggested, but i love to have some kind of visual feedback to know if the state of the proyect (quicksave i mean) is saved or not, like a dot or a * somewhere in the screen. Maybe something like the eventide H9 or the beatstep pro. If you make a change, the screen shows a indication, when you save the new state the indication dissapear.
Sorry for my English, I hope it makes sense.
Greetings.
2 Likes
Hi Brian!
I’m frequently messing myself up with the button release triggering the unit’s menu item on the same key…
Then again… maybe its… 
3 Likes
I can confirm this issue
1 Like
And i am experiencing it also.
1 Like
How about a unit that measures the amplitude of a trigger so you can use it to control whatever you want? Pulse to Height? It would wait for a trigger, observe the maximum voltage peak during the trigger and then hold that value until the next trigger.
7 Likes
Very late to the party, but also much appreciation and gratitude from me - this is a fantastic update
3 Likes
I might be wrong but–from what I can tell–I think that will make things more complicated for sample amplitude articulation.
By introducing a Pulse to Height unit, there are a few complications:
- Most clock/gate/trigger sources output uniform timing signals, so you would need to use an additional VCA to add amplitude variation to that stream. This is more complicated than the current strategy
- A bottom threshold would need to be established. This is the voltage where the Pulse to Height unit would still detect a trigger, but it would be represented as 0 V. This makes setting up the Velocity CV more finicky.
- This Pulse to Height would still be used to then modulate a VCA after the sampler. This can cause clicks on simpler samples if the timing isn’t correct. If the sampler has reset interpolation (i.e. a crossfade to prevent retrigger clicks), the trigger and the velocity signal shouldn’t necessarily be sent at the same time. One workaround is to add yet another unit before the VCA: a slew limiter.
Here’s what I mean:
1 Like
Ive got the same issue
I think the time is ready for a window comparator unit 
1 Like
I’ve noticed that when grain stretch and Looper are sharing the same buffer, Grain Stretch doesn’t visually update it’s window. Though you can hear the changes which means it’s indeed following along nicely, visual feedback in Grain Stretch shows a waveform that is a momentary grab of the buffer.
I have used slice on grid in the Grain Stretch unit, so perhaps it has something to do with this ?
1 Like
Yes, I have noticed this behavior as well when sharing the same buffer across both units. If you “slice on onset” and are feeding the buffer with new material does the 301 keep scanning the incoming audio and readjust slices in realtime? Not sure if this is possible but would be really cool if it could 
1 Like
Preamps! Thank you Brian! 
7 Likes