#44

I was having a difficult time myself. Tried it with my iphone, no signal registering at max volume. Tried it in Logic, no dice again, trouble getting the sampling rate correct and volume issues. It finally worked routing Ableton through my ES-9 with the volume turned down to -30db. Hope you’re able to find the winning combo with the gear that you have.

1 Like
#45

I can’t get mine to get to bootloader mode at the moment. Followed the instructions to the letter, but when I turn my case on all the outputs are dancing away like normal, no slow pulse on 6n. Hmm…

edit - I managed to resolve this by turning the case on once set to shape and cycle, turning off again, and resetting shape to sound. The same with both my JFs. Had no issues updating whilst playing back the update from Live at 3/4 volume, with a patch cable from the headphone jack of a laptop

#46

Did you turn all the knobs fully counterclockwise?

That was one I nearly missed!

1 Like
#47

I’m not sure what it was! I managed to persuade it to get to bootloader anyway

#48

My identity light is on before I send any audio to the run jack, (as soon as I turn on the case) Is this right?

#49

I had this, and it updated fine for me.

2 Likes
#50

I’ve just updated this beloved module. But there is some strange behaviour every there and then. When starting the system, and not playing it for half an hour, to warm up some analog VCO’s, it freezes. Or hanging notes, that just a command from teletype can stop…I have this experience with sending notes from ansible via iibus, and also teletype is on the playground. Am I doing something wrong, or are there others with the same experiences and solutions?

2 Likes
#51

Now that you mention it: I have not used my JF 4.0 much but I am getting many failures to boot up. It is on a bus with Teletype and F8R so I thought it was a I2C issue, but the timing is suspicious. I have not used any I2C commands for it yet since the update. About 50% of the time it does not boot, and I’m also unable up read F8R over I2C, so maybe it is holding the bus.

#52

At least, now I’ve got a much smoother working performance with JF and everything on the ii-bus. I just figured out, that it is not such a good idea, for example to send notes and triggers to a follower by both leaders, JF and TT. With the decision, to take only Ansible´s trigs and notes on the bus, and doing the trigs and notes from TT´s analog outputs, it works much smoother. …some hanging notes after stopping the system, but no freezing at all…

#53

Ah, yes, my worst I2C stability was when running with multiple leaders. JF and the Telex modules are particularly sensitive to I2C bus confusion.

I will have to dig deeper into my current issues and see if they are linked to I2C. I think not, since I haven’t been using I2C commands at all!

#54

I’m happy to take a look at any of these bus concerns if there is an issue only involving Ansible, Teletype, Crow, W/ and/or Just Friends. I don’t know enough about the other devices to be able to reasonably debug systems including them. So if you have a reproducable error state, please post a video & any scripts required to show the error.

#55

I’ve also had issues also since updating Just Friends effecting boot up . I can’t really pin down though, since I upgraded Crow and w/ also at the same time. It could also be an Ansible issue. I’ve since removed the 2nd JF and er301 from the bus.

#56

Any other tips for getting Just Friends into bootloader? I’ve tried every which way and cannot seem to get 6n to pulse on startup. All of the lights just stay off and the module is unresponsive to any flicks of the switches or turns on the encoders, until restarted with no cable in RUN.

Thanks in advance!

Edit: Nevermind - I’ve always had some weird things happen with my Rackbrute cases so I tried with a different power source and worked like a dream.

#57

I’ve had this happen with a Pittsburgh 208 case.

#58

Quick question @Galapagoose or somebody fast and certain aboutit, i need to verify that silver clouded v1 JF will work just fine and without limitations by itself and via i2c with crow - norns?

Or hands off?

#59

I have a silver version in my i2c setup. Works the same as a gold version.

2 Likes
#60

I was wondering if in the crow - jf - synthesis integration there was a way implemented to tame / volume control the voices to make better use of the mix out without clipping?

#61

As with many polysynths the easiest answer is “turn it down”. The last argument of the VOX and NOTE functions is for the voltage of that voice. I’d try capping your per-voice voltage and using a compressor to regain your lost volume if needed.

1 Like
#62

If you’re talking about regular (non-synthesis) usage, you can send a ii.jf.vtrigger(0, 3.0) message for example. Turns all of the channels down to a 3V level. As with the play_voice and play_note commands the value is remembered until a new velocity is received, or the device is restarted.

1 Like
#63

Question re. panel queries: this is probably simple, but how do I get just the specific -5/5 value returned when I query a jack? For instance,

print(crow.ii.jf.get('ramp'))

will return the following:

jf ii: name='ramp', device=1, arg=0, value=1.660868

Great! But when I attempt to use the query in my script to control something, I get an attempt to compare number with nil error.