Skip to main content

Extra Stuff in Arr from Snippets

Posted

Hi.

I'm not certain this is a bug, but it might be.  At any rate I don't understand this.

I have a Snippets page with saved scenes in memories A - F.

From a dead stop, I proceed to play my memories, A- F in order, doing nothing else.

This is what I got when I did  'Make Arrangement from Last Session' after.

How can this happen?  (if not a bug)

Should I not just see containers A - F in order, and nothing else?

 


Thu, 2024-02-01 - 04:39 Permalink

Do you have a version before the save? I opened it erased the arrangement saved re-opened and could not reproduce. 'Make Arrangement from Last Session' was greyed out.

Thu, 2024-02-01 - 10:16 Permalink

Your root container is set to align all children in a row. That totally rearranges the result.

The conversion should reset that switch though, so this is indeed a bug. As a workaround, just disable this switch on the Arrange tab before you convert.

Thu, 2024-02-01 - 15:02 Permalink

Thanks for the replies.

New attempt this morning, making a video this time.

Even though the switch is off, the output still doesn't quite make sense to me.  It is still not the simple sequential set of containers that it seems I should get here.

https://www.screencast.com/t/kfHnlXth7ui

I've attached the file from before doing the capture.

P.S.  Also an open question, for me, is why clicking on memories A and B wouldn't start the playback until after I rolled the dice once.  (This may be as intended.  If so, I would just like to understand it.)

Thu, 2024-02-01 - 15:17 Permalink

There's a bug with starting playback from a memory button. Is fixed with coming update.

The converted structure is condensed and redundancy is removed. Some containers may span multiple "buttons" depending on what was actually playing and for how long.

Thu, 2024-02-01 - 15:41 Permalink

The converted structure is condensed and redundancy is removed. Some containers may span multiple "buttons" depending on what was actually playing and for how long.

If that were not done, then would we have just linear containers of the memories as they were played back in order?

I'm not sure what particular operations might be made possible by the result that comes out of such processing.  Maybe there are some. (?)

What I do know is that what I really want to do after capturing a Snippets performance is to play it back and quickly, easily edit out the parts that don't "pass the audition".

I will never not have that desire.   Doesn't everybody?

 

Thu, 2024-02-01 - 15:47 Permalink

With things as they are now, is there a procedure using snapshots that would get me there (collapse the extra stuff, while not losing the designations of the Snippet memories stamped on the containers)?

I know I need to look more into Snapshots and how to use them!

 

Thu, 2024-02-01 - 16:05 Permalink

If that were not done, then would we have just linear containers of the memories as they were played back in order?

No. There is no such "order". Memories are just shortcuts to starting/stopping a preset selection of snippets whatever they are currently doing. You can schedule or unschedule any snippet at any time in the middle of something. Memories also may have snippets in common. These just keep playing where they currently are. A memory button does not reset all snippets to the start.

The condensed structure can be very helpful. If there's a phrase that doesn't work, you only need to delete it once even if it is playing for quite some time. Also, if a phrase is playing for the duration of, say, five "buttons", it will keep looping away according to its own logic. No artificial splitting into pieces just because the user happened to press a button.

Thu, 2024-02-01 - 16:07 Permalink

is there a procedure using snapshots that would get me there

You can drag a memory slot that you like directly to the arrangement.

Fri, 2024-02-02 - 16:54 Permalink

You can drag a memory slot that you like directly to the arrangement.

 

Nice, got it!

 

 

Sat, 2024-02-03 - 16:28 Permalink

You probably unscheduled one snippet in the middle of it

No, not the case.

For me this is reliably reproducible.   It happens to the last container every time.