Biset Tracker full walkthrough and tutorial

Plugins & Modules
1

Hi all!

This was requested by many people, so I thought I will publish this here also. I made a full walkthrough of the Tracker from Biset, going through all the features and how to use it.

Many people asked me also how it is compared to the hardware NerdSeq, and I think it’s a great introduction to the workflow. The NerdSeq is very very very deep, but if you’re interested in the NerdSeq, I highly recommend learning the Biset Tracker to see if you like the workflow.

Cheers!

36 Likes
2

Thanks Omri! Loved the tutorial. Saw the one from the developer and didn’t catch a mention of the „matrix“ part of the module in both videos.

Is this something still in development?

3

Thanks :slight_smile: Yeah, this is still not implemented…

4

The clip launcher is something i had overlooked, and its quite compelling for live performance. Thanks omri

1 Like
5

Cheers!

6

Hi Omri! Great walk-through. Is there ability to cut/copy/paste/move notes within the pattern?

7

unfortunately no :face_with_diagonal_mouth:

8

This is a terrific module. I’m hoping the the ability to cut/copy/paste/move, batch delete etc. will be added.

9

After the emerge of the Biset Tracker in the VCV library I thought there will be no need for another tracker, but …

… but I think it’s time to grab all that notes I made about a (perfect?) tracker module and maybe !!! start working on it :thinking:

3 Likes
10

I think the Bisset Tracker and his submodules are underestimated. But unfortunately it lacks important functions. I had contact with the developer, but he doesn’t want to develop the module any further.

11

I’m currently working on a complex sequencer myself, and I can imagine that they had had enough of it for a while once the module was finished :slight_smile:

2 Likes
12

nice module, I not saw all the video but seems like the workflow adequate for tracker users

13

I certainly understand that he’s had enough and doesn’t want to put any more time into it. However, it seems very close to being terrific. Cut, copy, paste would be a big workflow improvement.

14

I once foolishly made a sequencer (seq++) that is very complicated (at least inside). It took me an enormous amount of work, and was not nearly “worth it”.

I spent a huge amount of time making undo/redo work correctly, making it so you could safely edit while playing without priority inversion, making edits instantaneous even when tracks were huge, and writing hundreds of unit tests. After releasing it to general indifference I realized the obvious: only spend time making a module if you really want to do it - preferably to use it yourself.

Anyway, just an issue for any dev to resolve for themself. But I guess I’m not surprised that the majority of devs make some modules and then go away.

1 Like
15

That sounds like a very familiar scenario. I’ve spent the last 3.5 months developing my nearly finished TimeSeq module, refining features, writing unit tests, and documenting everything. But from the beginning, I knew it had one major hurdle: the user has to write a JSON script to run the sequencer, which I expect will narrow its potential audience considerably.

But I build it because I wanted that functionality in VCV Rack myself. And I very much enjoyed writing it and seeing that the concept I started out with actually works. So now I’m going to try and tackle my next hurdle: learning how actual audio processing works, instead of only building modules that operate on control CV and 1V/Oct signals :slight_smile:

2 Likes
16

btw, I just told someone on Facebook a) community bbs is better, b) someone is working on a sequencer that lets you trigger JSON (which I personally think is cool).

1 Like