#1698

The treatment of TXo and TXi being sequential, 1- 4 being the first module and 5-8 being the second and so forth was something I was hoping possible for more than one W/
I would like to send separate commands to the each W/ in my case, but there doesn’t seem to be any op to specify each module.

#1699

hi folks, interested in picking up a w/. I know there were some teething issues with this module upon intital release, were these all fixed in the latest firmware (1.2.1 i think)? was a hardware rev update required at all?

2 Likes
#1700

I’m still having issues with data on my SD card getting corrupted (resulting in audible glitches) all the time. I’ve already tried several SD cards but no luck so far. But since there are obiously lots of folks around here that are using w/, this doesn’t seem to be an issue with the module in general. Apart from that, I never experienced any issues with the module.

I think I’ve read somewhere around here about an upcoming firmware update, but I’m not sure and don’t have any details about that. But I’m really hope that it will maybe solve these issues, so I can finally use this awesome module without unwanted noises, cracks and glichtes :slight_smile:

Also, I’m still hoping that the firmware will one day become open source - at least there’s already this Github repo, but it’s still empty…

2 Likes
#1701

+1. There are a number of things that would be so helpful to add, particularly with respect to W/ Type and the ability to add more control from Teletype.

3 Likes
#1702

i think if you uh review the last year of this thread (sheesh) you will get a scope of the potential issues you may face with W/. I ran into an issue w/r/t the microSD card (which is think is the common hiccup), Mannequins sent me a new one, things have been fine since. Somewhere up there is a link to how to reformat a card yourself.

the newest firmware has some Very Nice New Functions that helped open the module a little more to my desires. I still think its worthwhile, kinda taking a backseat to my Squid Salmpler at the moment but really has done good work for me and its coming back in the next rotation.

2 Likes
#1703

I’ve had one for about a year and never had any of the “teething issues” that had been previously discussed here so it seems like those got resolved as far as I can tell, no hardware rev that I know of. Then I had this issue where it stopped responding, which I’ve seen a couple other people mention something similar—apparently being fixed by aforementioned update—once it’s back in good health it will return to being my favorite module :slight_smile: would be cool if w/type got expanded or there was crow possibilities in the future too…

2 Likes
#1704

Mine has been out of my case for a few months. I re-racked it last night for a specific application and experienced the freezes requiring reboot which brought me to remove it a while back.

I still find the module conceptually beautiful, but too unreliable to keep racked.

2 Likes
#1705

Absolutely! Also probably lots of potential for alternative firmwares, especially because of the very limited but on the other hand also very versatile interface and I/O capabilities.

Also, I’m pretty sure that especially for smaller manufacturers going open source can be of great benefit and actually accelerate the bug fixing process. But I’m probably preaching to the choir here. :wink:

That being said, I’m also sure that WR are aware of all this and have their reasons to keep the firmware proprietary for the time being…

#1706

Do you maybe know what microSD card exactly this is (size, manufacturer etc.)? Maybe I just tried the wrong ones until now…

#1707

Thanks all! I’m going to pick one up I think :slight_smile:

1 Like
#1708

Yeah ive been using mine heaps of late - so are the help cards now correct?
This module has so much potential - where’s Trent?

#1709

I’m not sure what help card you mean, but I’ve found this to be amazing http://withw.rustle.works/ (reposted from July).

+1 to all the ideas with using more than one of these with Teletype, it’d be amazing. And the issues with the SD card seem to be not so bad, if you look at it in the same way as you’d look at an actual reel of tape. A trade off for having access to 90 minutes.

2 Likes
#1710

my W/ is under the bed in the “office” so i can’t check exactly - this is the note I received from WR HQ about cards:

“If you’re going to replace the card yourself, we recommend a Class 10 card, and either 4GB or 8GB (note 8GB will not extend your tape time currently). 4GB cards tend to have faster access times. In particular we discourage using the more modern ‘Ultra’ or ‘Extreme’ speed cards- They sound like they’d be great, but W/ uses the SD card in a very non-traditonal way meaning these cards actually perform far worse than the older ones, and you’ll likely have audio dropouts in your recorded files.”

3 Likes
#1711

just as a follow up to the card stuff - the card I have from WR HQ is unbranded, class 10, 4gb.

2 Likes
#1712

I have two W/ that I use daily. There’s is nearly never an issue. I keep them in looper mode with triggers permanently connected from Pam’s. They just works so well as a looper that you can manually play the pitch shifts. Love them!
The main issue I come across is if I don’t engage them on start up or send them a trigger then they can become unresponsive, mainly one of them. A super rare issue is sometime one may not be responsive on startup but then I usually just turn my system off and back on. My using routine is to turn on the system, engage the W/‘s then hit PNW. That way I almost never have an issue.

5 Likes
#1713

How do you do this with a sequencer? Is it basically just creating a start/stop point that you can just choose to record in to?

#1714

With firmware 1.2.1 you can assign the THIS and THAT to different functions so I have dub - THAT and sample - THIS set. This lets you set the feedback with a voltage and send a trigger to reset the cue. That way you get synced delays and loops depending on your trigger tempo. While it’s playing you manually hold down play and flip the toggle switch up and down for pitch changes. With a long loop you can capture these pitch changes. If you want to just change the pitch of a loop without recording new audio or you like the pitch changes you made you can keep it as a loop by disengaging record. I’m hoping @Galapagoose will add more W/ type functions so I can use crow to actually do the pitch changes via CV. Mainly just x0.5, x1, x2 and x4 as well as the negative options. Would be cool to have a script that lets you do that as well as having loop points and cv modulation related to W/ coming out of crow.

12 Likes
#1715

Been wanting to play with reassigning THIS and THAT. It can be a bit heady to wrap the head around. I also want to do a better job of integrating my teletype scripts with it. Just haven’t gotten around to it. Plus I sent mine in to have a faulty card slot fixed. But once it’s back, I’ll try this out.

One thing I thought would work well is when making quantized music, creating a beat synced start/stop or loop points for different lengths and then having clock Pulses set the loop back to start point. This way, I could record something in to the loop at a quantized rate, pitch it however I want and at specified beat increments know that it’ll start from the top, returning it to proper beat.

Lots of cool potential tools to build!

1 Like
#1716

Today I have spent all afternoon experimenting with W/ feedback loops :smiley:

Here is a very simple patch - W/'s setup as @cosmicsoundexplorer explains above, mult outputs to inputs, patch a bipolar offset to THAT inputs, set a short loop, hit record, and start fiddling!

Here the outputs were tangled through ColdMac before being sent to the inputs, which made things a bit more interesting maybe -

5 Likes
#1717

Hey, my experience is exactly the same as you.
I have got two w/, one of them is connect ii (i2c) teletype. Like what you said, if I neglected it for a certain times it became freeze.