Quick edit image buffer is saved as 8bit image #34549

Open
opened 2013-03-07 03:49:17 +01:00 by kursad k · 14 comments
Member

%%%--- Operating System, Graphics card ---
Nvidia 750gtx, Windows7 64

- Blender version with error, and version that worked ---

2.66

- Short description of error ---

When painting textures it is common to export the current camera buffer to an editing applicationn and bring bacvk adn reapply as project in Blender and other apps. Blender provides this functionality as "quick edit" in the texture painting panel. It is all great however the buffer seems to be saved as 8bit which renders the integrity of an highbit (16/32) images. I believe that the quick edit buffer bit depth should be saved as the original image bit depth. As of right now the fidelity of an high bit image is compromised with 8 bit image buffers.

I use Photoshop for image editing so this is not an image editing app mistake, as in that would be with Gimp since it has no support for anything else besode 8bit images.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

Add a 32 bit image to your model for texture painting
open texturing mode
click quick edit on the texturing pane
It should open up your editing application for quick painting.

You can also try the blend file I attached.

%%%

%%%--- Operating System, Graphics card --- Nvidia 750gtx, Windows7 64 - Blender version with error, and version that worked --- 2.66 - Short description of error --- When painting textures it is common to export the current camera buffer to an editing applicationn and bring bacvk adn reapply as project in Blender and other apps. Blender provides this functionality as "quick edit" in the texture painting panel. It is all great however the buffer seems to be saved as 8bit which renders the integrity of an highbit (16/32) images. I believe that the quick edit buffer bit depth should be saved as the original image bit depth. As of right now the fidelity of an high bit image is compromised with 8 bit image buffers. I use Photoshop for image editing so this is not an image editing app mistake, as in that would be with Gimp since it has no support for anything else besode 8bit images. - Steps for others to reproduce the error (preferably based on attached .blend file) --- Add a 32 bit image to your model for texture painting open texturing mode click quick edit on the texturing pane It should open up your editing application for quick painting. You can also try the blend file I attached. %%%
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'

#69538 was marked as duplicate of this issue

#69538 was marked as duplicate of this issue
Author
Member

%%%Btw sorry about the typos, I realized them after the post .

%%%

%%%Btw sorry about the typos, I realized them after the post . %%%
Member

%%%I don't know this feature, and wouldn't know how to use it even. But for me it seems to be just a snapshot of the 3d viewport, which is 3x8 bits color by default.

Why would you expect viewports to be in 3x32 bits color?

%%%

%%%I don't know this feature, and wouldn't know how to use it even. But for me it seems to be just a snapshot of the 3d viewport, which is 3x8 bits color by default. Why would you expect viewports to be in 3x32 bits color? %%%
Author
Member

%%%Ton,

First of all it is a color fidelity problem. When you are working in 32 bits you would want all your colors stay truly be 32 bits during any operation. Presume that you are working on a higres high bit displacement(which is single channel high bit) / color map, and it is a float 32 bit linear image in Blender. When you take that projection to Photoshop paint it and bring back and reapply in projection mode ( the quick edit thing) in texture paint mode , you might run into color management or run into color fidelity problems. You just loose some of the information you might have painted in Blender during that back and forth. For game work that is perfectly fine, but for movie work that is a pipeline problem which is why I brought it up.

It is great that we have that option.But it is a tricky thing because people might not realize that they might loose color values between these operations.

cheers

k
%%%

%%%Ton, First of all it is a color fidelity problem. When you are working in 32 bits you would want all your colors stay truly be 32 bits during any operation. Presume that you are working on a higres high bit displacement(which is single channel high bit) / color map, and it is a float 32 bit linear image in Blender. When you take that projection to Photoshop paint it and bring back and reapply in projection mode ( the quick edit thing) in texture paint mode , you might run into color management or run into color fidelity problems. You just loose some of the information you might have painted in Blender during that back and forth. For game work that is perfectly fine, but for movie work that is a pipeline problem which is why I brought it up. It is great that we have that option.But it is a tricky thing because people might not realize that they might loose color values between these operations. cheers k %%%

%%%This can be supported, Ill check on it.%%%

%%%This can be supported, Ill check on it.%%%

%%%Note:

The intention of this feature is that you paint into a new layer and hide the existing image before saving.
This way the pixels from blender are mainly a reference, if you want you can save the image as 32bit-per-channel image, however it may be better to add some option in blender so you dont have to manually change the channel depth each time.%%%

%%%Note: The intention of this feature is that you paint into a new layer and hide the existing image before saving. This way the pixels from blender are mainly a reference, if you want you can save the image as 32bit-per-channel image, however it may be better to add some option in blender so you dont have to manually change the channel depth each time.%%%

Added subscriber: @Sergey

Added subscriber: @Sergey

Would be nice to support, but strictly speaking not a bug. Moving to TODO now http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Painting

Thanks for the report anyway!

Would be nice to support, but strictly speaking not a bug. Moving to TODO now http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Painting Thanks for the report anyway!

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'
Member

Added subscribers: @ssh4, @lichtwerk

Added subscribers: @ssh4, @lichtwerk

Let me add some notes, to may be rise priority a bit.

First of all. Textures can be not only 8 bit but 16 bit integer. In that case 8bit export to external app probably not so critical. But if texture 16/32bit float applying 8bit back from Photoshop or other, create a lot of issues. And good example was posted before.
This external app texturing feature one of huge blender benefits comparing to ZBrush or other. Alpha channel support allow fix 3D scan based textures without affecting correct parts of scanned texture.

Another problem is PNG itself. It Extremely slow. It have best compression ratio but extremely slower on saving or open. Will be better add choice using PNG, Tiff, PSD, EXR to external painting support.

Let me add some notes, to may be rise priority a bit. First of all. Textures can be not only 8 bit but 16 bit integer. In that case 8bit export to external app probably not so critical. But if texture 16/32bit float applying 8bit back from Photoshop or other, create a lot of issues. And good example was posted before. This external app texturing feature one of huge blender benefits comparing to ZBrush or other. Alpha channel support allow fix 3D scan based textures without affecting correct parts of scanned texture. Another problem is PNG itself. It Extremely slow. It have best compression ratio but extremely slower on saving or open. Will be better add choice using PNG, Tiff, PSD, EXR to external painting support.
Julien Kaspar added this to the Sculpt, Paint & Texture project 2023-02-08 10:49:06 +01:00
Philipp Oeser removed the
Interest
Sculpt, Paint & Texture
label 2023-02-10 09:12:57 +01:00

@ideasman42 Hi there, since this was re-opened a bit ago and marked as a duplicate, I was just wondering if there may have been a fix to this quick edit problem? Still running into the issue of the quick edit being a different color space (8 bit) instead of the baked 32 bit color space we're working on. The only work around we have right now is to lower our opacity. We would appreciate any direction in getting this fixed, thank you.

@ideasman42 Hi there, since this was re-opened a bit ago and marked as a duplicate, I was just wondering if there may have been a fix to this quick edit problem? Still running into the issue of the quick edit being a different color space (8 bit) instead of the baked 32 bit color space we're working on. The only work around we have right now is to lower our opacity. We would appreciate any direction in getting this fixed, thank you.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No Assignees
8 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#34549
No description provided.