Support for bam pack --ignore when creating Flamenco job #51116

New Issue

Francesco Siddi · 2017-04-03T11:52:18+02:00

Francesco Siddi commented

2017-04-03 11:52:18 +02:00

When packing lighting files for rendering, we currently do not ignore certain extensions. This means that .mov files used in the anim files as reference are then included in the pack as well. This generates hundreds of MBs overhead.

The simple solution is to edit the args of bam pack to ignore specific extensions

  args = [
      bpy.app.binary_path_python,
      '-m', 'bam.pack',
      '--input', str(base_blendfile),
      '--output', str(target_blendfile),
      '--exclude', '*.mov',
      '--mode', 'FILE',
  ]

But I imagine we want to make this a bit smarter and have a settings field, either in the add-on panel, or in the preferences, where such ignore patterns can be defined by the user.

The ignored files hardly change and should be ignored by default in every file, so I think a setting would be ok.

When packing lighting files for rendering, we currently do not ignore certain extensions. This means that .mov files used in the anim files as reference are then included in the pack as well. This generates hundreds of MBs overhead. The simple solution is to edit the args of bam pack to ignore specific extensions ``` args = [ bpy.app.binary_path_python, '-m', 'bam.pack', '--input', str(base_blendfile), '--output', str(target_blendfile), '--exclude', '*.mov', '--mode', 'FILE', ] ``` But I imagine we want to make this a bit smarter and have a settings field, either in the add-on panel, or in the preferences, where such ignore patterns can be defined by the user. The ignored files hardly change and should be ignored by default in every file, so I think a setting would be ok.

Sybren A. Stüvel was assigned by Francesco Siddi

2017-04-03 11:52:18 +02:00

Francesco Siddi commented

2017-04-03 11:52:18 +02:00

Changed status to: 'Open'

Francesco Siddi commented

2017-04-03 11:52:18 +02:00

Added subscriber: @fsiddi

Sybren A. Stüvel commented

2017-04-03 12:58:17 +02:00

Interesting. This would be something that can change on a file-by-file basis, I think. Tthere are too many video extensions to ignore, and there are cases when they shouldn't be ignored, so there is no good default value.
Maybe we can be a bit smarter about this, and temporarily unlink videos that are only used by the image editor, before bam-packing?

Interesting. This would be something that can change on a file-by-file basis, I think. Tthere are too many video extensions to ignore, and there are cases when they shouldn't be ignored, so there is no good default value. Maybe we can be a bit smarter about this, and temporarily unlink videos that are only used by the image editor, before bam-packing?

Francesco Siddi commented

2017-04-03 15:47:40 +02:00

Fo reference: in the context of a production (for example the current one) we use only 1-2 types of video (.mov and .mkv). I'm not sure I understand the "unlink videos used by the image editor". The videos I'm talking about are used in the sequencer for example.

Sybren A. Stüvel commented

2017-05-02 16:57:06 +02:00

Implemented in version 1.6.4 of the Blender Cloud add-on (which requires a recent master build of Blender, doesn't work with 2.78)

Sybren A. Stüvel commented

2017-05-02 17:01:37 +02:00

Changed status from 'Open' to: 'Resolved'

Sybren A. Stüvel closed this issue

2017-05-02 17:01:37 +02:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: archive/blender-cloud#51116

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Support for bam pack --ignore when creating Flamenco job #51116