studio/flamenco
studio/flamenco
12
30
Fork 38
Code Issues 63 Pull Requests 5 Releases Wiki Activity

Edit/override job parameters that affect job compilation #60116

New Issue
Closed
opened 2019-01-03 14:49:30 +01:00 by Sybren A. Stüvel · 5 comments
Sybren A. Stüvel commented 2019-01-03 14:49:30 +01:00
Owner
Copy Link

For editing job params that change the actual tasks:

  • Correct an error in the output format setting (e.g. was submitted saving as MKV, should have been EXR).
  • Adjust frame range.
  • Chunk size
For editing job params that change the actual tasks: - Correct an error in the output format setting (e.g. was submitted saving as MKV, should have been EXR). - Adjust frame range. - Chunk size
Sybren A. Stüvel commented 2019-01-03 14:49:30 +01:00
Author
Owner
Copy Link

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren
Michael Dingwall commented 2019-02-20 06:21:15 +01:00
Copy Link

Added subscriber: @macgeek21

Added subscriber: @macgeek21
Michael Dingwall commented 2019-02-20 06:21:15 +01:00
Copy Link

I was looking into something like this for the create-video task in the blender-render job compiler for the server. I want to be able to set the ffmpeg arguments that are being used to create the resulting video. As I was digging into this, I thought that using a variable override in the manager, similar to the path override for ffmpeg, could allow for at least making the output file an MP4 vs MKV. Is this barking up the wrong tree?

I was looking into something like this for the create-video task in the blender-render job compiler for the server. I want to be able to set the ffmpeg arguments that are being used to create the resulting video. As I was digging into this, I thought that using a variable override in the manager, similar to the path override for ffmpeg, could allow for at least making the output file an MP4 vs MKV. Is this barking up the wrong tree?
Sybren A. Stüvel commented 2022-02-28 13:17:34 +01:00
Author
Owner
Copy Link

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'
Sybren A. Stüvel commented 2022-02-28 13:17:34 +01:00
Author
Owner
Copy Link

A new generation of Flamenco (version 3.0) is in development (in the main branch at https://developer.blender.org/diffusion/F/), so all issues with Flamenco version 2 or older will be archived.

A new generation of Flamenco (version 3.0) is in development (in the `main` branch at https://developer.blender.org/diffusion/F/), so all issues with Flamenco version 2 or older will be archived.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Good First Issue
  
Priority
High

  
Priority
Low

  
Priority
Normal

  
Status
Archived

  
Status
Confirmed

  
Status
Needs Info from Developers

  
Status
Needs Information from User

  
Status
Needs Triage

  
Status
Resolved

  
Type
Bug

  
Type
Design

  
Type
Job Type
Custom Flamenco job type

  
Type
Known Issue

  
Type
Patch

  
Type
Report

  
Type
To Do

No Label
Good First Issue
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Job Type
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: studio/flamenco#60116
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?