Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Feature Request - HD Proxies

Stephen Webb

Well-known member
Joined
Dec 28, 2006
Messages
427
Reaction score
0
Points
0
Website
www.aefilms.co.uk
Would it be possible in a future build to implement a feature whereby the camera generates an _HD proxy?

What I have in mind is a QT file that, regardless of resolution or aspect ratio, will always be a 1920x1080 proxy. So if you shoot 4K 16:9 you'll have a HD proxy, if you shoot 2K 2:1 you'll have an HD proxy (letterboxed), etc...

This way there will always be something to edit from that is already formatted for an HD world.
 
Would it be possible in a future build to implement a feature whereby the camera generates an _HD proxy?

What I have in mind is a QT file that, regardless of resolution or aspect ratio, will always be a 1920x1080 proxy. So if you shoot 4K 16:9 you'll have a HD proxy, if you shoot 2K 2:1 you'll have an HD proxy (letterboxed), etc...

This way there will always be something to edit from that is already formatted for an HD world.

My guess is that one reason that Red is able to give 2K and 1K proxies out of 4K data is because wavelet decompression (Red appears to have JPEG 2000 flavor) allows you to extract 1K and 2K data without full 4K decode. 1920x1080 is not exactly a half of 4K in either direction, so it may be more difficult, but possible.
 
I was under the impression that the levels of detail in the wavelet compression weren't directly tied to resolution.

Actually they are to my understanding- it's literally a fraction of the original that's being decompressed on the fly. So resizing to a resolution that's not directly divisible by 4K presents an issue. Not that it's an issue that with enough processing and Nattress power thrown at couldn't be overcome.

Noah
 
I was under the impression that the levels of detail in the wavelet compression weren't directly tied to resolution.

You have to start somewhere (say 4K image), and that sets the size of subimages. Wavelet decomposition is quite similar to Laplacian pyramids and the following link shall help you in understanding how a 2K image might be decoded without full decode of 4K image data. Again the link is for Laplacian pyramids but the wavelet concept is very similar.

http://sepwww.stanford.edu/~morgan/texturematch/paper_html/node3.html
 
Might be worth introducing a 3840x2160 recording mode on the camera. That would allow for 1920x1080 proxies, and it also looks like 3840x2160 is shaping up to be a standard for ultra-HD displays.
 
Back
Top