I believe it’s the newest firmware but I’m not 100% sure about that, just got it used a few days ago.

Just for clarification, I can get things to work sometimes but it just seems buggy. I’m trying to figure out ways to replicate the crashes but it’s hard to keep track of everything without any visual cues.

You need to perform a firmware update as there is no certainty that the used unit was ever updated.

1 Like

anyone else’s W/ having “bad days”? mine has been temperamental

  • once it was stuck looping just a few samples when powered and nothing I did made any difference.
  • once it was stuck looping a short section and the controls didn’t help anything.
  • many a time it decided to click loudly where the cue point was, even though i hadn’t patched e.g. something rich in low frequency or DC or of the kind.

running latest firmware.

having a really rough time. i have reinstalled firmware 1.2, cleared tape, and cleared cues. i am getting ~lots~ of clicks and pops and audio dropouts, and previously recorded material is still hanging around and interjecting itself. no cv/this/that, just audio in, recording, and looping.

does switching to another tape help at all?

a fresh recording on a fresh tape works well. after bringing it back to the beginning of the tape, overdubbing, and setting cues for a loop (all separate instances, not all done in one playthrough) the clicks and previous material interjections return.

Not sure if my module crashed, but just turned the rack on and all the lights on W/ were out. Just checked the power and it’s fine. I tried booting up to Izzy and the play light just blinks. I’ve done it again and flicked Up, and it all seems to work ok again now. Not sure if I was in a weird mode or not, hard to tell!

1 Like

I have occasionally had this issue as well. I know that digital modules can be power hungry/sensitive on startup and I have quite a few on that section of power bus. I’ve not had the issue (that I remember) when I put w/ into my smaller portable rig with fewer other digital things. But this is only observation, absence of evidence is not evidence of absence.

A quick power cycle usually fixes it the first time.

EDIT: Thanks for the topic migration

1 Like

hmm, I’ve just done a firmware update, and cleared the tape. Now it’s just starting up with no lights again. I’ve just sent Whimsical an email, hopefully it’s something that can be fixed easily. Yeah Power wise, I’m only running 6 modules in a MN skiff altogether, I would have thought it should handle that! But yeah, wasn’t an issue before I hooke up Maths, maybe it is power related. :confused:

1 Like

i had this happen a few times on my old power supply/distro. i did a couple reasonable/voodoo solutions (reload firmware - unmaking clouds, W/ starts up fine).

haven’t had this problem w my recently installed Intellijel TPS 80, so yeah it’s probably a power hiccup in there even if yr not fully loaded.

1 Like

hmm, just taken my whole rack apart, and even with onlyw/ plugged in, tried another firmware update, and still the same issue. Hope Mannequins can get back to me on email support.

still learning my way around this lovely module- is there a way to use it like a delay, but introduce some pitch warbling to the delay line?

2 Likes

Hi @Obelisk!

Sorry to hear you are having issues - thanks for emailing us! Responding to you over there right now.

For everyone, in general, if you ever happen to experience an issue like this, please shoot us an email over at service@whimsicalraps.com so we can sort out your problem!

Absolutely! One option would be to set up a looping section of tape, locking in a feedback level that you like by using dub.THAT, and then switching to transport.THAT (or switching to NAV mode). You could also use reset triggers into sample.THIS or WS.CUE from Teletype. Let me know if you have questions about how to lock in a feedback level.

6 Likes

ok, not sure what was happening, but got things back up and running by ejecting the SD card and reinserting it. Now after doing an Izzy reboot, the onboarding starts and voice comes through. after the onboarding, the tape looks like it hadn’t been cleared even after trying that boot up combo at least a dozen times, but I’ve now installed a new firmware, and wiped again. This time it appears to be working correctly.

cool thanks! kind of a funny question- but how can I select sample.This, and Transport.That, beings that I have to hold down my THIS selection as toggle down, but I need to hit toggle up to select Transport.THAT

Ah, I just sent you a response and that was one of the things suggested in my email.

If you have a minute, it would be great if you could answer the questions I sent you just so we can log a little more data about your particular issue!

Sorry, to be clearer-

  1. sample.THIS and sample.THAT
  2. just a looping section of tape with transport.THAT or sample.THAT
  3. WS.CUE 0 with transport.THAT or sample.THAT

sample and transport CV modes can’t be paired for the reason you described.

If you would like to change your delay length, you can do it with the following techniques, respectively:

  1. changing trigger frequency into sample.THIS
  2. If using transport.THAT, using transport.THIS to select different loops on the tape with different lengths
  3. changing reset frequency of WS.CUE 0
8 Likes

Ok, I feel pretty stupid but I can’t follow the instructions above to use W/ as a simple delay. I’ve basically only used it as a basic SOS looper so far (mostly because I don’t have a lot of music time these days, and I tend to spend it doing things I already know :wink: ) but I’m obviously missing at least one crucial step here.

My W/ has the latest firmware.

Would it be possible for someone more familiar with the module than me to explain how to get it to behave as a simple delay (from the moment the module boots, for example) but just by mentioning the controls involved (buttons, etc.) and not their functions ? I.e. " sample .THIS and sample .THAT" without more context is not very clear to me, for example.

Thanks in advance :slight_smile:.

Wow, so your dub.THAT setting is held if you change the behaviour of THAT? is it all also saved over power cycles? This is a fantastic revelation
In your example above, is the warble applied both on recording audio to tape and play back? Or just playback?

I don’t think it is saved across power cycles. I wish it were!

1 Like

plug a voltage source into that. Press play, flick the toggle down and then up quickly. Press record.

voltage into that sets feedback amount. -3V or so is my favorite. how quickly you flicked the toggle sets the delay time. you can double or halve it by holding play and flicking up or down.

I made some assumptions about what settings you have, so if you get some weird result, let us know and we’ll try to talk you through it

9 Likes