How do I single step the seq with an external trigger?

[tapiocatwilight]

Running v2.0 C, only a midi I/O attached but nothing connected to it.

I want to advance the sequencer a single step using an external trigger, hopefully using Clock IN.
I tried sending single pulses to the clock inout jack, setting Clock IN to MOD.CLOCK, but it doesn't work right.

When I send a trigger to Clock IN, it steps once, but the next pulse advances two steps,
One step, then two, one, then two... consistantly. 
I tested with several trigger sources and it always does this on the leading edge of the trigger.
There's a little delay between the steps when it does the two step, it's not immediate.

What's the simple way to do this? I don't want to use a midi clock, 
a divide by 24 counter, or something in the sequence definition,
just a simple single step trigger.
Do need to change something else in a default new project?

[XORadmin]

It doesn’t work like this as with every clock it calculates a possible BPM, does internal a multiplication as the internal clock runs faster then only every clock signal. That is possibly why you get some side-effects in your situation (and possibly also if the calculations result in lower than 1 BPM which is rounded to 1 BPM)

You could use an external trigger on the cv in for example to clock a single (or multiple) tracks.

[tapiocatwilight]

"You could use an external trigger on the cv in for example to clock a single (or multiple) tracks."

So much of the manual is written like this. Thousands of possibilities and mentions of features,
but with no examples or explanation of how to use them.

This device has been so difficult get a handle on. I have to go up and down and back and forth in the documentation and menus
to hunt down how to use a feature because they're mentioned once in dense paragraphs that read more like a set of capabilities.
It's missing the next layer on top of what you've written, which is a waste if your time and effort adding features if only you know how to use them.

I appreciate the assembly language mind, and it's clear to you because you wrote and designed it all.
That isn't us. And "take it of leave it if you don't understand all I've done here." hurts.

If I had an ethernet port but needed to learn the hardware registers and write tcp/ip every time I want to send some packets. 
Flexible yes, but always tedious finding out how.

Please add documentation that says "Here's how to do this". Succinct examples, in short, standalone paragraphs.
Get a technical writer to work with you. 

It may be the world's best feature-packed table saw, but we have furniture to make. And we've lost more than a few fingers so far.

--

[XORadmin]

"You could use an external trigger on the cv in for example to clock a single (or multiple) tracks."

So much of the manual is written like this. Thousands of possibilities and mentions of features,
but with no examples or explanation of how to use them.

I pointed you only to another possibility which might get you to the result you want to have without knowing if it would be a possible solution for you. So why should I get into detail for that if it is possibly not what you want.
If I would put examples to any function of the NerdSEQ into the manual then the amount of manual pages would easily double plus real examples definitely need also audio. 
Even now it has so many pages and only a few people do read them.

I appreciate the assembly language mind, and it's clear to you because you wrote and designed it all.
That isn't us. And "take it of leave it if you don't understand all I've done here." hurts.

I guess you talk about the mapping features here?
The simple mapping of a source to a destination is fairly simple, well explained with examples and does not need any knowledge of algorithms or programming at all. This is usable for most of the users and has been requested many times (mapping of External sources to internal parameters).
The additional features here including that you could also use it to manipulate your data and create algorithms is a special thing and indeed not for everyone. I can't explain you how to program/code or create algorithms. I do explain in the manual basically how to use it and added examples here where I explain what the several rows are doing. That is a growing process and hopefully more people create maps and share them. And if someone wants to have a feature which is not available in the NerdSEQ, maybe someone can create it with a map instead...
The way how it is implemented is so it can work together with the simple mapping but still is very flexible and uses as little ressources as possible.

You know that I try to help where I can and try to explain what is possible and what not. And in your case I think I explained why your situation does not work as you intended and gave a tip that something else might be possible.

Get a technical writer to work with you. 

And who is paying for the technical writer? I had discussions with multiple people in the past who claimed that it was so bad and unlogical and that it should be better and none of them ever had good ideas for a redesign, different layout or topic combinations.

It may be the world's best feature-packed table saw, but we have furniture to make. And we've lost more than a few fingers so far.

Luckily no one loses any fingers here and they are many people who do create great furniture with it.

I am continuosly busy to get things better to improve the manual, to finetune the workflow and so on. And I am always happy to receive good constructive ideas which are worked out well.

So if you need any help or an explanation about my tip for the clock input per track in the first place, then let me know and I am happy to point you to the good direction.

[kilgore]

I wanted to briefly ressurect this thread to add some more information. I was also interested in using an arbitrarily timed trigger to advance the sequencer one step at a time. I asked over in the discord, and apparently this is now possible!

As Thomas wrote over on Discord:

"Meanwhile there is a function where you can do tht, progressing a step by an external trigger. This can be done per track, so you set a track to be "clocked" externally. It is not for all the tracks but the individual tracks but can set that up for each track. There are things to know, the sequencer must still be running as this also relies on the main clock. And it is not only a parameter you turn on but you set it up and got to involve the mappings."

Super excited that this is now possible. I haven't tried it out yet but I'm currently trying to set it up. I will report back here once I've got something working.

[XORadmin]

I wanted to briefly ressurect this thread to add some more information. I was also interested in using an arbitrarily timed trigger to advance the sequencer one step at a time. I asked over in the discord, and apparently this is now possible!

As Thomas wrote over on Discord:

"Meanwhile there is a function where you can do tht, progressing a step by an external trigger. This can be done per track, so you set a track to be "clocked" externally. It is not for all the tracks but the individual tracks but can set that up for each track. There are things to know, the sequencer must still be running as this also relies on the main clock. And it is not only a parameter you turn on but you set it up and got to involve the mappings."

Super excited that this is now possible. I haven't tried it out yet but I'm currently trying to set it up. I will report back here once I've got something working.

https://forum.xor.eu/showthread.php?tid=...3#pid10603

[kilgore]

Thanks again for the help Thomas! The other thread indeed had the answer, but I will post it here as it might make searching for this information easier for others.

As written above, it needs to be sorted using the MAPPING screen. Make sure your tracks clock is set to MAPPING (which you do in the Track Setup). In my case I'm using Track 1 and have the Clock set to MAPPING.

Then in the mapping screen, you need these two lines:

Code:

00 CV       IN 1
01 CALC     PASS     00=6  >  TRCK      TRK1      TICK

I had orginally tried this just mapping CV IN1 to CLOCK (doesn't work). Then I tried mapping it straight to TICK but this was also not quite right (because the trigger voltage was being interpreted as TICKs and it wasn't possible to find a voltage that would reliably send the right number of ticks).

Some how the CALC code is still voodoo to me, but it works! As Thomas writes:

This generates 6 ticks if the CV input changes from zero to any value. This works if the CV signal is clean and the CV input is calibrated properly.

Super excited about this! Such an amazing module!!