DanT: Time Lord

Plugins & Modules
22

The above visual fixes, plus improved set time & time limit are included in this new beta

1 Like
24

Yeah oops

25

So I guess you solved your own issue? Is there something that was not clear about the module, or any way I can make an improvement?

1 Like
26

To bad there wasn’t a video in the help file, I am doing alot of guessing with this… I managed to test this out and so far it looks like I can keep a gate open for a certain amount of time or I can use triggers in entrian to turn the gate off and on depending on what I am using. I am trying to send very long gates to perx vst and so far it looks like it is going to work fine.

27

Can you elaborate on these guesses at all so that i know what needs a better explanation?

1 Like
28

Seems that most of the gates do not work always on or off but it did enough for me to use it… I uploaded what I did to patch storage. I wasn’t able to do anything with the timers except look at them to see how long the gate was open and I don’t rule out there is a better module for me to use for this purpose.

29

I think there is some sort of bug in the time part of it but I can probably get it to work. My front end for perx seems to work great so it is amazing for what I am doing. I will see if I can get an example of the time thing up… Most people are likely not to have perx but I have the front end for it using your plugin free on patreon (for free members)

https://www.patreon.com/posts/vcv-front-end-134991277?utm_medium=clipboard_copy&utm_source=copyLink&utm_campaign=postshare_creator&utm_content=join_link

30

It is not obvious to me from either the patchstorage or the patreon, what your goal is.

Are you trying to send gates generated in VCV to Perx?

If you just need to convert triggers into gates, then there are more appropriate modules that are available.

Perx looks like a drum VST, if so, then perhaps a drum sequencer is what you need?

The purpose of Time Lord is to generate gates that start at a specific time and have a specific length.

From what you have said, it seems like you are not using it in this way…?

I apologise that Time Lord does not have a proper manual, the first post of this thread does have instructions for use though.

The basic user flow is like this:

  • Activate the number of channels you want
  • Optionally save the channel state (so that you can reset and start again without needing to re-activate the channels)
  • Set the start time and length of each active channel (optionally turn on repeating)
  • Send a trigger to the Run trigger input or click the Run button to start the timer
  • Now the module is running:
    • All channels will output an inverse gate initially
    • When the timer reaches a channel start time, that channel will become active
    • Active channels will output a gate, the inverse gate will stop
    • When an active channels length has elapsed (timer >= start time + length) the channel will be deactivated, the gate will end and the inverse gate will start
    • There will also be triggers output when the timer hits the start and length times
    • There is also a gate output while the timer is running, and a trigger output when the timer stops

Does this help at all?

If you describe what you are trying to achieve, then it will be easier for us to help you do that, either with Time Lord, or other modules.

1 Like
31

It seems like if I am trying to run a gate for a particular length of time that I need to have something hooked up underneath the timed gate in order to get it to work. I assume that is a bug… The drum machine I am using outputs a loop so using your module to turn the gate on and off seemed to work great but has alot of extra stuff to look at on the screen. Normally for just a normal one hit drum there is no reason to turn the gate on for extended periods of time.

32

I’m sorry but I don’t understand what you are trying to describe.

Here is a screenshot that shows how to create a gate in the simplest way:

Screenshot 2025-08-01 103647
Screenshot 2025-08-01 1036471243×884 136 KB

  • A: this is the run button, the green light means the timer is running
  • B: this is channel 1 and it is active, it has a white light
  • C: the start time of the channel is set to 10 seconds
  • D: the length of the channel is also set to 10 seconds
  • E: this is the channel 1 gate output

First I activate channel 1, then i set the start time and length.

Next I patch the gate output.

Now I press the Run button.

The timer starts to count up. When the timer gets to 10 seconds the gate turns on, when timer gets to 20 seconds (10 seconds after the start) the gate turns off.

There are two, lets call them “quirks”, that the module has which you might be encountering:

  • If the start time of a channel is 00:00:00 then the gate will never turn on.

    • This is not a bug, the timer starts at 00:00:00, so the first opportunity for a channel to activate is therefore 00:00:01

  • If the channel is in repeat mode and the length is greater than the start time, the channel will never turn off

    • This is also not a bug, in repeat mode, the gate will still be turned on when the timer reaches multiples of the start time, therefore the gate will remain on and the length will start counting from 0
33

I was doing something strange where I was connecting to 2 and then the gate at 1 started to work but maybe that is a feature and I need to look at that again and go by this picture.