#317

First make sure both W/s and Crow are upto date. ( I’m sure you have already done this.)
I connected the 2 W/s together with a single double headed i2c ribbon cable I made and connected those to crow. Next I put both W/s in synth mode. Loaded up the Initenere app and select wsynth for the outputs. Inserted a cable into W/ while holding record to select THIS/THAT function.
Do this for both W/s and make sure you select the same function. Then use Cold mac left to w/ 1 and right to w/2. When you sweep Cold mac it will effect each W in an opposite manner which is great.
Alternatively, just manually adjust one of the W/s and that will create a great stereo effect!
Hope that makes sense. Feel free to DM me if you need.

6 Likes
#318

I have two W/ and both now have the issue of when in Tape mode my play buttons are unresponsive. The LED lights up if fast forwarding or rewinding, but simply pushing play has no result. I tried reseting to default settings as described at the top of the thread, and have even re-flashed the firmware in both and the problem persists. I noticed this happen when after setting THIS & THAT with CV and then later removing the patch cables. The other functionality while in Tape mode seems to behave normally, Im just unable to actually play the tape anymore. Any help is appreciated!

#319

ok! i updated w/ no probs, but for updating crow i’ve run into a hitch…
cannot brew install dfu-util on my old mac in the studio (10.12 unsupported) and the pc does not see the dfu usb device - i have updated the PATH

#320

You can get dfu-util directly here, but let’s take crow-related conversation to a diff thread. http://dfu-util.sourceforge.net/

@BKCP i will investigate this & see if i can reproduce. did the new firmware work ok for a while, then stop working after connecting CV? Does the problem go away if you re-assign THIS and THAT to non-play related settings? Do you know which CV setting you selected before the play button stopped working?

1 Like
#321

yeah sorry, the general connectivity thread had been closed!

#322

Yes the new firmware worked great for a few days. I set THAT to control record level on both modules and it worked great until I unplugged the cv. Tried both a cold mac and teletype as cv sources.
I can re-assign THIS and THAT to non play related settings, according to the LED i think they are working properly, still unable to play the tape to hear their effects.

#323

ok thanks for the report. i think it might be related to the ‘loop light stops working’ issue above. will investigate as it definitely seems like something is getting incorrectly set in flash memory…

1 Like
#324

Beta 4 is updated in the top post!

Lots of behind-the-scenes changes to fix the last few issues. I think it’s ready to go, but would love some final eyes & ears to help catch anything showstopping.

Changes
  • FIX monitor level no longer affects record level
  • FIX CPU usage decreased in Tape mode (reduces loop point clicks at 2x speed)
  • FIX W/Tape CV Record displays correctly on lights
  • FIX CV assignment would break if pressing Down before selecting a destination
  • FIX Full validation of preset on load
  • FIX wdel.ii.mod_rate now gets & sets correctly
  • NEW alternate ii address selection on boot
  • FIX no more ‘click’ in wdel on first boot
  • FIX no more looppoint artifacts in Tape or Del (including at max speed)
  • FIX Tape could fail to load when loading deep into the tape.
  • FIX Del’s lowpass now sounds much better at loop points
  • FIX Less drift & jitter at loop points in Del & Tape

Of course there’s always chances things revert, so please let me know if you have issues! Hoping to tie this up & move fully into documentation over the weekend.

28 Likes
#325

:eyes: :exclamation:

4 Likes
#326

Playing in Tape mode is working properly for me with the latest update. This is really great, Thank you!

#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