Flamenco render job submission fails #65726
Labels
No Label
legacy module
Modeling
legacy project
Blender Cloud
legacy project
Documentation
legacy project
Infrastructure: blender.org
legacy project
Infrastructure: Websites
legacy project
Modeling
legacy project
Pillar
legacy project
Pillar Framework
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Design
Type::Report
Type::To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: archive/blender-cloud#65726
Loading…
Reference in New Issue
Block a user
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?
System Information
Operating system: Windows 10
Graphics card: AMD Radeon (TM) R9 Fury Series
Blender Version
Broken: version: 2.79 (sub 7), branch: blender2.7, commit date: 2019-04-09 16:45, hash: 10f724cec5e3
Submitting certain .blend files to the Flamenco manager results in an error, apparently occurring when copying associated assets from the .blend file to the Flamenco render job folder. Trying multiple files, I found that I can generate this error with an audio file in the video sequencer or when I have an external Alembic file referenced absolutely in a Mesh Sequence Cache modifier, even if that file is in an accessible location.
Sample file with WAV sound in the video sequencer and an Alembic file reference.
DevTest.blend
Added subscriber: @JoelHowe
Which version of the Blender Cloud add-on was used?
Latest version as of yesterday (1.13.4) but with the wheel file you had sent me (attached here)
blender_asset_tracer-1.1.2-py3-none-any.whl.
Please give us files we can use to reproduce the issue. The blend file you uploaded packs just fine, albeit with warnings about missing files.
It would also help to know the layout of your files. What directory is set as the project directory? You're using drive R:, is that a network drive (if so, which protocol?) or a local disk?
Adding a sound file to the sequencer in an empty .blend file was enough to reproduce the error for me, but I am attaching this actual file. This file has the proprietary elements removed, including the WAV file in the sequencer. To get this to submit to Flamenco without error, I have to delete the WAV audio and both the Alembic fluid surface and the Ocean modifier fluid surface.
Flamenco-Error.blend
I have been able to successfully submit to Flamenco a version of the file that has the object with an Ocean modifier, but only when the Cache path for that modifier was empty.
UPDATE: It looks like just changing Cache path helped submit this, as I wasn't able to submit today with an empty value but then changing it to "//" a relative reference to the current folder, it submitted.
As an addition to these not-yet-answered questions: what have you set as job storage and job output directories? With the Flamenco-Error.blend file you're using the D: drive, what kind of drive is that?
D:/ is a local physical data drive on my main Win 10 workstation.
R:/ is the Flamenco project.
R:/ is a network mapped folder location to D:/Flamenco, so in the case of submitting the job, R:/ points to the same hard drive. R:/ was created using Windows "Map network drive", which I don't believe allows you to specify a protocol.
All Flamenco workers have an R:/ mapped back to my workstation, which is also running Flamenco manager.
Inside R:/ are three folders:
@JoelHowe can you try with this BAT wheel file? Just remove any exist
blender_asset_tracer*.whl
file from thewheels
directory of the Blender Cloud add-on, then put this one in place and restart Blender.blender_asset_tracer-1.2.dev1-py3-none-any.whl
Error is still occurring for both 2.79 and 2.80, but only when a WAV file is in the video sequencer and I try to submit to Flamenco. The .blend files don't submit and get an error as below, with the display in the Flamenco Render tab reading "Found asset Narration-Audio.wav" when it stops packing. All files submit properly once the audio track has been removed, which is an acceptable workaround for me.
I have discovered that the error during the job submission can be prevented if "Relative paths only" is turned on in the Blender Cloud settings. I am not sure if that will introduce other issues, or if this is on by default, but it appears that it addresses the issue.
I suspect it has to do with the behaviour of
Path.resolve()
(doc). AFAIK on Windows it also "resolves" mapped drive letters to their\\SERVER\share\path\to\file
notation, which is a pain in the rear end.@JoelHowe can you install Python 3.7, run
pip install -U blender-asset-tracer
and give us the output ofbat list R:/project/thefile.blend
? You can also trybat pack -p R:/project R:/project/thefile.blend testpack
; this will create a directorytestpack
in the current working directory, and put the BAT pack in there.Testing with BAT directly will probably be easier than trying to use Blender with the Cloud add-on, and can provide us with more detailed info. If you replace
bat
in the above commands withbat -d
you should get debug-level messages.Unfortunately I won't have time to do this, but on a positive note I am unable to replicate this issue in Blender 2.81 with latest Blender Cloud plugin.
Added subscriber: @MaciejJutrzenka
so u are saying it all works fine with 2.81? correct? that would means that we can close this as fixed/.
It is not 100% fixed, but I can confirm that I have certain .blend files with audio tracks in them that submit properly now in 2.81. I am not sure why some others don't submit to Flamenco, but there is the easy workaround of deleting the audio track before submitting the render or turning on "Relative paths only" in the Cloud plugin settings.
Changed status from 'Open' to: 'Archived'
I'll close this as 'Archived' then; if you know of a way for us to reproduce the issue we can always reopen.