Pooling Patterns of item

[Ivannn Bennnettt]

It's connected items (midi and audio) inside one container between copies of them.

for instance:

[foxAsteria]

You can use the "propagate" actions to propagate changes between item copies. Maybe that helps?

[Ivannn Bennnettt]

Originally Posted by foxAsteria

You can use the "propagate" actions to propagate changes between item copies. Maybe that helps?

Thanks, yeah I know it's good feature but I mean kinda pattern for group of items.

[Ivannn Bennnettt]

added pic
I hope it would a bit clearer what I mean

[foxAsteria]

Looks like you want pooled regions. It's a good idea.

[Ivannn Bennnettt]

Originally Posted by foxAsteria

Looks like you want pooled regions. It's a good idea.

I wanna pool what inside)

[foxAsteria]

Originally Posted by Ivannn Bennnettt

I wanna pool what inside)

So...pooled item groups?

[Ivannn Bennnettt]

Originally Posted by foxAsteria

So...pooled item groups?

Item group in Reaper it's rather fasting one.

That one is pooling and propagate whole stuff inside itself between copies.

[foxAsteria]

Sorry I can't understand that last post at all, but perhaps subprojects could work for you. They are separate projects that can exist as Items in another project, so I think any edits you make to that subproject should occur in all the item duplicates.

I do, however, wish we had pooled audio items that worked just like pooled MIDI items, and pooled item groups would be a natural extension of that.

You might want to edit your post title to "Pooled Item Groups," since that seems more to the point and could attract more interest.

[Ivannn Bennnettt]

Something like that but automatically

[foxAsteria]

Pooled item groups. Yea, I get it. Did you try subprojects?

[Ivannn Bennnettt]

Originally Posted by foxAsteria

Pooled item groups. Yea, I get it. Did you try subprojects?

one gif better than thousand words)

Yeah I've used subpoject it's great thing)

btw I'd like have script new subpoject via copy

and marker for this one

[enroe]

@Ivannn Bennnettt:

Your problemmm of "pooling many items" is
the same as mmmy problem. Look here:

--> https://forum.cockos.com/showthread.php?t=205643

Greetinnngs!

[Ivannn Bennnettt]

Hey)
That looks quite similar.
Reaper is really lacking one

[enroe]

Originally Posted by Ivannn Bennnettt

Hey)
That looks quite similar.
Reaper is really lacking one

Yes yes!

If you call it "pooled patterns of items"
or "pooled box (with items inside)" is equal.

Every time you think of repetitive patterns -
which are typical in almost every music style -
you come to think about "pooled patterns" ...
this is ubiquitous.

[deeb]

i told in other thread already: this looks like Area Selection feature, with added feature of pooling area selection which would be really good. But first area selection must be working.

[enroe]

Originally Posted by deeb

i told in other thread already: this looks like Area Selection feature, with added feature of pooling area selection which would be really good. But first area selection must be working.

Not really.

An "item selection" is a temporary selection of items
to move, copy or cut off.

An "item pattern" (or item-box) is a permanent summary
of items, which is and remains visualized by a box. In other words,
the arrangement window changes because, in addition to bare items,
you also have these item patterns (or item boxes).

The visual representation as boxes is important if you don't want
to sink into chaos. But it is also important because you want to use
these boxes as references. In the Reaper language this is called
"pooling".

Look here: "Pooled Boxes" or "Meta-Items".

[enroe]

Originally Posted by foxAsteria

Pooled item groups. Yea, I get it. Did you try subprojects?

Yes, subprojects are one workaround.

There are 3 main disadvantages with subprojects, if you use
them for "repetitive parts" in the arrange-window:

1. The creation of subprojects is tedious and cumbersome.
You need to rename the subproject, to create regions
and to make it run synchonously (but these problems
could possibly be cured by an improvement of subprojects)

2. With subprojects you loose all the routing and all fx based
on that routing. You can create subprojects from several items
or tracks, but you will always loose all your routings and fx.

3. With subprojects you can synchronize both, parent and
subproject, but you have to be very careful: You must set
the same loop for both, and you have to fiddle around to
open both project-windows so that you can see both, parent
and subproject, at the same time and synchronized. In the
fast practice this is at least uncomfortable.

-------------------------------------------------------------------------

BirdBird put it in words:

Originally Posted by BirdBird

It is almost always necessary to tweak the elements of a song in
the context of the song. Attempting this with subprojects would be
like trying to open a door in another part of your house using a
string tied to its door knob.

[MonkeyBars]

I have created my version of this feature in ReaScript: it's called Superglue. Check it out here.

[mtk]

This is great idea. I see it as pooled subprojects, without the need for rendering and using separate tabs to edit it but working more like a track folders with a pooled item representing what's inside the folder.

And having it solved in this way solves the need for fx containers to some point (not completely ofc.), because it would be possible to do all the routing inside that folder.