Still reprogramming my ways to incorporate this new pattern flow, but let’s talk about the default sound, and fast access to parameters. Beef (or your fave plant based substitute)!
PS… Any tips for connecting directly to the OP-Z via Bluetooth??
@blipson , @aMunchkinElfGraduate
The latest FW update adds;
-
Out-of-scale chord playback (selection was already possible via editing step on the chord track, but playback was quantized to the nearest legal root note for the scale - this can now be turned off). Set the new “FrE.c”/“FrEE Chrd” parameter under 4/Ar on the Global Song mode to “yes”.
-
A “SavE Song” option is now available in the Song mode’s Glob context menu, if you booted your Woovebox with auto-save disabled.
7 Likes
I connect to Wooveconnect successfully. I leave it connected for about 30 minutes and there’s no evidence of firmware update success or failure. After that, I reboot to no auto-save, but I don’t fnd SavE Song in the Song mode’s Glob context menu. To verify, I see Init Song (and others) in that menu.
I had a huge mental block during my first few hours with the Woovebox. I’m sure there will be more confusion to come. My confusion is a result of using the Digitone exclusively.
On the Digitone, if I select or edit a “track sound”, that sound is only active for the current pattern. If I want to clone the track sound, I do it by copying and pasting the pattern into another pattern slot. The current track sound can also be copied without copying all the settings and trigs.
On the Woovebox, on the other hand, selecting or editing a track sound applies that selection or edit to all patterns 1-16 of a particular track. Why was it so difficult for me to understand this?
On the Woovebox, when I edit Osc1 and Osc2, for example, I am editing them for the entire Track, rather than the active pattern.
Someone on another thread is already trying to sell their Woovebox, claiming that it’s too deep or complicated. I told myself that I wouldintially be lost and confused with this new device, and I was right. But that’s the way it always goes. This device has a different paradigm of usage. I need to be patient. I am looking forward to reading more input from other Elektronauts who bought the Woovebox.
You should see a popup almost immediately.
Does the screen mirroring work? When you launch Wooveconnect, two windows open, the one with the Blue text, and another with a “virtual” Woovebox. As soon as you connect to the Woovebox, that window should come alive and mirror your Woovebox.
If it does not, then it would appear that messages are getting lost (including a message that provides Wooveconnect with the firmware version of your Woovebox)
Thank you. I’m hopeful that this is largely the extent of your learning curve; “unlearning” the workflow of another device that you are so intimately familiar with.
It’s indeed a different paradigm, much closer to something like the TE OP-Z; there’s a bunch of tracks that have their associated sounds (or kits). And all patterns under those tracks are playing those sounds exclusively**.
From here, you have the massive advantage of knowing what a first-rate device like the Digitakt can do for your music. You will likely already be quite familiar with many of the concepts behind sound design/synthesis, sampling, dynamics and effects. As a result you will be well positioned to quickly take advantage of the Woovebox equivalents; you will know what you are looking for to change/tweak/accomplish and what such a parameter or concept would be called. You won’t need explaining what an ADSR envelope generator does, or what a low pass filter does. You will hopefully be able to hit the ground running.
** the Woovebox does have an optional multi-instrument mode where tracks can “borrow” another track’s sound, but that’s for another day 
1 Like
I’m reporting a problem with the new SavE Song in the Song mode’s Glob context menu feature. I’m not necessarily reporting a problem with Wooveconnect.
I connect to Wooveconnect successfully. I get the popup you describe, and it accurately tracks the state of my Woovebox. However, the connection always get dropped after about 90 seconds, and I have to re-connect in Audio MIDI Studio. There’s no indication of why the connection drops, and it always reconnects when I click the connect button in Audio MIDI Studio.
ADDED: The Bluetooth connection stays up indefinitiely if I keep the Woovebox playing.
There’s never been any indicator of firmware-related activity, but you’ve said the update is automatic, so I don’t expect to see any feedback. When I reboot to no auto-save mode off, I don’t fnd SavE Song in the Song mode’s Glob context menu. To verify, I see Init Song (and others) in that menu. This all implies that the firmware update never happens.
The update requires your consent through a pop-up. The pop-up should happen no more than 10 seconds after making a connection.
I just issued a fix for macOS devices specifically, so please go ahead and reload Wooveconnect.
Once the firmware has been uploaded to your Woovebox (you will see a progress indicator) you should see your Woovebox going through an update sequence.
As part of the update, the new SavE Song option should now appear if you boot with auto-save off.
Any trouble, do let me know.
2 Likes
That’s what I was missing. I originally thought you meant the popup that mirrors the Woovebox.
It’s working now. My mistake was apparently that Opera was caching something from the web page, but when I made sure to open Wooveconnect “fresh,” the update went OK, and I see the new save feature.
2 Likes
Awesome! 
I’ve been thrown a good few curveballs with Wooveconnect over the past few days, so I’m happy to hear the upgrade went well. There’s an infinite amount of OS/BT adapter/browser combos…
2 Likes
I wrote my first “song” last night on the Woovebox. It was the first thing that popped into my head. The main theme from Dvorak’s “Humoresque”. My wife’s violin student had been playing it an hour early and it was stuck in my head. I am sensing that the workflow can be pretty fast. While arranging the fragments of the song, I realized that there was no reason for me to have created any duplicate patterns. This is another profound difference in workflow from my Digitone. Elektron created a “Song Mode” as an afterthought, while on the Woovebox, the Song Mode and the Seq are more integrated into a deliberate workflow. Nice!
My learning progress, sadly, is painfully slow. I am okay with this, however, as I’ve learned other hard things as an adult. Unicycling, for example: I was the world’s slowest learner but can now execute some pretty fringe technique, (such as riding backwards-downhill-offroad with both hands on the seat). Or kendama, the Japanese ball and cup toy. I can execute some pretty hard tricks on it. But, in both cases, I put many hours into learning. And I think the same thing is going to be true for the Woovebox. Anyway, just wanted you to know I’m not a quitter, nor do I feel like quitting on the Woovebox.
As brilliantly as this device is executed, I must say the docs leave me scratching my head. I feel like they were written for someone who is already familiar with the Woovebox, rather than for a beginner like myself. I had a manual for a graphing calculator. The examples were explained keystroke by keystroke. Examples like that would be helpful. I know that basic principles of the interface are explained on a particular page of the docs, but I would still prefer more button-by-button help in the other sections. I find myself jumping a lot between the sections of docs. Most of the docs’ sections are prefaced with an introductory overview of a function or musical idea . I find those explanations difficult to absorb while I still am having trouble navigating the Woovebox. When a new concept finally makes it through my thick head, the introductory remarks seem spot on, however. A teaching mentor once told me, “Engagement before information.” That was in reference to teaching kids, I know. Most of your audience are adults. But, IMO, the docs could engage in a bit more “hand holding.”
Best wishes!
2 Likes
The “The very basics” and “Quick start guide” sections do that to a significant degree. Did you work through them first, or just jump right into it? My wish is that they would render the web-based manual to PDF so that I can bookmark and highlight as I please and also keep a copy on my phone.
2 Likes
Would it be possible in a firmware update to use the line-in for receiving a clock sync pulse instead?
Also: I appreciate all the little UI details such as the quick-access to the sequencer page and back again, and when setting up song fragments the track items remember the last option used… no repeated scrolling to get back to the same pattern option on each track again and again (here’s looking at you, Korg…). Multi-selection etc make things smoother than you’d think.
2 Likes
Would it be possible in a firmware update to use the line-in for receiving a clock sync pulse instead?
I’ve certainly thought about that! I’d want to do a little more research on clock sync pulses, voltages, etc. before officially recommending people route their clock sync pulses into a line-in level input though…
2 Likes
Made great progress with the WB yesterday. Still waiting for a bluetooth adapter for my computer so I can update the firmware.
A couple of questions (and I’m hoping for more Elektronauts users to chime in):
I successfully followed all the steps in Multi-Instrument Mode section of the docs. However, in the preface of that section, you mentioned more complex chords (more than 4 members). I initially assumed this meant that a single MIM step could inherit more than one sound. But I don’t think that is right. The chords you’re referring to…are they made by combining more than one MIM track?
Since I haven’t updated the firmware yet, I haven’t tried the new option you added for creating chords. But the pre-existing implementation is pretty cool. I noticed that when I audition a chord, then press the modifier key until I find the appropriate chord “flavor” … if I decide to “double-check” the sound of the chord a second time, the WB reverts back to the chord-flavor originally on that button.
Is it possible (or practical) for chord-modifications to change the state of the buttons? For example, if I decided I wanted a major chord instead of a minor chord on a particular button, then of course I’d have to change it, once…but then could it retain that state until I changed it again? The implications of this (without have given it nearly as much thought as the esteemed dev) is that a custom button configuration for the chords/types/inversions would be built dynamically as the user interacted with the chords.
Another tiny detail. The WB, when turned on, defaults to Song #1. My typical use-case is to return to the same song I was working on last time. Tiny, insignificant detail…
I use the Digitone extensively. It has a lot of tools for eliminating pops and clicks (transients). This is going to be an area of growth for me on the Woovebox. Some sounds can be tamed more easily than others. Some oscillator modes are more conducive to transients popping up. For example, I’ve found that removing transients is more difficult on the Cd (chord) track than on individual tracks. I am confident that the tools exist on the WB to clean up transients, but I’m far from mastering them.
I successfully followed all the steps in Multi-Instrument Mode section of the docs. However, in the preface of that section, you mentioned more complex chords (more than 4 members). I initially assumed this meant that a single MIM step could inherit more than one sound. But I don’t think that is right. The chords you’re referring to…are they made by combining more than one MIM track?
The chord track does not allow for chords that consist of more than four notes. If you need a chord that has more than four notes, for example some 9th chord, you can play the 7 equivalent (e.g. the same chord, but missing the 9th) and use another track to supply the fifth note (9th). Multi-instrument mode allows you to use the timbre of the chord track, so it all sounds like the one chord.
E.g. if you get commissioned to write the next James Bond score, now you can. 
Is it possible (or practical) for chord-modifications to change the state of the buttons? For example, if I decided I wanted a major chord instead of a minor chord on a particular button, then of course I’d have to change it, once…but then could it retain that state until I changed it again? The implications of this (without have given it nearly as much thought as the esteemed dev) is that a custom button configuration for the chords/types/inversions would be built dynamically as the user interacted with the chords.
This is not a crazy idea at its core. I could explore this. Thank you.
I use the Digitone extensively. It has a lot of tools for eliminating pops and clicks (transients). This is going to be an area of growth for me on the Woovebox. Some sounds can be tamed more easily than others. Some oscillator modes are more conducive to transients popping up. For example, I’ve found that removing transients is more difficult on the Cd (chord) track than on individual tracks. I am confident that the tools exist on the WB to clean up transients, but I’m far from mastering them.
There are indeed a good few ways to avoid (or accentuate) transients. First stop would be to - on the Osc1/Osc2 pages - set Ph.St (“Phase Start”) to a value where a waveform starts at 0. This is usually a value of 0, but can depend on the algorithm. You will want to set Ph.rn (“Phase Range”) to 0 as well, so that phase is always reset to 0.
If need be, you can get more heavy-handed by performing self-gating in the dynamics page.
Do note that many presets deliberately have a free running oscillator setup as part of an effort to emulate analog behavior; as you know pops and clicks are part of the analog charm for some timbres with a near-0 attack.
As you likely know, accentuating transients can also greatly help with sounds punching through in a busy mix. There are some audio examples in the Side-chaining, gating, ducking and compression section of the docs.
2 Likes
I just made the James Bond chord (minor triad with added major 7 and 9) on my Woovebox using the Cd (chord track) and two “multi-instrument” tracks borrowing the chord sound. It boggles my brain considering how many different ways there are to achieve this chord on the Woovebox (different combinations of individual tracks, multi-instrument-mode tracks, the chord track). Thanks for your added explanation. It cleared up my confusion.
Best wishes!
3 Likes
Hi, I’ve a problem trying to update the firmware. I’m using Chrome under macOs.
I connect the Woovebox via bluetooth midi to my mac the. I launch wooveconnect.
A popup appear askint to update firmware to last available release; I confirm and wooveconnect start to download the new firmware, showing progressove numbers on the device (and on the web mirror).
As soon as it reach number 99, the wooveconnect page goes back to home saying the unit is connected and tonstart operations via context menu while both the device and the mirror on web page hang showing “rcv 99”.
I’ve waited more than 10 minutes but the situation didn’t change.
If I turn off the wb, at the new start the wooveconnect page restart asking the ok to update with new firmware.
Where is my mistake ?
Thanks GF
P.s. the bt connection is stable during the whole process
@Woovebox This thing is freaking awesome!
I only have one request, can you please add a savestate for the headphone volume? Maybe in the global settings?
Everytime I turn it on, I have to set the volume up again. Thanks in advance
@Woovebox hi, i’m having an issue with sample playback; i’ve got 7 wavs uploaded to my US01 kit. following the instructions @ Using samples in your songs: Using a sample kit i select the kick track, set the behavior to SMPK, scroll to patch page, init via holding write and short pressing value then long pressing value (3+ sec), release value and release write. head over to OSC1 and select US01.
now… all 7 of my samples sound fine. i lay down some kicks. then i select the snare track, do the same exact steps and load the same US01 kit. after finding that the track was transposed (shouldn’t patch init clear this?) and resetting it to 0, now the sample in slot 1 sounds garbled, but the other 6 sound ok. luckily, the snare sample i want is one of the ok ones. so i lay down some snares.
i go to hi hat track and do the same steps, same kit, and slot 1 gives me an even more garbled sound, and slots 2-7 are silent. i go through the steps about 10 more times, check the transpose (it’s 0), the other params seem the same as kick so i’m not sure why the different behavior? i try track A1, and it gives me the snare behavior: sample 1 is janky, 2-7 sound ok.
i thought maybe it’s because i’m loading the same kit multiple times? so i go to a new song, and start with the hi hat track, but it’s the same: janky sample 1, no sample 2-7.
are there secret parameters that are janking up my track? maybe some context menus hiding values that aren’t initting?
also, hardware-wise: if i push the left side of the power button to the right, it clicks over, but it doesn’t turn on the unit. i have to push down on the button and then slide it over. i’m guessing the red plastic (or resin or whatever) isn’t fully seated on the underlying switch. i hope the misfires aren’t going to wear down the inside of the plastic over time.
also: wooveconnect firmware update often fails with the same rcv 99 issue @gfcalvi was having, sometimes it goes to rcv 00, sometimes i get some other error that i can’t remember (i thought it was “CONN ERR” but it definitely didn’t say that). i tried a different laptop and it worked the first time. so maybe my laptop has weak bluetooth? but it seems fine otherwise. and i get similar errors when trying to load samples. some samples work ok (maybe the shorter ones?), some fail in different ways each time.
finally: what’s the best channel for support? here, reddit, email?
thanks!
1 Like