Posted
Hi.
Consider a snippets matrix like so:
On the left side we have single-Figure snippets. These are the one we multi-schedule, dice, and save to snippet memories (SMs), which we then accumulate in libraries.
On the right side we have mixed snippets, each one a full band groove, the result of dragging saved SMs to the Structure timeline and from there into the snippets matrix. (These also can be accumulated in libraries by dragging back to a library from the Structure timeline.)
Now, with all those full-band grooves right at-hand as snippets in the matrix, the need is to play them back one-at-a-time. IOW, the playback needs to be exclusive, exactly as-if they were all in the same column. SImply put, we need to get around the limitation of having only at most 16 rows. As the pictures shows, it is very easy to exceed this.
#1 One answer would be to allow an arbitrarily large snippets matrix. In general, this would not be impossible to do - it's the approach taken by Ableton and Bitwig. I wouldn't be against this at all, if it is practical to implement in Synfire. Possibly though, it would be a real &#%# to implement!
#2 OTOH, another answer would be a switch that changes the behavior of the matrix playback so that only one snippet can be played back at a time - again, as-if the matrix were one giant column.
Just guessing, but I think #2 might be much simpler/quicker to implement than #1.
And, even if #1 is an ultimate goal, #2 is would be very useful on it's own in any case.
Sa., 01.06.2024 - 22:16 Permalink
I've been toying around with this idea in my head as well, though I have yet to implement multi instrument snippets for fear of complications down the line. My thought was to be able to drag snippets into each other using a "merge" or "replace" mode just like you can for a harmonic context using shift/alt/ctrl and avoid the extra steps of, Copying SM to library, Copying to Arrangement & Copying back to Snippet Grid. Just my 2 cents.
Sa., 01.06.2024 - 23:08 Permalink
The issue is usability. Scrolling a large grid is not convenient because ideally you want to see all of them at once to know what's going on.
Absolutely!
I would likely find a gigantic grid too large to be practically useful.
However, I would suggest, say, 32 x 32 (twice the current max) as small enough to be practically operable while bumping out limitations that are currently hit in real life.
Example: the columns of mixed snippets in the picture above. That's 32 slots that could be in one column to get exclusivity (w/o the suggested behavior switch).
I also note though that someone might actually say "Yes, please" to a super-sized grid because by good arrangement of content they would never need to leave the local area to do what they want to do next. The neighboring local area would be quick and easy to get to, as compared to trying to navigate randomly across a continental landscape.
Also, a grid much larger in one dimension and smaller in the other could be good as well. You could linearly lay out a whole composition like that, while letting any part of it run live for an arbitrarily determined-at-the-moment amount of time.
--
Regardless of the grid sizes available, having the suggested exclusive switch for playback behavior addresses exactly what you say above - being able to see a full screen of snippets at once and have one-at-a-time exclusive playback of any snippet without it mattering where on the screen it appears.
So., 02.06.2024 - 12:34 Permalink
If you want to merge snippets, use the phrase editor and its headers column to select/copy phrases and/or individual parameters.
A general drag/drop mechanism would not be much faster. You'd still need to decide which phrases and parameters to replace in case of collisions with dialog boxes popping up. Selecting a phrase (instrument header) and Command-C/V (Copy/Paste) is a as intuitive as it gets.