p2or / blender-loom Goto Github PK

When I encode an image sequence...lets say 40 frames.. .LOOM sometimes stops encoding after an random amount of frames. Sometimes it at 70%, sometimes at 56%... and sometimes it finsihes correctly..

What could be the cause of this? Im running Blender 2.9 cycles

I have a very simple scene of grease pencil animation. I would like to let loom render only the keyframes as usual, so I open the Render Image Sequence dialogue and hit the Verify Output icon in order to select only the keyframed frames. But it selects the entire timeline instead.

The terminal output seem to think every frame has something in it, somehow...

Info: 246 Frames [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 242, 243, 244, 245, 246] will be rendered to \animatic_###.bmp

Here's the problematic file:

Animatic_006Cc.zip

I have an image sequence I'm trying to render
Error:

• I am on windows 10
• I have ffmpeg installed and the path set in Loom preferences. I have restarted blender.
  • I have directed the path to the /ffmpeg/, /ffmpeg/bin/, and ~/bin/ffmpeg.exe but they all throw the same error.
  • My ffmpeg path is C:\ffmpeg-2023-06-11-git-09621fd7d9-full_build - Do I need to rename the directory to just 'ffmpeg' or does it not matter?
• I have verified in command prompt that ffmpeg is installed and that .png is an available format viaffmpeg -encoders and and ffmpeg -codecs
  • zlib is also an available encoder. I've read that zlib not being installed can cause ffmpeg to not recognize .pngs, but that's not the case here.
    

Output settings:

• I tried this with the File Format set to .png as well and it throws the same error

Encode image sequence settings:

P.S. This toolset is amazing. It has single-handedly saved a project I've been working on for two months, and I expect to be getting a lot of use out of it on future projects. Thanks so much for making it!

I've noticed that Blender tends to crash randomly during the nth trigger/call to loom for rendering (clicking ok)

I am running 3.5.1, any ideas about what could be causing it? The addon is incredibly useful and I don't want to use other convoluted addons for the same purpose.

Hello. I love your addon, it helps me alot. But there is one thing : i run 2 computers rendering on same animation. Usually i use overwrite disabled and placeholder enabled.

Place holders will make an empty file frame, while being rendered so other computer will skip that frame (so wont make 2 computers working on same frame).

but loom batch rendering apparently dont make placeholders, so it could end up rendering on same frames. Or maybe i misconfigured? thank you!

Hey, great library, my only gripe is that if you're working with a rig that has a pose library, and you choose 'Render selected keyframes' those poses will be added as keyframes, as the pose lib is just an action strip.

So if I have anim with keyframes on frames 0 and 10, and a few poses in the pose lib, it'll output 0,1,2,3.. and 10 as the selected range, since all_selected_ctrl_points () seems to look through all actions of the object.

As I looked through the code, I noticed one can Alt click the option to trigger the selected_ctrl_points function instead of the all_selected_ctrl_points function, but I couldn't find this in the instructions, perhaps I missed it, but I think it might be a good idea for this to be either the default or an explicit option, since I'm guessing using the pose lib is quite common.

Thanks for the great addon!

Versions tested: 2.93, 3.0, addon version 0.8.3

not sure if this duplicate

Hi,

Thanks for making this plugin.

I tried to add globals like $MM to datetime.datetime.now().month.strftime("%m") but it turned out to be false when being evaluated, so instead of having the current month number, I would get NO-MM in the file name.

I tried to add import datetime in the python file but it doesn't change anything. Could you consider adding support for date time in presets?

I would suggest token naming be following:
"$YYYY": datetime.datetime.now().strftime("%Y"),
"$YY": datetime.datetime.now().strftime("%y"),
"$MM": datetime.datetime.now().strftime("%m"),
"$DD": datetime.datetime.now().strftime("%d"),
"$hh": datetime.datetime.now().strftime("%H"),
"$mm": datetime.datetime.now().strftime("%M"),
"$ss": datetime.datetime.now().strftime("%S"),

Would be possible to animate the speed change for the slow motion?

Example: 1.0, 1.1, 1.3, 1.6, 2.0, 2.5, 3.1, 3.8, 4.6, 5.5, 6.5 ...
To create a ramp for the speed.

Using the graph editor would be ideal like:
https://github.com/hxxr/time-remapper

Thank you.

I guess this might fall into the 'feature request' pile, but sharing in any case...

I think a lot of my problems getting the correct frames from 'Render Selected Keyframes' have stemmed from this issue.

It would be great if the selected keyframes in the Dope Sheet could be extracted via 'Render Selected Keyframes' without the objects themselves being necessarily selected. For example in a scene involving lots of props, character, cameras etc. It would be awesome to just select the keyframes via the Dope Sheet summary, to be sure and catch all keys in the shot, even if an object or rig isn't explicitly selected.

I hope this is a possible thing!

Many thanks again,

Stephen.

The docs says:

• You can verify the image sequence on disk before encoding by clicking the Verify Image Sequence operator , which also detects all frames missing frames of the sequence

• In case there are missing frames, the addon either provides an utility function to fill the gaps of the image sequence with copies of the nearest frame to get the full lenght animation and another operator to render all missing frames:

  

I'm very interested in this feature, as combined with the render from selected keyframes it allows a big speed up in any 2D-ish animation.

Though in my case, it doesn't seem to work. I hit the ghost icon as suggested, which does this:

But nothing else happens, I don't see the buttons as in the docs.

Just like a title says.
It can't Render
When I try to add new blend file, new windows batch appear without single blend inserted.
I usually use this featurein 2.79 below and it's working.
Please can you fix it ? This plugin really helping my project 🙏 and not babysitting to 1 blend file to another

hi there!

i may have found a bug, but i admit i'm both new to blender and new to loom... please be gentle!

it looks like if i try to render via ctrl+shift+alt+F12 and select a single file that contains two viewlayers, both are seemingly rendered, but then only the last one is written to disk and labelled whatever the 'output' was set at time of saving the file.

it's like it needs a forced refresh when switching viewlayers or something...?

Cheers,
Jeremy

here's my repro steps:
-- have two viewlayers:

-- have them both set to render:


-- have the output path set to:
D:\Work\training\blender\camera_tracking\render\cg$VIEWLAYER\v07$VIEWLAYER_v07.

-- save the file
-- hit ctrl+shift_alt+F12 and load the file:

-- hit 'ok' and watch it render, noting it renders both viewlayers, but only writes to disk one.

Blender 3.4.1 (hash 55485cb379f7 built 2022-12-20 01:51:19)
Read prefs: C:\Users\OEM\AppData\Roaming\Blender Foundation\Blender\3.4\config\userpref.blend
Read blend: D:\Work\training\blender\camera_tracking\building_scene_v03.blend
Info: Read library:  'D:\Work\training\blender\assetLibrary\donut\donut_base_v01_bundle.blend', '//..\assetLibrary\donut\donut_base_v01_bundle.blend', parent '<direct>'
Info: 'D:\Work\training\blender\camera_tracking\render\cg\prpDonut01\v07' created
Fra:1 Mem:138.98M (Peak 138.99M) | Time:00:00.32 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Synchronizing object | chair
Fra:1 Mem:139.02M (Peak 139.02M) | Time:00:00.32 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Synchronizing object | donut
Fra:1 Mem:140.30M (Peak 143.55M) | Time:00:00.33 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Synchronizing object | icing
Fra:1 Mem:154.48M (Peak 157.25M) | Time:00:00.35 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Synchronizing object | sprinkle_source.001
Fra:1 Mem:154.50M (Peak 157.25M) | Time:00:00.35 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Synchronizing object | sprinkle_source.004
Fra:1 Mem:154.52M (Peak 157.25M) | Time:00:00.35 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Synchronizing object | sprinkle_source.003
Fra:1 Mem:154.54M (Peak 157.25M) | Time:00:00.35 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Synchronizing object | sprinkle_source.002
Fra:1 Mem:154.55M (Peak 157.25M) | Time:00:00.35 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Synchronizing object | sprinkle_source
Fra:1 Mem:154.59M (Peak 157.25M) | Time:00:00.35 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Synchronizing object | Sphere
Fra:1 Mem:154.66M (Peak 157.25M) | Time:00:00.35 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Synchronizing object | Sphere.001
Fra:1 Mem:154.72M (Peak 157.25M) | Time:00:00.35 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Synchronizing object | Sphere.002
Fra:1 Mem:154.79M (Peak 157.25M) | Time:00:00.35 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Synchronizing object | Sphere.003
Fra:1 Mem:154.86M (Peak 157.25M) | Time:00:00.35 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Synchronizing object | Sphere.004
Fra:1 Mem:154.88M (Peak 157.25M) | Time:00:00.35 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Synchronizing object | sunscreen
Fra:1 Mem:154.89M (Peak 157.25M) | Time:00:00.36 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Initializing
Fra:1 Mem:154.88M (Peak 166.00M) | Time:00:00.36 | Mem:0.00M, Peak:0.00M | Scene, prpDonut01 | Updating Images | Loading donut_base
Fra:1 Mem:155.90M (Peak 166.00M) | Time:00:00.41 | Mem:1.00M, Peak:1.00M | Scene, prpDonut01 | Waiting for render to start
Fra:1 Mem:155.90M (Peak 166.00M) | Time:00:00.41 | Mem:1.00M, Peak:1.00M | Scene, prpDonut01 | Loading render kernels (may take a few minutes the first time)
Fra:1 Mem:155.90M (Peak 173.67M) | Time:00:00.46 | Mem:1.02M, Peak:1.02M | Scene, prpDonut01 | Updating Scene
Fra:1 Mem:155.90M (Peak 173.67M) | Time:00:00.46 | Mem:1.02M, Peak:1.02M | Scene, prpDonut01 | Updating Shaders
Fra:1 Mem:156.41M (Peak 173.67M) | Time:00:00.47 | Mem:1.03M, Peak:1.03M | Scene, prpDonut01 | Updating Procedurals
Fra:1 Mem:156.41M (Peak 173.67M) | Time:00:00.47 | Mem:1.03M, Peak:1.03M | Scene, prpDonut01 | Updating Background
Fra:1 Mem:156.41M (Peak 173.67M) | Time:00:00.47 | Mem:1.03M, Peak:1.03M | Scene, prpDonut01 | Updating Camera
Fra:1 Mem:156.41M (Peak 173.67M) | Time:00:00.47 | Mem:1.03M, Peak:1.03M | Scene, prpDonut01 | Updating Meshes Flags
Fra:1 Mem:156.41M (Peak 173.67M) | Time:00:00.47 | Mem:1.03M, Peak:1.03M | Scene, prpDonut01 | Updating Objects
Fra:1 Mem:156.41M (Peak 173.67M) | Time:00:00.47 | Mem:1.03M, Peak:1.03M | Scene, prpDonut01 | Updating Objects | Copying Transformations to device
Fra:1 Mem:156.43M (Peak 173.67M) | Time:00:00.47 | Mem:1.07M, Peak:1.07M | Scene, prpDonut01 | Updating Objects | Applying Static Transformations
Fra:1 Mem:156.43M (Peak 173.67M) | Time:00:00.47 | Mem:1.07M, Peak:1.07M | Scene, prpDonut01 | Updating Particle SystemsFra:1 Mem:156.43M (Peak 173.67M) | Time:00:00.47 | Mem:1.07M, Peak:1.07M | Scene, prpDonut01 | Updating Particle Systems | Copying Particles to device
Fra:1 Mem:156.43M (Peak 173.67M) | Time:00:00.47 | Mem:1.07M, Peak:1.07M | Scene, prpDonut01 | Updating Meshes
Fra:1 Mem:162.37M (Peak 173.67M) | Time:00:00.48 | Mem:1.07M, Peak:1.07M | Scene, prpDonut01 | Updating Mesh | Computing attributes
Fra:1 Mem:165.09M (Peak 173.67M) | Time:00:00.48 | Mem:1.07M, Peak:1.07M | Scene, prpDonut01 | Updating Mesh | Copying Attributes to device
Fra:1 Mem:165.07M (Peak 173.67M) | Time:00:00.48 | Mem:3.77M, Peak:3.77M | Scene, prpDonut01 | Updating Geometry BVH Cylinder 15/15 | Building BVH
Fra:1 Mem:165.07M (Peak 173.67M) | Time:00:00.48 | Mem:3.77M, Peak:3.77M | Scene, prpDonut01 | Updating Geometry BVH Torus.003 4/15 | Building OptiX acceleration structure
Fra:1 Mem:165.07M (Peak 173.67M) | Time:00:00.50 | Mem:12.23M, Peak:46.14M | Scene, prpDonut01 | Updating Scene BVH | Building
Fra:1 Mem:165.08M (Peak 173.67M) | Time:00:00.50 | Mem:12.23M, Peak:46.14M | Scene, prpDonut01 | Updating Scene BVH | Building OptiX acceleration structure
Fra:1 Mem:165.08M (Peak 173.67M) | Time:00:00.56 | Mem:12.27M, Peak:46.14M | Scene, prpDonut01 | Updating Scene BVH | Copying BVH to device
Fra:1 Mem:165.08M (Peak 173.67M) | Time:00:00.56 | Mem:12.27M, Peak:46.14M | Scene, prpDonut01 | Updating Mesh | Computing normals
Fra:1 Mem:191.10M (Peak 191.10M) | Time:00:00.57 | Mem:12.27M, Peak:46.14M | Scene, prpDonut01 | Updating Mesh | Copying Mesh to device
Fra:1 Mem:191.10M (Peak 191.10M) | Time:00:00.57 | Mem:38.29M, Peak:46.14M | Scene, prpDonut01 | Updating Objects Flags
Fra:1 Mem:191.10M (Peak 191.10M) | Time:00:00.57 | Mem:38.29M, Peak:46.14M | Scene, prpDonut01 | Updating Primitive Offsets
Fra:1 Mem:191.10M (Peak 191.10M) | Time:00:00.57 | Mem:38.29M, Peak:46.14M | Scene, prpDonut01 | Updating Images
Fra:1 Mem:191.10M (Peak 191.10M) | Time:00:00.57 | Mem:38.29M, Peak:46.14M | Scene, prpDonut01 | Updating Images | Loading Image0001.exr
Fra:1 Mem:191.10M (Peak 191.10M) | Time:00:00.57 | Mem:38.29M, Peak:46.14M | Scene, prpDonut01 | Updating Images | Loading IMG_20230208_145920.jpg
Fra:1 Mem:389.17M (Peak 389.17M) | Time:00:00.68 | Mem:236.36M, Peak:236.36M | Scene, prpDonut01 | Updating Camera Volume
Fra:1 Mem:389.17M (Peak 389.17M) | Time:00:00.68 | Mem:236.36M, Peak:236.36M | Scene, prpDonut01 | Updating Lookup Tables
Fra:1 Mem:389.17M (Peak 389.17M) | Time:00:00.68 | Mem:236.62M, Peak:236.62M | Scene, prpDonut01 | Updating Lights
Fra:1 Mem:389.17M (Peak 389.17M) | Time:00:00.69 | Mem:236.62M, Peak:236.62M | Scene, prpDonut01 | Updating Lights | Computing distribution
Fra:1 Mem:389.17M (Peak 389.17M) | Time:00:00.69 | Mem:236.62M, Peak:236.62M | Scene, prpDonut01 | Updating Integrator
Fra:1 Mem:390.17M (Peak 390.17M) | Time:00:00.69 | Mem:237.62M, Peak:237.62M | Scene, prpDonut01 | Updating Film
Fra:1 Mem:390.17M (Peak 390.43M) | Time:00:00.69 | Mem:237.37M, Peak:237.62M | Scene, prpDonut01 | Updating Lookup Tables
Fra:1 Mem:390.17M (Peak 390.43M) | Time:00:00.69 | Mem:237.62M, Peak:237.62M | Scene, prpDonut01 | Updating Baking
Fra:1 Mem:390.17M (Peak 390.43M) | Time:00:00.69 | Mem:237.62M, Peak:237.62M | Scene, prpDonut01 | Updating Device | Writing constant memory
Fra:1 Mem:390.18M (Peak 390.43M) | Time:00:00.69 | Mem:237.62M, Peak:237.62M | Scene, prpDonut01 | Loading denoising kernels (may take a few minutes the first time)
Fra:1 Mem:396.56M (Peak 396.56M) | Time:00:00.71 | Mem:766.75M, Peak:766.75M | Scene, prpDonut01 | Sample 0/512
Fra:1 Mem:546.85M (Peak 546.85M) | Time:00:00.72 | Remaining:00:07.10 | Mem:917.05M, Peak:917.05M | Scene, prpDonut01 | Sample 1/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:00.99 | Remaining:00:01.51 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 80/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.00 | Remaining:00:01.27 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 96/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.02 | Remaining:00:01.09 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 112/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.03 | Remaining:00:00.95 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 128/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.04 | Remaining:00:00.84 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 144/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.05 | Remaining:00:00.75 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 160/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.07 | Remaining:00:00.68 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 176/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.08 | Remaining:00:00.61 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 192/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.09 | Remaining:00:00.55 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 208/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.11 | Remaining:00:00.50 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 224/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.12 | Remaining:00:00.46 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 240/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.13 | Remaining:00:00.42 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 256/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.14 | Remaining:00:00.38 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 272/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.15 | Remaining:00:00.34 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 288/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.17 | Remaining:00:00.31 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 304/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.18 | Remaining:00:00.28 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 320/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.19 | Remaining:00:00.25 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 336/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.20 | Remaining:00:00.22 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 352/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.22 | Remaining:00:00.19 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 368/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.23 | Remaining:00:00.17 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 384/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.24 | Remaining:00:00.14 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 400/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.25 | Remaining:00:00.12 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 416/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.26 | Remaining:00:00.10 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 432/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.28 | Remaining:00:00.08 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 448/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.29 | Remaining:00:00.05 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 464/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.30 | Remaining:00:00.03 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 480/512
Fra:1 Mem:546.86M (Peak 546.88M) | Time:00:01.31 | Remaining:00:00.01 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 496/512
Fra:1 Mem:720.89M (Peak 815.81M) | Time:00:03.39 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Sample 512/512
Fra:1 Mem:720.89M (Peak 815.81M) | Time:00:03.39 | Mem:917.06M, Peak:917.06M | Scene, prpDonut01 | Finished
Fra:1 Mem:720.81M (Peak 815.81M) | Time:00:03.39 | Mem:917.06M, Peak:917.06M | Scene, contactDonutToBook01 | Synchronizing object | table.001
Fra:1 Mem:720.84M (Peak 815.81M) | Time:00:03.39 | Mem:917.06M, Peak:917.06M | Scene, contactDonutToBook01 | Synchronizing object | chair.001
Fra:1 Mem:720.84M (Peak 815.81M) | Time:00:03.39 | Mem:917.06M, Peak:917.06M | Scene, contactDonutToBook01 | Initializing
Fra:1 Mem:720.83M (Peak 815.81M) | Time:00:03.39 | Mem:917.06M, Peak:917.06M | Scene, contactDonutToBook01 | Waiting for render to start
Fra:1 Mem:720.83M (Peak 815.81M) | Time:00:03.40 | Mem:917.06M, Peak:917.06M | Scene, contactDonutToBook01 | Loading render kernels (may take a few minutes the first time)
Fra:1 Mem:720.83M (Peak 815.81M) | Time:00:03.40 | Mem:917.06M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Scene
Fra:1 Mem:720.83M (Peak 815.81M) | Time:00:03.40 | Mem:917.06M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Shaders
Fra:1 Mem:720.83M (Peak 815.81M) | Time:00:03.40 | Mem:917.06M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Background
Fra:1 Mem:720.83M (Peak 815.81M) | Time:00:03.40 | Mem:917.06M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Camera
Fra:1 Mem:720.83M (Peak 815.81M) | Time:00:03.40 | Mem:917.06M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Meshes Flags
Fra:1 Mem:720.83M (Peak 815.81M) | Time:00:03.40 | Mem:917.06M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Objects
Fra:1 Mem:720.79M (Peak 815.81M) | Time:00:03.40 | Mem:917.02M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Objects | Copying Transformations to device
Fra:1 Mem:720.80M (Peak 815.81M) | Time:00:03.40 | Mem:917.05M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Objects | Applying Static Transformations
Fra:1 Mem:720.80M (Peak 815.81M) | Time:00:03.40 | Mem:917.05M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Particle Systems
Fra:1 Mem:720.80M (Peak 815.81M) | Time:00:03.41 | Mem:917.05M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Meshes
Fra:1 Mem:692.08M (Peak 815.81M) | Time:00:03.41 | Mem:888.33M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Mesh | Computing attributes
Fra:1 Mem:694.80M (Peak 815.81M) | Time:00:03.41 | Mem:888.34M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Mesh | Copying Attributes to device
Fra:1 Mem:694.78M (Peak 815.81M) | Time:00:03.41 | Mem:891.04M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Geometry BVH Cube.003 2/2 | Building BVH
Fra:1 Mem:694.78M (Peak 815.81M) | Time:00:03.41 | Mem:891.04M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Geometry BVH Cube.004 1/2 | Building BVH
Fra:1 Mem:694.78M (Peak 815.81M) | Time:00:03.41 | Mem:890.99M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Geometry BVH Cube.004 1/2 | Building OptiX acceleration structure
Fra:1 Mem:694.78M (Peak 815.81M) | Time:00:03.41 | Mem:890.99M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Scene BVH | Building
Fra:1 Mem:694.78M (Peak 815.81M) | Time:00:03.41 | Mem:890.99M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Scene BVH | Building OptiX acceleration structure
Fra:1 Mem:694.78M (Peak 815.81M) | Time:00:03.41 | Mem:891.03M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Scene BVH | Copying BVH to device
Fra:1 Mem:694.78M (Peak 815.81M) | Time:00:03.42 | Mem:891.03M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Mesh | Computing normals
Fra:1 Mem:720.79M (Peak 815.81M) | Time:00:03.43 | Mem:891.03M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Mesh | Copying Mesh to device
Fra:1 Mem:720.79M (Peak 815.81M) | Time:00:03.43 | Mem:917.04M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Objects Flags
Fra:1 Mem:720.79M (Peak 815.81M) | Time:00:03.43 | Mem:917.04M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Primitive Offsets
Fra:1 Mem:720.79M (Peak 815.81M) | Time:00:03.43 | Mem:917.04M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Images
Fra:1 Mem:720.79M (Peak 815.81M) | Time:00:03.44 | Mem:917.04M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Camera Volume
Fra:1 Mem:720.79M (Peak 815.81M) | Time:00:03.44 | Mem:917.04M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Lookup Tables
Fra:1 Mem:720.79M (Peak 815.81M) | Time:00:03.44 | Mem:917.04M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Lights
Fra:1 Mem:720.79M (Peak 815.81M) | Time:00:03.44 | Mem:917.04M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Lights | Computing distribution
Fra:1 Mem:720.79M (Peak 815.81M) | Time:00:03.44 | Mem:917.04M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Integrator
Fra:1 Mem:720.29M (Peak 815.81M) | Time:00:03.44 | Mem:916.54M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Film
Fra:1 Mem:720.29M (Peak 815.81M) | Time:00:03.44 | Mem:916.54M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Lookup Tables
Fra:1 Mem:720.29M (Peak 815.81M) | Time:00:03.44 | Mem:916.54M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Baking
Fra:1 Mem:720.29M (Peak 815.81M) | Time:00:03.44 | Mem:916.54M, Peak:917.06M | Scene, contactDonutToBook01 | Updating Device | Writing constant memory
Fra:1 Mem:720.29M (Peak 815.81M) | Time:00:03.44 | Mem:916.54M, Peak:917.06M | Scene, contactDonutToBook01 | Sample 0/128
Fra:1 Mem:838.95M (Peak 838.95M) | Time:00:03.49 | Remaining:00:05.63 | Mem:1035.19M, Peak:1035.19M | Scene, contactDonutToBook01 | Sample 1/128
Fra:1 Mem:838.95M (Peak 838.96M) | Time:00:04.83 | Remaining:00:00.83 | Mem:1035.19M, Peak:1035.19M | Scene, contactDonutToBook01 | Sample 80/128
Fra:1 Mem:838.95M (Peak 838.96M) | Time:00:05.12 | Remaining:00:00.56 | Mem:1035.19M, Peak:1035.19M | Scene, contactDonutToBook01 | Sample 96/128
Fra:1 Mem:838.95M (Peak 838.96M) | Time:00:05.42 | Remaining:00:00.28 | Mem:1035.19M, Peak:1035.19M | Scene, contactDonutToBook01 | Sample 112/128
Fra:1 Mem:838.95M (Peak 981.33M) | Time:00:09.34 | Mem:1035.19M, Peak:1035.19M | Scene, contactDonutToBook01 | Sample 128/128
Fra:1 Mem:838.95M (Peak 981.33M) | Time:00:09.34 | Mem:1035.19M, Peak:1035.19M | Scene, contactDonutToBook01 | Finished
Saved: 'D:\Work\training\blender\camera_tracking\render\cg\prpDonut01\v07\prpDonut01_v07.0001.exr'
 Time: 00:09.48 (Saving: 00:00.14)

Info: Saved "building_scene_v03.blend"

Blender quit
Press any key to continue . . .`

-- further backed up by both not appearing on disk:

Hi, I have a pretty long sequence that I wanted to render out with Loom. Its about 1100 frames, spread over different frame ranges (200-300, 415-550, etcetc)

I wanted Loom to render this out during the night, but when I got back it only did 17 frames and nothing more. I have tried this a couple of times...and this keeps happening . Somethimes after 50 frames, sometimes after 230 frames. It just stops.

Just to be clear..im talking about the rendering of the images, not encoding the sequence with FFMpeg.

Im on windows 10 64 bit, blender 2.91 and Im rendering with cycles. Also im on a AMD Threadripper system with 64 RAM.. The rendering is done with CPU+GPY (GTX 1080Ti). Please let me know if you need more info

Please advise.

oh and a quick additional question: does blender need te be running in order to use the command line rendering? Or can I just start the command line render..and then quit Blender?

loom doesnt even create "loom" folder under scripts folder

Dear p2or,

First off, I just want to say how helpful your addon is to so many people, Loom provides a simple and elegant solution customised batch rendering in Blender, so thank you very much for creating Loom.

I did want to bring to your attention a small issue I have encountered in Loom 0.3 in Blender 2.80 (Windows 10, 64bit) when utilising 'Batch Render and Encode'

Encoding to any available codec when the blender file output is set to OpenEXR fails the encoding, returning the error

'[prores @ 00000214f7913040] encoding with ProRes Proxy/LT/422/422 HQ (apco, apcs, apcn, ap4h) profile, need YUV422P10 input'

This appears to be specific to the 'Batch render and encode' option as utilising 'Encode Image Sequence' on the same EXR sequence is successful.

When the blender file output is set to .JPG, the encoding part of 'Batch Render and Encode' is successful.

Best regards,
Tim

Howdy! Awesome addon here. I just ran into one problem -- I frequently want the output directory to change based on the global variables, not just the filename (which seems to be the behavior currently). e.g. right now I can do //output/$BLEND_frame#### as an output name, but I can't do //output/$BLEND/frame#### as a filename, which is how I normally handle my render outputs. If you could make it so this would work, that would be amazing.

Bonus points if you would also have it make any subdirectories needed (so I don't have to create them by hand), but I'd be more than happy if the variable replacement worked for directories at all.

Thanks! <3

Hi p2or,
I've been doing more testing to figure out the issues I was having and whether I need to report anything. But in the meantime I thought I'd post a couple of things I've discovered. This first one I hope is a fairly simple bug fix.

As the title suggests, 'Fill gaps with copies' in the encode panel only fills frames between the min and max existing frames. It would be great, and I think expected, that the function would fill to the start and end of the scene frame range, since typically it's important to keep shot frame ranges consistent through layout, previs, to editing and final render, say.

I've attached a basic scene file which renders on frames 2 and 8, with a scene frame range of 1-10. After rendering with 'Render Selected Keyframes' the FGwC function fills in frames 3-7, but not 1, 9 or 10.

Many thanks!
Stephen.

FillSeqTest.zip

Hi,

I installed the addon on blender 2.80 (build from 26.06.2019) and when I'm trying to activate the addon it trows me some errors like:

Traceback (most recent call last):
  File "C:\Program Files\Blender 2.80 beta\2.80\scripts\modules\addon_utils.py", line 351, in enable
    mod = __import__(module_name)
  File "C:\Users\RASVAN PAVEL\AppData\Roaming\Blender Foundation\Blender\2.80\scripts\addons\loom.py", line 26, in <module>
    from numpy import arange, around, isclose
  File "C:\Program Files\Blender 2.80 beta\2.80\python\lib\site-packages\numpy\__init__.py", line 142, in <module>
    from . import add_newdocs
  File "C:\Program Files\Blender 2.80 beta\2.80\python\lib\site-packages\numpy\add_newdocs.py", line 13, in <module>
    from numpy.lib import add_newdoc
  File "C:\Program Files\Blender 2.80 beta\2.80\python\lib\site-packages\numpy\lib\__init__.py", line 8, in <module>
    from .type_check import *
  File "C:\Program Files\Blender 2.80 beta\2.80\python\lib\site-packages\numpy\lib\type_check.py", line 11, in <module>
    import numpy.core.numeric as _nx
ImportError: cannot import name 'core' from 'numpy' (C:\Program Files\Blender 2.80 beta\2.80\python\lib\site-packages\numpy\__init__.py)

Just wanted to say THANK YOU for creating Loom - totally saved my sanity. I have a really long mo-cap sequence that has some broken frames scattered around in it - I was dreading having to baby-sit a patchwork render. Honestly this should be built-in to Blender ...

Thanks again

Joe

Says empty selection.

Thanks for your effort the issue is if I am rendering from a start frame higher than 9999 it does not automatically detect unrendered frames because it has more than 5 digits

Great tool! Is there is a way to set overwrite "Date created" when saving the image sequence. The logic makes perfect sense changing the "Date modified" time stamp with each render, but what do I do if I want fresh "Date created" timestamp for the files without creating a new directory for the sequence output? does this result from windows log or can I set this in loom.py/blender?

Thanks

Sorry in advance if I've missed something. I see there is a function for this in encoding a sequence, but it would be awesome to have this option, maybe as a utility, to fill the gaps in an image sequence, to be used in other software.

E.g. I want to render .exr files, on 2s primarily with some frame ranges on 1s and 3s. If I could render those frames with loom, then fill the gaps with copies, I could import those image sequences into Resolve for comp, edit and grading.

Thanks for the very cool tools!

I would be nice to be able to know from which marker is related the image by exporting the Marker name in the output name, before the image number for example.

blendname_markername_####.png

Hey just wanted to let you know loom won't install in Blender 3.0 beta or 3.1 Alpha because of the error:

AttributeError: 'module' object has no attribute 'TOPBAR_MT_app'

This may have some relevant info: https://www.mail-archive.com/[email protected]/msg150277.html

Thanks!

So i called my folder "Blender GN Simulation 3.5" and tried to batch render from there and i got this:

/Users/chris/Downloads/Blender3.5 GN simulation/Blender.app/Contents/MacOS/blender -b "/Users/chris/Downloads/gn_sim_collision-tut2.blend" --python-expr "import bpy;bpy.ops.render.image_sequence(frames='1-200', isolate_numbers=False,render_silent=True, digits=4)" -t 10
read -n1 -r -p "Press any key to continue..." key
exit

although i don't know what this means, but this didn't render...and i assume there are some "" missing?

This is a bit of a niche feature request, but I'd like to be able to input a frame range (i.e. 2053-2000) and have loom render the frames in that order. Currently it will render the range correctly, but it always starts at the lowest number.

I'm not sure how you handle video encode, though. Maybe a checkbox or dropdown that says encode video in rendered order or encode video in frame number order.

Thanks! This is an awesome addon and was exactly what I was looking for.

Hello and thanks for this great and useful tool.

In Blender 2.90 alpha the Spacebar or F3 operator menu has changed and the Render specific Keyframes operator no longer works.

Thanks for taking a look.

Using the # wildcard in the output path and rendering image sequence with the addon (ctrl shift f12) only works if # is/are the last characters, otherwise i get this error:

example of a non working path (doesn't work even without global variable usage)

Blender 3.4.1 stable

blender.crash.txt

Updated to version 0.8.9
Redner via the command line stopped working. Can you help me what's wrong here?

I selected some of my grease pencil drawing, and open the menu, but all of them are grey, and when I click on " render select keyframe" it doesn't respond at all.

• Module Registration
• Class Registration (Naming, Access)
• Display Enum (Render Image Sequence)?
  ...

Generally, Loom has been terrific. Love it.
But of late, Batch has stopped working.
I use Blender with Octane.
The files do render without Loom, so I suppose they are solid files.
A message has been generated: "Octane has tried to start multiple times",Which is odd, as Octane is running pre Batch launch.
Any guidance appreciated.
Win10, 2 Nvidia 3080s

I was wondering if there is a way for me to customize my Command Line when using Render Image Sequence. Is this possible?

I am currently trying to find a way to make Loom compatible with Turbo Tools V3
Here's where you can take a look: https://blendermarket.com/products/turbo-tools-v3---turbo-render-turbo-comp-temporal-stabilizer/docs

According to their document, they stated:

To render from the command line use:
Animation:

blender -b "E:\blender\benchmark scenes\classroom\Classroom.blend" --python-expr "import bpy; bpy.ops.threedi.render_animation()"

Still image:

blender -b "E:\blender\benchmark scenes\classroom\Classroom.blend" --python-expr "import bpy; bpy.ops.threedi.render_still()"

btw thank you for developing such a fantastic add-on. I truly adore it.

Realy nice addon, Thx!

I propose to introduce the ability to automatically save the render (F12) to the path specified using global variables.
Now path in compositor->output_node after pressing F12 leads to saving the file in C:$BLEND$CAMERA\ (OS: windows) without replacing global variables in path-string

I understand that you can press the button "Bake Globals" ( bpy.ops.loom.globals_bake(action='APPLY') ), but in Scene more cameras and I would like to have this function to replace global variables by default or optionally included in the settings of the scene or addon.

Blender versions: 2.92, 3.1, 3.3

Thanks! Igor

Hi!

When I try to use the Batch Render and Encode dialogue, i choose my blend file, set the ranges and press ok.. however, I then get a "Specified output folder foes not exist (persmission denied)" error

Just to be clear: its using the output folder of the blend file I chose right? I have tried a couple of different locations (also on different disks)..but I keep getting that error... And Im the administrator on this computer (its my own)

What can this problem be? please advise.. thanks!

Hi! Thank you for this add-on it's helping me quite a bit. I noticed in the documentation it says you can fill the gaps in the image sequence by pulling the closest frame available. Is there a way to change it so it specifically targets only the previous frame?

As an example, say I'm rendering something in constant interpolation, so there is only really a change after a keyframe is placed. So say I have a keyframe at frame 20 and another keyframe at frame 30.

So I ask the addon to render only 2 frames (20 and 30) and I want specifically for it to copy only frame 20 to fill from 21-29 without using 30 for the frames that would be closer to it (as in 26-29).

So is there a way or could you add the option to only go from the frame previously rendered instead of the frames "closer"?

no alpha render in Batch Dialog even if I choose 4444 XQ, however it works as expected if I rendered it by win+shift+F9, so I have to render the frames first than encode the alpha video by win+shift+F9
by the way Iam using the latest version

I cannot for the life of me work out how to just render keyframes.

I know I tested this program and got it to work at some point in the past so I'm sure it's something I'm missing this time.

But the "f3" to add just the keyframes doesn't seem to work. I seem to remember a menu option when I'd search loom from the dopesheet but I just can't bring it up.

I can only render image sequences in default cube files. Is there a "not to do" list that I can follow the steps to be able to render?

This is probably more to do with Blender but just thought I'd mention it as I don't see it with anything else.

In Blender 3.1 3.2 when using loom 'render with commandline' option my blender ui gets corrupted but if I mouse over the panels they restore to normal so it doesn't crash or anything.

.

I can't find the button to toggle Limit by Object Selection, so loom render all object's selected keyframes.Anyone knows where it is?
Thankyou~

Maybe a useful feature would be an option to select the render engine used for output i.e. sometimes I like to render frames using workbench, to do so I need to go to the render engine for the scene and change it then change it back to eevee or cycles for normal rendering.

Thanks!

I'm trying to render a specific frame range of the animation that I've created. It is composed by 320 frames, so let's say that I want to render from frame 5 to 320.

Loom does not work as expected in my scenario. In fact the problem is that the window should give me the chance to choose which frames to render does not open when I invoke it by pressing Ctrl+Shift+F12, but it works with a fresh scene. Please see the attached images below... Thanks.

Hello,

I have stumbled upon your addon and found it really useful as its the first implementation I have found of variables in output file names that has enough versatility!

However I would like to propose some enhancements given my use case where the benefits of your addon cannot be used to their fullest.

I have several shots that I wish to render of objects with multiple camera angles. These are for creating standardised object renders (a ball and a cube in my example). To make this work each object is set up in its own scene:

I set up each object in a separate scene because it allows me to bind cameras of the individual views to markers (Ctrl+B when camera is selected) so that I can set up a render sequence for all the required views of each object (within a scene):

Within each scene I am able to specify the output using loom which is fantastic, because the scene can hold the name of the object, and the cameras the names of the views:

Up to here it is everything I hoped for. The cameras bound to markers actually register correctly in the Global variables when saving the frame names:

However, part of the workflow I am trying to establish is to have the ability to re-render each shot for either 1 object, or ALL objects. To achieve this I simply create a new "All Renders" scene and move to the Video Editing Sequencer. There I add in all the other Object Scenes one after the other so that all views can be rendered one after the next:

This is the point at which loom's functionality breaks down. The moment I use the Render Image Sequence (CTRL+SHIFT+F12) loom proceeds to render the correct number of frames...

..but then simply reports the error that no cameras can be found within the scene:

It would be amazing if the already solid Global variables functionality of loom could be extended to work in this case.

Lastly if the Global variables functionality can also be extended not only to work within the video sequencer when the scenes are being called from an external scene, but also to work with the File Output node file path system, I think this would largely solve many people's desires for variables within filenames.

The reason I would personally want Global variables within the file output nodes is because I would actually prefer to save each object's render in more than one place as various people would end up using them.

I hope this is a suggestion that is implementable as I believe many people would find it incredibly useful.

I really enjoy using Loom and it works great.
I am just not sure wether i didn't find that feature or whether is isn't here: if i render an image, i would like to save the next image with a new name (although it is the same frame), so e.g. a version number which automatically increases for each image would be great.
Maybe that's already possible?
Thanks, have a great day,
Christoph

As we discussed in our previous thread, just pulling it out for clarity--again I'm mostly looking at 'Render Selected Keyframes' for my workflow.

It would be superb to have an option, a boolean toggle I guess to limit keyframes to within the scene frame range automatically. Accidentally rendering outside of the frame range could cause a number of issues in a larger production.

Thanks!
Stephen.

Right now you can override the render settings with a preset, but this is applied to all blend files in a batch. I render posters in Blender, and some of them are landscape and some are portrait resolution. If there was a button to set a preset for each blend file individually in the Loom Batch window, I could render all the posters in one go.