Raincloud/Flamenco-Management
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Use job name instead of blend name for render output paths

Browse Source
This commit is contained in:
Nathan
2026-03-06 16:00:57 -07:00
parent fff57d2b73
commit 9005e18438
4 changed files with 459 additions and 425 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.specstory/history/2026-02-10_22-00Z-error-in-blender-file-cleanup-command.md
+258 -413
View File
@@ -96,7 +96,6 @@ Let me look at the workspace to see if this is the Flamenco project and if there
---
From the snippet you pasted there’s no error — the log level is `INF` and it says `command exited successfully` for the ffmpeg step. Checking the project for how the cleanup command is built; the only suspicious part is the quoted Python passed to Blender.
@@ -116,211 +115,42 @@ Parameters:
"caseInsensitive": false
}
```
Result:
Additional data:
```json
{
"success": {
"pattern": "python-expr|blender-render|playblast-cleanup",
"path": "c:\\Users\\Nathan\\Desktop\\flamenco",
"outputMode": "content",
"workspaceResults": {
"c:\\Users\\Nathan\\Desktop\\flamenco": {
"content": {
"matches": [
{
"file": ".\\scripts\\TalkingHeads Custom Render.js",
"matches": [
{
"lineNumber": 310,
"content": " const command = author.Command(\"blender-render\", {"
}
]
},
{
"file": ".\\.specstory\\history\\2026-01-09_20-34Z-flamenco-project-file-path-consistency.md",
"matches": [
{
"lineNumber": 5529,
"content": " \"contents\": \"function authorRenderTasks(settings, renderDir, renderOutput) {\\n print(\\\"authorRenderTasks(\\\", renderDir, renderOutput, \\\")\\\");\\n let renderTasks = [];\\n let chunks = frameChunker(settings.frames, settings.chunk_size);\\n\\n let baseArgs = [];\\n if (settings.scene) {\\n baseArgs = baseArgs.concat([\\\"--scene\\\", settings.scene]);\\n }\\n\\n for (let chunk of chunks) {\\n const task = author.Task(`render-${chunk}`, \\\"blender\\\");\\n const command = author.Command(\\\"blender-render\\\", {\\n exe: \\\"{blender}\\\",\\n exeArgs: \\\"{blenderArgs}\\\",\\n argsBefore: [],\\n blendfile: settings.blendfile,\\n args: baseArgs.concat([\\n \\\"--render-output\\\", path.join(renderDir, path.basename(renderOutput)),\\n \\\"--render-format\\\", settings.format,\\n \\\"--render-frame\\\", chunk.replaceAll(\\\"-\\\", \\\"..\\\"), // Convert to Blender frame range notation.\\n [... omitted end of long line]"
},
{
"lineNumber": 5580,
"content": " \"text\": \" const command = author.Command(\\\"blender-render\\\", {\","
}
]
},
{
"file": ".\\.specstory\\history\\2026-01-09_18-22Z-nexus-manager-access-issue.md",
"matches": [
{
"lineNumber": 1243,
"content": " \"contents\": \"**System Information**\\nOperating System(s): Win11 25h2\\n\\n**Flamenco Version**\\nIs Broken: 3.8.2\\nWorked OK: unknown\\n\\nWhen Flamenco is ran from a Windows machine, with the shared-storage set to an SMB share, the symlinks (Windows reparse points) created by Shaman appear to be either completely useless at worst, or context dependent at best.\\n\\nI don't know if this is a bug, or if I'm doing something wrong. But I can't get a windows system to create proper Windows Reparse points on an SMB share. And I'm [not the only one in recent history](https://www.reddit.com/r/blenderhelp/comments/1onwaj1/need_help_with_windows_flamenco_worker_file/) who has struggled to get Shaman to work with Windows and Samba.\\n\\n1. Download and configure Flamenco\\n2. Configure the security policy as instructed [in the documentation](https://flamenco.blender.org/usage/shared-storage/shaman/#windows)\\n3. Enable symlinks on the (Linux) machine hosting your SMB share, as instructed [in the do [... omitted end of long line]"
},
{
"lineNumber": 1340,
"content": " \"text\": \" 'F:\\\\software\\\\Blender\\\\blender.exe' -b -y --gpu-backend opengl 'F:\\\\jobs/SSD_2B/SSD_2B.flamenco.blend' --python-expr '\","
},
{
"lineNumber": 1367,
"content": " \"text\": \"' --python-expr 'import bpy; bpy.context.scene.cycles.device = '\\\"'\\\"'GPU'\\\"'\\\"'' --render-output 'F:/renders/SSD_2B/2026-01-08_151057/######' --render-format PNG --render-frame 0..15\","
},
{
"lineNumber": 3089,
"content": " \"contents\": \"**System Information**\\nOperating System(s): Win11 25h2\\n\\n**Flamenco Version**\\nIs Broken: 3.8.2\\nWorked OK: unknown\\n\\nWhen Flamenco is ran from a Windows machine, with the shared-storage set to an SMB share, the symlinks (Windows reparse points) created by Shaman appear to be either completely useless at worst, or context dependent at best.\\n\\nI don't know if this is a bug, or if I'm doing something wrong. But I can't get a windows system to create proper Windows Reparse points on an SMB share. And I'm [not the only one in recent history](https://www.reddit.com/r/blenderhelp/comments/1onwaj1/need_help_with_windows_flamenco_worker_file/) who has struggled to get Shaman to work with Windows and Samba.\\n\\n1. Download and configure Flamenco\\n2. Configure the security policy as instructed [in the documentation](https://flamenco.blender.org/usage/shared-storage/shaman/#windows)\\n3. Enable symlinks on the (Linux) machine hosting your SMB share, as instructed [in the do [... omitted end of long line]"
},
{
"lineNumber": 3186,
"content": " \"text\": \" 'F:\\\\software\\\\Blender\\\\blender.exe' -b -y --gpu-backend opengl 'F:\\\\jobs/SSD_2B/SSD_2B.flamenco.blend' --python-expr '\","
},
{
"lineNumber": 3213,
"content": " \"text\": \"' --python-expr 'import bpy; bpy.context.scene.cycles.device = '\\\"'\\\"'GPU'\\\"'\\\"'' --render-output 'F:/renders/SSD_2B/2026-01-08_151057/######' --render-format PNG --render-frame 0..15\","
}
]
},
{
"file": ".\\.specstory\\history\\2026-01-08_17-28Z-shaman-symlinking-for-windows-samba.md",
"matches": [
{
"lineNumber": 1219,
"content": " 'F:\\software\\Blender\\blender.exe' -b -y --gpu-backend opengl 'F:\\jobs/SSD_2B_test/SSD_2B.flamenco.blend' --python-expr '"
},
{
"lineNumber": 1226,
"content": "' --python-expr 'import bpy; bpy.context.scene.cycles.device = '\"'\"'GPU'\"'\"'' --render-output 'F:/renders/SSD_2B_test/2026-01-08_113553/######' --render-format PNG --render-frame 0..15"
},
{
"lineNumber": 1243,
"content": " 'F:\\software\\Blender\\blender.exe' -b -y --gpu-backend opengl 'F:\\jobs/SSD_2B_test/SSD_2B.flamenco.blend' --python-expr '"
},
{
"lineNumber": 1250,
"content": "' --python-expr 'import bpy; bpy.context.scene.cycles.device = '\"'\"'GPU'\"'\"'' --render-output 'F:/renders/SSD_2B_test/2026-01-08_113553/######' --render-format PNG --render-frame 0..15"
},
{
"lineNumber": 1267,
"content": " 'F:\\software\\Blender\\blender.exe' -b -y --gpu-backend opengl 'F:\\jobs/SSD_2B_test/SSD_2B.flamenco.blend' --python-expr '"
},
{
"lineNumber": 1274,
"content": "' --python-expr 'import bpy; bpy.context.scene.cycles.device = '\"'\"'GPU'\"'\"'' --render-output 'F:/renders/SSD_2B_test/2026-01-08_113553/######' --render-format PNG --render-frame 0..15"
},
{
"lineNumber": 2382,
"content": " 'F:\\software\\Blender\\blender.exe' -b -y --gpu-backend opengl 'F:\\jobs/SSD_2B_test/SSD_2B.flamenco.blend' --python-expr '"
},
{
"lineNumber": 2389,
"content": "' --python-expr 'import bpy; bpy.context.scene.cycles.device = '\"'\"'GPU'\"'\"'' --render-output 'F:/renders/SSD_2B_test/2026-01-08_120320/######' --render-format PNG --render-frame 16..31"
},
{
"lineNumber": 3099,
"content": " 'F:\\software\\Blender\\blender.exe' -b -y --gpu-backend opengl 'F:\\jobs/SSD_2B_test/SSD_2B.flamenco.blend' --python-expr '"
},
{
"lineNumber": 3106,
"content": "' --python-expr 'import bpy; bpy.context.scene.cycles.device = '\"'\"'GPU'\"'\"'' --render-output 'F:/renders/SSD_2B_test/2026-01-08_121410/######' --render-format PNG --render-frame 0..15"
},
{
"lineNumber": 3916,
"content": " 'F:\\software\\Blender\\blender.exe' -b -y --gpu-backend opengl 'F:\\jobs/SSD_2B_test/SSD_2B.flamenco.blend' --python-expr '"
},
{
"lineNumber": 3923,
"content": "' --python-expr 'import bpy; bpy.context.scene.cycles.device = '\"'\"'GPU'\"'\"'' --render-output 'F:/renders/SSD_2B_test/2026-01-08_123211/######' --render-format PNG --render-frame 0..15"
},
{
"lineNumber": 5086,
"content": " 'F:\\software\\Blender\\blender.exe' -b -y --gpu-backend opengl 'F:\\jobs/SSD_2B/SSD_2B.flamenco.blend' --python-expr '"
},
{
"lineNumber": 5093,
"content": "' --python-expr 'import bpy; bpy.context.scene.cycles.device = '\"'\"'GPU'\"'\"'' --render-output 'F:/renders/SSD_2B/2026-01-08_124237/######' --render-format PNG --render-frame 16..31"
},
{
"lineNumber": 5110,
"content": " 'F:\\software\\Blender\\blender.exe' -b -y --gpu-backend opengl 'F:\\jobs/SSD_2B/SSD_2B.flamenco.blend' --python-expr '"
},
{
"lineNumber": 5117,
"content": "' --python-expr 'import bpy; bpy.context.scene.cycles.device = '\"'\"'GPU'\"'\"'' --render-output 'F:/renders/SSD_2B/2026-01-08_124237/######' --render-format PNG --render-frame 16..31"
},
{
"lineNumber": 5414,
"content": " 'F:\\software\\Blender\\blender.exe' -b -y --gpu-backend opengl 'F:\\jobs/SSD_2B/SSD_2B.flamenco.blend' --python-expr '"
},
{
"lineNumber": 5421,
"content": "' --python-expr 'import bpy; bpy.context.scene.cycles.device = '\"'\"'GPU'\"'\"'' --render-output 'F:/renders/SSD_2B/2026-01-08_124237/######' --render-format PNG --render-frame 0..15"
},
{
"lineNumber": 5438,
"content": " 'F:\\software\\Blender\\blender.exe' -b -y --gpu-backend opengl 'F:\\jobs/SSD_2B/SSD_2B.flamenco.blend' --python-expr '"
},
{
"lineNumber": 5445,
"content": "' --python-expr 'import bpy; bpy.context.scene.cycles.device = '\"'\"'GPU'\"'\"'' --render-output 'F:/renders/SSD_2B/2026-01-08_124237/######' --render-format PNG --render-frame 0..15"
},
{
"lineNumber": 5462,
"content": " 'F:\\software\\Blender\\blender.exe' -b -y --gpu-backend opengl 'F:\\jobs/SSD_2B/SSD_2B.flamenco.blend' --python-expr '"
},
{
"lineNumber": 5469,
"content": "' --python-expr 'import bpy; bpy.context.scene.cycles.device = '\"'\"'GPU'\"'\"'' --render-output 'F:/renders/SSD_2B/2026-01-08_124237/######' --render-format PNG --render-frame 0..15"
},
{
"lineNumber": 5486,
"content": " 'F:\\software\\Blender\\blender.exe' -b -y --gpu-backend opengl 'F:\\jobs/SSD_2B/SSD_2B.flamenco.blend' --python-expr '"
},
{
"lineNumber": 5493,
"content": "' --python-expr 'import bpy; bpy.context.scene.cycles.device = '\"'\"'GPU'\"'\"'' --render-output 'F:/renders/SSD_2B/2026-01-08_124237/######' --render-format PNG --render-frame 0..15"
}
]
},
{
"file": ".\\scripts\\TalkingHeads cycles_optix_gpu.js",
"matches": [
{
"lineNumber": 255,
"content": " '--python-expr',"
},
{
"lineNumber": 257,
"content": " '--python-expr',"
},
{
"lineNumber": 277,
"content": " task_invariant_args.push('--python-expr');"
},
{
"lineNumber": 287,
"content": " const command = author.Command('blender-render', {"
}
]
},
{
"file": ".\\.specstory\\history\\2025-05-06_20-07Z-switching-to-optix-gpu-rendering.md",
"matches": [
{
"lineNumber": 232,
"content": "blender --background --python-expr \"import bpy; bpy.context.preferences.addons['cycles'].preferences.compute_device_type = 'OPTIX'; bpy.context.preferences.addons['cycles'].preferences.get_devices(); [device.use = True for device in bpy.context.preferences.addons['cycles'].preferences.devices if device.type == 'OPTIX']; [setattr(scene.cycles, 'device', 'GPU') for scene in bpy.data.scenes]; bpy.ops.wm.save_userpref()\""
},
{
"lineNumber": 272,
"content": "blender --background --python-expr \"import bpy; bpy.context.preferences.addons['cycles'].preferences.compute_device_type = 'OPTIX'; bpy.context.preferences.addons['cycles'].preferences.get_devices(); [setattr(device, 'use', True) for device in bpy.context.preferences.addons['cycles'].preferences.devices if device.type == 'OPTIX']; [setattr(scene.cycles, 'device', 'GPU') for scene in bpy.data.scenes]; bpy.ops.wm.save_userpref()\""
}
]
}
],
"totalLines": 39,
"totalMatchedLines": 39
}
}
"isPruned": true,
"pattern": "python-expr|blender-render|playblast-cleanup",
"path": "c:\\Users\\Nathan\\Desktop\\flamenco",
"outputMode": "content",
"totalFiles": 6,
"totalMatches": 39,
"topFiles": [
{
"uri": ".\\scripts\\TalkingHeads Custom Render.js",
"matchCount": 1
},
{
"uri": ".\\.specstory\\history\\2026-01-09_20-34Z-flamenco-project-file-path-consistency.md",
"matchCount": 2
},
{
"uri": ".\\.specstory\\history\\2026-01-09_18-22Z-nexus-manager-access-issue.md",
"matchCount": 6
},
{
"uri": ".\\.specstory\\history\\2026-01-08_17-28Z-shaman-symlinking-for-windows-samba.md",
"matchCount": 24
},
{
"uri": ".\\scripts\\TalkingHeads cycles_optix_gpu.js",
"matchCount": 4
},
{
"uri": ".\\.specstory\\history\\2025-05-06_20-07Z-switching-to-optix-gpu-rendering.md",
"matchCount": 2
}
}
]
}
```
Status: **completed**
@@ -343,220 +173,65 @@ Parameters:
"targetDirectory": "c:\\Users\\Nathan\\Desktop\\flamenco"
}
```
Result:
Additional data:
```json
{
"directoryTreeRoot": {
"absPath": "c:\\Users\\Nathan\\Desktop\\flamenco",
"childrenDirs": [
{
"absPath": "c:\\Users\\Nathan\\Desktop\\flamenco\\.specstory",
"childrenDirs": [
{
"absPath": "c:\\Users\\Nathan\\Desktop\\flamenco\\.specstory\\history",
"childrenFiles": [
{
"name": "2025-04-04_17-25Z-creating-worker2-scripts-for-flamenco.md"
},
{
"name": "2025-04-23_20-48Z-network-drive-mapping-and-file-copying-script.md"
},
{
"name": "2025-04-25_19-30Z-i9-13ks-setup-troubleshooting.md"
},
{
"name": "2025-05-05_16-17Z-flamenco-job-status-troubleshooting.md"
},
{
"name": "2025-05-06_20-07Z-switching-to-optix-gpu-rendering.md"
},
{
"name": "2025-05-06_21-34Z-identifying-mistakes-and-seeking-guidance.md"
},
{
"name": "2025-05-07_22-05Z-script-modification-for-masterbox.md"
},
{
"name": "2025-05-12_16-04Z-technical-scripting-and-troubleshooting-discussion.md"
},
{
"name": "2025-05-13_23-13Z-bypassing-password-prompts-in-script.md"
},
{
"name": "2025-05-14_15-49Z-cmd-worker-error-handling-and-retry-logic.md"
},
{
"name": "2025-05-23_23-12Z-replace-remotecmd-with-remotesimplified.md"
},
{
"name": "2025-06-03_00-04Z-change-retry-function-to-infinite-retries.md"
},
{
"name": "2025-07-15_18-30Z-configure-launch-standard-worker-for-flamenco-3-7.md"
},
{
"name": "2025-08-13_18-59Z-remove-seq-from-jobname-format.md"
},
{
"name": "2025-11-03_19-27Z-create-sister-script-for-sheepit.md"
},
{
"name": "2025-11-06_17-28Z-update-path-structure-for-renders.md"
},
{
"name": "2025-11-19_17-03Z-why-is-git-frozen.md"
},
{
"name": "2025-11-21_01-14Z-workers-failing-and-ssh-connection-issues.md"
},
{
"name": "2025-11-21_16-43Z-fixing-sheepit-worker-incompatibility.md"
},
{
"name": "2026-01-08_17-28Z-shaman-symlinking-for-windows-samba.md"
},
{
"name": "2026-01-08_23-42Z-windows-symlinking-error.md"
}
],
"fullSubtreeExtensionCounts": {
".md": 3
},
"numFiles": 3
}
],
"childrenFiles": [
{
"name": ".gitignore"
}
],
"fullSubtreeExtensionCounts": {
".md": 3
},
"numFiles": 3
},
{
"absPath": "c:\\Users\\Nathan\\Desktop\\flamenco\\scripts",
"childrenFiles": [
{
"name": "outline.txt"
},
{
"name": "TalkingHeads Custom Render.js"
},
{
"name": "TalkingHeads cycles_optix_gpu.js"
}
],
"childrenWereProcessed": true
},
{
"absPath": "c:\\Users\\Nathan\\Desktop\\flamenco\\sqlite",
"childrenFiles": [
{
"name": "2025.04.17.09.50.29_flamenco-manager.sqlite"
},
{
"name": "2025.04.21.09.53.46_flamenco-manager.sqlite"
},
{
"name": "2025.04.22.09.37.45_flamenco-manager.sqlite"
},
{
"name": "2025.04.24.09.43.08_flamenco-manager.sqlite"
},
{
"name": "2025.04.25.09.55.50_flamenco-manager.sqlite"
},
{
"name": "2025.05.05.10.09.33_flamenco-manager.sqlite"
},
{
"name": "2025.05.05.16.15.03_flamenco-manager.sqlite"
},
{
"name": "2025.05.09.09.38.44_flamenco-manager.sqlite"
},
{
"name": "2025.05.12.10.52.00_flamenco-manager.sqlite"
},
{
"name": "2025.05.28.17.21.15_flamenco-manager.sqlite"
},
{
"name": "2025.06.06.09.50.20_flamenco-manager.sqlite"
},
{
"name": "2025.06.17.13.57.17_flamenco-manager.sqlite"
},
{
"name": "2025.07.01.11.02.08_flamenco-manager.sqlite"
},
{
"name": "2025.07.10.10.00.59_flamenco-manager.sqlite"
},
{
"name": "2025.07.15.10.16.07_flamenco-manager.sqlite"
},
{
"name": "2025.07.15.14.04.28_flamenco-manager.sqlite"
},
{
"name": "2025.07.22.09.37.20_flamenco-manager.sqlite"
},
{
"name": "2025.07.28.09.34.53_flamenco-manager.sqlite"
},
{
"name": "2025.09.11.11.39.47_flamenco-manager.sqlite"
},
{
"name": "2025.10.27.12.46.53_flamenco-manager.sqlite"
},
{
"name": "2025.11.19.11.05.13_flamenco-manager.sqlite"
},
{
"name": "2026.01.08.10.06.50_flamenco-manager.sqlite"
},
{
"name": "2026.02.10.10.22.19_flamenco-manager.sqlite"
}
],
"childrenWereProcessed": true
}
],
"childrenFiles": [
{
"name": ".cursorindexingignore"
},
{
"name": ".gitattributes"
},
{
"name": ".gitignore"
},
{
"name": "linux_flamenco_manager.bat"
},
{
"name": "unified_flamenco_launcher.bat"
},
{
"name": "unified_flamenco_launcher.ps1"
},
{
"name": "unified_sheepit_launcher.bat"
},
{
"name": "unified_sheepit_launcher.ps1"
}
],
"fullSubtreeExtensionCounts": {
".md": 3
"isPruned": true,
"rootPath": "c:\\Users\\Nathan\\Desktop\\flamenco",
"totalDirs": 4,
"totalFiles": 56,
"topEntries": [
{
"path": "c:\\Users\\Nathan\\Desktop\\flamenco\\.specstory",
"isDir": true,
"numFiles": 3
},
"numFiles": 3
{
"path": "c:\\Users\\Nathan\\Desktop\\flamenco\\scripts",
"isDir": true,
"numFiles": 0
},
{
"path": "c:\\Users\\Nathan\\Desktop\\flamenco\\sqlite",
"isDir": true,
"numFiles": 0
},
{
"path": "c:\\Users\\Nathan\\Desktop\\flamenco/.cursorindexingignore",
"isDir": false
},
{
"path": "c:\\Users\\Nathan\\Desktop\\flamenco/.gitattributes",
"isDir": false
},
{
"path": "c:\\Users\\Nathan\\Desktop\\flamenco/.gitignore",
"isDir": false
},
{
"path": "c:\\Users\\Nathan\\Desktop\\flamenco/linux_flamenco_manager.bat",
"isDir": false
},
{
"path": "c:\\Users\\Nathan\\Desktop\\flamenco/unified_flamenco_launcher.bat",
"isDir": false
},
{
"path": "c:\\Users\\Nathan\\Desktop\\flamenco/unified_flamenco_launcher.ps1",
"isDir": false
},
{
"path": "c:\\Users\\Nathan\\Desktop\\flamenco/unified_sheepit_launcher.bat",
"isDir": false
},
{
"path": "c:\\Users\\Nathan\\Desktop\\flamenco/unified_sheepit_launcher.ps1",
"isDir": false
}
],
"extensionCounts": {
".md": 3
}
}
```
@@ -570,7 +245,177 @@ Status: **completed**
<think><details><summary>Thought Process</summary>
The log the user shared doesn't show an actual error line (no ERR or failure). The "BasedPlayblast" job type and "playblast-cleanup" task aren't in this repo's scripts (TalkingHe</details></think>
The log the user shared doesn't show an actual error line (no ERR or failure). The "BasedPlayblast" job type and "playblast-cleanup" task aren't in this repo's scripts (TalkingHeads Custom Render.js, etc.) — so that job type likely comes from elsewhere (e.g. Flamenco Manager addon for Blender or another job author).
I'll summarize for the user:
1. **There’s no error in the snippet** — it’s all INF and “command exited successfully”.
2. **Possible confusion**: The `'"'"'` in the log is normal: it’s how a single quote is escaped in a shell when the whole Python code is wrapped in single quotes (so `we've` becomes `we'"'"'ve`). That’s correct and shouldn’t cause a failure.
3. If something is failing, it’s either **after** this log (e.g. Blender failing when running the cleanup script) or in a different log. I should say that clearly and suggest they check for ERR lines or the next log lines after the “going to run” line.
</details></think>
---
In the snippet you pasted there is **no error**. Everything is at INFO level and the ffmpeg step is reported as successful.
What the log shows:
1. **14:59:28** – ffmpeg runs (frames → video).
2. **14:59:59** – `command exited successfully` for that ffmpeg command.
3. **15:00:04** – The next task, **playblast-cleanup**, is picked up and the Blender command is logged (“going to run: …”).
So up to that point the pipeline is behaving normally.
The only odd-looking part is the **`'"'"'`** in the command line. That’s **not** an error. It’s normal shell quoting: the whole Python script is in single quotes, so an apostrophe inside the script (e.g. in “we’ve”) is escaped as `'"'"'` (end quote, literal `'`, start quote). So the script is being passed correctly.
If something is actually failing, it’s either:
- **After** this log (e.g. Blender failing while running the cleanup script), or
- In another place (e.g. Manager UI, or a line with **ERR** / “failed” / non‑zero exit).
Next steps that usually help:
1. Scroll a bit further in the **same** log and look for the next line after “going to run: …” — e.g. “command exited” with a non‑zero code or an ERR line.
2. Search the log for `ERR` or `failed` or `exit` to find the first real failure.
3. If the cleanup task is the one that fails, check whether the path
`A:/1 Amazon_Active_Projects/260206_PAE_2026/Blends/animations/blast/PAE_animation 1H`
exists and is writable from the machine where the worker runs (e.g. drive `A:` and permissions).
If you can paste the **next few lines** after the “going to run” line (or the first line that says ERR/failed), we can pinpoint the actual error.
---
_**User**_
flamenco manager can't start
PS C:\Users\Nathan\Desktop\flamenco> C:\Users\Nathan\Desktop\flamenco\linux_flamenco_manager.bat
Connecting to nexus and starting Flamenco Manager...
2026-02-23T12:34:26-07:00 INF starting Flamenco arch=amd64 git=51a41a19 os=linux osDetail="Debian GNU/Linux 12 (bookworm) (6.12.15-production+truenas)" releaseCycle=release version=3.8.2
2026-02-23T12:34:26-07:00 INF loading configuration file=flamenco-manager.yaml
2026-02-23T12:34:26-07:00 INF listening port=8888
2026-02-23T12:34:26-07:00 WRN SSDP: net.ListenPacket error: listen udp4 0.0.0.0:1900: bind: address already in use
2026-02-23T12:34:26-07:00 ERR Unable to create UPnP/SSDP server. This means that Workers will not be able to automatically find this Manager. Run them with the `-manager URL` argument, picking a URL from this list. urls=["http://10.1.10.3:8888/","http://100.98.46.102:8888/","http://172.16.0.1:8888/","http://172.16.1.1:8888/","http://172.16.2.1:8888/","http://172.16.3.1:8888/","http://172.16.4.1:8888/","http://172.16.5.1:8888/","http://[fd7a:115c:a1e0::e601:2e6c]:8888/","http://[fdd0::1]:8888/","http://[fdd0:0:0:1::1]:8888/","http://[fdd0:0:0:2::1]:8888/","http://[fdd0:0:0:3::1]:8888/","http://[fdd0:0:0:4::1]:8888/","http://[fdd0:0:0:5::1]:8888/","http://127.0.0.1:8888/","http://[::1]:8888/"]
2026-02-23T12:34:26-07:00 INF opening database file=flamenco-manager.sqlite
2026-02-23T12:34:26-07:00 INF shaman: opening file store storageDir=/mnt/PHOENIX/flamenco/file-store
2026-02-23T12:34:26-07:00 INF opening checkout directory checkoutDir=/mnt/PHOENIX/flamenco/jobs
2026-02-23T12:34:26-07:00 INF serving job-specific files directly from disk onDisk=/mnt/PHOENIX/flamenco/software/Flamenco/flamenco-manager-storage url=/job-files
2026-02-23T12:34:26-07:00 INF sleep scheduler starting checkInterval=1m0s
2026-02-23T12:34:26-07:00 INF TimeoutChecker: starting up checkInterval=1m0s initialSleep=5m0s taskTimeout=10m0s workerTimeout=1m0s
2026-02-23T12:34:26-07:00 INF database: periodic integrity check starting period=10m0s
2026-02-23T12:34:26-07:00 WRN HTTP server unexpectedly shut down error="listen tcp :8888: bind: address already in use"
2026-02-23T12:34:26-07:00 ERR HTTP server error, shutting down the application error="listen tcp :8888: bind: address already in use"
2026-02-23T12:34:26-07:00 INF sleep scheduler shutting down
2026-02-23T12:34:26-07:00 INF going to shut down the service willRestart=false
2026-02-23T12:34:26-07:00 INF TimeoutChecker: shutting down
2026-02-23T12:34:26-07:00 ERR database: could not perform checkpointing operation on write-ahead log at startup. Please report a bug at https://flamenco.blender.org/get-involved cause="context canceled"
2026-02-23T12:34:26-07:00 INF database: will perform periodic checkpoint period=15m0s
2026-02-23T12:34:26-07:00 INF database: stopped periodic checkpoint
2026-02-23T12:34:26-07:00 INF possible URLs at which to reach Flamenco Manager count=17
2026-02-23T12:34:26-07:00 INF - http://10.1.10.3:8888/
2026-02-23T12:34:26-07:00 INF - http://100.98.46.102:8888/
2026-02-23T12:34:26-07:00 INF - http://172.16.0.1:8888/
2026-02-23T12:34:26-07:00 INF - http://172.16.1.1:8888/
2026-02-23T12:34:26-07:00 INF - http://172.16.2.1:8888/
2026-02-23T12:34:26-07:00 INF - http://172.16.3.1:8888/
2026-02-23T12:34:26-07:00 INF - http://172.16.4.1:8888/
2026-02-23T12:34:26-07:00 INF - http://172.16.5.1:8888/
2026-02-23T12:34:26-07:00 INF - http://[fd7a:115c:a1e0::e601:2e6c]:8888/
2026-02-23T12:34:26-07:00 INF - http://[fdd0::1]:8888/
2026-02-23T12:34:26-07:00 INF - http://[fdd0:0:0:1::1]:8888/
2026-02-23T12:34:26-07:00 INF - http://[fdd0:0:0:2::1]:8888/
2026-02-23T12:34:26-07:00 INF - http://[fdd0:0:0:3::1]:8888/
2026-02-23T12:34:26-07:00 INF - http://[fdd0:0:0:4::1]:8888/
2026-02-23T12:34:26-07:00 INF - http://[fdd0:0:0:5::1]:8888/
2026-02-23T12:34:26-07:00 INF - http://127.0.0.1:8888/
2026-02-23T12:34:26-07:00 INF - http://[::1]:8888/
2026-02-23T12:34:27-07:00 INF Flamenco Manager service shut down willRestart=false
2026-02-23T12:34:27-07:00 INF stopping the Flamenco Manager process
---
_**Agent (model default, mode Agent)**_
<think><details><summary>Thought Process</summary>
The user is trying to start Flamenco Manager but it's failing. Looking at the logs:
1. **WRN SSDP: net.ListenPacket error: listen udp4 0.0.0.0:1900: bind: address already in use** - Port 1900 (UPnP/SSDP) is already in use
2. **ERR HTTP server error, shutting down the application error="listen tcp :8888: bind: address already in use"** - Port 8888 (the main HTTP port) is already in use
So the actual problem is: **something else is already using port 8888** (and 1900). The Manager starts, loads config, tries to listen on 8888, fails because the port is bound, and then shuts down.
The fix is either:
1. Stop whatever is using port 8888 (likely another Flamenco Manager instance, or another service)
2. Or configure Flamenco Manager to use a different port
Let me check the batch file they're running to understand how the manager is started and if we can suggest changing the port or killing the existing process.
</details></think>
---
Port 8888 is already in use, so Flamenco Manager can't bind and exits. Checking how the manager is started:
---
<tool-use data-tool-type="read" data-tool-name="read_file_v2">
<details><summary>Tool use: **read_file_v2** • Read file: c:\Users\Nathan\Desktop\flamenco\linux_flamenco_manager.bat</summary>
</details>
</tool-use>
---
<think><details><summary>Thought Process</summary>
So the batch file SSHs into a machine called "nexus" (which is running Debian/TrueNAS based on the log) and runs the flamenco-manager there. The port conflict is on the **nexus** (Linux) side, not on the Windows machine.
So the user needs to on the nexus server:
1. Find what's using port 8888 (and optionally 1900)
2. Stop it (e.g. kill the old Flamenco Manager process), then start again
Or configure Flamenco Manager to use a different port in flamenco-manager.yaml on the nexus.
I'll give them clear steps: how to find and kill the process on the Linux (nexus) side, and optionally how to use a different port.
</details></think>
---
Flamenco Manager is failing because **port 8888 is already in use** on the **nexus** server (the log says `listen tcp :8888: bind: address already in use`). Your batch file SSHs to nexus and runs the manager there, so the conflict is on nexus.
**Fix: free port 8888 on nexus**
On the nexus machine (SSH in first), run:
```bash
# See what is using port 8888
sudo lsof -i :8888
# or
sudo ss -tlnp | grep 8888
```
Often it’s an old Flamenco Manager that didn’t exit. Stop it:
```bash
# If it's flamenco-manager
pkill -f flamenco-manager
```
Then start Flamenco Manager again from Windows with your batch file.
**Optional: use another port**
If you want to keep something else on 8888, set a different port in the config on nexus:
- Edit `/mnt/PHOENIX/flamenco/software/Flamenco/flamenco-manager.yaml` (or wherever your config is) and set something like:
- `port: 8889`
- Restart the manager. Workers will need to use the new URL (e.g. `http://10.1.10.3:8889/`).
**Summary:** Something (very likely a previous Flamenco Manager) is already bound to 8888 on nexus. Find it with `lsof`/`ss`, stop that process (e.g. `pkill -f flamenco-manager`), then run `linux_flamenco_manager.bat` again.
---
.specstory/history/2026-03-06_22-52Z-sequence-determination-in-custom-javascripts.md
+189
View File
@@ -0,0 +1,189 @@
<!-- Generated by SpecStory, Markdown v2.1.0 -->
<!-- cursor Session c800408d-ddad-4d90-ad26-f9da441539ae (2026-03-06 22:52Z) -->
# Sequence determination in custom JavaScripts (2026-03-06 22:52Z)
_**User**_
For both custom javascripts, it appears we currently use blendname to determine the sequence. Can we use job name instead? That way, different sequences can be created from the same blend just by changing the job name before submission.
---
_**Agent (model kimi-k2.5, mode Agent)**_
<think><details><summary>Thought Process</summary>
The user wants to modify the custom JavaScript files to use job name instead of blend name to determine the sequence. Let me first find and read the relevant files to understand the current implementation.</details></think>
---
<tool-use data-tool-type="generic" data-tool-name="glob_file_search">
<details>
<summary>Tool use: **glob_file_search** • Searched codebase "undefined" • **2** results in **1** directory</summary>
Directory: **undefined** (2 files)
| File |
|------|
| `scripts/TalkingHeads cycles_optix_gpu.js` |
| `scripts/TalkingHeads Custom Render.js` |
</details>
</tool-use>
---
<think><details><summary>Thought Process</summary>
Found both JavaScript files. Let me read them to understand how they currently use blendname to determine the sequence.</details></think>
---
<tool-use data-tool-type="read" data-tool-name="read_file_v2">
<details><summary>Tool use: **read_file_v2** • Read file: c:\Users\Nathan\Desktop\flamenco\scripts\TalkingHeads Custom Render.js</summary>
</details>
</tool-use>
---
<tool-use data-tool-type="read" data-tool-name="read_file_v2">
<details><summary>Tool use: **read_file_v2** • Read file: c:\Users\Nathan\Desktop\flamenco\scripts\TalkingHeads cycles_optix_gpu.js</summary>
</details>
</tool-use>
---
<think><details><summary>Thought Process</summary>
Now I understand the issue. Both scripts use `blendname` (derived from `path.stem(settings.blendfile)`) to determine the sequence folder and output file naming. The user wants to use the job name instead so that different sequences can be created from the same blend file just by changing the job name.
Let me identify all the places where blendname is used:
1. In `TalkingHeads Custom Render.js`:
- Line 207: `const blendname = path.stem(settings.blendfile).replace('.flamenco', '');`
- Line 217: Used in path construction `parts.push(blendname, \`${blendname}_######\`);`
- Line 347: `const stem = path.stem(settings.blendfile).replace('.flamenco', '');` (for video output)
- Line 74: The `render_output_path` eval also uses blend name
2. In `TalkingHeads cycles_optix_gpu.js`:
- Line 381: `const blendname = path.stem(settings.blendfile).replace('.flamenco', '');`
- Line 385: Used in path construction `parts.push(blendname, \`${blendname}_######\`);`
- Line 314: `const stem = path.stem(settings.blendfile).replace('.flamenco', '');` (for video output)
- Line 65: The `render_output_path` eval also uses blend name
In Flamenco job scripts, the job object should have a `name` property that contains the job name. Looking at the compileJob function signature, it receives a `job` object.
I need to:
1. Add a new setting `job_name` that gets the job name
2. Or use `job.name` directly in the compileJob function
Looking at the Flamenco API, job objects typically have a `name` property.
I'll modify the scripts to prioritize the job name when creating output paths. By using `job.name || blendname`, I ensure flexibility in naming while maintaining a fallback to the original blend file name. This approach allows users to customize their sequence output without changing the underlying blend file structure.
The key modifications will involve:
- Replacing hardcoded blendname references
- Adding a dynamic naming mechanism
- Ensuring backward compatibility with existing render workflows</details></think>
---
I see the issue. Both scripts use `blendname` (derived from the blendfile filename) to determine the output folder and filename pattern. To use the job name instead, I need to modify the `computeAutoRenderOutputPath` functions and the video task functions to use `job.name` instead of `blendname`.
Let me make those changes.
---
<tool-use data-tool-type="write" data-tool-name="edit_file_v2">
<details><summary>Tool use: **edit_file_v2** • Edit file: c:\Users\Nathan\Desktop\flamenco\scripts\TalkingHeads Custom Render.js</summary>
</details>
</tool-use>
---
<tool-use data-tool-type="write" data-tool-name="edit_file_v2">
<details><summary>Tool use: **edit_file_v2** • Edit file: c:\Users\Nathan\Desktop\flamenco\scripts\TalkingHeads Custom Render.js</summary>
</details>
</tool-use>
---
<tool-use data-tool-type="write" data-tool-name="edit_file_v2">
<details><summary>Tool use: **edit_file_v2** • Edit file: c:\Users\Nathan\Desktop\flamenco\scripts\TalkingHeads cycles_optix_gpu.js</summary>
</details>
</tool-use>
---
<tool-use data-tool-type="write" data-tool-name="edit_file_v2">
<details><summary>Tool use: **edit_file_v2** • Edit file: c:\Users\Nathan\Desktop\flamenco\scripts\TalkingHeads cycles_optix_gpu.js</summary>
</details>
</tool-use>
---
<think><details><summary>Thought Process</summary>
All four edits were successful. Now I should also update the `render_output_path` eval in both files to use job name instead of blend name. Let me check those lines.</details></think>
---
Now I need to update the `render_output_path` eval expressions in both files to use job name instead of blend name.
---
<tool-use data-tool-type="write" data-tool-name="edit_file_v2">
<details><summary>Tool use: **edit_file_v2** • Edit file: c:\Users\Nathan\Desktop\flamenco\scripts\TalkingHeads Custom Render.js</summary>
</details>
</tool-use>
---
<tool-use data-tool-type="write" data-tool-name="edit_file_v2">
<details><summary>Tool use: **edit_file_v2** • Edit file: c:\Users\Nathan\Desktop\flamenco\scripts\TalkingHeads cycles_optix_gpu.js</summary>
</details>
</tool-use>
---
<think><details><summary>Thought Process</summary>
All edits are complete. Let me verify the changes by reading the relevant sections of both files to make sure everything looks correct.</details></think>
---
Done. Both scripts now use the job name instead of the blend name to determine the sequence folder and output file naming.
**Summary of changes:**
1. **`computeAutoRenderOutputPath` function** (in both files): Now uses `job.name` as the sequence folder name, with a fallback to the blend filename if no job name is set.
2. **`authorCreateVideoTask` function** (in both files): Now derives the output video filename from the render directory (which is based on the job name), ensuring the video name matches the sequence folder.
3. **`render_output_path` eval** (in both files): Updated the auto-eval expression to use `job.name` when available, falling back to the blend filename.
This means you can now:
- Submit the same `.blend` file multiple times with different job names
- Each job will render to its own sequence folder based on the job name
- The output files will be named according to the job name
Example: If you have `Shot_010.blend` and submit it with job name `Shot_010_take1`, renders go to `.../Renders/Shot_010_take1/Shot_010_take1_######.png`. Change the job name to `Shot_010_take2` for a different sequence output.
---
scripts/TalkingHeads Custom Render.js
+6 -6
View File
@@ -72,7 +72,7 @@ const JOB_TYPE = {
type: "string",
subtype: "file_path",
editable: false,
eval: "((lambda Path, abspath, os_path, settings_obj, blend: str(Path(abspath(settings_obj.render_output_root or '//')) / (((str(settings_obj.submodule or '').strip()) if (settings_obj.use_submodule and str(settings_obj.submodule or '').strip()) else ((os_path.basename(os_path.dirname(bpy.data.filepath))) if settings_obj.use_submodule else ''))) / blend / (blend + '_######')))(__import__('pathlib').Path, __import__('os').path.abspath, __import__('os').path, settings, __import__('os').path.splitext(__import__('os').path.basename(bpy.data.filepath))[0]))",
eval: "((lambda Path, abspath, os_path, settings_obj, jobname: str(Path(abspath(settings_obj.render_output_root or '//')) / (((str(settings_obj.submodule or '').strip()) if (settings_obj.use_submodule and str(settings_obj.submodule or '').strip()) else ((os_path.basename(os_path.dirname(bpy.data.filepath))) if settings_obj.use_submodule else ''))) / jobname / (jobname + '_######')))(__import__('pathlib').Path, __import__('os').path.abspath, __import__('os').path, settings, (job.name if 'job' in dir() and job and job.name else __import__('os').path.splitext(__import__('os').path.basename(bpy.data.filepath))[0])))",
description: "Final file path of where render output will be saved"
},
@@ -204,17 +204,17 @@ function computeAutoRenderOutputPath(job) {
renderRoot = path.join(path.dirname(settings.blendfile), 'Renders');
}
const blendname = path.stem(settings.blendfile).replace('.flamenco', '');
const jobname = (job.name || path.stem(settings.blendfile).replace('.flamenco', '')).trim();
print('AutoPath: blendfile=', settings.blendfile);
print('AutoPath: projectRoot=', projectRoot);
print('AutoPath: renderRoot=', renderRoot);
print('AutoPath: submodule=', submodule);
print('AutoPath: blendname=', blendname);
print('AutoPath: jobname=', jobname);
const parts = [renderRoot];
if (submodule) parts.push(submodule);
parts.push(blendname, `${blendname}_######`);
parts.push(jobname, `${jobname}_######`);
const finalPath = path.join.apply(path, parts);
print('AutoPath: finalPath=', finalPath);
return finalPath;
@@ -344,8 +344,8 @@ function authorCreateVideoTask(settings, renderDir) {
frames = `${firstFrame}-${lastFrame}`;
}
const stem = path.stem(settings.blendfile).replace('.flamenco', '');
const outfile = path.join(renderDir, `${stem}-${frames}.mp4`);
const jobname = path.basename(renderDir);
const outfile = path.join(renderDir, `${jobname}-${frames}.mp4`);
const outfileExt = needsPreviews ? ".jpg" : settings.image_file_extension;
const task = author.Task('preview-video', 'ffmpeg');
scripts/TalkingHeads cycles_optix_gpu.js
+6 -6
View File
@@ -56,13 +56,13 @@ const JOB_TYPE = {
description:
"Optional submodule under Renders (e.g. 'Waterspider B'). If empty, omitted.",
},
{
{
key: 'render_output_path',
type: 'string',
subtype: 'file_path',
editable: false,
eval:
"((lambda Path, abspath, os_path, settings_obj, blend: str(Path(abspath(settings_obj.render_output_root or '//')) / (((str(settings_obj.submodule or '').strip()) if (settings_obj.use_submodule and str(settings_obj.submodule or '').strip()) else ((os_path.basename(os_path.dirname(bpy.data.filepath))) if settings_obj.use_submodule else ''))) / blend / (blend + '_######')))(__import__('pathlib').Path, __import__('os').path.abspath, __import__('os').path, settings, __import__('os').path.splitext(__import__('os').path.basename(bpy.data.filepath))[0]))",
"((lambda Path, abspath, os_path, settings_obj, jobname: str(Path(abspath(settings_obj.render_output_root or '//')) / (((str(settings_obj.submodule or '').strip()) if (settings_obj.use_submodule and str(settings_obj.submodule or '').strip()) else ((os_path.basename(os_path.dirname(bpy.data.filepath))) if settings_obj.use_submodule else ''))) / jobname / (jobname + '_######')))(__import__('pathlib').Path, __import__('os').path.abspath, __import__('os').path, settings, (job.name if 'job' in dir() and job and job.name else __import__('os').path.splitext(__import__('os').path.basename(bpy.data.filepath))[0])))",
description: 'Final file path of where render output will be saved',
},
@@ -311,8 +311,8 @@ function authorCreateVideoTask(settings, renderDir) {
return;
}
const stem = path.stem(settings.blendfile).replace('.flamenco', '');
const outfile = path.join(renderDir, `${stem}-${settings.frames}.mp4`);
const jobname = path.basename(renderDir);
const outfile = path.join(renderDir, `${jobname}-${settings.frames}.mp4`);
const outfileExt = needsPreviews ? '.jpg' : settings.image_file_extension;
const task = author.Task('preview-video', 'ffmpeg');
@@ -378,11 +378,11 @@ function computeAutoRenderOutputPath(job) {
} else {
renderRoot = path.join(path.dirname(settings.blendfile), 'Renders');
}
const blendname = path.stem(settings.blendfile).replace('.flamenco', '');
const jobname = (job.name || path.stem(settings.blendfile).replace('.flamenco', '')).trim();
const parts = [renderRoot];
if (submodule) parts.push(submodule);
parts.push(blendname, `${blendname}_######`);
parts.push(jobname, `${jobname}_######`);
return path.join.apply(path, parts);
}