Ok, thanks. @Galapagoose is that something we could hope for in the future?

Here’s the full list of JF 4.0 I2C commands which includes an offset for TIME but not RAMP. The RAMP et al knob positions (with CV value offset!) can be gotten but not set.

edit: on a re-read, my ex-catholic senses picked up on this nicene phrasing, ā€œbe gotten but not setā€ā€¦

1 Like

Thanks, that’s useful, I’ll have a look!

I’m not planning to add this to the module because I believe it breaks the what you see is what you get nature of the interface. If there’s a really interesting use case that this would enable I’d consider it, but in the near term, I’d suggest to just use a patch cable.

TIME has ii-control because it is an arbitrarily chosen range (ie the knob could meaningfully turn ā€˜beyond’ the limit of the physical knob). Having ii-control enables precise pitch setting / tuning (a common complaint due to no FINE control).

5 Likes

I’m sometimes experiencing hanging notes with just type (JF.MODE 1) and JF.NOTE. The mode rocker on the module is on ā€œtransientā€, the hanging notes fade out if I quickly switch to ā€œcycleā€ and back.

In this particular script I’m sending just friends two notes, with a short (1ms-100ms) delay in between, it didn’t happen in my previous script where I always had longer between notes.

Am I doing something wrong?

Let me know if there’s anything I can do to help!

1 Like

AFAIK this is a Thing That Happens

1 Like

I’m also having this issue when sending two notes to to the same voice with a short delay between the two

Aka a bug that would be nice to have fixed?

2 Likes

I didn’t know this happened in Transient mode… I thought people only experienced it in sustain, but knowing this gives me something to track down. Can’t promise a release asap, but it’s logged!

Can you make reliably hang with a certain delay time? Or is it always a ā€˜sometimes’ thing? If you can reliably reproduce, please post the script.

Also - are you all on Teletype, or is this on crow too?

To confirm, @ilikeorangethecolour is using JF.VOX and @a773 is using JF.NOTE both with the same issue occurring? In the JF.VOX case, after a voice has ā€˜hung’ do further messages release the envelope, or does it stay stuck open, but changes the note? Or is it just ignored altogether until released?

1 Like

Hey @Galapagoose

I’m just looking back at my Teletype script from yesterday. I was just able to reproduce it again, however this time without delay, I can keep experimenting to see if I can reproduce the behaviour again with delay.

Script 1

JF.VOX 1 V 0 V 5

Scipt 2

JF.VOX 1 V 1 V 5

If I trigger both scripts at the same time, script 2 takes precident over script 1, and the note will hang indefinitely until another trigger is received on either script. I’m not sure if this is what is supposed to happen or if it isn’t expected behaviour.

Let me know if this helps. Thank you

1 Like

I did also notice some idiosyncracies with hanging notes from JF.VOX using Teletype with transient mode. Nothing that didn’t sound musical, and it was the result of jamming tons of delayed metro copies through and lots of internal variables… But did seem to be related to triggers getting jammed close together. For what it’s worth.

It was my intention to affirm your experience, not dismiss your concern.

@Galapagoose I experience this issue with both JF.NOTE and JF.VOX. New messages clear hung notes as the new notes sound. I’m on TT. Tend to experience this when consecutive notes are within ~150 MS or less of each other. Issue is much less common since 4.0 (something about the language of this release made me think of it as a known issue).

1 Like