Well if the issue is only the last step of pressing record again to stop recording maybe that’s something that can be reverted back to the way it was on the previous version? I can see how having record automatically turn off might be more universal and a bit more conducive to live performance because it’s more “careful”, less prone to accidents, etc…
I definitely don’t like the idea of having just a two button press looper, I like the idea of it being more of a “tape” then simply a digital looper… but I could probably be convinced. I think what I miss the most is being able to arbitrarily change the loop by adding cues within… cutting the loop in half or doubling it might be more “musical” in some contexts (especially if you’re looping with a clock signal over i2c) but it also seems to take it away from the “tape” metaphor make it more like a live looper… My gut feeling is that this foot in both worlds is limiting and makes it not quite doing one thing or the other as well as it could. These metaphors are only useful where they’re useful, so “this is not enough like real tape!” is not by itself a legitimate criticism, I realize, but tapping into that tradition of music was one of the things I liked about v.1
Okay so, solutions. To me the thing that seems most obvious (although maybe way too much work) is that tape mode should either be fully “tape” mode (more like v.1) or it should commit to being “loop mode” — focused on time synced live looping, clear buffer on start up (don’t need a 6hr buffer), maybe your two button press loop option. Much simpler interface (more similar to delay and synth modes in their simplicity—I’ve pretty much already learned them, whereas tape mode i have to refer back here every time). Is there a world where this mode doesn’t even require an SD card? People would be sad about losing the tape, and the ability to play back recorded audio from previous sessions, but maybe that’s a sacrifice that would be worth it for a newly imagined instrument geared towards use as a looper (which the current version seems to only halfway do). Is that the kind of sacrifice you and @baleen are asking for with this version?
I’m not advocating for this personally, I’m just trying to distill how you think this can be improved. For me, improvement would mean moving away from the looper pedal metaphor and more towards the tape machine metaphor—play means playing till you press it to stop and can continuously be sped and slowed and reversed, record means recording till you press it to stop with control over the overdub, cues persists and can continue to be added to manipulate loop points like chalk on a tape (okay the metaphors are falling apart lol, please check me if I’m out of pocket with this). This combination of functions is not easy to imagine on this interface: for example, if you set cues via the switch, you can’t also use it to continuously speed or slow or bump the “tape”.
In the beta’s current state, tape mode seems like the weak link to me as well (and it’s got the most glitchy/weird behavior where it’s difficult for me to even report whats going on because I don’t know if it’s reproducible or what’s happening exactly). I tried doing some loop tests to emulate @mlogger 's workflow as described, and it seems like if you press record off right before setting the loop end then nothing gets recorded? And sometimes it seems like the loop points don’t get put where I expect them—sort of like when you set a cue point to loop on v.1 and then you pass a cue point so when you set the final cue to begin looping it loops from the middle cue point… except there’s no cue points here so I must be doing something else wrong? Or there’s a bug? Sometimes things don’t seem to record at all if I’m toggling record on and off when looping (trying to punch things in). I’m not sure what’s going on there because it works sometimes and I can’t figure out what the difference is…
I bring up this idea of a “loop mode” because it seems like that would be able to have simple enough controls where it might be able to fit into the “language” of “delay” and “synth” modes… whereas the current tape mode has an almost entirely different language both from the other modes and from the previous version, making it difficult to learn… or it’s just buggy in it’s current state and I’m a nincompoop which is entirely possible and likely. I suspect it’s a combination of the two I hope this long post is helpful somehow.
TLDR: I would be sad to loose some of the tapeyness of w/ but maybe the halfstep towards a livelooper/livesampler with this firmware indicates that that’s the proper space for the “tape mode” to live in? And that it should fully embrace that?
PS if this “tape mode” became a more simplified “loop mode” would that make v.1 support more likely? I would hope so, but v.1 support is probably completely untenable in either case (unless it becomes open sourced at a later date, which I got the sense was implied in the livestream, but I may be wrong about that…)
PPS this post was so long it had a TLDR and a PS, smdh.