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

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

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

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

This is definitely something that I do.

4 Likes

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 ?

Hi
just popping in here because i have a similar experience and i tried the swapping the sd card from a working W/ into the unresponsive one and Yes it works again!!
So i see “tape.bin”

is there a place for a fresh tape.bin or what? when i replace the tape.bin into the WSLASH it’s unresponsive again ./// strange

I think some of the above comments are true, the card in the unresponsive one has become corrupted, i can clear it and re-format it to FAT32 but i cannot copy a working “tape.bin” onto it

i do not have another 4GB Sd on hand i am going to try with an extra 8GB one just for the hell of it and i’ll report back

Request sent
Thank you

@oscillateur @shreeswifty
I’m presently working on a solution to the problems you’re experiencing. The issue is that the SD card doesn’t initialize fast enough and the driver timesout, eventually causing a freeze. This boot time seems to get longer as the cards age, but should be able to be worked around.

For the moment you can use another card if you have one handy, otherwise I’d like to request your patience. I’m away from the studio for the holidays and there’s noone there to send you replacements.

I don’t believe the cards are fundamentally broken, it’s just the driver on the module isn’t smart enough to deal with the changing cars currently.

Planning to have v2.0 ready early in the new year, which will comprehensively deal with this issue, or present an alternate path forward re card issues if it’s not solvable in code.

20 Likes

Hi
I Appreciate that you have identified the solution. I tried with another card and tried to flash the firmware on the one that does not work but I am 1.) unable to copy the “tape.bin” from one card to another so I 2.) tried to flash a new sdcard without success.

I have one working W/ and two non functional and I would like if possible to use them over the holiday break so I would love a suggestion for how to revive either of them

I’m of course frustrated because I DO very much like want that functionality in my case. So rather than returning the two faulty modules for credit or whatever to Control I’m up for a workaround

I’m going to get another micro SD card to see if it fixes my problem. The original one is a 4GB class 10, so I suppose I need something with at least the same specs, but is there a limit in size ? I think W/ will only use 4GB anyway, but smaller cards can actually end up being more expensive now as they’re not sold that much…

And once I get another card, what’s the process ? Format it in Fat32 and that’s it ? Is there anything else to do ?

fat32 is what i used

Making the SD card image is described here. Not for the faint of heart, careful you don’t wipe your hard drive! Edit: evidently you do not need to do this unless you want Izzy on the SD card.

2 Likes

Formatting the card is 100% unnecessary. W/ itself disregards the file system altogether, so you can put in a fresh card directly. We only use the FAT32 & tape.bin setup to allow the data on SD card to be accessed by a theoretical future PC application.

We use 4GB Class10 because they tested as the fastest access times in this specific use case (rapid switching between reading & writing with small chunks or data). Larger cards should still work, but the newer ‘ultra’ style cards tend to have latency pauses once in a while which can cause audible gaps in recording or playback.

4 Likes

I’ll try with a new card

Hi,

I was reading over the imaging instructions. I just wanted to verify that if you don’t care about putting Izzy on a disk you can place a formatted card in without doing all the other stuff and it will work? Thanks.

Changing the micro SD card fixed my issues. The W/ is now behaving as expected :slight_smile:.

I’m a bit worried about the future though, as I do not know if the new card will continue working well for a long time or not.

I also somehow can’t make my Teletype control W/ through i2c anymore, but that might be because of cabling issues. The i2c cable is properly connected on both modules, I also re-flashed the latest firmware on W/ just in case. Is there anything else than cable issues that could explain that ? Typing something like WS.PLAY 1 used to work immediately, but nothing happens with the W/ commands anymore…

Edit : is there a sure way to test from Teletype if W/ is properly receiving commands ?

So far (for lack of better understanding), I’ve been using my w/ mostly as tape delay/looper. My usual workflow is setting two cue points, then looping between them while using THAT to adjust the overdub level.

Recently however, this technique does not work anymore. As soon as I plug in a cable into THAT while playing the loop in live mode, the behaviour of THAT does no longer change the recording level, but the playback speed/direction.

I’m not sure if this is a technical issue (unlikely) or just me doing something wrong (very likely). It’s been a while since I used the aforementioned technique, so maybe I just forgot some little detail…

Has anyone around here experienced the same problem?

Since the 1.2 version of the firmware (I think), the behaviour of the This and That jacks can be chosen, yours likely has another setting than the one you want to use, as playback pitch is one of the options. The exact way to set these explained in the manual (online version, as this from a post-initial release feature).

2 Likes

I’ve already tried the different modes described in the manual and I think DUB is the (default) one I’m looking for. However, the problem is still there, even after switching to DUB mode…