Hi Andras,
I started thinking about this. One issue is that there are 16 sample slots. I’m wondering how this might be accomplished, and here’s one strategy:
However, I’m not sure if that’s really any better than the current sample selection process? Any ideas?
I realize that “hidden” features aren’t ideal, so tonight I added a context menu to AutobreakStudio which gives you another way of shifting the sequences left or right:
This will go live with the next update.
Also, here’s some fun… did you know that you can change the sequence lengths by holding the CTRL key while dragging on any sequencer?
It does indeed, Perfection 
Just give it a try with NYSTHI MusicalBox2. I think it feels so intuitive, comfortable, and quick to use.
I also believe that once the code is optimized in Sampler16P it could be a great addition to your more complex modules (Autobreak Studio, SamplerX8, Groovebox, etc.)
The context menu could look like this
Load individual samples
Sample slot 1>
Load new sample
Replace from folder >
SNARE1.WAV
SNARE2.WAV
SNARE3.WAV
SNARE4.WAV
SNARE5.WAV
SNARE6.WAV
Sample slot 2>
Load new sample
Replace from folder >
BD_AC.WAV
BD_ELECTRO.WAV
DB_SAMBA.WAV
SHAKER.WAV
CUICA1.WAV
CUICA2.WAV
Just for reference the Sampler16P menu looks something like this at the moment:
Load individual samples
1: SNARE3.WAV
2: SHAKER.WAV
3: [EMPTY]
4: [EMPTY]
Thanks for thinking this through! I think it’s worth a shot, and I’ll code up a prototype soon. 
Hi @FiroLFO,
I gave it a try using MusicalBox2, but I don’t think that I’m going to take that approach. Here’s why:
MusicalBox2 takes 3 clicks to load a sample: 1) Right click to open context menu, 2) Select CURRENT SAMPLES, 3) Select sample.
With the menu that you propose, it would take 4 clicks to load a sample. 1) Right click to open context menu, 2) Click on Sample Slot, 3) Click on Replace from folder, 4) Click on sample
With the current implementation, it takes 3 clicks to load a sample. Well, technically two clicks and a double-click: 1) Right click to open context menu, 2) Click on Sample Slot, 3) Double click on sample.
With MusicalBox2, if there are a LOT of samples, it’s really tedious to scroll through them. At least on Windows, there is no scroll bar for menu items. You can use the scroll wheel, but it take multiple “scrolls” to get through a large list of samples. Of course, the OS’s file selection dialog box provides scroll bars, plus search capabilities.
In my humble opinion, is not a big enough improvement to change. Thanks for keeping the ideas rolling, and I’m sorry if I sometimes decide to not implement them. 
I’m glad you took the time and checked that out! And thanks for considering!
Maybe this has been asked before and I missed it; but I’ve always been curious about why you don’t implement drag and drop of samples? I know that NYSTHI Simpliciter has this feature.
I went with 2.21.2 as it does not hang the module browser.
EDIT: git checkout tags/2.21.2 && make && make dist
EDIT2: you might need a git fetch --all --tags as suggested by some sources.
EDIT3: Not a fan of these warnings.
I’m not a fan of those scary warnings either, but there’s not much we can do about it – they are in the VCV Rack code.
I didn’t know that drag-and-drop samples was even possible! I’ll research it when I have time.
I also don’t know why the modules aren’t loading. However, I suspect it has something to do with file paths in linux, or unicode support.
I had a user report a similar issue before who reinstalled essentially their entire operating system, which fixed the problem. Obviously, this isn’t a great solution. See: Background JPG not loading - suggestions for troubleshooting? (was: file::exists false). Unfortunately, I never figured out how to solve this. I’d love some support from VCV Rack, if possible!
Thanks,
Bret
Yeah, me either! As @cosinekitty mentioned, these are triggered by VCV Rack. My arrays aren’t out of bounds (I’m 99% sure?), and I’m not really sure why VCV Rack is throwing warnings for this? It happens to me too. I’m totally open minded if anyone wants to peek at my code and point out any shortcomings. I’m not always right, and I appreciate people’s thoughts on my code!!
Can you wright what do I need to do step by step?
If you have built rack. I’m not sure where the SDK directory for your plugins is. I’m not sure if you have build-essentials and git installed.
cd ~/Rack/plugins
git clone git@github.com:clone45/voxglitch.git
cd voxglitch
git fetch --all --tags
git checkout tags/2.21.2
make
make dist
The plugin will be in voxglitch/dist.
Wait, is this Linux? Can I install previous version of plugin without it? Sorry I’m new to all this
It works for me as a developer. For the library, the plugin developer has to fix and submit to the library build pipeline. It then becomes an updated version a few days later. I’m running lin-arm64 so no library for me yet as it is experimental and I only get what I build myself.
Hi everyone!
However, I’m happy to announce a new upcoming module: “Drum Randomizer”.
Here’s an attempt to describe it:
Imagine that you have a 16 step drum pattern. Maybe you’ve used the Imprompu GATE-SEQ-64 to sequence this pattern. It’s great, but you want to add some variation to it. Specifically, you want some of the beats to play based on a percentage. Maybe, for example, you want a gate at step #3 to play only 50% of the time.
Drum Randomizer to the rescue!
The drum randomizer assumes a pattern length of 16 steps. (This might be configurable in the future.) Each of the 16 steps can be assigned a percentage chance of passing through to the output. It’s multi-channel, so you can use it to modify multiple incoming patterns (up to 16) and the output is also multi-channel.
I’m fairly close to finishing it. It shouldn’t take much longer! I know that there are a number of requests still in my queue. The Drum Randomizer is something that I personally wanted, so it got promoted to the top of my list. Ha ha ha.
PS: I’m still job hunting, which isn’t going very well, which is why I haven’t been more active. If you know of any openings for an engineering manager, please let me know!
Randomizing is life. Can’t wait!!
Why did you pick the Gate-seq-64 as an example, because this is one of the few gate sequencers that already has this function build in ? 
When activating a given step by clicking it once, it will turn green showing that the step is on. Clicking the “p” button turns it yellow, and the main display shows the probability associated with this step. While the probability remains shown, the probability can be adjusted with the main knob, in 0.02 increments, between 0 and 1. When a yellow step is selected, clicking the “p” button again will turn it off.
