#42

I was getting crashes in synth mode with these commands:

JF.VOX 1 N 3 V 5

JF.VOX 2 N RRAND 1 12 V 5

they were being triggered via an ansible. worked fine so long as i did not touch the knobs at slow clock rates but as i sped it up it would crash. Also I was putting the JF into synth mode in live mode on the TT.

#44

synth mode:
seems no matter the triggering/note assignment situation,
a few minutes of delicious turning of any combination of knobs will start to crackle the sound and ultimately crash JF.
hard to pinpoint exacts at this point.
*
JF crashes instantly upon entering synth mode
like one out of ten times,
with various knob set positions and nothing else going on
*
occasionally flipping sustain to cycle in synth mode crashes
*
wild CURVE turning usually causes at least crackling
*
powering up teletype with scene initialized to synth mode
and a script trigger pre-attached always crashes,
sometimes before TT visibly turns on

1 Like
#45

I encountered all of the above problems with frequent crashes moments after JF.MODE 1.

Having JF.MODE 1 in an init script when tt boots is particularly problematic because when JF locked up it often causes the next JF command from TT to cause TT to lockup.

When entering synth mode (interactively) I seemed to get repeating phantom triggers at a rate dependent on the TIME knob even when nothing was patched in on the front TR jacks nor anything being sent from TT.

…at one point I did get the synth MODE running for a bit (still with the phantom triggers) and got really excited by the range of sounds one could get across a single voice!

…in normal mode (JF.MODE 0) with shape and transient selected I’m seeing 6N triggered for no apparent reason.

Time at 8s
Intone at 12:00
Ramp at 9:00
FM at 12:00
Curve at 9:00

…no triggers connected

On the TT

1 JF.TR 1 1

2 JF.TR 2 1

3 JF.VTR 3 V RRAND 1 8

4 JF.TR RRAND 1 4 1
JF.SHIFT V RRAND 1 3

…with the TT being triggered via ansible cycles (unsynced and fairly slow, once per second at most)

2 Likes
#46

That is definitely a Teletype bug too. It might be worth looking a bit deeper into it to see what causes the Teletype to lock up and try to defend against it.

1 Like
#47

I suppose this is something that happens also when Earthsea locks up so it indeed seems to be TT related too.

#48

In rhythmic envelope mode the number of repeated envelopes is different depending on whether the voice was triggered digitally or via the TRIGGERS jack.

select shape mode
select transient

live
JF.MODE 1
JF.QT 8

script
1: JF.TICK 8 (sent repeatedly via TT)

live
JF.VOX 1 8 0 ===> produces one envelope (expected)

TRIGGER IN (identity) ===> produces two envelopes (not expected)

JF.VOX 1 8 3 ====> produces four envelopes (expected)

TRIGGER IN (identity) ===> produces five envelopes (not expected)

Basically when triggered via TT one gets “repeats + 1” envelopes as documented but “repeats + 2” if triggered via the via the model trigger inputs.

1 Like
#49

…I’m also not sure that JF.TICK with values in the BPM range is working but then this could be pilot error on my part.

What I was expecting was that if say JF.TICK 120 was issued then any automatic re-trigger would fire at 120 BPM rate (without having to send a stream of JT.TICK 1 commands at 120 BPM from TT). What seems to be the case is that regardless of what value I pass to JF.TICK in the 49-255 range the triggers repeat at an extremely fast rate (not visible via the output LEDs on JF, only via a scope)

Setup:

shape selected
transient selected

intone at 12:00
ramp at 10:00
fm at 12:00
curve at 1:00
time at minimum (fully clockwise)

live on TT
JF.MODE 1
JF.QT 8 (this seems to have no effect)
JF.TICK 60
JF.VOX 1 4 2 (has the side effect of setting repeat for direct TRIGGERS)

jf-vox-1-4-2.jpg806×605 215 KB

live on TT
JF.TICK (any bpm) doesn’t change the rate at which the triggers automatically repeat

…but if one changes the DIVISIONS value passed to JF.VOX one does see that it has an effect in that if one doubles the DIVISIONS value it doubles the rate of the re-trigger (which is the opposite of what I might have expected, I would have expected it to half the re-trigger rate, i.e. divisions controls the number of ticks counted before a re-trigger).

live on TT
JF.VOX 1 8 2 (still using repeated direct TRIGGERS)

jf-vox-1-8-2.jpg806×605 219 KB

(sorry for the bad scope pictures, I didn’t have a USB drive small enough to use with the scope).

#50

I see now re-reading the just-type docs that this is the intended behavior for DIVISIONS (the doubling of rate when doubling the divisions) so I guess the JF.TICK in bpm range is the only thing which doesn’t appear to be working.

#51

Finally got this set up last night and encountered the same bugs as everyone else. Came here and I see that everyone is seeing the same stuff. What I did hear, though, only made me extra excited to see this firmware move forward. Thanks for your awesome work!

A question: because it’s a digital module, will it be emitting set frequencies in synth mode without the ability to tune the oscillators using the pots? It was hard to tell last night because my fiddling would glitch out the module and I’d have to hard reset. Not having to tune it would actually be a welcome thing, though, for squares like me who tend to use western scales.

What will be the lowest and highest notes it will emit, though? The range I was getting seemed to start more in lower middle-of-the-piano territory. Will thar be b-a-s-s?

#52

Finally expect to have some time to dig in this week. :sunny:

A few questions, regarding stability:

  1. Am I right that the stability issues only crop up when integrating with TT? That is, JF solo is unchanged?
  2. Is synth mode stable enough to be playable/productive? Any further reports/workarounds from the field?

And regarding integration, am I right that this will play nice with the TT update for ansible-1.3.0?

1 Like
#53
  1. seems so
  2. not exactly productive, but fun
  3. yes
1 Like
#54

This is mostly right.

Under the hood the whole DSP loop has been re-written but the net-result should be identical (much attention was paid to this!). A couple tiny bugs have been fixed, and the through-zero FM behaviour has been modified (TZ is only available in cycle mode now, due to inconsolable philosophical problems eg “what happens before an envelope?”).

4 Likes
#55

Great to hear!

It looks like a bunch of issues are known so I’ll probably refrain from gratuitous reports. If there’s anything you do want tested, let me know.

Cheers @altoaiello!

#56

I doubt any report is gratuitous at this point, especially specific, reproducible glitches!

#57

tbh there’s probably not a lot to gain from trying to use the firmware at present. I’ve since spent a lot of time working on optimizing the DSP code to avoid the crashes in 2 ways:
1- Not running out of audio-loop time by optimizing the processing.
2- Making the loop ‘gracefully’ skip frames when it does indeed run out of time.

It’s the lack of the 2nd point above that is causing the existing crashes which unfortunately occur too frequently for this to be truly useful as an instrument rn.

Hoping to have some time to work on it over the next week, but neck deep in a new project which has derailed 100% of my energy.

9 Likes
#58

i just wanna send positive waves your way and say i love you trent

continually amazed by what you’ve done
keep at it mate

6 Likes
#59

Thanks for the candor. I’ll hold off for the next rev. Good luck with the new project!

1 Like
#60

New project? :slight_smile: :slight_smile: :slight_smile:

1 Like
#61

And you just play a Bach cello suite in to revert?

#62

"…due to inconsolable philosophical problems eg “what happens before an envelope?” "

Can I just say I’ve had this phrase stuck in my head?

<3

4 Likes