#332

I have been tossing around the idea of creating some simple i2c control of w/ with the teletype and grid ops. Granted, this basically is VERY niche in that you need a teletype, an i2c bus AND a grid for the teletype grid ops, but it would add some physical buttons to the whole kit and work flow. I’ve just started to get my head around the module and teletype, so it might be a while till I get everything worked out (gonna take some time away from this stuff after my baby is born) but it’s still a fun idea and a nice companion to the whole thing.

7 Likes
#333

I’d love this! 20 sweet sweet chars

#334

I believe someone made a script just like the one you are describing

1 Like
#335

Thank you for the advice!! :slight_smile:

#336

I’d be curious to see it. I had looked around and not seen anything yet. But hey! A working script is a working script!

#337

i think this is what you’re looking for

4 Likes
#338

Mission Accomplished, y’all! We can pack it all in. Thanks for finding this. Would’ve been cool to make myself, but can’t complain with the dang results. Haha.

3 Likes
#339

My ‘working’ W/ just exploded, like INSANE volume spike of digital noise, out of nowhere. Has anyone had this happen to them? Cleared tape seems to be working, but increasingly feeling like this module is still too buggy to rely on.

#340

OK, it’s been over 2 weeks since Trent said he’d mail me a new micro SD card, and I’ve been ignoring it while I wait, but now I noticed that that W/ isn’t even powering on like the other one. There’s a little flicker of the white light above loop and then no other lights. It doesn’t respond to signal coming in or anything.

Anyone experience that before?

Thanks!
Connor

#341

i have had 3 W/'s , one just stop working. I sold one that worked perfectly then i regretted it and bought another one it just stopped power up and also what i find is that the faceplate separates from the body and the play light stops illuminating. i was right in the middle of a project so i had to replace it but i am more than a little curios to hear other experiences too. i love what it does and it’s size but this post reminded me

#342

Yeah, I’m sort of trying to develop some work for live shows next summer and I really am having a hard time deciding if it’s going to work reliably enough. I had emailed Trent asking if he would be open to selling me some backup cards that I could take with me, just in case they had issues. Haven’t heard back in 2 weeks about that question either.

Definitely found that the form factor and ergonomics weren’t as problematic as I thought they might be. I had been having a good time with a pair of them. The reliability remains the big mystery. Given how relatively silent this thread is, perhaps most people have abandoned the module? I have no idea really.

#343

The thing I struggle with is the lack of ability to set cue points programmatically, either via CV or i2c (unless I’m missing something and that’s possible). That would make synced loops and delays more possible.

Crow was a big effort and it sounds like they just moved HQ as well. Maybe when the dust settles and there’s been sufficient rest and downtime there will be energy for further W/ development.

1 Like
#344

Mine fails regularly (as in, completely unresponsive, won’t play). At one point, I could no longer get it to function with a reboot (and nothing would work, so I couldn’t clear tape). I was certain it was bricked until I managed to get it working again by powering on as of updating firmware.

I’ve kept it racked since, when it works, it can be quite useful for its size; but I probably incorporate it into ten percent of my patches on account of the unreliability.

#345

i’ve said this privately but for the sake of the post: I really like and almost love W/. does a lot of “almost exactly” what I want a sampler/looper-ish module to do and my preference is to keep one in my rack.

upthread I reported a failure literally days before a gig. didn’t wreck the gig, didn’t cripple my patch. maybe it never happens again, but (as I also wrote upthread) we had the same failure.

1 Like
#346

I have 3 W/ and seldom, if ever, run into problems that aren’t user error (mostly when messing around with cues). If I am silent in the help thread, it’s because I am using the module and it’s working as intended :sweat_smile:

4 Likes
#347

Word, well, that’s good to know - I appreciate you breaking your silence :slight_smile:

I suppose I’ll keep posting when I have issues in hopes that someone else has experienced the issues I’ve seen. I think what has been confounding is just not knowing what user errors even are I guess. That idea of isolating problems and figuring out what leads to them and how to undo them. Agree that it seems that the cue point exploration has led to more issues than any other approach.

I feel like clearing the tape should sort of serve as a reset and clear out the errors, but when that doesn’t work, what would you suggest to address possible user errors? (If you have any advice at least).

Hope Trent won’t mind my sharing this, but here’s what he said when he responded to my queries last night. Posting it in hopes of sharing knowledge if others experience similar issues:

“The no-lights situation is symptomatic of an SD card that won’t initialize. My experience is that the cards fail quickly if they are going to, so I believe you’ll be fine if things go well for the first few sessions with it. Another (confounding) solution is to swap the SD card between modules. This will often make them both work again, although I cannot for the life of me explain why.”

3 Likes
#348

Hey, I’ve been quiet in here too because I’ve found a work around that generally helps me with the issue that I have occasionally.

I occasionally have an issue where W/ does not power up correctly and is unresponsive. I have most of my sequencing and sound making modules in my main case, but my W/, coldmac, uO_C, plaits, pam’s, are in a 4ms pod. My issues have all been on power up, so its easy for me to power cycle just the pod without cutting power to my main oscillators. Bonus being that I have a sort of little modular sketchpad that plays nicely on the couch away from my desk when I want.

Since the firmware update (a very long time ago now) I think I’ve had less problems with the module locking up if ignored for too long while on. Then again, if I don’t start patching up W/ at the begging of a session, I usually don’t use it. Also I’ve noticed that it doesn’t love being modulated during power-up, so usually pull inputs from THIS/THAT before cycling.

1 Like
#349

Interesting insight on the inputs into THIS/THAT.

I definitely only pulled the trigger and decided to explore the W/ when it seemed like the most recent firmware addressed a lot of the concerns people had. In general I’ve had a blast with it, when it’s been functional. One of mine has been this whole time (barring the weird digital noise freakout once), which is great, and yeah, I’ve been honing in on approaches that don’t push it too hard and still allow for some fun possibilities while minimizing the chances of it freaking out. That’s my hope.

1 Like
#350

This is definitely something that I do.

4 Likes
#351

My W/ seems to have died or is at least seriously ill… :frowning:

It worked yesterday, I turned my modular on today and the right LED above loop very, very briefly lights up and then nothing. I tried several power connectors, same thing. My case is an Intellijel Palette, all the other modules work fine in it today.

Any idea of what is wrong and how it can be fixed ? I noticed that the front panel can slide a little bit, but I have no idea what kind of screwdriver is needed to fasten the two weird small screws on the front panel…

I also tried removing the i2c connectors, no change… Everything looks fine from the outside (no bent pin or anything).

@Galapagoose, @voidstar : any idea of what could be going on here ?