The section called "sample length" (I labeled it at 48:44 seconds) is where the sample length is input. I set that with the "coarse" and "fine" knob, whenever entering in a new sample. I have the sample divided into 32 segments that each has 64 slices. I'll get to setting that up in one of the following videos. If you did want to have a knob to change between different sample lengths (for example, if you want to use a multisample with various clips, determined by the Select knob), then you could have a knob going into a merge (set to nearest), connected to a modulator, that is assigned to the coarse and fine knobs of the main sample length. That way you could set up several snapshots of different sample lengths. Then you could have the knob that controls that merge, also control the select knob. That is not how I set mine up, because I like to be able to see all my segments on 1 clip, and not have to open the multisample editor. But either way would work. I could show a method for doing that in one of the following videos.

@@user-uo5dq4ov7i thanks! I just now realized the value readout there is the length of the sample :) works perfectly when I set it

Hi, it sounds like "loop start" and "play start" on the sampler aren't assigned correctly. In this video, I show how to assign those to the keyboard at around. 35 minutes in. That is for beat division slicing. I start showing manual slicing in the next video.

Thanks a lot. I'll be probably covering a couple other methods for getting manual slicing to work in the next video. Especially, since there was an issue that came up at the end with the timing. I might just switch the main playing slice to be receiving directly from the outer patch, instead of from the scanned values. Sometimes that method can cause problems. But, I find it to generally be a useful technique. It just requires a bit of troubleshooting. Either way, I hope that people will find it useful to see the troubleshooting process that goes with experimenting with different methods. If I put it at 2.4 khz, that might have been on accident. In my patch, I either had it running at 24k or 32k. It doesn't really matter. It just needs to be fast. Anyway, I will probably record the next video this weekend.

If you mean, something like rewire, Bitwig doesn't support it. You could send an audio stream directly to Ableton by creating a virtual bus. On WIndows, there are 3rd party programs that can set that up, like VB cable (which is free). On Mac, you can create a virtual device in "audio midi settings"

I've been really wanting to. I need to learn c++ though.

@@AndreiOlenev i was about to say the same thing man, you are a magician. Just hire someone for the coding or just sell in a good vst idè to someone that can code and make it together

I didn't notice that. The setup in this video is a little different than what I used. The split modules that send to the mix on the parseq8 modules, might be out of sync. One thing you could do, is instead of using the split module, you could make a logic setup, where you run off the signal that is controlling each of the parseq's phase modulation, and say that "if that signal is equal or greater to 0, and less than one", than plug those into the modulators that control the mix. That way, the mix will be exactly tied to the phase of each modulator. Anyway, I saved the project in the video, so When I follow it up, I'll troubleshoot issues that might have happened in the first one. But, off the top of my head, the only thing I can think of is that the split module is out of sync with the rest. So, for now, that logic setup would fix it. Thanks for letting me know.

Also, in case, my description of that logic setup is confusing. Take the individual signals that are going into each of the modulators that control the phase of the parseq8s. There will be 3 separate logic setups for each. The setup looks like this: The signal runs into the top input of a "greater or equal to" module, with a constant of 0 plugged into the bottom input. Then also plug the signal into the top input of a "less than" module, and plug a 1 into the bottom input. Then plug both of those logic modules into an "and" module. Then, connect that to the modulator that controls the mix of that parseq8. Repeat for the other 2.

@@user-uo5dq4ov7i thanks for your response and explanation. I was able to get it flowing correctly but had to use a less than or equal rather then just "less than" connected to the 1 constant. for all 3 of them and for the 2nd and 3rd one, had to use a greater than 0 rather than great or equal to 0. looking forward to your next video on this, cheers!

@@stephenredding31 Cool. Glad it worked out. I'll look into what went wrong with the split module. I probably should have tested everything before ending the video. But, issues like that arise all the time, so I'm hoping in these videos that if people see the process of things like this going wrong, and troubleshooting them, that it can be helpful.

@@AndreiOlenev It was helpful for sure!

This is the most recent video I did on stutter effects. It is pretty much the same one as in this video kzfaq.info/get/bejne/pcl1opp_0J2ufps.html

If you have your transport controlling a split module, then you can run your transport into a scaler at 8/1, and run that into the split module. Connect the 8 data modules to the split module, and connect them to a merge, that is controlled by the transport. I show that in this video.

Ah amazing I’ve been scratching my head on doing this for a while for my own weird sequencers thank you. Apologies for not watching the whole thing first 😅

@@WavejumperUK Thanks. I like running sequencers like that, mostly for the visual aspect, because it makes it easier to see how many beats/bars have played.

I just started recording tutorial videos again. I took a pretty long break from it. I'm going to be uploading a handful in the coming weeks. I haven't recorded pt2 to the graincloud yet, because, I'm reworking the patch, to change some of the features.

I hear you. My plans get very scattered. This has been a long ongoing project. Every time, I think it's done, I start using it, and end up going down a rabbit hole reworking it. I'm close to done with a new album too. Once I finish it, I want to get back into tutorials, and finally do a pack of devices. I want to do more general tutorials as well, not just focusing on The Grid.

@@AndreiOlenev Great, but please if you do so, try to start from scratch as it's almost impossible to follow when you show already fininished grids, that would be very very helpful, thank you !

@@artakan303 Thanks for the advice. I was thinking to make a series that explores different techniques for for building projects like this in the Grid. through the process of making this patch, I've tried many different methods. Each has their pros and cons. And depending on what somebody is trying to build, some methods would be better than others. I was thinking that might help better for people who have different types of slicers/glitchers they want to make, instead of just building an exact copy of my slicer patch. I think it would be cool to see what types of patches people come up with using the techniques I've been exploring, because they might go in very different directions than I do, and make devices that I wouldn't have thought of. I think to start with though, I should show the most basic ways of getting start/ loop times, and envelope hold time (to stop slices before the loop point). Those are the first challenges in making slicers.

@@AndreiOlenev great, yeah the goal is not to copy/paste but to understand what is going on ... I tried a bit with your previous video, and yeah the real fun starts when you get what you're doing and start experimenting.... So please restart with the basics ... many thanks and looking forward to it !

Dr. Soon already went public.

I plan on putting together a pack of Grid patches soon. The patch in this video has been an ongoing project, for about a year. I have a bunch of different versions of it. I will probably end up rebuilding it to make a more simplified version for the pack. I'm in the middle of finishing up an album though. When I'm done, I will switch gears, and start organizing some of my Grid patches into a pack, as well as getting back into making tutorial videos. For this patch, I have tried many different ways of setting it up to get a mix of the features I want, with reasonable CPU usage. I think I've finally gotten the down a method that works really well. The first pack will be a handful of devices geared towards glitch/idm production.

@@AndreiOlenev Looking forward to ;)