Welcome to our community

Be a part of something great, join today!

Register Log in
  • 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 :)

Ooooo the prettty flowers...

2k export as tiff or dpx is properly downsampled from 4k raw data. You can get a % or so better quality by doing it yourself from 4k image data - see image I posted on the resolution thread.

Graeme
 
Is it true that Red Code is NOT visually lossless?
 
Rob Lohman said:
That could very well be. The current quality of the QuickTime codec is very good, but not extreme high-quality yet.

The reason for this is that it's not doing a full 4K debayer and then downsampling that to whatever resolution you're looking at. That *option* will be added soon.

Currently it's using wavelet lower resolution extracts which could result in some of the things you might've seen.
Click to expand...

Hmmm, if it needs too much resources to do a high quality decode, then why don't you make two wrapper versions? One for a draft version (like the one we have today, for offlining) and a high quality one (in case one needs the QuickTime for onlining). What do you think?
 
Jim Arthurs said:
Holy Cow, Rob, that's a non-trivial bit of info that I've not heard before... that explains so MUCH of what people are seeing... that and the "sharpening" on by default are the two major causes of grief with the current processed output, IMO.
Click to expand...

Only RED ALERT! has default sharpening, QuickTime codec does not. However, the QT codec does not has the full 4K debayer + downsample.

The included readme file with the software package mentions this fact. But since we'll add a really high-quality version soon it was mostly important to the early adopters.
 
big lebowski said:
Hmmm, if it needs too much resources to do a high quality decode, then why don't you make two wrapper versions? One for a draft version (like the one we have today, for offlining) and a high quality one (in case one needs the QuickTime for onlining). What do you think?
Click to expand...

At the moment we have a high and draft quality codec. Problem is that you need to change codecs and that might require a reboot etc. Future versions will look at the high-quality flag from qt player and quality settings in FCP to see what it needs to do.

There are some more ideas floating in my head how to easily fine tune this and let people set decode modes without requiring codec swaps (which suck).
 
Rob Lohman said:
At the moment we have a high and draft quality codec. Problem is that you need to change codecs and that might require a reboot etc.
Click to expand...
Wouldn't it only require an application relaunch in Mac Os? Still not an elegant solution though.

Rob Lohman said:
Future versions will look at the high-quality flag from qt player and quality settings in FCP to see what it needs to do.
Click to expand...
Yeah I hoped you'd go this route. That worked pretty good early on with the DV codec. But of course it would tend to favor the slowest decode when scrubbing and trimming in FCP, which again could seem unresponsive to the user depending on performance.

Great stuff. Hopefully Apple will play ball on the gamma issues :-)
 
Now we only need to invent better bandwidth for downloading everyones giant quicktime clips.
Maybe a codec that acts like bittorrent and can grab information from where ever it can.
 
Rob Lohman said:
At the moment we have a high and draft quality codec. Problem is that you need to change codecs and that might require a reboot etc. Future versions will look at the high-quality flag from qt player and quality settings in FCP to see what it needs to do.

There are some more ideas floating in my head how to easily fine tune this and let people set decode modes without requiring codec swaps (which suck).
Click to expand...

Rob,

I thought the idea behind the codec was to have the 4K file playing back at selectable proxies. This would mean that the 4K file is playing back at 2K, 1K, etc. from the 4K file and the 2K, 1K proxies work are being decoded from the "master 4K file.

Where is the bottleneck?

David
 
David: that is exactly what is happening and is available today with our system. However, there are also different quality settings (besides resolution) that impact decoding times. We are talking about that setting and how to best control it.
 
Rob Lohman said:
David: that is exactly what is happening and is available today with our system. However, there are also different quality settings (besides resolution) that impact decoding times. We are talking about that setting and how to best control it.
Click to expand...

Thanks Rob. I apreciate you taking the time to answer.

David
 
Settings in system preferences

Settings in system preferences

Rob Lohman said:
David: that is exactly what is happening and is available today with our system. However, there are also different quality settings (besides resolution) that impact decoding times. We are talking about that setting and how to best control it.
Click to expand...

Rob, could that be in System Preferences? Just add a menu in witch you can set the decoding parameters for the whole system. Just my thought... out in the blue...
 
Thanks for the suggestion Christian, that is one of the possibilities on my list ;)
 
You must log in or register to reply here.
Back
Top