Q100639: Limitations of cross-sketching app workflows

SUMMARY

This article analyzes workflows where more than one sketching app is used within a Sequence, lists known limitations with these methods, and provides context for such limitations.

Multiple sketching apps might be used if several artists are collaborating on a Sequence, or if one artist who likes switching between apps is working in the Sequence, and both cases are relevant for this article.

 

MORE INFORMATION

The below flowcharts include all combinations of sketching apps, and include Storyboard Pro (later abbreviated to SBP) and Photoshop (later abbreviated to PS) scenarios that don’t use the built-in integrations like the PS plugin or the SBP “Conformation” process. In that case, note how panels will behave in the same way as they would if a non-supported sketching software was used. All limitations are marked in red.

The flowchart below shows the behavior of a panel that is first created in PS or another sketching app, sent to Flix, and is then revised in SBP:

cross-sketching app workflows - Nick- PS_Flix_SBP.png

 

The next flowchart shows the behavior of a panel that starts in SBP, sent to Flix, and then is revised in PS or another sketching app. It is important to note that the behaviors displayed in this flowchart also apply to panels that went through the steps in the flowchart above, before continuing down the paths below:

The following tables provide further context for the limitations displayed in red. Note that some limitations are grouped as they are related:

Dialogue is lost

As shown in the flowcharts above, these limitations are always a consequence of not using the built-in integrations. Understandably, should artists use software that don't have Flix integrations, there is no other choice than to perform manual exports/imports to get panels in and out of Flix. However, we strongly recommend that artists using PS or SBP utilize the tools Flix provides to maintain consistency and avoid requiring additional work from other departments.

When timing/duration is lost, a panel's duration will set to the Default Flix Panel Duration value located in File > Preferences... > General > Default Flix Panel Duration 

Framing might differ

Timing is lost*

 

Layers are flattened

This occurs when a panel that didn’t initially originate in SBP is sent there via the expected integration. This includes cases where a SBP panel is revised in PS via the plugin, and is then sent back to SBP.

Unfortunately, even though Flix always sends SBP the original artwork as it was imported initially, any layers will be merged automatically due to SBP behavior during its “Conformation” process.

If SBP 22 or newer is used, layers should be preserved and no longer be flattened. However, please note that any groups/folders used to organize layers will still be removed even while using more recent versions of SBP.

 

New panel ID

From the flowcharts above there is one main scenario where panels will be assigned a new ID instead of versioning up the original panel: a revised panel is manually imported to Flix without using the Import Panel Revisions button.

If the default Import New Panels option is used instead, the new panel will not be associated with the original panel and will be given a new ID. In the first flowchart, you may notice that timing loss is sometimes linked to the loss of the original panel ID, which is due to the fact that a panel’s duration is saved against its ID. Replacing a panel, rather than importing a new one, keeps the ID and adds a new version to it, preserving the duration it had before being revised.
It is also important to note that the Import Panel Revisions option can only be used for one panel at a time, and it is not currently possible to import a batch of panel revisions.

Maintaining panel IDs is critical for Production tracking, and allows previous revisions to be easily accessible should the need arise. As such, it's important to avoid situations that cause revised panels to have new panel IDs wherever possible.

There is another case where panels change their IDs that is not linked to cross-sketching app workflows: duplicating a panel. When a panel is duplicated, a new ID is created since two panels with the same ID cannot coexist within the Panel Browser. If you would like to have a way for duplicates to show the same ID, please submit a Feature Request with Foundry Support.

Original panel won’t be versioned up

Panel Should not Version Up

As a result of a bug or other unexpected issues, it is possible for a new version of a panel to be created, even if it has not been revised. For example, please refer to the following bug report:

ID 544665 - Panel not originating from SBP will version up even if it is not updated

 

In conclusion, most limitations that occur when using multiple sketching applications within the same sequence can be mitigated by using the built-in integrations. The limitations that persist even with the integrations are a consequence of current incompatibilities between Flix and other applications.

 

FURTHER HELP

For an overview of the Photoshop<>Flix round trip, and how to use the available plugin, please refer to our Flix & Photoshop tutorial.

There is also a similar tutorial for the Flix & Storyboard Pro round trip.

For a list of supported third-party software for Story and Editorial, Third-Party Application Support keeps an updated list for the latest Flix version; please keep in mind that some Flix versions support different versions so if you are not on the latest, refer to the Release Notes instead.

If you are having issues with loss of dialogue, timing, or change of IDs, and the scenarios described in this article don’t seem to pertain to your case, please open a support ticket and make sure to provide the following information:

  • Any known steps that reproduced the issue
  • Any third-party software used and their versions
  • Flix version used
  • A CSV exported from Flix for the sequence revisions(s) involved in the issue

If you are unsure of how to open a support ticket, please refer to Q100064: How to raise a support ticket

    We're sorry to hear that

    Please tell us why