Page MenuHome

Storyboarding: New add-on for storyboarding (Storypencil)
Closed, ResolvedPublicDESIGN

Description

This add-on is the same used in Annency demos and was tested but @Matias Mendiola (mendio) and @Daniel Martinez Lara (pepeland) in real productions.

Known Iussues:

  • The add-on does not work when using workspace scene pin. There is an open task already open (T100165)

Note: @Matias Mendiola (mendio) has all documentation manual ready for upload.

Event Timeline

Antonio Vazquez (antoniov) changed the task status from Needs Triage to Confirmed.Aug 27 2022, 11:46 AM
Antonio Vazquez (antoniov) created this task.
Antonio Vazquez (antoniov) renamed this task from Storyboarding: New add-on for storyboarding to Storyboarding: New add-on for storyboarding (Storypencil).Aug 27 2022, 11:58 AM
Antonio Vazquez (antoniov) updated the task description. (Show Details)

So stoked for this! Thank you guys for putting this together :D Can't wait to see the documentation bc I don't think I'm working it properly lol.

Hi @Matias Mendiola (mendio),
Hope all is good!
Would you mind releasing the documentation for this Add-on when you have a spare moment?
I've got it working but my timeline doesn't sync between my windows like Daniels showcase back in June. Paul C. and I would love to run through it together and setup our files to give this a go :)
Thank you!
Maurits Valk

@Maurits Valk (storyvalk) I can't update the Blender official documentation before the Add-on approval, could you explain better the problem you encountered so we can help?

Hi @Matias Mendiola (mendio),
All good regarding the documentation. I manage to get everything working except for the timeline to sync between the scenes. I noticed Daniel's twitter demo had his timeline in both the sequencer and dopesheet synced per scene. So when he started a new 'scene/shot' the timeline would start at the beginning of that scene instead of where you last left the timeline in that dopesheet.
Here's a pic of mysetup below. The dopesheet timeline should be at the first frame since the vse timeline is at the start of that scene strip.
If this is not the intention then that's totally cool, it just looked like Daniel's setup was different. Another small thing is the Blender window still has a project title at the top but Daniel doesnt have that. I'd love to know how to remove that so you have two clean separate windows (unfortunately googling for an hour didn't solve it)

Thank you!!

obsStudio can remove the top of blender window or any software for recording purpose maybe this is due to that

Thank you, @hamza.SMA (hamza.elbarmaki) - that helps solve the title bar. The outstanding issue is the timeline syncing between VSE window and the scene I'm drawing in. Any tips would be appreciated :)

@Campbell Barton (campbellbarton) Could take a look at the add-on before moving it to add-on contrib? The add-on has been tested a lot and works fine (we know some issues, but they are more Blender limitations that are not very important).

Our idea is put in contrib for 3.4 and after receiving feedback from more Studios, move to official in future releases.

@Antonio Vazquez (antoniov) I had a browse through the addon and in general, besides License headers (which should be in all files, other points are optional before committing to contrib).

  • Use SPDX license headers for all files.

Other suggestions/notes (not a full review).

  • Use relative imports instead of importing from storypencil.
  • operator_exists("workspace.scene_pin_toggle") shouldn't be needed when in contrib.
  • root = scene.view_layers[0].layer_collection - shouldn't the windows view_layer be used instead?
  • STORYPENCIL_OT_RenderAction video_ext / image_ext, are duplicating data available in Blender, we could expose this via an API.

@Matias Mendiola (mendio) Could you check that this version works as expected. I have done several changes requested by @Campbell Barton (campbellbarton) and I want to be sure before pushing the add-on to contrib

@Campbell Barton (campbellbarton) I have fixed the license, the relative import and removed operator_exists

About view_layer, this function reads the collection of the strip scene, not the current window.

@Matias Mendiola (mendio) Could you check that this version works as expected. I have done several changes requested by @Campbell Barton (campbellbarton) and I want to be sure before pushing the add-on to contrib

Everything seems to be working fine

The add-on has been pushed to blender-addons-contrib

@Matias Mendiola (mendio) You can upload the documentation.

@Maurits Valk (storyvalk)
I have the same issue.
I can't replicate Daniel's setup and sync doesn't seem to work (or maybe I don't know how to make it work!).

It was a bug, already fixed, please compile master again

Sorry in advance for the question, but the addon (and sync) seems to work for me when you check the Edit/Open in New Window, but does not work when the option is unchecked.
@Matias Mendiola (mendio) Was your last message to me? Who should compile to master?

Sorry, I assumed you are compiling Blender yourself. You can download the daily build to try the add-on here (Blender 3.4 Alpha) https://builder.blender.org/download/daily/

Yep, I've downloaded the lastest nightly and still can't get it to work like Daniel's example. I've tried on both of my rigs (Win11 & MacOs).

You mentioned that when using "Open in New Window" it works right in sync.
What is exactly the problem you have when not using this workflow and edit the source scene going back and forth from the VSE and the scene?

Not vanilla blender but:

I am trying to use it right now with the Heavypoly setup and when I create a new scene, it is not an empty one, it is one that links data between the first scene. Modifying the newly made scene also modifies the original one.

edit:
the base scene also seems to get modified.

I will look into why that setup affects it and post my findings here if I find any.

Not vanilla blender but:

I am trying to use it right now with the Heavypoly setup and when I create a new scene, it is not an empty one, it is one that links data between the first scene. Modifying the newly made scene also modifies the original one.

edit:
the base scene also seems to get modified.

I will look into why that setup affects it and post my findings here if I find any.

Seems like in preferences, Editing>Objects>Duplicate Data>Grease Pencil

has to be checked on to make the addon functional. Perhaps it's an idea to note that in the documentation?

I see, glad you found the problem but since this is a corner case and you are not using the default Blender settings we cannot consider this a bug.
Anyway I'll see if we could make the addon address this in some way.

@Matias Mendiola (mendio) I guess my question is how does Daniel manage to get this workspace setup when clicking on Edit:


Where he has the global Sequencer window at the bottom and a Drawing one (that switches from shot to shot) at the top...
I can sort of replicate what he's done by clicking on the Open in new window option, but then I have to manually stack the two open windows. Is that the correct workflow?
Again, very sorry to ask, but I'm just trying to duplicate Daniel's workflow which is great, but doesn't seem setup by default when you first use the addon...

yes, unfortunately there is no way to stack automatically the windows for the user.
This workflow is better suite when using multiple monitors or a pen display like Wacom Cintiq. You can work in one monitor with the main edit, and in the other in sync on the source scenes