@Woovebox So glad I found this thread! I’ve mainly been active on the OP-1 Field thread on here. Missed the boat on the first batch of Wooveboxen - have signed up with both my email addresses and send an email to info@ as well though I’m in Adelaide so hopefully shipping is easy and I can nab one from the next batch.
Will start reading through this whole thread on my lunch break today, looking forward to it. What a super awesome little product. (little in size, not in scope)
Got a few synth videos on my channel and planning more, will definitely do some with Woovebox when I get it - more video tutorials will be helpful for people.
Don’t burn yourself out - but it’s very nice to see a developer so responsive to feedback and so on, picked up on a lot of that from Freebeat’s video on the Woovebox.
Moved from Chrome to Opera on Mac (12.3.1 Monterey) but the issue is still there: the device hangs at “rcv 99” on the firmware update. The same problem is still there when trying to upload samples.
On the other direction, song dump is working fine.
The connection on Mac is a bit unstable. I am on the latest version and latest chrome.
When sending samples, I had to keep pushing buttons on the woovebox that kept the Bluetooth connection alive. I am not sure if this would help updating, because updating worked for me somehow.
Tried pushing buttons but no luck. the connection is stable; it seems the device is not getting that the transfer is finished. It hangs at 99 both on firmware update and sample loading.
UPDATE: I managed to perform the firmware update on an android phone. Sample loading is still not working on mac. Now I have to figure out how to make a drag and drop on Chrome on Android
On Ubuntu Linux 22.04 running both Firefox and Chrome, pairing with Wooveconnect failed. I followed the instructions for configuring Firefox. My WB is showing as “Connected” in the bluetooth settings of my computer. But the Wooveconnect browser window just says “Disconnected”. The pop-up window displays fine (though I have no idea what it’s for, nor can I interact with it.
I am pretty certain this is NOT a dev issue. The research I’ve done tells me that Linux has a flaky implementation of MIDI bluetooth. A few years ago I was working with a MIDI bluetooth keyboard, and I fell down a technical rabbit hole getting the thing to work.
Next steps: I will try to pair my bluetooth MIDI piano keyboard to my computer. If I can get that working, maybe that’ll unlock the problem with Wooveconnect.
Great news! I got Wooveconnect working on Ubuntu. I hope I am reproducing the steps correctly. Here goes:
In a new tab: BlueZ with MIDI over BLE Support
This page describes how to enable MIDI bluetooth in Bluez (bluetooth server). I guess that it is not configured by default. Follow ALL the instructions on this page.
In another tab: http://www.bluez.org/
Scroll down and make note of the latest version number. While following the instructionsin step 1, above, replacing the version number in the commands with the version number of the latest version.
The instructions in step 1 include a reboot of the machine.
Finally, I only got this to work on the Chrome browser. Firefox is still a no-go, even after following the directions. I’d love it if someone could shine more light on the Linux/Firefox issue with Wooveconnect.
Hope this helps. It is going to take a community to debug all the issues surrounding different browsers/operating systems, etc.
After some very superficial tinkering I’m impressed with the woovebox.
Once you get your head around the modes - and realise you are in a pages system and what those pages offer - it starts to become more navigable.
There appears to be a big framework in the palm of your hand with this, but needs some learning.
It is well more than half way between a Pocket Operator and the M8.
With use, for some who are prepared to learn it, it may be more appealing than the M8 as a sketch box as the UI is cerebral rather than a complex screen/tracker. M8 is amazing but this is an alternative.
It fits my portable tool option for chord progression, beats, lead ideas. With very decent tweak capabilities.
Key hurdle is you need to invest in figuring it out. Once I get fluid with that, what would I rather pull out in an airport? I think maybe the woovebox
I also find it way more easy to go from idea to loop with the woovebox than my m8. I have mine for 3 days now and can’t put it down. It is absolutely brilliant.
It made me rethink my whole gear setup and workflow.
I made an account just to comment on this thread, hi hello
I really like my woovebox, I found the first day or so quite frustrating but reading through the (pretty good) online manual has done a lot to illuminate the way things are and the ways I can be doing things. I still feel like I have a lot to learn (so much untapped potential) but after a few more days I feel quite comfortable laying down a bunch of tracks and navigating through the menus. This will take some time but I think it will keep paying off
I really enjoy how easy it is to lay out a pattern, add some variation per step, and just go wild in jam city. Is there a way to affect per track volume in live mode without breaking the flow?
Also, is there a woovebox forum or discord or something? I’d love to be able to chat in a dedicated community for this thing.
Unsure about a dedicated forum, but this place is pretty great - there are some clever cookies here. The OP-1 Field thread on Elektronauts is arguably better than the whole OP-1 Forum. But yeah I’ll join a dedicated Woovebox one should it appear.
I don’t have one yet, can’t even order as out of stock - but have read the manual etc. amazing unit. The M8 never really interested me because the tracker workflow without keys is something I felt would be very slow to get ideas in. The pocket operator style note entry on Woovebox is the best option for a device of this size I feel. I could live with that.
Really can’t wait to get one. I only have one pocket operator (PO-20 arcade) and an Orba2 (the sampling one) I’ll probably finish up some videos on those and move them along. OP-1 Field is my main portable music gadget, but Woovebox does a lot more in many ways and is far more portable, it can go where OP-1 can’t. They’ll complement each other really well too I feel, especially as both have BLE.
I had my first Woovebox dream last night. I was in a grocery store. In the checkout line with a parent was an eight year-old kid mindlessly playing with a Woovebox, turning the knob with no real attention to what they were doing, as if it were a fidget spinner. I was somehow able to hear the audio output.
My dream self-analysis is this: I would prefer that the Woovebox end up in the hands of adults (or those with the discipline to learn it). My reason is selfish: People who’ve learned the WB are more likely to give constructive comments on the forum.
I checked out the Reddit page on the Woovebox. No one answering anyone’s questions. A lot of heat but no light. I suppose that is to be expected, as the Woovebox is so completely brand new.
Thank you for the suggestion. I de-reddited myself around the time of the third party app death announcement so I am selfish when I ask for a discord as that’s the only thing I really use any more.
This place seems nice though so I will keep coming here for now
I get you, the community on the woovebox is still fresh and new. Give it some time to grow, it will get better once more people will get their wooveboxes.
I am in the process of making a project (scrolling music for my students) using the Woovebox for the audio. I kept things pretty basic. I’m definitely not winning any prizes for artistry on this one…just trying to follow-through on a complete workflow.
What I don’t understand is: The song I dumped to Wooveconnect is exactly 1:00 long. But 12 seconds of extra silence was placed at the end of the resulting .wav file.
I am guessing the reason is: 12 seconds is long enough to account for a very long reverb or delay tail at the end of a song?
This behavior is by no means a deal-breaker, as I can automate the trimming of the audio based on the length and tempo of the song. Just curious.
I really hope discussion and support can stay on a forum like Elekronauts. It’s just so much easier to keep track of issues in this format rather than Reddit (or worse, Facebook). Bookmarking, notification, a followable chronology–all the stuff we need for tech support, etc.–they’re all much better on this kind of forum technology than the kind that Reddit uses.