I have never had a question about a piece of gear that Elektronauts couldn’t answer. In fact almost every question I’ve ever had was answered by simply using the search function and many of these questions had many sweet answers that led me down awesome paths I hadn’t even considered. I’m sure it’ll be like that for the Woovebox too as time passes.
10 Likes
precisely what got me interested in the woovebox.
Tried the M8 for a couple months but ironically I couldnt get as far as what I would do with the Polyend Tracker.
I love the no -nonsense sequencer of the woovebox, it is very easy to get into a fast workflow, get something going and care about the details of your layers or sound design later…
very nice piece of gear, love it.
3 Likes
Finally got the Woove after a long time at the customs. I’ve been composing a lot with it and I really enjoy the workflow and sound you can make of it!
One thing I don’t really get is the switching between songs!
I’m trying to change it in the global menu by holding “Play” and any of the numbers but as mentioned above, it really is a hit and miss all the time.
I sometimes hear the sounds I’ve made on all the tracks, but the pattern is empty. And sometimes the patterns are all there and all the sounds?
Could anybody help me with the exact combination to change songs?
Sounds like you might be getting song and pattern switching mixed up as they use the same mechanism but from different screens.
From the Song screen (press the knob then the Song button) you can press Play and then the 16 buttons to select a song. From any other screen doing this will change the Pattern number instead.
Hey, can anyone tell me how many posts I gotta post before I can upload a song or something? Don’t make me start a Discord server… 
1 Like
To answer, directly, your question…
To change songs while in SONG MODE, hold play + a 1-16 track button.
To change songs while in ANY OTHER MODE, hold VALUE and press A8 to re-enter SONG MODE.
When you turn on the Woovebox, you are in Song Mode. Holding PLAY + pressing any of the buttons changes to that SONG. Pressing Play, then, while in Song Mode, will only play music if a Song has been constructed (by selecting Fragments, etc.) for that Song. This could be a possible reason why you’re not hearing any music when pressing PLAY.
To navigate from Song Mode to the Seq page for the selected song, Hold Value and press one of the buttons. This will take you to the Seq(uencer) Mode for whichever track button you pressed. Keep in mind that when returning to SEQ mode from SONG MODE, you will automatically be placed in whatever PATTERN you were previously in. To change PATTERN at this point, hold PLAY + 1-16 PATTERN button.
Seq Mode will only show illuminated buttons if there active steps on the current PATTERN for that TRACK. There will be a Pattern Number at the top left of the display. Pressing Play, while in SEQ mode, plays whatever material is on the the 1-16 tracks FOR THAT PATTERN. I emphasize that, because the layering of parts may/may not be different from the the layering of the parts in SONG mode. Coming from a different machine’s workflow, this took me some time to get my head around. The #3 pattern for one Track may be 4x as long as the #3 pattern of another track. This may cause playback In SEQ mode, when patterns are chained together, to not sound as intended. That is where SONG mode comes in. SONG mode (when a song is constructed)is able to set a length on each Fragment, whereas in SEQ mode will just just start playing all the #3 (for example) patterns from the beginning. It is better, IMO, instead of thinking about “patterns”, think about them like “ideas” (with potentially different lengths). Don’t fall in the trap of thinking that all the #3 patterns, for example, necessarily need to play at the same time. Otherwise, you will end up creating or cloning a lot of unnecessary patterns. Remember that everything ultimately comes together in SONG mode.
4 Likes
the thing that confused me at first was that on the song page, after you select your song (play + 1-16), then when you hit play it plays the song i.e. fragment 01, which would be empty at first. if you were working on a loop, you’d have to enter a track (value + 1-13 or long press 14-16), and then when you press play it plays pattern 01 of all tracks.
hope that helps! bit of a learning curve but i think it makes sense once it clicks.
3 Likes
Ahhh… that makes sense. Sorry to jump in 
Haven’t even been able to order one yet, but have been ingesting the manual But yes, the Song is where you string together the Fragments that the Patterns with play on the Tracks, so if previously working on a Pattern it won’t be assigned in a Song fragment or whatever yet. Or at least as I understand it.
Woovebox, size is approximately 10cm X 10cm x 2M deep
1 Like
This, 
finally made sense!
Thank you!
Another question, I’m looking at the online manual and can’t find any info about copying patterns, I’d like to copy Pattern 1 to Pattern 2 and make some minor adjustments to the tracks, is this possible?
While in SEQ mode, access the CONTEXT menu by holding WRITE + VALUE click. Continue Holding WRITE while clicking WRITE to cycle through the various choices in the CONTEXT menu. One of the choices is Copy Pttn. Change pattern and perform the PSTE Pttn context menu function. Long-press Value while on any CONTEXT menu item…to execute it.
The caveat is: You will only be copying the pattern of the particular track you are on. Now, you may already know this but ask yourself, “Why can’t the Woovebox copy, for example, all the #1 patterns for all the 1-16 tracks?”
This lack-of-feature initially threw me for a loop. Thanks to some explanation from the developer and some time spent with the unit, I’ve freed up my mind and no longer feel this feature is necessary. However, I have to think about my workflow in a radically different way compared to my much used Digitone.
If you still want to copy all the, say, #1 patterns for tracks 1-16, then you will have to switch tracks and access the context menu Copy Pttn / PSTE Pttn functions. This may seem like a repetitive nightmare. Or, conversely, you can just program new Track-patterns from scratch. Or, do a combination of Copy-Paste and fresh entry.
I tried to explain this in my last post but probably muddled it up: Don’t think about putting a song together in SEQ mode. That is what SONG mode is for. Free your mind from thinking you have to create simultaneous music while in SEQ mode. In SEQ mode, all the 1-16 tracks will play their, say, pattern #3. But the #3 patterns, for different tracks, can exist in different parts of the song. Again, it all gets fixed in Song Mode. I had trouble understanding this, and I also have great difficulty explaining it.
Good luck!
3 Likes
Feature Request: Increase Metronome Range (esp. in the lower tempi).
Use Case: I make the canned-music for my students in a variety of speeds for practice purposes. Typically, 8-10 different-speed versions of the same song.
Workaround: An effective BPM of less than 80 can be achieved by setting the b.div for each track-pattern to a higher number.
Problem with this workaround: The change in b.div has to be executed on every track-pattern. But there are more changes. Now, the length parameter needs to be changed accordingly for every step. And we need to go to Song Mode and adjust up the length in beats/measures of all the Fragments. And, if there are time-based effects, those will need to be adjusted accordingly. In the FreeBeats review, he seemed to suggest that changing the effective BPM was easy. It is definitely time-consuming.
Now, I may be the only person concerned with this use-case scenario. But, please, please, dear Developer, is it possible to bring the low-end of BPM down to 30 (like it is on my Digitone)?
There is a second workaround. Start the project at a double BPM and double b.div. Then I can slow it down, let’s say, to an effective 40 bpm. This possible method adds a lot of confusion. I very much prefer displayed BPM to be the same as apparent BPM
1 Like
+1
To me it’s seems more 7.5 x 7
Ima be honest. the Woovebox is what the OP-Z should have been
3 Likes
Bug or feature?
When I make a multi-instrument track, composed of bass drum, hihat and snare, on Track A1, everything works fine. However, when I attempt the same using the Ar (arpeggio)or Pc (percussion) track (and maybe others, haven’t checked completely), the sounds don’t comply with the previously selected sounds on the BD, SN or HH track (or any of those tracks’ sounds, for that matter). The sound I get it filtered and distorted, and sometimes the resulting sounds includes various bizarre sweeps, like the device is haunted. Huh?
My understanding is that any track (except the Cd track) can be made into a multi-instrument track. Maybe there is some other setting associated with the Ar or Pc track which is causing the unwanted behavior, but I have yet to find it.
I am using the latest firmware. I performed a factory reset and the problem persisted. Wondering if anyone else can emulate (or solve) this problem. The obvious workaround is not to use those particular tracks as multi-instrument tracks, but I am curious what is going on, here. Thanks to anyone in the community who can enlighten me.
Just wanted to say thanks to the community for not posting for 23 hours on this thread. That gave me the opportunity to answer my own question from my most previous post. Here is the answer:
Problem: Using certain tracks for multi-instrument caused the resulting sounds to be different/wrong.
Solution:
Some tracks default to a particular octave transposition. Entering a multi-instrument drum track on the Ar, without first adjusting the default transposition from -12 up to 0, puts the resulting drum sounds down an octave. And, some of the weirder, “haunted” sounds I mentioned were a result of the filter resonating with these new/unwanted frequencies.
An interesting thing about the global transposition is that it applies to notes entered after the transposition is set. When I entered the multi-instrument pattern, then changed the transposition, nothing happened.
I just did some experimenting. It appears that individual note-steps inherit and are adjusted by the value-state of GLOB TRNS when the note is entered. I’ve only had a minute to get my head around this idea, but the implications are, among other things, the ability to enter different subsets of notes on a certain track in different transpositions. Woove!
Below are the default transpositions of tracks in their initialized states:
1/Cd: -12
2/bS: -36
3/Ld: 0
4/Ar: -12
5/Ki: 0
6/Sn: -13 (!?)
7/Hh through 16/A8: 0
EDIT: I was still having problems, tonight, that were not fixable using the above method. Specifically, I was wondering why a multi-drum pattern that worked on A5…freaked out on A1. To find the problem, I compared the A5 and A1 tracks, going through every page/setting. The culprit was: Track A1’s Osc Styl (Oscillator Style, which is found on both the Osc1 and Osc2 page), was set to Analog. If set to Mdrn (modern?) or Dgtl (digital), the multi-instrument drums will work correctly. This is very intriguing behavior, as most every menu setting in a multi-instrument track doesn’t do anything, defaulting instead to the settings from the “borrowed” tracks for each step.
5 Likes
The possibilities with multi instrument tracks are really blowing my mind. I did a simple experiment last night. I created two bass tracks. Set the ADSR envelope of one to be short and the envelope of the other to be long. Then created a third, multi-instrument track, on which I combined the long and short bass notes. All of the sudden, the bass part was way more interesting. And this was a super-basic example.
People talk about varying the music using conditionals and randomization. I am talking about something more deliberate. And using step modification of a normal (non-multi-instrumental) track to achieve what I’m suggesting…I think would run into the limitations of the unit (particularly settings that apply to every step)…not to mention that editing individual steps is time-consuming.
1 Like
Extended unboxing video
2 Likes
Thanks for the video. At about 1:35, you say “Since I already have tracks that are filled with steps in Song Mode 1, tapping play will play these tracks.”
It should be clarified that Play only works in Song mode when Fragments have been assigned.
It seems that, at some point, we would want the operating system to be open source. This is kind of a tricky proposition, however, due to the low-level optimization by the developer. Trying to dig deeper into the user-interface has been a challenge for me. I can’t even fathom what coding the thing would be like. But bottom line, the thought of having to rely on a single person to keep the WB working…is kind of scary.
I am hoping that, within 5 years, someone will produce a DIY tutorial on battery change.
That said it’s already working, and very mature for a new launch, so if you never connect it to the internet again, it works.
So much nicer than awaiting the next ‘essential’ software upgrade from NI etc
Battery is a good point - sounds like it is fragile to disassemble - worst case scenario is you have a permanent usb battery backpack.
Why would it ever need to be open source?
My only ‘gripe’ is mistrust of the write and play buttons. Have had many random play activations when no where near the machine. A tactile button would be nicer.
Would also like to replace the encoder with more of a fingertip dial flat with the screen.
I’d also like if I could add my own buttons - probably not too difficult if I used the current button accessible points and soldered to a bigger overlay in a bigger box.
But the hardware is what it is and perfectly functional in a tiny-already format.
Have to say I’m astounded after a week messing with this at the cleverness of the software design.
It’s so nice when music tech can still surprise you when there is so much sameyness out there, let alone in a budget box dominated by the IP effort that is baked in.
Closest comparison is the OP-Z and they’re both great. Wooze might benefit from a dedicated master button effects page approach for stutter, glitch and on the fly remix sort of macros that the OP-Z shines at, particularly given that the Wooze tracks are already identifiable as Cd, Bs, Ld etc
1 Like
Have any of you tried to stem export yet? Just curious how many tracks it can output and if the process is easy and not buggy (ie - polyend tracker exported stuff that was a little off tempo sometimes).