Speed up processing of 2x Photomode images by pre-emptive rendering

[GBO Possum]

I usually use the 1x setting to achieve a faster preview of my images, and, if I like the result, I will always go back to camera mode, change to 2x, reprocess and Save. I almost never save in 1x resolution.

Then I have to go back into the camera settings to restore the 1x setting. This is a slow process. Sometimes I forget to reset to 1x and have to wait for the long 2x rendering process to complete.

I'd like to be provided with a "hiding" button in the 1x preview mode. The function of this button would be a combined "Render in 2x and Save". The button would only appear when controller controls are moved, and would fade out of the way when I stop moving the controls.

And here is how I would speed up the process. Having asked for a 1x rendering, once this has been presented to me, the software should always go ahead and render the image in 2x in the background just in case I want to save it. After duly considering my work of art (which takes time), if I like the image I'd make the "Render in 2x and Save" button pop up and click it. The software would complete the 2x rendering (if it's not already complete) and save it.

Thus rendering processing time would be overlapped with my thought processes and would improve photographic productivity.

 

[GBO Possum]

Do you mostly save 1x or 2x images?

 

[SnakeOfBacon]

wait, there's an option to render the photos in higher than 1080p?

 

[GBO Possum]

wait, there's an option to render the photos in higher than 1080p?

Yes, 2x gives you 3,840 by 2,160 pixels.

The downside is that it takes a while to render, which is why I suggested that rendering should be done proactively, just in case the photographer decided he/she wanted the extra resolution. If the PS3 CPUs are just sitting there waiting for the photographer to make a decision, they might as well be rendering the 8.3 megapixel version "just in case".

 

[Verbal]

Neat idea. Wouldn't even need preemptive rendering, just give me a "Save as 2x" button when viewing the 1x image. Waiting a few seconds would still beat the dozen key presses it takes now...

 

[SnakeOfBacon]

Neat idea. Wouldn't even need preemptive rendering, just give me a "Save as 2x" button when viewing the 1x image. Waiting a few seconds would still beat the dozen key presses it takes now...

Hmmm... So you're suggesting that after taking a photo, we could have seperate buttons to save the picture in either 1080p or 4k. Keep in mind that for the 4k image, the game would need to discard the 1080p preview, then render the entire picture and all of its effects once more in 4x the resolution. You would save button presses but potentially waste a lot of time.
I think a better idea would be to leave the system alone and maybe assign the magnification setting to an unused controller button.

 

[GBO Possum]

What I'm proposing is to have the system calculate both the 1080p and the 4k versions. The first task would be to calculate the 1080p, and present that for approval to the photographer. The second task, without waiting for any input from the photographer, would be to calculate the 4k image anyway, retaining the 1080p version.

If the photographer requests saving the 4k image after it has been completed, then the 4k image is saved.

If the 4k image is incomplete at the time of the save request, then the UI will present a progress bar showing how much more computing is required. The 4k image rendering will continue, and at completion, will be saved.

If the photographer chooses the 1080p version of the image and exits the mode, the partial or complete 4k image will be discarded. However, there may be circumstances where the photographer wants to save the 4k image even if the 1080p image has already been saved. The algorithm should avoid prematurely discarding either image.

It is possible that the 1080p image is actually one quarter of the actual pixels of the 4k image, so at the end of the 1080p rendering, the 4k job is 25% complete. But I'm not sure of this.

 

[SnakeOfBacon]

...It is possible that the 1080p image is actually one quarter of the actual pixels of the 4k image, so at the end of the 1080p rendering, the 4k job is 25% complete. But I'm not sure of this.

No, everything else you said was fine and I agree with you (even if I do think it's overcomplicating things), but just want to let you know, while the 4k picture does have 4x more pixels than the 1080p picture, they are not the same pixels. None of the work done to capture the lower resolution image will help with the higher resolution image, as they do not contain the same parts of the picture.

 

[GBO Possum]

No, everything else you said was fine and I agree with you (even if I do think it's overcomplicating things), but just want to let you know, while the 4k picture does have 4x more pixels than the 1080p picture, they are not the same pixels. None of the work done to capture the lower resolution image will help with the higher resolution image, as they do not contain the same parts of the picture.

I agree on both points. My description was over complicated.

To net it down, I simply want to see unused CPU cycles used for potentially productive purposes.

 

[SnakeOfBacon]

I agree on both points. My description was over complicated.

To net it down, I simply want to see unused CPU cycles used for potentially productive purposes.

Fair enough, and I want to see a shortcut button for magnification (AND A PREVIEW IN TH VIEWFINDER WITHOUT HUGE BLACK BORDERS, LIKE IN GT5, BUT THAT IS A TOPIC FOR ANOTHER THREAD)