#462

Yes that was a typo! I have updated the post - sorry long day!

Currently, the hierarchy for the PLAY commands did not get entirely implemented, hence the bug
above! This is design work which will need to be done in the future. In general though, the latest value that the module receives for a given parameter should set the value of that parameter. With cables plugged in, the module will be continuously using the voltage on that cable to update the parameter, thus overriding whatever the last TT command was. There is still a question though as to how to interpret the polarity of WS.PLAY in transport.THAT.

  • WS.LOOP does not have any CV conflicts as there is no way to engage/disengage looping with CV.
  • WS.CUE could potentially have an interaction with using THIS in NAV mode or transport.THIS in LIVE mode - this is something we will need to make sure is working exactly as desired though the likely implementation will be that it does not trigger a redirect - I believe that is how it is currently functioning but not at a case to verify at the moment.
  • WS.REC interacts with dub.THIS - whatever the current recording state is, a trigger should always flip it. It also interacts with dub.THAT - whatever voltage is present at THAT should set the dub level when activating recording via WS.REC, not the polarity of the argument. Activating recording via TT is no different than activating via a button press or trigger.
  • WS.PLAY obviously has work which needs to be done I can’t say right now precisely how it will work as there are some considerations that must be made in relation to other commands which may be implemented! The main question is what should happen when you send in positive voltage but then run WS.PLAY -1.

Can you give me a specific example of this? As far as I am aware it should pretty much be the other way around as is?

#463

I think this clears up some confusion actually. I must be confusing the result of WS.PLAY commands with CV from TT into THAT. This is very helpful!

Thank you for detailing where the w/type commands are up to and the expected behaviour, I think this is useful info for others using this (and that).

EDIT: in dub.THIS the WS.REC seems to have precedence over THIS input. I have triggers running into THIS input and then execute WS.REC 0 (whilst play is controlled by voltage into sample.THAT) and I would expect to be punching in recording whilst recording is disable via TT but the triggers into THIS have no effect.

#464

edit: not a bug!

it’s been pretty quiet around here! i was stopping by to check for a w/type bug i ran into tonight, but it looks like the w/type-CV hierarchy issue that @yoyosandshoes was most recently talking about - i was using CV into THAT to control feedback while playing the tape, and then when i stopped the tape with WS.PLAY the CV didn’t control the tape speed like it usually would when the play button hasn’t been pressed. i had to manually start and stop play with the button for the CV to be recognized again.

side note: any progress report on w/ stuff from the whimiscal raps folks would be really really appreciated!

1 Like
#465

This sounds like not a bug. From the W/ Type page

  • nb: these settings will not change W/s mode. be sure to check the lights above the toggle to know which mode you’re in.
#466

ah! thank you for clarifying! that makes sense.

1 Like
#467
#468

can someone explain me better Sample alternate mode for THIS and THAT?
by my understanding THIS act as a sort of clock/reset to the latest cue (relaunching the cue sampled) and THAT set the speed.
In this mode act something like a “delay”? you record a cue, and by resetting you delay it right?

#469

I have been using it as a time-synced looper, with the reset into this coming around in time with a track of Kria. That track of Kria is sent into that to let me repitch what I’ve recorded.

2 Likes
#470

i recorded some of the audio crackling/overdub issues i have been having
this is fresh 1.2.1 install, fresh tape, no cue points set other than one initial to begin the recording. no cv control. no nonsense. fox only. final destination.

0:00 - 0:10 is audio straight from clouds, thru rosie, out into audio interface
0:12 - 0:50 is the same bit of audio recorded straight into w/ and then played back
0:52 - end is the same audio pitched down one octave (from clouds), then recorded into w/ in overdub mode. peeks from previous audio at :59, 1:21, 1:27.

#471

Thanks for the audio sample - could you make it downloadable so I can view the waveform in an editor (to see the clicks, rather than just hear them). I’m assuming the clicks are in the recorded material, so if you rewind and play again it retains clicks in the same place - could you confirm this?

Regarding the last part, it sounds as though you had tried to overwrite (not overdub?) the previous audio. The glitch at 1:21 is the previously recorded material being retained on the tape?

1 Like
#472

it is now downloadable. the clicks are in the recorded material.
you are correct, it is was overwrite, not overdub.
i am assuming it is the previously recorded material, it felt similar in sound. those are tiny blips though and i am not completely sure.

here are the full contents of tape 2 recorded as wav
it has a more extreme example of the clipping and overwriting clicks

https://www.drop box.com/s/x9jv8mne1o2moo7/help%20w%20wav%20full.wav?dl=0

just now, i switched to tape 3 and am unable to recreate the behavior. i switched to tape 2, fast forwarded to a blank area, and am unable to recreate the behavior. i havent cleared tapes yet.

1 Like
#473

Hi all. First post here. Glad to join lines :wink:

I got a used w/ couple of weeks ago. Started to really like how it makes me interact with the modular. But yesterday I came across an unpleasant discovery - i can no longer record without clicks and crackles. Every new recording I make gets distorted briefly, sometimes at loop points sometimes not.
It wasn’t like that before. W/ clicked occasionally on cue points but mostly it was barely noticeable. Now it’s not really possible to make anything but glitch music with it. :space_invader:
here’s a link to a video I took of the issue:

I really hope there’s a solution for this problem as I have planned to use it for my performance next week. :slight_smile:

#474

I’m sure @voidstar can answer better than me (you might also drop an email, see W/ Firmware Update (v1.2.1))
Have you tried clearing the tape (see bottom of page here)? Do you know if it’s on the latest firmware?

  • Select the tape you wish to clear
  • Turn off your synthesizer
  • Hold record + down and turn on your synthesizer
  • The orange play light will flash, press it, then press the matching lights to confirm you really want to clear it!
  • W/ will now reboot to that same tape, now cleared of all data
#475

Thanks for a quick reply! I’ll sure drop an email to whimsicalraps.

Yes, i’ve tried clearing the tape, doesn’t help.

I asked the previous owner if it’s up to date and he assured me on that. But is there a way to check the fw?

#476

I’m pretty sure there’s no indicators to tell the FW, think the only way to be sure would be to update it :slightly_smiling_face:

(I think I had something similar on a previous FW, but after updating & clearing tape, no problems. Before that, I would run it into an HP filter which eliminated the click).

#477

Hi there! New here, and really interested about this module… seems to be so creative… But prior to order one, and after reading this whole conversation, i wanted to get your thoughts about the final “robustness” of the firmware.
Understand that the last firmware iteration ironed out lots of bugs. Understand also that some strange behaviour can certainly still occur.
In it current state, do you feel that the W/ is usable, and reliable for what it is advertised?
I mean, capturing audio of sketches in a linear fashion, and at some point, jamming with it in a loop fashion way?
I’m certainly not a CV wizard or mad experimentation scientist, i doubt that i’m gonna push the module over its limits… but who knows.
Thanks for your input :slight_smile:

#478

It is certainly usable - i havent had any bugs whilst using it on the latest firmware

2 Likes
#479

It can; on mine it does.

Usable - yes. Reliable - depends how you define “reliable” as in how much is enough for you. I wouldn’t exactly call it mission-critical-robust. If you want to use it in a live performance, there seems to be a higher risk to it than with other modules. Less reliable than a Clouds or a Morphagene in my experience.

That’s its basic use right? Provided you don’t run into old recording bits, it works well. If you get comfortable with the UI, it’s a fairly quick process to layer stuff. Mind those clicks though…

We don’t know what its limits are… Right now certainly it can get into a bit of a state if you push it, but I’ve never been able to provide steps to replicate.

Anyone know and willing to share what’s on the cards for W/?

1 Like
#480

thanks for this overview. Is the batch number have any responsibility in the behaviour of the module? Also do I have to install the last firmware prior to the first warm-up?
those clicks are that annoying? due to no zero cross loop point?

#481

As I understand it, no, the batch number isn’t relevant. I would certainly install the latest firmware, but I don’t think you need to do that prior to first warm up. Yes, that it the reason for the clicks. Also, worth clearing the tapes from time to time.