The Great BitWig Migration

[H20nly]

You always seem to have some well thought out solutions so whatever it is you come up with I'm sure to support.

I'm pretty sure the spec team would strongly disagree with you on that point

therein lies the problem.

[regretfullySaid]

I brainfarted as far as being able to switch arrangements, in which Tabbing seems the simplest idea for going about it atm.
That would be nice...

[H20nly]

my concern with that would be the moment between being on Tab A and switching to Tab B... it seems to me that would be the moment of catastrophic failure in a live situation as the "engine" starts up on Tab B. it would be cool if you could enable the tab, but keep it idle so it's ready at a moment's notice...

Tab A
queue B

Switch to B
queue C

Switch to C
queue D

and so on...

then again maybe that's what's happening... but an hour set consisting of at least 12 (or more) song structures and their routing and effects seems like a bit much to have all queued up.

[regretfullySaid]

Well, switching arrangements live isn't something I thought about, but I don't see why it would be too different from switching scenes, or even to a different part of the timeline in the same arrangement....not to say that it would be easy...

Personally I think live-wise the user should merge sets and and do the maintenance, that includes pre-determining their return setup.
This is why having a master template is important, and constantly saving it. You start to average out what's most important to you and how you work, to the point where you don't really need to add much anymore, everything is already laid out for you and you can get straight to producing and performing.
And isn't the end goal to blur the line between the 2?

Otherwise Bitwigs approach to toggling audio engines seems good at this point in time for switching arrangements.

Actually, something I did for a live set for someone was make small arrangements 'per scene' through the extensive use of clip envelopes. Thing's like automating volume, filter, etc, so that even though the loops were 4-16 bars, they evolved so much over time that it didn't overall repeat until 64-128 bars and each scene sounded like it was playing something laid out in Arrangement. I assume Unlinked Clip Envelopes are still an overlooked tool? It's powerful...

BUT SINCE YOU CAN'T EDIT AUDIO CLIPS IN SESSION VIEW you still have to make cuts if needed in Arrangement, but the point being is that one can get used to porting your arrangements back to session (which we've already been able to do and the ''consolidate to new scene' addition in 9 is very handy') so, I dunno.

While other hosts can have handy things like tabbed arrangements I try to think if it would fit into Live's aesthetic, and I'm not sure what could fit, especially when what I just previously described has been available and not that tedious to do.

Either way, Angstrom can come up with the hows.

[H20nly]

Well, switching arrangements live isn't something I thought about, but I don't see why it would be too different from switching scenes, or even to a different part of the timeline in the same arrangement....not to say that it would be easy...

yeah, agreed... but if there are major differences in the 2 arrangements i would expect more crashes. as much as it would be nice to arrange this via templates, someone will always want more.

"i was playing my 65 track set with 12 sends and 27 effects and clicked on Tab B to switch to my 55 track set with only 9 sends and 26 effects when my DAW crashed" i'm switching to /reaper/logic/bitwig/live/studio1/blah fuck you DAW! i'll show you through lots of angry posts how angry i am!"

[Machinesworking]

^^^ A quick test of switching Sets VS switching tabs in Bitwig and there's no discernible difference in loading time. the only advantage would be have a whole project of sets in Bitwig VS trips to the menu in Live.
So score that one as 'possibly' better.

[H20nly]

so it's an integrated set of shortcuts to sets

[Machinesworking]

so it's an integrated set of shortcuts to sets

I will say that Kontakt and Machfive 3, the Samplers I used to swallow up memory like fat guys seem to load memory into RAM and swap files because in both DAWs the initial loading of the sample library was brutally slow and each subsequent load was about 1/5 the time. So if you're going to load large sample libraries into a Live Set during a performance it would be smart to 'preload' all the Sets once as that would probably speed up the loading time significantly. So with Bitwig you have a very visual way of knowing whether you've done this in the form of tabs.
I'd say that's a win for the wig, but only barely.

[regretfullySaid]

Live's Sampler should've been Mach 5 before Mach 5

[Machinesworking]

Live's Sampler should've been Mach 5 before Mach 5

If Live's Sampler was even half as good as Machfive 3 I would be the biggest fan of Suite ever.

[TheNobleNemesis]

Why is this thread not dead?

[TheNobleNemesis]

Oh wait, I just bumped it.

Aaand I did it again. Oops.

[eyeknow]

something to do anyways

[timday]

Why is this thread not dead?

Because after like 45 pages Machinesworking raised a sensible point that was able to be tested. Now that's done though, let the drama recommence.

[H20nly]