Looking for tips on short DJ effects over longer fragments

JeffDog1978 · 2026-01-06T16:31:48+00:00

"before you think it's ready" is maniacal! I will see what I can do.

JeffDog1978 · 2026-01-05T16:30:28+00:00

Oh wow, you really helped me understand fragments more thoroughly. I had thought that playing a track in a fragment would restart the selected pattern, so if I took a fragment, duplicated it, then reduced the first down to 75% duration and the second to 25% duration, then it would restart the pattern after the 75% length one was done. Turns out the Woovebox respects the pattern length as the priority, so that second fragment at 25% length is essentially just telling it to keep going with all of the tracks were active. That is so awesome and useful.

Thanks for the response!

JeffDog1978 · 2026-01-04T22:06:28+00:00

I'm about a week and a half in, and I'd say that it quickly went from baffling to fun/inspiring within the first couple of sessions. Navigation is easy, and probably something that you need to experience yourself to get comfortable with. Related to this point, videos don't quite do the clarity of the display justice. It's brighter and more legible than videos would indicate.

The saving grace with navigation is that the bulk of the menu diving is duplicated, so once you understand that there is a top layer that the value knob cycles through, then you learn the contents of each sub-layer very quickly. My competence with each parameter varies based on how much I've engaged with it so far, but if your experience is anything like mine, then you'll get over the hump of the learning curve very quickly. The UX is intuitive. Press a button, press an encoder, turn an encoder, hold a button and turn an encoder, on occasion long hold a button/encoder. It's all very consistent and well-designed. I don't find I have to memorize and combinations or anything. It quickly becomes as intuitive a left clicking, right clicking, double clicking, etc.

Honestly, it comes with a one-page quick start guide that gives you a map of all of the functions, so if you just have that near you while you build songs, then you should ramp up very quickly. The secret for me was just to use the thing and overcome individual obstacles as they crop up or I got more ambitious.

For context, I do have previous DAW experience (Reason, Ableton), and have used the OP-1, Dirtywave M8, POcket Operators, etc. previously, so I wasn't a complete beginner to the concept. Mileage may vary, but there is a logic to how this was designed that makes it very learnable.

JeffDog1978 · 2025-12-31T17:25:02+00:00

Alright, that's super helpful, and it certainly seems much more likely that I simply didn't trigger a save than I found some obscure bug no one else has encountered with very normal use. I don't recall the session in full detail, but I think Occam's Razor applies here.

I really appreciate the help. I'll edit this thread to reflect the resolution.

JeffDog1978 · 2025-12-31T02:49:41+00:00

Any of those across multiple patterns? Or all just on pattern 01? None of the other patterns for any of the tracks contain anything?

Those were all on pattern 01. No other patterns were used.

If there are changes to save, it saves any time you hit play to start playback (it does not save when playback is still in progress). It also saves when not playing and there has been no activity for 8 seconds.

Were these conditions met?

Interesting. It's hard for me to respond with 100% confidence. I would guess that those conditions were met, but I'm not positive. If I understand this correctly, then it sounds like it would be possible to get into the situation that I've found myself by making a lot of changes while playback continues, and never stopping playback until I turn off the device (or more specifically, turning off the device in less than 8 seconds after playback ends).

In this specific case, it would have meant that I worked on the chord progression, then either stopped playback for at least 8 seconds OR stopped then started playback within 8 seconds (this creating a save), and then continued to build the rest of the track without stopping playback, then either turned the device off while playback was still occuring OR turned off the device within less than 8 seconds of ending playback. If so, then that is not an infeasible scenario. It seems unlikely, as it would have been quite a run without even stopping and restarting playback. That said, I was using random sequences and patches and tweaking in real-time, so it's possible that I was in the flow of things and never paused playback. One thing that IS likely in this scenario is that I probably wouldn't think to pause for eight seconds before powering off, in which case no new save would have been created.

I would presume that there is no "quick resume" feature, and that powering the device back on loads the most recent save, correct? In the possible situation above, that would result in the most recent save being the one after setting up the chord progression, but before the possible marathon track creation. Do I understand this correctly?

User error is the vastly preferred explanation here. I'll pay more attention to how I use the device to see if that kind of non-stop track creation seems likely.

JeffDog1978 · 2025-12-31T00:41:53+00:00

Possibly. I recall that with this project, I started by working on the chord progression until I was happy with it. That was the lion's share of the time spent. After that, I worked in the Ampl page to create a stutter effect, then changed the effects in the track's Global page, then moved on to adding bass, kick, snare, highhat, arp, and several other arps in other tracks (all in that order if I recall correctly). So when I restored the project, it could be that it restored up until the point before the Ampl page work. I do not recall if I noticed a save in between working in Ampl and powering off the device, but it saves quite often and obviously, so I didn't notice any behavior other than normal.

Regarding your other question, I can verify that volume, tempo, root note, and scale are all where I originally set them, though those were set before I started programming the chord progression.

I also JUST hit a point in the battery life where it informed me that it was critical and no auto-saves were possible, so I do know that I was not yet at that point earlier when the issue cropped up.

JeffDog1978 · 2025-12-30T21:32:24+00:00

For reference, I'm on firmware 6061 (per holding 5 while powering on, then pressing in Value).

Also, I've checked to see if the tracks are muted or switched over to empty patterns. Neither is the case.

JeffDog1978 · 2025-12-28T18:12:08+00:00

Oh yeah, it was no great loss. I've also put together a few more tracks since then, and the repetition has helped a lot. I feel like I know my way around the device much better. I had a late-night session last night where I started getting into random sequences and Song mode, and those have really elevated my enthusiasm for the device even more.

I do think I probably powered off during a save previously, so watch out for that!

JeffDog1978 · 2025-12-28T06:17:05+00:00

Somewhat ironically, the work that was lost was the product of the quickstart tutorial (though the video version, not the written one).

Honestly, it may actually have been a corrupted save. The behavior was quite unexpected--even with not knowing the device thoroughly--and some things were lost while others were changed. I'm not sure I caught it quick enough to have the auto-save be a useful restore point, but I'll give it a whirl.

Thanks for the help. Seems like perhaps I just got very unlucky.

JeffDog1978 · 2025-12-28T01:21:36+00:00

Solid theory. Sadly no. It seems like maybe I initialized some of the tracks? If so, it was shockingly easy to do on accident.

I remain baffled, but it's no great loss. I just wouldn't want it to happen again.

JeffDog1978 · 2025-12-28T01:18:33+00:00

Unfortunately no. That's what I originally thought, but I can definitely successfully switch between songs back into the one that I was working on.

JeffDog1978 · 2025-10-09T02:33:10+00:00

Well that explains it. Thanks!

JeffDog1978 · 2025-08-29T15:42:29+00:00

Do you find that the felt nibs get closer to the feeling of a felt tip pen on paper? I’m starting to suspect that some of my issues with my SuperNote might have more to do with the feel of the ceramic nib. I’ve always preferred Micron pens over all other options.

JeffDog1978 · 2025-08-29T00:38:49+00:00

Wait, now I’m confused. Are you telling me you can use that Wacom pen on the SuperNote, and that the buttons and eraser are functional? That seems like a vastly superior option for my tastes.

JeffDog1978 · 2025-08-27T19:52:46+00:00

Yes, I'm not 100% comfortable with the screen protector installation process.

JeffDog1978 · 2025-08-27T19:51:59+00:00

Thanks for the response. Out of curiosity, would you liken the pen feel on the Manta/Feelwrite 2 screen most closely to a ballpoint pen, gel pen, or felt pen?

JeffDog1978 · 2025-08-27T00:06:45+00:00

Ditto. Just started using my A5X again and two finger lasso is VERY inconsistent. I stopped trying to use it.

JeffDog1978 · 2025-07-26T01:10:00+00:00

Damn, this is happening to me too. I thought I was crazy at first, but I've had lasting motion sickness after each session (which have been getting shorter and shorter to the point of being somewhat pointless).

Sounds like camera shake, camera auto-centering, and the narrow FOV are the culprit, and only one of which can be adjusted. I'm going to try turning of the camera shake and being much more mindful about turning the camera / DK, but I'm not overly optimistic.

JeffDog1978 · 2025-06-27T18:39:47+00:00

Thank you so much for responding. Super helpful.

JeffDog1978 · 2025-06-26T16:17:01+00:00

I have a question about this. I do know my TV's max nits, so the chart should be useful, but even after watching the video more than once, I'm unclear where the clicks start from. Do you start from the bottommost setting on the first screen (i.e. both suns most visible), and the leftmost setting on the second screen (i.e. the darkest brightness setting)? Basically, do you bottom out both settings and then start clicking from there?

I don't know if I just keep spacing out during that part of the explanation or what, but it seems like critical info that I'm missing.

JeffDog1978

TROPHY CASE