Welcome to our community

Be a part of something great, join today!

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 :)

Two Weeks... Change is COMING!!

Jay,

Your posts are well informed, level headed, and above all... fair to everyone involved.

Thanks! We need that on this board.

-Thor
 
Tomorrow!!!

Tomorrow!!!

Sorry I've been doing this for each day and I could not help myself!

Do I really think the SDK will be out at 12:01am tomorrow? Most likely not, but I am fairly confident it will be out very soon. Little bird has told me they are close, but it's a pretty big job.

So, I'm gonna keep fanning the flames.. If for no other reason that it's fun!

Jay
 
Jay A. Kelley said:
Besides, it would only be a matter of time before the file is hacked by someone who wants to do a better job of meeting customers demands in regards to things like speed.
Click to expand...


The only way for this to not happen is to keep the RED open for all platforms.

The way it should be...

Otherwise... M-hm. :ninja:
 
Now the release build 16 is out, the next announcement from RED will be about releasing SDK. Fingers crossed.
 
Actually it would be nice if companies already have the SDK and their implementations ready, but just waiting for the go-ahead from RED.

But I don't know how exactly these things work...
 
Today Is The Day!!

Today Is The Day!!

Ok (Looking around)

SO WHERE THE HELL IS IT... IT WAS MIDNIGHT OVER SEVEN HOURS AGO....


DAMN!!!


He he he... Kidding... Actually I was quite pleased to see the release version of Build 16 as that was alway known to be the step before the SDK.

I have no doubt the SDK is close...

This is exciting!

Jay
 
I say let RED debayer all footage so they can control the quality, they built the camera, know the FPN, and all other issues with the chip. Let them make the best possible image and feed it to 3rd party apps to do as they will.
 
I simply can't trust that 3rd parties would know how to get the best from the sensor without knowing all the details of the olpf, sensor design, processing and compression. I would not put my clients jobs at risk by using tools that make assumptions. I've been burned by that before.
 
Using 3rd party methods to decode RAW happens often in the DSLR world.

I don't have a problem with it as long as the company documents the results of their methods in a way that can be verified.

-Thor
 
Debayering has nothing to do with knowing the Sensor,
but Knowing Math and the rihgt and fast algorithms...
There is a Loss of resolution about 30 to 50% depending on the Debayering Algorithm...
I've not yet testet how exact red is, but i'm pritty shure, that there are third party Companies out there, who can do the job much faster...
 
The results vary tremendously between programs with some being unusable and others being better. That's exactly how I got burned. I output stills from company X software but the agency got the raw also. They output using a different method and said that my output was dogshit compared to what they output with the Nikon tools. End result was a lost client.
 
Ariana, That is reasonable now that you have a choice, however you are asking not to have that choice. Do you think Nikon's demosaic would be as good as it is if it didn't have to complete with the engines in Aperture and Lightroom (third demosaic and workflow solutions for a large range of RAW cameras?) A co-worker also prefers the Nikon's demosaic over Lightroom's, yet chooses the Adobe package as the workflow is better (maybe Lightroom 2 has more demosaic improvements.) Competition is good, let's see that happen and give the end user the choice.
 
Thor Wixom said:
Using 3rd party methods to decode RAW happens often in the DSLR world.

I don't have a problem with it as long as the company documents the results of their methods in a way that can be verified.

-Thor
Click to expand...

Well said, I can agree on that. Still though, if you make the camera I can assume your going to know best how to build images from it.

If Red was my company and I cared as much as Jim does about the quality of the images I would sure never let my code in the wild for anyone to LinBayer it into hell. To me, it only makes sense that Jim would feed the best images out via RGB and let others do what is needed with that, even if it took more time. The other option is the bless others that want to take on the debayer and give them the tools/knowledge to make sure the images are up to par with a "certified" RED program.
 
D.A.N said:
Ariana, That is reasonable now that you have a choice, however you are asking not to have that choice. Do you think Nikon's demosaic would be as good as it is if it didn't have to complete with the engines in Aperture and Lightroom (third demosaic and workflow solutions for a large range of RAW cameras?) A co-worker also prefers the Nikon's demosaic over Lightroom's, yet chooses the Adobe package as the workflow is better (maybe Lightroom 2 has more demosaic improvements.) Competition is good, let's see that happen and give the end user the choice.
Click to expand...

I didn't say no choice but there should be a known quality level that should meet or exceed the manufactures quality and it should be tested and documented on various types of images. Otherwise we just have chaos. Do really want to spend a boatload of money on iridas software knowing that their debayer is suboptimal? No way. I would buy their software if knew for a fact that it was at least as good as RED's which I am very happy with.
 
You must log in or register to reply here.
Back
Top