It happened to me as well. My assumption is that the USB cable was providing power to things on the 5v rail and some things on your case were getting powered off your computer. I didn’t have any problems, everything seems to be working fine, so it is safe to assume that there shouldn’t be an issue on your system either.

1 Like

So when you say, “DEL.X will execute more than once”, does that mean:

DEL.X 3 100: TR.P 1
TR.P 2
TR.P 3

will send out three pulses to output 1 100ms apart, then a pulse to output 2 & then output 3? Or does the 2nd & 3rd delay get prepended to subsequent commands, and the above example would be equivalent to this code:

DEL 100: TR.P 1
DEL 100: TR.P 2
DEL 100: TR.P 3

?

DEL.X 3 100: TR.P 1 
TR.P 2
TR.P 3

Will send the following (now is the time the above code is called)
now: TR.P 2 and TR.P 3
now + 100ms: TR.P 1
now + 200ms: TR.P 1
now + 300ms: TR.P 1

2 Likes

20 characters of yes

1 Like

20 characters of thanks!

Interesting, I wondered about that, so TR.P 2 and 3 will actually run BEFORE the TR.P 1’s will. Good to know, that might explain why my attempt to use DEL 10: A IN to fix what appeared to be a gate/CV timing issue was doing some weird things…

So what do I do if I want to delay 10ms and not do ANY of the rest of the script until that delay has completed? The use of DEL 10: causes things to execute out of order, but what I want is simply to delay the entire script start for 10 ms to allow the IN CV value to settle before I grab it, and then everything else uses that value…

You could place it in another script and call that with delay. AFAIK there’s not OP for stopping/halting/sleeping/waiting in TT…

You seem to expect DEL to stop executing like time.sleep() in python, but in fact it places commands in the delay buffer/queue and continues immediately (like placing them in a new thread if you’re familiar with parallel programming)…

That’s what I was trying to clarify. The problem is, it seems kind of wasteful to have to create a one line script that just has:

DEL 10: SCRIPT 7

Just so you can insure that there is a delay between the initial trigger and its processing. It’s not uncommon for modules to have issues with the timing between a gate and the change in a CV, and I was seeing them without the delay so figure I need to stall the acquisition of the input CV. Problem is, every other part of the script is dependent on having that input CV so it all needs to be delayed, not just the first command.

I suppose another approach would be to push all the commands in the script on the S stack and then do:

DEL 10: S.ALL

Though that eats up the stack so you pretty much can’t use it for anything else.

Also, does this work and treat the whole line as one “command” that will be delayed in toto?

DEL 10: A IN; B + 1 B

??

Yep, those both work! To be real I have never used the stack but I think that is an excellent use for it.

Just wanted to come back and report that I’ve done this, but oddly, my max value is now 16383… I suppose that’s fine, but wonder if missing that final value will cause me a headache down the road.

At the moment, I’m not super-concerned about it, but has anyone else encountered this?

(Synopsis here to save anyone curious some scrolling: Calibrating PARAM value and I now have a range of 0-16383 instead of 0-16384. I was getting 0-16320 and used the command PARAM.CAL.MAX with the knob fully CW to increase it, but not fully.)

2 Likes

The full range is 0-16383 so you’re good.
If it went up to 16384 you would have 16385 possible values.

4 Likes

Yes, 16383 is the largest number you can store in 14 bits, which is undoubtedly the resolution of the A/D converter. 0-16383 is actually, 16384 unique values. Any more than that and it won’t fit in 14 bits.

2 Likes

Hello there! I think this is a very simple thing to do, but I am not getting it working.
I want a Kria CV to be written in, let’s say variable A, as a Note-number, not a Voltage. When I try:
A KR.CV 4 …then I just get a voltage.
I want to use this variable then to create chords with the N.S command, to let JF play chords, according to a root note from Kria… Arrrgh, Sorry, this seems to be so easy…!!!

A / KR.CV 4 N 1
(or A VN KR.CV 4 if you are on latest beta)

1 Like

thanks a lot, you saved my day. I will never ever forget this…

That makes so much sense. Thanks to you and @oscillateur for clarifying!

Sorry, it seemed to be so easy, but it is not. I know the code is right. But the thing that happens is that the variable is one semitone out of tune from the 2nd scale-note on. I’ve tried to figure out, what´s wrong. But I can’t find a reason, why this happens. When I store in parallel the value of my note in another variable, I get the exact value. Each semitone is a value of 136 apart, an octave is exactly the value of 1636. But when I try to transform it to Note with the calculation, a value of 272 should be a N 2, but I get a 1. And a value of 136 writes a 0 to the variable. What am I missing? Is this a known issue, do I have to offset every note-number above 0!? Would be great to hear from you, or anybody out there…

1 Like

Can you show us the bit of code that’s causing the problem? (Just wondering if you’re using the O variable which updates by one each time it’s accessed… probably not, but it might be easier to see the code just to be sure it’s not something tricksy like that :slight_smile: )

No O in the code. It is pretty easy, what I am doing. I want to store Kria-CV in a variable as a N-Value, to use it the to generate chords on JF with the N.S operator. The Scene looks very easy, it works to play the right scale when I do:
D KR.CV 4
JF.VOX 1 D V 8
…but this way I can not use it in the N.S operator to make chords out of one track of Kria, so I tried to store the value of my Kria CV in a variable as a N value with this command
D / KR.CV 4 N 1
JF.VOX 1 N D V 8
…but this works just for the root note, every tone above is one semitone to low. Thanks…

Some kind of off-by-one error. Do the KR.CV values go negative? That would be an issue, too.

Try
D + / KR.CV 4 N 1 1
or install the beta and try the VN OP (I would actually love some user feedback on that OP!).