the more i think about it, the more i like your approach to just extend what we already have in tracktion.whyterabbyt wrote:Shouldnt do. We already have loop recording, we already have a view which shows us takes, and those takes can be split to separate new tracks. The only thing needing added to replicate what POLAR seems to do is as TSC seemed to suggest earlier; a slight change in which takes get muted or played.klangbastler wrote:this all is already sounding pretty complicated to deal with, without getting used to it and knowledge about dropdownmenus and so on ...
Strictly speaking, I'd have thought there were only a couple of commonly used combinations of mute/play behaviour (regular looping is mute everything except the current take, the basic POLAR type looping seems to play everything but mute the previous take), but I suggested what I did because that would cover all possible variations anyone might ever ask for. Many are probably redundant, it could easily be simplified. Maybe all it needs is a switch between 'mute all previous takes' and 'mute last take only', or something similar, Im not sure, I hadnt worked out what might be useful to other people.
The UI Im suggesting for muting/playing takes I think makes sense, though, because its based around something we're already familiar with; mutes and solos. And I also think that being able to manually choose to preview more than one take at a time from the stack of takes might be useful in other circumstances (and if that happens, then maintaining the mute/solo state when unpacking the takes is only sane.)
But its only a hairsbreadth away from existing DAW functionality, ie loop recording. Making it a special case is what's not easy or obvious. Making them both different variations of the same slightly extended functionality is easier and obviouser(*)... Loop-recorded takes becomes slightly more like tracks (because they're already nearly there, albeit optionally) by making them display like tracks by default, and adding mutes and solos to them, and there's a little bit more control over which takes get automatically muted/solo'd and which dont when the loop restarts. That's it.that's why i believe a dedicated dialog like in the DP example rally makes sense. things have to be easy and obvious to stay creative and not get caught in dealing with functions of the daw.
(*) but with worser grammar.
and i still see the beauty of the simplicity of a dedicated looprecording interface.
but it's true, that tracktion is already almost there with looprecording and its takemanagement. it just needs to be brought a little further.
so this probably makes more sense, then to develop another interface.
now the idea is out, let's see what TSC will bring to the table