#327

just updated: everything smooth as butter! No more “loop led issues”. The little w/syn sounds lovable, very impressive.
Thank you @Galapagoose for this!!!

#328

thanks for all your hard work and updates on this.

#329

is anyone else having trouble with norns → crow → w/ communications?

even trying to access the w/ help files in the maiden REPL throws an error.

crow.ii.wsyn.help()
lua: stdin:1: attempt to index a nil value (field 'wsyn')
stack traceback:
	stdin:1: in main chunk

i get the same traceback for all the w/ modes…

#330

They have to get added to norns, specifically this file which indicates it was generated from the crow ii definitions by this script. You can always directly send some text to crow, e.g. crow.send('ii.wsyn.help()')

3 Likes
#331

Ahh! thanks for the info!

edit: that got me sorted @csboling :grinning:

2 Likes
#332

Just wondering if anyone had noticed a slight distortion from W/synth when playing all four voices simultaneously?
Is there an option to lower the velocity of voices like of JF?
Thinking this would help the issue.

#333

I tend to tilt the a/d envelope setting a bit and get less distortion. Say -4.5 or closer to 0v. The wave shape also seems to have a great effect here, more sinusoidal than square or tri/saw.

1 Like
#334

Thanks for the tip!
I’ll give it go and see how it fairs.

#335

Would love a way to control the volume of recorded material in Tape mode, Maybe a “Mix” parameter like in Delay mode.

1 Like
#336

This is an interesting idea I’d like to explore, but I’m going to finish 2.0 as is before adding features. I’ve noted it in the issue tracker.

At present there is not, unless you’re using the ii interface. The distortion is caused because individual notes are at ‘eurorack levels’ which means even 3 voices at full level will clip. It’s a balance between short, non-overlapping sounds, being loud enough, versus long poly-tones distorting. This is the same problem as the ‘ALL’ output on Three Sisters.

One thing to note is the Gate input is pulse-width sensitive, so if your gate source can send shorter pulses, it can reduce the effective volume. This won’t work with the fastest attack settings though.

I’ve noted the issue in the tracker & will think about solutions. Either an option to set the output level on device, or a compressor/limiter at the output.

This is correct. There’s already a PR open - just waiting for the next norns update to push it out.

Glad to see it’s working well for everyone so far!

15 Likes
#337

Thanks for the detailed response!
When I first tried W/synth it was via the front panel inputs and didn’t notice any distortion but I may revisit it now that you have mentioned its gate input is pulse-width sensitive, sound interesting.
I’ve been using W/synth mainly with the ii interface and have only noticed it distorting when multiple voices play. Knowing that the volume of the voices is accessible via the ii interface is great news. Would this be a setting I could adjust for app or maybe have added to them?
Also your ideas on setting output level or adding a compressor/limiter sounds promising too :slight_smile:

#338

in w/tape, is there a way to “tap loop” via i2c? looking to use i2c to reset the loop.

#339

Hmmm…? I thought you had answered that here, which I understand to be:

  • Jump timestamp to where you want end point to be
  • Set end point
  • Jump timestamp to where you want start point to be
  • Set start point
2 Likes
#340

argh, you are totally right. i was thinking about things all wrong. apologies for the noise!

as an aside, if i understand the docs, loop_next(0) might be the “one liner” i was looking for.

edit: loop_next(0) works perfectly!

3 Likes
#341

@Galapagoose I’m trying to figure out what the various options for the wsyn.patch i2c command do. So far I’ve come up with this from experimenting with the second argument:

  • 1 = ramp
  • 2 = curve
  • 3 = fm_index
  • 4 = fm_env
  • 5 = lpg_time
  • 6 = lpg_symmetry
  • 7 = velocity (seems to trigger the voice at zero-crossings)
  • 8 = ??? (doesn’t seem to be responding)
  • 9 = fm_ratio (numerator)
  • 10 = fm_ratio (denominator)

Does that look right? What should ii.wsyn.patch(1, 8) be affecting?

I love being able to control the module like this over i2c!

1 Like
#342

This is mostly correct. You have fm_index and fm_env reversed I believe.

7 = gate. Allocates a new voice, with pitch controlled by v8 while the gate is high. Velocity is always ~5Vp2p
8 = v8. Sets the pitch of the current voice, while gate is high.

So v8 won’t do anything in isolation - it needs to be paired with gate to be meaningful.

I’m writing up docs presently, so thanks for the reminder to cover this stuff. I almost didn’t include the patch function, but it seemed handy if one were writing multiple scripts to switch the functionality automatically.

At this point I believe the firmware won’t change again before 2.0 - I won’t make it official until there’s new documentation, but for now you can feel confident to use it & should expect it to be relatively bug free.

If you do have any issues that arise, please log them here, and I’ll try to get fixes squeezed in pre 2.0.

12 Likes