Saving single image of image sequence: image.save_render(): Could not acquire buffer from image. #94051

New Issue

Paul Golter · 2021-12-14T10:16:36+01:00

Paul Golter commented

2021-12-14 10:16:36 +01:00

System Information
Operating system: Linux-5.15.5-76051505-generic-x86_64-with-glibc2.33 64 Bits
Graphics card: Radeon RX 590 Series (POLARIS10, DRM 3.42.0, 5.15.5-76051505-generic, LLVM 12.0.0) AMD 4.6 (Core Profile) Mesa 21.2.2

Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2021-12-14 05:17, hash: c097c7b855
Worked: (newest version of Blender that worked as expected)

Short description of error
When trying to call the .save_render() function via the PythonAPI on an image datablock that holds an image sequence Blender throws the "Could not acquire buffer from image. " error.

Exact steps for others to reproduce the error

Load any image sequence in image editor.
Call bpy,data.images- .save_render()

I appended a zip with an already prepared blend file and image sequence. You can use that for convenience. bug_report_bundle.zip

**System Information** Operating system: Linux-5.15.5-76051505-generic-x86_64-with-glibc2.33 64 Bits Graphics card: Radeon RX 590 Series (POLARIS10, DRM 3.42.0, 5.15.5-76051505-generic, LLVM 12.0.0) AMD 4.6 (Core Profile) Mesa 21.2.2 **Blender Version** Broken: version: 3.1.0 Alpha, branch: master, commit date: 2021-12-14 05:17, hash: `c097c7b855` Worked: (newest version of Blender that worked as expected) **Short description of error** When trying to call the .save_render() function via the PythonAPI on an image datablock that holds an image sequence Blender throws the "Could not acquire buffer from image. " error. **Exact steps for others to reproduce the error** 1. Load any image sequence in image editor. 2. Call bpy,data.images- [ ].save_render() I appended a zip with an already prepared blend file and image sequence. You can use that for convenience. [bug_report_bundle.zip](https://archive.blender.org/developer/F12739037/bug_report_bundle.zip)

Paul Golter commented

2021-12-14 10:16:36 +01:00

Added subscriber: @paulgolter

Paul Golter commented

2021-12-14 10:18:25 +01:00

This hack fixes the error:

https://developer.blender.org/P2644

But it would propably require a nicer solution than that.

This hack fixes the error: https://developer.blender.org/P2644 But it would propably require a nicer solution than that.

Brecht Van Lommel commented

2021-12-14 17:21:50 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2021-12-14 17:21:50 +01:00

What do you need it to do?

Save the entire frame range? Or do you need a parameter so you can specify the frame to save?

What do you need it to do? Save the entire frame range? Or do you need a parameter so you can specify the frame to save?

Paul Golter commented

2021-12-15 10:15:48 +01:00

Hey @brecht,

There are a couple of parameters that would be great to have to control the export:

framenr
layer index (for multilayer)
pass index (for multilayer)

I already chatted with @ideasman42 about this briefly and we were thinking that it would be great to be able to pass an ImageUser to functions like this and others that have similar problems. Currently there is no way to create an ImageUser with Python and a question would be how to handle the lifetime and storage of that ImageUser.

Campbell still wanted to get some opinions on how to approach this. Here a small extract out of that conversation:

Support image user as arguments to these functions.

Support either creating image users from Python or coercing data such as a dictionary into an image user.
Perhaps we could support image_user={"frame": 42, eye='LEFT'} - where RNA handles creating the image user for the lifetime of the function.

Would love to hear your opinion on this.

Hey @brecht, There are a couple of parameters that would be great to have to control the export: - framenr - layer index (for multilayer) - pass index (for multilayer) I already chatted with @ideasman42 about this briefly and we were thinking that it would be great to be able to pass an `ImageUser` to functions like this and others that have similar problems. Currently there is no way to create an `ImageUser` with Python and a question would be how to handle the lifetime and storage of that `ImageUser`. Campbell still wanted to get some opinions on how to approach this. Here a small extract out of that conversation: > - Support image user as arguments to these functions. > - Support either creating image users from Python or coercing data such as a dictionary into an image user. > Perhaps we could support image_user={"frame": 42, eye='LEFT'} - where RNA handles creating the image user for the lifetime of the function. Would love to hear your opinion on this.

Paul Golter commented

2021-12-15 10:21:37 +01:00

Added subscriber: @ideasman42

Brecht Van Lommel commented

2021-12-16 18:46:23 +01:00

Personally I would add individual arguments for frame/layer/pass rather than adding ImageUser as a concept to the API, but either way works.

Personally I would add individual arguments for frame/layer/pass rather than adding `ImageUser` as a concept to the API, but either way works.

Philipp Oeser commented

2022-01-18 12:20:46 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Philipp Oeser commented

2022-01-18 12:21:00 +01:00

Added subscriber: @lichtwerk

Bastien Montagne added this to the Core project 2023-02-09 15:42:54 +01:00

Bastien Montagne removed this from the Core project 2023-02-09 18:20:37 +01:00

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Saving single image of image sequence: image.save_render(): Could not acquire buffer from image. #94051