When working on big presentations (100+ scenes), it is difficult to make sure changes performed were limited to what was intended. It would be great to have a tool that can either track changes, or compare two presentations scene-by-scene (sort of like a txt diff tool, or Acrobat’s compare feature… though hopefully less buggy than the latter).
Related – I find I accidentally shift around content when scrolling through the scene pane, or scene structure panes.
It is a sales presentation featuring all of the clients products and educational content. No way around the number of scenes unfortunately.
When starting on a major update, the previous presentation is saved as a new version and then edits are performed. The issue is that in incorporating the new scenes, we are always worried to mess up old scenes by accident (mainly the order due to the issue described of it being easy to move a scene by accident). This is again a concern for any minor revisions that are requested post-deployment.
A simple thing that could help is to be able to export the scene list as some sort of text / tabular file to make comparison of the scene list between new and old easier. This way we could easily verify that no scenes were displaced by accident. Even better would be ability to export as a PDF.
Thanks for your reply!
EDIT - Sorry, I do not follow on your notes comment.
Have you not tried to create something in a scroll collection with multiple groups this is a lot easier to manage the content?
For this point have you tried to add 10 scenes into a sequence within the composer scene management this would help you out if you can not change the number of scenes you have?
I think @Seb would agree with me on this point about having to build such a large experience you need to have a think about how you are going to tackle such a large experience but also building it in the most efficient way possible because it will save you the heartache in the future.
I do agree Louie, and actually I already discussed this with Elizabeth in a call.
Her experience isn’t simple to factorize in less scenes, since a lot of scenes are “almost similar” in their layouts but have their small differences which, somehow, can justify to make different scenes.
Refactoring the whole thing in less scenes would be possible, but would create a much complex structure to build, and she’s already far in her XP creation.